[AXON-29] chore: initial setup of Github CI #2
Conversation
This file contains 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
sdzh-atlassian
force-pushed
the
setup-ci
branch
from
44b9e42 to
d840e4a
Compare
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 is this?
Initial setup for the CI pipelines in the new repo:
.github/workflows/build.yaml- regular builds.github/workflows/release.yaml- regular releases, triggered by tags, same as before.github/workflows/release-nightly.yaml- WIP nightly releasesThe node setup should be cached
The actual releasing functionality is stubbed for now - but I've tested out the PAT verification and it works:
NPM dependencies cache
To bring the builds here in line with our old BB setup, I've tried setting up cache for NPM dependencies as described here. However, the improvement in time it seems to yield is fairly negligible:
No cache:
Cache:
This is all completely alright at the moment - but in the future, we might want to look into
npm run compilecommand and speed that up - it's the biggest offender for DevProd right now 😉How was this tested