ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

[Yash Dabhi]

Hi all,

when I am trying to run job getting below error. Getting this while checking out the source code.

It happened all of sudden. I was working fine with the same configuration. 

Please advise what can be done. 

> git fetch --tags ssh://${git_url}.git CICD
 > git rev-parse refs/remotes/origin/9^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/9^{commit} # timeout=10
 > git rev-parse origin/9^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
An attempt to send an e-mail to empty list of recipients, ignored.
[BFA] Scanning build for known causes...
[BFA] Found failure cause(s):
[BFA] GIT Revision Error from category SCM
[BFA] Done. 0s

Thank you!

[Mark Waite]

That seems to indicate that you previously had a branch named '9' and now the branch named '9' no longer exists.

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/68dc0a47-6c28-4027-8fa2-ed6c3e6a5492%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Yash Dabhi]

Hi Mark,

Thanks for the reply. 

I tried cloning the branch in my local and it clones fine. Branch exists and able to commit as well. Not sure why it stopped working suddenly. 

Thanks,
Yash

[Mark Waite]

You might check that the job definition was not changed recently.  If that shows nothing of interest, you could login to the workspace last used for the clone and perform the same commands in that clone.  That may help identify what is failing.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a02980bc-c27f-4515-bd65-d9405af2b3e4%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Yash Dabhi]

Thanks Mark,

I was able to find the root cause. I had root access issue on the server when job triggers the build and new folder didn't have write access to clone the repo. 

Thanks again for the help!

Thanks,
Yash