-
Notifications
You must be signed in to change notification settings - Fork 437
Fix source-build CI to not run tarball build when tarball creation fails #14678
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
Fix source-build CI to not run tarball build when tarball creation fails #14678
Conversation
42a6b92 to
03dfcd6
Compare
| # Always attempt to run the bootstrap leg (e.g. even when stage 1 tests fail) in order to get a complete accessment of the build status. | ||
| # The bootstrap build will shortcut if the stage 1 build failed. | ||
| condition: and(${{ parameters.condition }}, succeededOrFailed()) | ||
| condition: succeededOrFailed() |
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.
Would we want succeeded() instead of succeededOrFailed()? It looks to me like succeededOrFailed() will run every time regardless of the dependsOn.
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.
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.
See the above comment. We want to try to run the bootstrap leg even when the stage 1 matrix does not completely pass. If one distro fails or a unit test fails, we should still try to run the bootstrap leg in order to get a complete assessment on the built.
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 think this is fine based on the comment above. Bootstrapping should fail quite early if we don't even have a tarball or something.
| # Always attempt to run the bootstrap leg (e.g. even when stage 1 tests fail) in order to get a complete accessment of the build status. | ||
| # The bootstrap build will shortcut if the stage 1 build failed. | ||
| condition: and(${{ parameters.condition }}, succeededOrFailed()) | ||
| condition: succeededOrFailed() |
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 think this is fine based on the comment above. Bootstrapping should fail quite early if we don't even have a tarball or something.
…ils (dotnet#14678) * Fix source-build CI to not run tarball build when tarball creation failed * Bad fix * Revert test patch
* [release/6.0.1xx] Enable online and offline source-build tarball build in all PRs (#14711) * Enable online and offline source-build tarball build in all PRs (#14620) * Fix source-build CI to not run tarball build when tarball creation fails (#14678) * Fix source-build CI to not run tarball build when tarball creation failed * Bad fix * Revert test patch * update global.json and Versions.props for .NET SDK 6.0.110 (#14717) * [release/6.0.1xx] Re-write dotnet-watch smoke test (#14367) * Re-write dotnet-watch smoke test * Revert async changes * Disable source-build tarball validation for non 6.0.1xx legs Co-authored-by: Michael Simons <[email protected]> Co-authored-by: NET Source-Build Bot <[email protected]> Co-authored-by: Logan Bussell <[email protected]> Co-authored-by: Jason Zhai <[email protected]>
* [automated] Merge branch 'release/6.0.1xx' => 'release/6.0.3xx' (#14726) * [release/6.0.1xx] Enable online and offline source-build tarball build in all PRs (#14711) * Enable online and offline source-build tarball build in all PRs (#14620) * Fix source-build CI to not run tarball build when tarball creation fails (#14678) * Fix source-build CI to not run tarball build when tarball creation failed * Bad fix * Revert test patch * update global.json and Versions.props for .NET SDK 6.0.110 (#14717) * [release/6.0.1xx] Re-write dotnet-watch smoke test (#14367) * Re-write dotnet-watch smoke test * Revert async changes * Disable source-build tarball validation for non 6.0.1xx legs Co-authored-by: Michael Simons <[email protected]> Co-authored-by: NET Source-Build Bot <[email protected]> Co-authored-by: Logan Bussell <[email protected]> Co-authored-by: Jason Zhai <[email protected]> * Update asp.net templates (#14687) * Update asp.net templates (#14688) Co-authored-by: Michael Simons <[email protected]> Co-authored-by: NET Source-Build Bot <[email protected]> Co-authored-by: Logan Bussell <[email protected]> Co-authored-by: Jason Zhai <[email protected]> Co-authored-by: Marc Paine <[email protected]> Co-authored-by: William Godbe <[email protected]> Co-authored-by: v-wuzhai <[email protected]>
The changes in #14620 regressed the tarball build CI. It was getting run even when tarball creation failed. This can be seen by looking at the checks run for the first commit of #14670.