Added numbered symlinks to build steps for ease of use - #2467
Added numbered symlinks to build steps for ease of use#2467craigcomstock wants to merge 6 commits into
Conversation
|
Thanks for submitting a pull request! Maybe @craigcomstock can review this? |
c98ba71 to
9795a2b
Compare
|
@cf-bottom jenkins please |
|
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/14623/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-14623/ |
0b42a13 to
57b5998
Compare
|
Looks like pr-pipeline is not happy. I will debug and make sure this works in both cases: pr-pipeline and build-in-container. 👍 |
f5a07bd to
d44af5b
Compare
|
Looking awesome in pr-pipeline and 🤞 for in-container build |
…de the container Ticket: ENT-12599 Changelog: none
Ticket: ENT-12599 Changelog: None
8f34e8b to
420d0ce
Compare
|
bootstrap-mission-portal was being skipped due to ROLE != hub in bootstrap-pr jenkins job. I added a check for JOB_NAME=bootstrap-pr. |
The numbered steps are symlinks to existing scripts. The artifacts output directory had to be refactored slightly to work in both containers and regular build hosts. Some existing scripts were split up or refactored to migrate steps previously in build-in-container-inner.sh to build-script scripts. Ticket: ENT-12599 Changelog: None pull better mission portal bootstrap code from old bootstrap-tarballs
Ticket: None Changelog: None
Ticket: none Changelog: none
c207d01 to
14727ae
Compare
| # let setup-cfengine-build-host.sh know we are in a container and bootstrapping | ||
| RUN touch /etc/cfengine-in-container.flag |
There was a problem hiding this comment.
WRT this flag file name, I'd maybe distinguish whether we're talking about building CFEngine in a container, or running CFEngine in a container. But no big deal of course.
There was a problem hiding this comment.
yeah, makes sense. would be easy to change :)
No description provided.