-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docIndex to kick off the docs SDK CI run for main #47434
Conversation
…hould be kicked off as part of a manual run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the issue was transient and another retry succeeded in kicking off the pipeline (I canceled that run because I'm just testing functionality)
This failures has nothing to do with my change but rather with an incident that pretty much affected things fetching from azure |
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Daniel Jurek <[email protected]>
The docIndex runs ran without issue. The net - core - ci run that's running isn't testing anything in this PR. I'm going to merge this. |
Right now, the docs SDK CI runs run a scheduled run against main and the timing of the runs is isn't great. The solution here is to have the docIndex runs kick off SDK CI the run against main the same way we're kicking off the run against the daily branch. This will remove anything fiddly.
As part of this change, add a parameter, defaulting to false, to determine whether or not the SDK CI run should be kicked off.
This is what the parameter I'd added looks like. It's the second checkbox down, unchecked by default.
This is the docIndex run with it unchecked. Notice it didn't kick off the SDK CI run.
This is the docIndex run with it checked. It would have kicked off the run but there's a weird authentication thing happening in pipelines right now that's affecting Azure.