lzap
October 5, 2021, 6:25am
1
Hey,
can we get our 3.0 release plugin pipeline triggered for the following rebase:
Discovery is broken due to Puppet extraction until we bump the version to 1.0.3. Thanks.
ekohl
October 5, 2021, 9:55am
2
Looks like at least the RPM pipeline was red. Looks like it couldn’t pull in the el7-scl repo, probably due to some intermittent network issue. I’ve kicked off foreman-plugins-nightly-rpm-pipeline #758 [Jenkins] and that’s green now.
Could we also propagate the plugins into the 3.0 or do we need to wait for 3.0.1?
ekohl
October 5, 2021, 2:47pm
4
This was the cherry pick commit:
committed 05:54AM - 05 Oct 21 UTC
(cherry picked from commit ef3c0e3c69c6beb63177e249b78fea58fd1cf5e9)
That was built here:
https://ci.theforeman.org/view/3.0/job/foreman-packaging-rpm-3.0-release/27/
And I’ve kicked off a build which should propagate it:
https://ci.theforeman.org/job/foreman-plugins-3.0-rpm-pipeline/67/
2 Likes