Hi!
With an update of Jenkins (or at least its git-plugin), fetching git repositories has changed a bit. This now causes issues with running some of the jobs for Gluster.
https://github.com/gluster/centosci/issues/148 suggests to enable the allowSecondFetch option. This seems to be a newly introduced option, and is only available in recently updated Jenkins deployments. The option can be found under
allowSecondFetch
Manage Jenking -> Configure System -> Git plugin
<img alt="jenkins-git-2nd-fetch.png" src="/centos-infra/issue/raw/files/7e9cb0b2f623d23534352d1ca670af79ed5e38309edca4cce7b7cb7661409de3-jenkins-git-2nd-fetch.png" />
Updated but it seems that from Jenkins PoV it's considered a "workaround". Setting is now enable and saved but don't know if that needed a jenkins restart, (not done). Can you verify if that fixes your issue ? but worth probably also migrating such job to the new ocp/openshift setup and so have your own jenkins server/pod there ?
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue tagged with: centos-ci-infra, low-gain, low-trouble
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Thanks! It seems this was not the (only?) problem in the CI jobs. There was a change introdiced by renaming branches (master -> main) which prevented deploying updated JJB configurations.
Maybe the allowSecondFetch is not needed after all...
Thanks for the feedback. So ok to close ?
yes, ok to close.
Thanks for the help!
Metadata Update from @devos: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.