Skip to content

[release/7.0] CI: Run runtime-extra-platforms with batched builds for release - #76615

Merged
carlossanlop merged 1 commit into
dotnet:release/7.0from
radical:extra-platforms-ci-7
Oct 4, 2022
Merged

[release/7.0] CI: Run runtime-extra-platforms with batched builds for release#76615
carlossanlop merged 1 commit into
dotnet:release/7.0from
radical:extra-platforms-ci-7

Conversation

@radical

Copy link
Copy Markdown
Member

Backport of PR #76587 .

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.

Customer impact

Infrastructure only change, so no customer impact.

Testing

Manual testing

Risk

none

…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.
@radicalradical added this to the 7.0.0 milestone Oct 4, 2022
@ghostghost assigned radicalOct 4, 2022
@ghost

ghost commented Oct 4, 2022

Copy link
Copy Markdown

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of PR #76587 .

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.

Customer impact

Infrastructure only change, so no customer impact.

Testing

Manual testing

Risk

none

Author:radical
Assignees:-
Labels:

area-Infrastructure

Milestone:-

@radicalradical added the Servicing-consider Issue for next servicing release review label Oct 4, 2022
@lewinglewing removed the Servicing-consider Issue for next servicing release review label Oct 4, 2022
@lewing

Copy link
Copy Markdown
Member

this is just infrastructure no need to involve tactics

@lewing

Copy link
Copy Markdown
Member

@akoeplinger@steveisok can one of you sign off

@radical

Copy link
Copy Markdown
MemberAuthor

/azp run runtime-extra-platforms

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@radical

Copy link
Copy Markdown
MemberAuthor

Canceled the runtime-extra-platforms run. I had triggered it just to check that there weren't any yml issues.

@radical

Copy link
Copy Markdown
MemberAuthor

@carlossanlop ready to go!

@carlossanlop

Copy link
Copy Markdown
Contributor

Approved, CI verified, infra-only change. Ready to merge. :shipit:

@carlossanlop
carlossanlop merged commit 8743673 into dotnet:release/7.0Oct 4, 2022
@ghostghost locked as resolved and limited conversation to collaborators Nov 4, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@radical@lewing@carlossanlop@akoeplinger