Update CI scripts from master (3.27) - #2378
Conversation
|
@cf-bottom jenkins no tests |
|
Sure, I triggered a build: [NO TESTS] Jenkins: https://ci.cfengine.com/job/pr-pipeline/14315/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-14315/ |
|
@cf-bottom jenkins no tests |
|
Sure, I triggered a build: [NO TESTS] Jenkins: https://ci.cfengine.com/job/pr-pipeline/14317/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-14317/ |
There have been many changes and all of them should likely be cherry picked but I don't want to bother finding them all. The ci directory is pretty safe to just pull en-masse from master. In ENT-11241 and ENT-14330 we migrated to running setup-cfengine-build-host.sh in several important CI jobs so the updates need to be in all LTS branches. Ticket: ENT-14330 Changelog: none Conflicts: ci/fix-buildhost.sh
The symlink step was failing due to the tarball itself matching the glob Ticket: none Changelog: none (cherry picked from commit f3c42b2)
39aa361 to
a6caff3
Compare
|
@cf-bottom jenkins no tests |
|
Alright, I triggered a build: [NO TESTS] Jenkins: https://ci.cfengine.com/job/pr-pipeline/14319/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-14319/ |
… conditions when operating on jenkins files Happened once that chown -R jenkins /home/jenkins complained of missing files. Ticket: none Changelog: none
1ec71a5 to
aa71454
Compare
|
retry of ubu22hub saw no issue with setup-cfengine-build-host race condition on chowning files to jenkins. @cf-bottom jenkins no tests again please |
|
Sure, I triggered a build: [NO TESTS] Jenkins: https://ci.cfengine.com/job/pr-pipeline/14327/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-14327/ |
Some find commands require a path to search in. Ticket: ENT-11241 Changelog: none (cherry picked from commit dd61423)
e7ff7e3 to
89a67d5
Compare
|
ci is green. ready to go. https://ci.cfengine.com/job/pr-pipeline/14352/ (green but badges aren't quite working currently) |
$(pwd) was the jenkins workspace directory which does not have proxy-target.txt so revert back to $HOME rhel/centos-7 need centos-7-setup-devtoolset-11.sh and also realpath to find the right place to source. Limit that to hosts which have realpath and fail fast on rhel/centos-7 hosts that do not have realpath available. Ticket: ENT-11241 Changelog: none (cherry picked from commit dbc1efb)
89a67d5 to
93b0347
Compare
3 participants
There have been many changes and all of them should likely be cherry picked but I don't want to bother finding them all.
The ci directory is pretty safe to just pull en-masse from master.
In ENT-11241 and ENT-14330 we migrated to running setup-cfengine-build-host.sh in several important CI jobs so the updates need to be in all LTS branches.
Ticket: ENT-14330
Changelog: none