Closed e-gris closed 5 years ago
The other piece is the CJC addition. I put up https://github.com/puppetlabs/ci-job-configs/pull/5672 and will build and run an experimental pipeline which should allow us to test this locally by updating the ref in configs/composnents/puppet-runtime.json
to point to the artifacts that job publishes (something like the following):
{"location":"http://builds.delivery.puppetlabs.net/puppet-runtime/{some-number}/artifacts/","version":"{some-number}"}
Then we can build it with something like bundle exec build puppet-bolt el-8-x86_64
. Once we have a build we can install it on a red hat 8 node and make sure things look good.
So the experimental pipeline failed (https://jenkins-platform.delivery.puppetlabs.net/view/__experimental%20automatic/job/experimental_auto_bolt-runtime_runtime-vanagon-packaging_master/BUILD_TARGET=el-8-x86_64,SLAVE_LABEL=worker/1/console ).
My guess is that we will want to use native gcc
instead of pl-build-tools
. So we will need a PR against puppet-runtime like https://github.com/puppetlabs/puppet-runtime/pull/133/commits/a33b803514b3b065c8098b14656e4351792f105c
ahh yeah, there is no pl-build-tools repo for el 8: http://pl-build-tools.delivery.puppetlabs.net/yum/
So, should this change be dependent on pl-build-tools updates?
I don't think so, we're trying to phase out pl-build-tools, and the native tools on el-8 should be sufficient
I think, then, this should be ready to go once approved. I'm leaving for vacation tomorrow. @donoghuc or @mwaggett , are either of you available to shepherd this through?
@e-gris I can take care of shepherding this through. I think I would like to take ownership of the ticket and move to the bolt kanban so we can track the integration status and the update to bolt installation docs.
This is my first go on something like this. I think it is this simple.