I have a problem with some Jenkins pipelines: When I trigger them with old commits, I receive the following error:
git rev-parse e14aea3d252fc61f29ee7f41e623a78e0e0e5e47^{commit} # timeout=10
git rev-parse origin/e14aea3d252fc61f29ee7f41e623a78e0e0e5e47^{commit} # timeout=10
git rev-parse e14aea3d252fc61f29ee7f41e623a78e0e0e5e47^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
ERROR: Maximum checkout retry attempts reached, aborting

In the example above, the commit is 5 months old. The pipeline receives 3 parameters: the repository name, branch name and commit sha1. I use Bitbucket as the repository hosting service.
This problem doesn't occur with newer commits (when I trigger the pipeline with commits from two months ago or from a few days ago, it works fine. Therefore, I think that the problem is not with Jenkins configuration. In addition, I verified that "shallow clone" and "lightweight checkout" options are not marked.)
Jenkins Configuration:
Configuration-part1 Configuration-part2
Does anybody have any ideas how to solve this?
This can occur due to two issues:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With