-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Ubuntu 12.04
I have a build parameter, branch, which is passed to the git "Branches to build" setting. When this parameter is set to '*', '**', or is empty, the last built revision gets built again instead of an updated branch HEAD. Setting this parameter to a specific branch name, such as 'development' or 'master' will build the HEAD of the specified branch. Directly setting git "Branches to build" to '*', '**', or leaving it empty will cause an updated branch HEAD to build properly.
- is duplicated by
-
JENKINS-21719 Unable to get Branch to build variable to work with wildcard
-
- Open
-
- is related to
-
JENKINS-23714 specified git branch to checkout/build is not used
-
- Closed
-
[JENKINS-20969] When branch build parameter is '*', '**' or empty, a stale revision is built
Description | Original: I have a build parameter, branch, which is passed to the git "Branches to build" setting. When this parameter is set to '*', '**', or is empty, the last built revision gets built again instead of an updated branch HEAD. Setting this parameter to a specific branch name, such as 'development' or 'master' will build the HEAD of the specified branch. Directly setting git "Branches to build" to '*', '**', or leaving it empty will cause an updated branch HEAD to build properly. | New: I have a build parameter, branch, which is passed to the git "Branches to build" setting. When this parameter is set to '\*', '**', or is empty, the last built revision gets built again instead of an updated branch HEAD. Setting this parameter to a specific branch name, such as 'development' or 'master' will build the HEAD of the specified branch. Directly setting git "Branches to build" to '\*', '**', or leaving it empty will cause an updated branch HEAD to build properly. |
Description | Original: I have a build parameter, branch, which is passed to the git "Branches to build" setting. When this parameter is set to '\*', '**', or is empty, the last built revision gets built again instead of an updated branch HEAD. Setting this parameter to a specific branch name, such as 'development' or 'master' will build the HEAD of the specified branch. Directly setting git "Branches to build" to '\*', '**', or leaving it empty will cause an updated branch HEAD to build properly. | New: I have a build parameter, branch, which is passed to the git "Branches to build" setting. When this parameter is set to '\*', '\*\*', or is empty, the last built revision gets built again instead of an updated branch HEAD. Setting this parameter to a specific branch name, such as 'development' or 'master' will build the HEAD of the specified branch. Directly setting git "Branches to build" to '\*', '\*\*', or leaving it empty will cause an updated branch HEAD to build properly. |
Link | New: This issue is duplicated by JENKINS-21719 [ JENKINS-21719 ] |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 152810 ] | New: JNJira + In-Review [ 178328 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] |