On Wednesday, 15 May 2019 21:28:52 UTC+1, Mark Waite wrote:
>
>
> You can often avoid the guessing by naming the branch precisely, as in
> 'origin/develop'.
>
I attempted to use 'origin/develop' as the branch name, but that causes the
job to fail the checkout with "ERROR: Couldn't find any revision to build.
Verify the repository and branch configuration for this job". Here's the
pipeline I'm testing this with:
node('linux') {
stage('checkout') {
git branch: 'origin/develop', ...
}
}
The last line of output before the failure is a 'git fetch' call which is
identical to a run using a branch name of 'develop' which will then
checkout successfully.
--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/f03ac832-bad1-42cb-8840-ce0cb632ae21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
