Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI jobs failing after renaming branch master to main #148

Closed
obnoxxx opened this issue Feb 21, 2021 · 7 comments
Closed

CI jobs failing after renaming branch master to main #148

obnoxxx opened this issue Feb 21, 2021 · 7 comments
Assignees

Comments

@obnoxxx
Copy link
Collaborator

obnoxxx commented Feb 21, 2021

Despite having changed the branch from origin/master to origin/main for the nightly-samba-builds job in #143 (and others as well), the jobs still fail like this:

Cloning the remote Git repository
Cloning repository https://github.com/gluster/centosci.git
 > git init /home/gluster/workspace/gluster_nightly-samba-rpm-builds # timeout=10
Fetching upstream changes from https://github.com/gluster/centosci.git
 > git --version # timeout=10
 > git --version # 'git version 1.8.3.1'
 > git fetch --tags --progress https://github.com/gluster/centosci.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/gluster/centosci.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse origin/master^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

Seems like there is some problem with the system still having the master branch located somewhere.

See e.g. https://ci.centos.org/view/Gluster/job/gluster_nightly-samba-rpm-builds/391/console (latest nightly) or https://ci.centos.org/view/Gluster/job/gluster_nightly-samba-rpm-builds/390/console triggered from gluster/samba-integration#137

@obnoxxx
Copy link
Collaborator Author

obnoxxx commented Feb 21, 2021

@nixpanic - any clues?

Some googling indicated avoiding the second fetch may introduce the problems.
Some leads indicate an allowSecondFetch option to the git plugin, but I don't know how or where to set it.

@nixpanic
Copy link
Member

jenkins-git-2nd-fetch

This options is under the https://<jenkins-host>/configure page. Because Gluster still uses the shared Jenkins deployment, changing this option requires a ticket at https://pagure.io/centos-infra/issues

@nixpanic
Copy link
Member

Requested the option at https://pagure.io/centos-infra/issue/230

@obnoxxx
Copy link
Collaborator Author

obnoxxx commented Feb 22, 2021

Thanks @nixpanic - let's see if that helps...

@obnoxxx
Copy link
Collaborator Author

obnoxxx commented Feb 22, 2021

This seems to be fixed with #149

@anoopcs9
Copy link
Collaborator

Requested the option at https://pagure.io/centos-infra/issue/230

So did we make a change with Jenkins configuration for git plugin?

@anoopcs9
Copy link
Collaborator

Closing the issue as we are successfully running the integration job in Jenkins for a while now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants