Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Incorrect branch names in newly spawned jobs #81

Open
sherabi opened this issue Feb 25, 2015 · 4 comments
Open

Incorrect branch names in newly spawned jobs #81

sherabi opened this issue Feb 25, 2015 · 4 comments

Comments

@sherabi
Copy link

sherabi commented Feb 25, 2015

Hi,
As part of gradle switches I entered the following...
-DjenkinsUrl=http://forge:8080 -DgitUrl=git@scm:product/platform -DtemplateJobPrefix=MINT_Platform_3.7 -DtemplateBranchName=develop -DbranchNameRegex=.*/v37/feature/MINT-.+ -DjenkinsUser=xxxx -DjenkinsPassword=xxxx -DstartOnCreate=true -DnestedView=Wolverine

The branches matching my regex are correctly identified:
10:05:53 executing command: git ls-remote --heads git@scm:product/platform
10:05:54 944bdbc4c66082be384ebc9b697c9926e39b5cab refs/heads/develop
10:05:54 0de938a7a5838d411ffef4d5bbc009c1c30344ba refs/heads/feature/MINT-1328-sam-lifecycle
10:05:54 c4ab58609decebf671dce70b4467cde7932c19b8 refs/heads/feature/MINT-1330
10:05:54 b196866cb62053d7d0fa93912e1a0ba83855218c refs/heads/feature/MINT-1331
10:05:54 fd599c0905d3ddd107d75eaedbdc5b1e7560bcf5 refs/heads/feature/MINT-1353
10:05:54 7d4ab98cdc85f1f041e1a70b7cb909c5d128035a refs/heads/feature/MINT-1368
10:05:54 a8fbcce869520885e6c1b30f169ec55df74a0679 refs/heads/feature/MINT-1371
10:05:54 7d3014bb13d9cd4a8bfa54fa6d4aa2b4b2764585 refs/heads/feature/MINT-1378
10:05:54 cbe8b0f5522768b461294323d47c9bd1bb7b2064 refs/heads/feature/MINT-1390
10:05:54 588fcaf5b5a6250cd385307f68b7c86f41bbfd4d refs/heads/feature/MINT-1441
10:05:54 20bd990fd9d73eedff844720f9ac6e8e2eeefc02 refs/heads/feature/MINT-1449
10:05:54 650e91c29d654b6af2c5916a7ae900497143a1cf refs/heads/feature/MINT-1453
10:05:54 b6435fb2f799f4d5cdbe63984a7ceb8e8afe9fba refs/heads/feature/MINT-357
10:05:54 73a7f87688f55ca7f8dd8d036ece169f2148a0d7 refs/heads/master
10:05:54 a6b089d8cce683aed85becb5dcff02233a9aa98d refs/heads/support/v3.5
10:05:54 3e59d628d6d4f3f867af58a04333d328af7b6ead refs/heads/support/v3.7
10:05:54 caee7b0054754cd9d6db0aba6929c826840677b4 refs/heads/support/v37/develop
10:05:54 * d5583f156a64528b57177c7f0b116b3803d2d400 refs/heads/support/v37/feature/MINT-1329
10:05:54 * c169316ba713071968f315dfb6d4e32de241cf17 refs/heads/support/v37/feature/MINT-1446
10:05:54 * 8af32416ac0ddf63a03ab2476d74d8964358bac2 refs/heads/support/v37/feature/MINT-1452

See the ones marked in asterix....
However the newly spawned jobs show the following as their branch specifiers
support/v37/support/v37/feature/MINT-1329
support/v37/support/v37/feature/MINT-1446
support/v37/support/v37/feature/MINT-1452

Notice that support/v37 occurs twice as part of the branch specifier on the newly created jobs. I think this is a bug.
Thanks!

@jamesdh
Copy link
Contributor

jamesdh commented Jun 28, 2015

@sherabi Did you ever resolve this? I've never seen this nor have there been any other reports of this.

@sherabi
Copy link
Author

sherabi commented Jul 9, 2015

Hi James,
I was able to eventually figure this out by reading your code. Essentially the job name is where you parse the branch name from. This really should be changed to instead read the configuration file because it renders the branch field in the jenkins job useless. I can put in any branch name in the build job and it could be a dummy branch name since the branch name your code is really concerned with is actually in the name of the build job.

@jamesdh
Copy link
Contributor

jamesdh commented Jul 9, 2015

Can you provide a link (to the source in GitHub) where you think the error is?

@jamesdh
Copy link
Contributor

jamesdh commented Jul 9, 2015

Or even better, write a test that exposes the error?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants