Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
ci: Publish result images as Azure artifacts.#17011
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
I'm thinking we probably want to add a condition so publishing works when stuff fails, but I didn't add it here just to see what the results look like. Should we publishalways oronly on failure? |
I guess only-on-failure is good enough for now? |
Hmm, looks like I need to give it a stage-specific name. |
So Windows Prerelease build failed because nothing was actually run. Seems we're a bit too relaxed with that one. |
I added the on-failure condition, and skipped artifacts for the Prerelease build (which is broken right now). You can see what it looks like in theprevious build. In the top card, under the Related heading, there is the "9 published" link which points to the artifacts. If you're on a specific Job view, then there's a link to "1 artifact produced". |
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.
Looks great! 👍
This should allow us to debug result images if they're failing on Azure.