CircleCI: Dynamic config setup #32925
Draft
Conversation
This file contains hidden or 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
|
View your CI Pipeline Execution ↗ for commit 6e6f348
☁️ Nx Cloud last updated this comment at |
52 tasks
52 tasks
…ategy for improved CI performance
…config generation, streamlining the CI setup process.
… and running E2E tests, improving CI workflow and job execution.
…improving test execution consistency and clarity.
…nsistent root path specification for workspace persistence.
…ancing CI workflow and sandbox creation process.
…andbox creation, optimizing resource allocation and improving CI job execution.
…or network commands, ensuring consistent address resolution and improving reliability of CI jobs.
…box creation command, streamlining the CI job execution process.
…eation command, enhancing the CI job execution process.
…in sandbox creation command across all relevant scripts, improving CI job execution.
…never' flags in sandbox and E2E test commands, improving command consistency.
…rc.yml' files instead of using touch commands, improving file handling and command execution.
…e writing 'yarn.lock' and '.yarnrc.yml' files, improving file management and ensuring proper execution.
…he background and update wait commands for improved server readiness checks, enhancing CI job execution.
…ation, enhancing debugging capabilities and improving CI job monitoring.
…eps for better debugging
…or isOutdated, isPrerelease, selectedConfig, selectedDirectory, and outputDirectoryName to enhance traceability during execution.
…neration it's another layer of abstraction, and blocks finding usages, the preferred method of creating re-usable chucks on config is using helpers.ts
…nable JUnit reporting for various test commands
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What I did
Related: #19476
Tracking: #32936
I'm overhauling the CI config.
In this PR I introduce the
scripts/cifolder, in which a CircleCI config is dynamically generated.This dynamic generation allows us to check the repo/PR/branch state and read dynamic config files (such as
sandboxes-templates.ts) to determine what the optimum CI workflow would look like.Here's is an overview:
The hope is that in the future, we'll be able to do change detection, and instead of adding
ci:*-labels to PRs, we automatically only run affected sanboxes.Testing
The changes in this PR are covered in the following automated tests:
Manual testing
We should run this PR with each
ci:*-label at least once, checking if every runs as expected.