Skip to content
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 to Analyze job condition #37212

Merged
merged 1 commit into from
Sep 5, 2024

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Sep 5, 2024

@catalinaperalta reported an issue with Analyze unexpectedly failing due to inability to find the relevant artifact. The source turned out to be Build_Extended failing.

The reason behind Build_Extended failing doesn't actually matter. What matters is that due to the job condition governing Analyze, we would run Analyze even if Build_Extended (its sole dependency) failed! If Build_Extended fails, then the artifact packages_extended, which Analyze REQUIRES to be present, won't exist named as packages_extended! If the artifact doesn't exist, it can't be downloaded in Analyze, and we get failures that complain about being unable to locate the wheel.

Simply change the condition to succeeded(), which will delay the job run until Build_Extended passes.

…re is that we need to download packages_extended from the build_extended stage, so having it set as succededOrFailed() when buildextended DOES fail, means that we can't get the artifact anyway! may as well remove the dependency
@scbedd scbedd self-assigned this Sep 5, 2024
@scbedd scbedd merged commit 66ccfb8 into Azure:main Sep 5, 2024
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants