CI: Run runtime-extra-platforms with batched builds for release
#76587
+18
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.. branches. Currently, for `release/*` branches, the pipeline is run twice a day, if there are any changes since the last *successful* run. In contrast, the `runtime` pipeline only runs batched builds for the release branches. This can get into a situation like: 1. commit ABC pushed to the release branch 2. `runtime` builds for ABC -- batched build 3. `runtime-extra-platforms` builds on a schedule, but this pipeline is unstable, and fails. 4. `runtime-extra-platforms` now runs twice a day, till we have a new commit, because the pipeline is never green Instead, this changes the behavior to match `runtime` pipeline, and only run batched builds.
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details.. branches. Currently, for This can get into a situation like:
Instead, this changes the behavior to match
|
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue Details.. branches. Currently, for This can get into a situation like:
Instead, this changes the behavior to match
|
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
akoeplinger
approved these changes
Oct 4, 2022
|
/backport to release/7.0 |
|
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3183480938 |
|
@radical backporting to release/7.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: CI: Run `runtime-extra-platforms` with batched builds for release
Using index info to reconstruct a base tree...
M eng/pipelines/runtime-extra-platforms.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/runtime-extra-platforms.yml
CONFLICT (content): Merge conflict in eng/pipelines/runtime-extra-platforms.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 CI: Run `runtime-extra-platforms` with batched builds for release
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
radical
added a commit
to radical/runtime
that referenced
this pull request
Oct 4, 2022
…tnet#76587) .. branches. Currently, for `release/*` branches, the pipeline is run twice a day, if there are any changes since the last *successful* run. In contrast, the `runtime` pipeline only runs batched builds for the release branches. This can get into a situation like: 1. commit ABC pushed to the release branch 2. `runtime` builds for ABC -- batched build 3. `runtime-extra-platforms` builds on a schedule, but this pipeline is unstable, and fails. 4. `runtime-extra-platforms` now runs twice a day, till we have a new commit, because the pipeline is never green Instead, this changes the behavior to match `runtime` pipeline, and only run batched builds.
carlossanlop
pushed a commit
that referenced
this pull request
Oct 4, 2022
…6587) (#76615) .. branches. Currently, for `release/*` branches, the pipeline is run twice a day, if there are any changes since the last *successful* run. In contrast, the `runtime` pipeline only runs batched builds for the release branches. This can get into a situation like: 1. commit ABC pushed to the release branch 2. `runtime` builds for ABC -- batched build 3. `runtime-extra-platforms` builds on a schedule, but this pipeline is unstable, and fails. 4. `runtime-extra-platforms` now runs twice a day, till we have a new commit, because the pipeline is never green Instead, this changes the behavior to match `runtime` pipeline, and only run batched builds.
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.. branches.
Currently, for
release/*branches, the pipeline is run twice a day, if there are any changes since the last successful run. In contrast, theruntimepipeline only runs batched builds for the release branches.This can get into a situation like:
runtimebuilds for ABC -- batched buildruntime-extra-platformsbuilds on a schedule, but this pipeline is unstable, and fails.runtime-extra-platformsnow runs twice a day, till we have a new commit, because the pipeline is never greenInstead, this changes the behavior to match
runtimepipeline, and only run batched builds.