This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
HERO_CI shallow clone integration
#37
Closed
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
i. Add shallow clone for `hero-gcc-toolchain` when `HERO_CI` is set. ii. Clean after installation on every GCC build stage when `HERO_CI` is set.
|
I'm closing this PR and I'm moving such modifications on a cumulative PR. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Dear @accuminium,
this patch integrates on the shallow clone for the submodules included inside
hero-gcc-toolchain.Modifications
i. Add shallow clone for
hero-gcc-toolchainwhenHERO_CIis set. (Fix #24)ii. Clean after installation on every GCC build stage when
HERO_CIis set.Now is not anymore necessary to use any
git submodulecommand from the root folder ofhero-sdk. Everything is done within the builder script. WhenHERO_CIenvironmental variable is set the script clone the submodules shallowly otherwise it get them regularly.I also added a new CI task on our Jenkins server that uses the Jenkins Pipeline. The pipeline controls all the builder targets one-by-one:
https://iis-jenkins.ee.ethz.ch/view/hero-sdk/job/hero-sdk-pipeline/
Here the old CI task that control the
-Abuild flow:https://iis-jenkins.ee.ethz.ch/view/hero-sdk/job/hero-sdk-centos7/
I also tried to integrate such modifications on you
travisbranch to see if it fix the problem of memory footprint. Here the branch https://github.com/pulp-platform/hero-sdk/tree/travis-dev-integration.Here the build (still going)
https://travis-ci.org/pulp-platform/hero-sdk/builds/441381805?utm_source=github_status&utm_medium=notification
I think, anyway, that travis at the moment is anyway too slow.