So now I created a new project specifying a branch: But the result is the same, I am not sure what's wrong in my configuration: the logs says:
*No candidate revisions* *ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.* *Recording test results* *Skipping Cobertura coverage report as build was not UNSTABLE or better ...* *Finished: FAILURE* And the out put of `git branch -a` in workspace of the job is still the same: It doesn't show any remote branches: I cloned the project in manually in a temp directory and the above list all branches as it should. Any idea what might be happening here? p.s. following is the branch config: Branches to build Branch Specifier (blank for default): On Sunday, 27 January 2013 16:19:45 UTC+4, Ahmed Mubbashir Khan wrote: > > Plus on executing 'git branch -a' > It doesn't list any of the other remote branch, see: > $ git branch -a > * (no branch) > master > remotes/origin/HEAD -> origin/master > remotes/origin/master > > > > On Sunday, 27 January 2013 16:13:09 UTC+4, Ahmed Mubbashir Khan wrote: >> >> Hi All, >> I configured a porject with a specific branch, then instead of >> specifiying a branch I though it would be better if I go with the default >> behaviour that is build every branch. >> I removed the the branch name from 'Branches to build' but on polling it >> seems like that it is still looking for changes in the old branch. >> So the question is: Can I change a barnach in 'Branches to build' in >> configuration after building a project in a specific branch >> >> Following is the pooling log: >> >> Polling for changes in >> Seen branch in repository origin/HEAD >> Seen branch in repository origin/master -> What it seems like that its >> still looking only changes only in master >> Done. Took 5.1 sec >> No changes >> >> >> I am using jenkins version 1.499 and git plugin version 1.1.26 >> >> >> thoughts? >> >>
