-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Ubuntu 14.04.1 LTS x64
OpenJDK 1.7.0_65 using package defaults for all settings
Jenkins 1.579 run w/ Jetty, but using Apache 2.4 proxy for authentication
git plugin 2.2.5
multi-scm plugin 0.3
Jenkins installed via apt from pkg.jenkins-ci.org. Slaves are launched via SSH or DCOM depending on platform.
Various browsers are in use.
Ubuntu 14.04.1 LTS x64 OpenJDK 1.7.0_65 using package defaults for all settings Jenkins 1.579 run w/ Jetty, but using Apache 2.4 proxy for authentication git plugin 2.2.5 multi-scm plugin 0.3 Jenkins installed via apt from pkg.jenkins-ci.org. Slaves are launched via SSH or DCOM depending on platform. Various browsers are in use.
I marked this as an improvement instead of a bug because I am not sure if 'scmName' is designed to show the information I'm looking for.
I am trying to figure out how best to do custom build tags for multi-repo builds, based on some internal business rules we have for tag name and content. One thing I noticed while looking at build results through the API is that the 'scmName' property under 'buildsByBranchName' is not populated, even if I give each repo a name under advanced, or have 'unique scm name' selected in my job config. This is true w/ both the multi-scm config and when using the git plugin directly, so I think it's a git plugin 'issue'.
I think it would be easier to match output to repo if the scmName property reflected the custom name I put in the job config. Or if another property displayed that information. See below for an example of what I'm looking at.
{
"buildsByBranchName" : {
"rel1.00" : {
"buildNumber" : 38,
"buildResult" : null,
"marked" : {
"SHA1" : "34e051320e481dd2b8a175d36ef5a2dd5d3fa5ad",
"branch" : [
]
},
"revision" : {
"SHA1" : "34e051320e481dd2b8a175d36ef5a2dd5d3fa5ad",
"branch" : [
]
}
}
},
"lastBuiltRevision" : {
"SHA1" : "34e051320e481dd2b8a175d36ef5a2dd5d3fa5ad",
"branch" : [
]
},
"remoteUrls" : [
"ssh://user@git.company.com/project.git"
],
"scmName" : ""
},