dotnet/runtime

Cleanup dev-innerloop pipeline to remove legs that are no longer needed to be exercised there

Open

#50,110 opened on Mar 23, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
area-Infrastructurehelp wanted

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

In the beginning we added some legs in the dev-innerloop pipeline to protect developer workflow that wasn't exercised in CI, i.e: build.cmd libs+mono. However, we added mobile platforms to the main pipeline or runtime-staging that exercise some of this scenarios, so we can remove them from dev-innerloop and save some machine time there.

Tis is from: https://github.com/dotnet/runtime/pull/50102#discussion_r599716180

Contributor guide

Research direction
Locate the dev innerloop pipeline definition (likely a YAML file) in the repository. Identify the legs that were added for protection but are now covered by other pipelines (e.g., main or runtime staging). Remove those legs and verify that the pipeline still passes.
Tech stack
None
Domain
devops
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitUnderstanding of CI/CD pipelines
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75