Skip to content

Separated CI/CD pipeline to parallel architecture build stage and optional version creation stage #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 21, 2024

Conversation

roddyrap
Copy link
Collaborator

Also only uploading artifacts if a version is created, in order to reduce space

@roddyrap
Copy link
Collaborator Author

MR purpose changed: Release was reverted to old way. This is because static-gdb releases are really large and there's a good case using artifacts will cause us to surpass the free 500MB storage limit, even if we delete the artifacts after a day

@guyush1
Copy link
Owner

guyush1 commented Dec 21, 2024

LGTM! Nice job

Base automatically changed from using-submodules to develop December 21, 2024 11:26
Using a matrix and job separation we can make the architectures compile
parallel to eachother, hopefully reducing the time required for builds
and also simplifying the process of building a single architecture.

A problem that we encountered is that with Python the resulting packed
tars are very large. Each release is in the order of tens of megabytes.
Using artifacts in our pipeline can easily make us surpass the maximum
size limit for free GitHub accounts (500 MB).
Because of this, we use the regular non-parallel pipeline for release
build. Releasing the version from the same job the build was performed
in allows us to directly access the build files instead of using
artifacts.

Separated release and MR pipelines.
There's no real reason to assume the host machine is X64.
@roddyrap roddyrap merged commit c44e675 into develop Dec 21, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants