-
Improvement
-
Resolution: Unresolved
-
Major
-
None
I have a parameterized job that asks the user which changeset he wants to build.
The Mercurial plugin claims to support only branch names in 'Source Code Management -> Branch'. If I supply a changeset instead, it usually works, notwithstanding.
The only caveat is: If said changeset already exists in the local workspace repository, Hudson will build the most recent changeset, not the one I asked for.
- is related to
-
JENKINS-7282 Specifying an old changeset as branch name builds the most recent changeset instead
- Closed
-
JENKINS-5396 Support tags instead of branches
- Resolved