| Issue |
166216
|
| Summary |
Monorepo-wide CI checks should not trigger on projects that don't need them
|
| Labels |
infrastructure
|
| Assignees |
|
| Reporter |
ldionne
|
Libc++ does not use the monorepo-wide CI checks defined in [premerge.yaml](https://github.com/llvm/llvm-project/blob/288ef04d2f19c5b0e4ce3cae450c63a365ab11e9/.github/workflows/premerge.yaml). However, these jobs still run on all LLVM pull requests, only to determine that there's nothing to do for libc++ and then be no-ops.
<img width="844" height="381" alt="Image" src="" />
<img width="1136" height="394" alt="Image" src="" />
This creates noise and confusion when submitting PRs to LLVM projects that don't use these checks. Note that libc++ itself suffers from a similar problem: it imposes its BuiltKite pipeline checks on all LLVM monorepo PRs, which creates noise for all non-libc++ contributions. I am trying to address that in https://github.com/llvm/llvm-project/pull/165928.
Since we have a single monorepo for all of LLVM, I think it will be important going forward to ensure proper "insulation" between projects (when relevant) to avoid this.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
