Unfortunately, this does not seem to be fixed (for me, at least) in 2.0.1.
Steps to reproduce:
1. Create a new job. Use a git repo with multiple branches. Set the 'Branches to build > Branch specifier' to a specific branch, e.g. 'feature/my-feature'
2. Run a build
Building in workspace /var/lib/jenkins/main/jobs/JOB_NAME/workspace
Fetching changes from the remote Git repository
Fetching upstream changes from ssh://...REPO URL...
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
- the clone works fine if I don't specify a branch
- even after a successful clone, if I edit the job config to specify a branch, it fails with the same error as above.
I don't know much about the internals of the Git plugin, but it looks like it's not doing a fetch, so it doesn't know what remote branches are available.