microsoft / microsoft/fluentui

ci: v9 release pipelines should execute same checks like PR

Open
#24,811 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Build System CI Fluent UI react-components (v9) Resolution: Soft Close Type: Feature
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Library

React Components / v9 (@fluentui/react-components)

Describe the feature that you would like added

We run test/lint/build in separate task synchronously for v9 release pipeline while on PR everything is run in parallel. This slows down release pipeline time.
 
PR:
 
image

 
V9 release: 
 
image

Last but not least we don't run type-checks, which might cause issue for release as we dont enforce PR branch always up to date so things may break. we should unify these pipelines.

Have you discussed this feature with our team

v-build

Additional context

No response

Validations
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by locating the PR and v9 release pipeline definitions, then compare how their test, lint, and build tasks are scheduled. Align the release checks with the PR checks, including type-checks, and verify that the release pipeline completes successfully with the intended parallel execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.