Thanks @Mark. I switched to using refspecs and it seems to have addressed
the issue.
On Tuesday, June 27, 2017 at 5:53:07 PM UTC-4, Abhijith Reddy wrote:
>
> Whenever i specify a branch with GitSCM i see the following issue
> Couldn't find any revision to build. Verify the repository and branch
Can you try with something like that inside your Jenkinsfile :
node {
deleteDir()
checkout scm
}
Jenkins seems to be already able to retrieve your Jenkinsfile, so you don't
need to give all SCM details inside it, see
On Tuesday, June 27, 2017 at 5:01:46 PM UTC-6, Mark Waite wrote:
>
> I suspect you're encountering a conflict between the git plugin
> maintaining compatibility with old behavior, and the desire to support
> branch names which contain slashes.
>
> Refer to the online help in the git plugin for
I suspect you're encountering a conflict between the git plugin maintaining
compatibility with old behavior, and the desire to support branch names
which contain slashes.
Refer to the online help in the git plugin for alternate ways to define a
branch name. The format "word/word" is
Whenever i specify a branch with GitSCM i see the following issue
Couldn't find any revision to build. Verify the repository and branch
configuration for this job.
Here's my Jenkinsfile
node {
deleteDir()
checkout([$class: 'GitSCM', branches: [[name: 'feature/my-branch]],
