date:20151230

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Baltrinic commented on  JENKINS-26587 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Checkout fails with Multiple SCMs plugin on commit notification  
 
 
 
 
 
 
 
 
 
 
Just tested it out and yes, we are still seeing the issue. From our perspective, this is a major regression. I'll open up a separate ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-32258) Excessive Git --Rev-Parse invocation when using Prune

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Baltrinic updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32258 
 
 
 
  Excessive Git --Rev-Parse invocation when using Prune  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Baltrinic 
 
 
 
 
 
 
 
 
 
 h2. HistoryThis was originally discussed in the comments of JENKINS-26587 as it was first identified as a regression when testing that issue.  As Git Plugin 2.4.1 has how been release w/o resolving this regression, it has escaped and I am opening a separate ticket.h2. Description of ProblemPreviously in (and correctly?)  for  when using the "Prune stale remote-tracking branches" behavior,  in  every build, after the {{git checkout -f}} but before the {{git reset --hard}} there was a {{git rev-parse --verify HEAD}} command. Now in place of the single rev-parse command there is a {{git rev-parse /remotes/origin/...}} command _for every remote branch that exists_. h2. Steps to reproduce.  # Install a baseline Jenkins Master, which will include the Git Plugin v 2.4.1. (We used the 1.625.3 LTS version.)# Setup credentials so that it can authenticate to a remote repo. (We use Atlasssian Stas.h.# Create a freestyle job to pull from a remote git repo that has multiple (preferably many) branches.  * branch specifier origin/master  * Additional Behaviors: Prune stale remote-tracking branches.Run the job and observe the output.  It will be something similar to the following:{code}Building on master in workspace /var/lib/jenkins/workspace/git-test > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://git@stash:7999/TEST/test.git # timeout=10Pruning obsolete local branchesFetching upstream changes from ssh://git@stash:7999/TEST/test.git > git --version # timeout=10using GIT_SSH to set credentials Credential ID: jenkins-stash-ssh > git fetch --tags --progress ssh://git@stash:7999/TEST/test.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 38b70706154d37132bb67b82af7317e2ed85f9aa (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 38b70706154d37132bb67b82af7317e2ed85f9aaFirst time build. Skipping changelog. > git branch -a # timeout=10 > git rev-parse remotes/origin/CMOBL-4832-create-separate-onarrival-api^{commit} # timeout=10 > git rev-parse remotes/origin/CROSSTAB-5545^{commit} # timeout=10 > git rev-parse remotes/origin/CROSSTAB-5802^{commit} # timeout=10 > git rev-parse remotes/origin/CROSSTAB-5803^{commit} # timeout=10... several thousand ref-parses later ... > git rev-parse remotes/origin/webformtomvc-part1^{commit} # timeout=10 > git rev-parse remotes/origin/wip-csn-6200^{commit} # timeout=10 > git rev-parse remotes/origin/wip-prod-20347^{commit} # timeout=10Finished: SUCCESS{code}With 17K+ remote branches  in our repository, this added fifteen minutes to builds that previously took three to eight minutes total. Obviously we could stand to clean up some old branches but this behavior is not acceptable.h2. Workarounds# Remove the prune stale branches behavior.# Downgrade to Git Plugin 2.4.0

[JIRA] [git-plugin] (JENKINS-32258) Excessive Git --Rev-Parse invocation when using Prune

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Baltrinic created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32258 
 
 
 
  Excessive Git --Rev-Parse invocation when using Prune  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 31/Dec/15 4:26 AM 
 
 
 

Environment:
 

 Introduced in Git Plugin 2.4.1 
 
 
 

Labels:
 

 git git-plugin 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Kenneth Baltrinic 
 
 
 
 
 
 
 
 
 
 
History 
This was originally discussed in the comments of 

JENKINS-26587
 as it was first identified as a regression when testing that issue. As Git Plugin 2.4.1 has how been release w/o resolving this regression, it has escaped and I am opening a separate ticket. 
Description of Problem 
Previously in (and correctly?) for when using the "Prune stale remote-tracking branches" behavior, every build, after the git checkout -f but before the git reset --hard there was a

[JIRA] [robot-plugin] (JENKINS-32118) Opening Robot Framework log failed

2015-12-30 Thread ale...@margasov.ru (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexei Margasov commented on  JENKINS-32118 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Opening Robot Framework log failed  
 
 
 
 
 
 
 
 
 
 
The bug appeared after I updated version jenkins from 1.616 to 1.625.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-31925) GitSCM default values not properly defined

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-31925 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GitSCM default values not properly defined  
 
 
 
 
 
 
 
 
 
 
Nice. I was not aware of the DataBoundConstructor addition in 1.535. That looks very promising to improve some especially heavyweight optional behaviors in the git plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-31925) GitSCM default values not properly defined

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite edited a comment on  JENKINS-31925 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GitSCM default values not properly defined  
 
 
 
 
 
 
 
 
 
 Nice.  I was not aware of the [DataBoundSetter addition in 1.535|https://groups.google.com/forum/#!topic/jenkinsci-dev/58-DEvuJZWI].  That looks very promising to improve some especially  heavyweight optional behaviors  long constructors  in the git plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-31925) GitSCM default values not properly defined

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite edited a comment on  JENKINS-31925 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GitSCM default values not properly defined  
 
 
 
 
 
 
 
 
 
 Nice.  I was not aware of the [ DataBoundConstructor DataBoundSetter  addition in 1.535|https://groups.google.com/forum/#!topic/jenkinsci-dev/58-DEvuJZWI].  That looks very promising to improve some especially heavyweight optional behaviors in the git plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31937) Excluded Regions not applied if other changes in repository

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31937 
 
 
 
  Excluded Regions not applied if other changes in repository  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [clang-scanbuild-plugin] (JENKINS-32229) Latest version fails to find reports directory

2015-12-30 Thread rged...@vulcanft.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ross Geddis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32229 
 
 
 
  Latest version fails to find reports directory  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 clang-scanbuild-plugin 
 
 
 

Created:
 

 30/Dec/15 5:47 PM 
 
 
 

Environment:
 

 clang-scanbuild-plugin-1.7 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Ross Geddis 
 
 
 
 
 
 
 
 
 
 
After updating to the latest version of this plugin, there has been an issue with finding the clang scan build reports directory. The plugin is configured with:  
 

Mark build as unstable when threshold is exceeded? == unset/false
 

Report folder == clangScanBuildReports (default value)
 
 
After a project, configured with the plugin has been build, the following exception is seen in the console 

 

ERROR: Build step failed with exception
java.lang.NullPointerException
	at

[JIRA] [aws-java-sdk-plugin] (JENKINS-32162) Please bump to latest aws-java-sdk

2015-12-30 Thread vinc...@latombe.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe commented on  JENKINS-32162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Please bump to latest aws-java-sdk  
 
 
 
 
 
 
 
 
 
 
1.10.42 released. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [aws-java-sdk-plugin] (JENKINS-32162) Please bump to latest aws-java-sdk

2015-12-30 Thread vinc...@latombe.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32162 
 
 
 
  Please bump to latest aws-java-sdk  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [delivery-pipeline-plugin] (JENKINS-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery

2015-12-30 Thread cristianofon...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 cristiano fontes commented on  JENKINS-30043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Step Jobs are placed after Post Build Action Jobs in delivery  
 
 
 
 
 
 
 
 
 
 
Second this, just released my delivery pipeline and It's really confusing for management people, they went crazy over this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Baltrinic commented on  JENKINS-26587 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Checkout fails with Multiple SCMs plugin on commit notification  
 
 
 
 
 
 
 
 
 
 
Mark Waite Did the issue with excessive git rev-parse invocations get resolved? I took a look through the post Dec 3 commit history and didn't see anything obvious. I plan to test this out over the holiday weekend to be sure and am hoping its is resolved.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31937) Excluded Regions not applied if other changes in repository

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-31937 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Excluded Regions not applied if other changes in repository  
 
 
 
 
 
 
 
 
 
 
Alistair Haig, it is not a bug. 
For your project1 job use that in your Excluded Regions: 

 
/shared/.*
/project2/.*
 

 
And this for your project2: 

 
/shared/.*
/project1/.*
 

 
The result will be similar to: 

 
Started on Dec 30, 2015 6:06:00 PM
Received SCM poll call on master for OSS-31937-2 on Dec 30, 2015 6:06:17 PM
https://subversion.assembla.com/svn/oss-31937/shared is at revision 12
Ignored revision 12: Found only excluded paths: /project2/README, /shared/README
https://subversion.assembla.com/svn/oss-31937/project1 is at revision 7
Done. Took 24 sec
No changes
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31937) Excluded Regions not applied if other changes in repository

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto edited a comment on  JENKINS-31937 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Excluded Regions not applied if other changes in repository  
 
 
 
 
 
 
 
 
 
 [~ali_haig], it is not a bug.For your {{project1}} job use that in your  {{  * Excluded Regions }} * :{noformat}/shared/.*/project2/.*{noformat}And this for your {{project2}}:{noformat}/shared/.*/project1/.*{noformat}The result will be similar to:{noformat}Started on Dec 30, 2015 6:06:00 PMReceived SCM poll call on master for OSS-31937-2 on Dec 30, 2015 6:06:17 PMhttps://subversion.assembla.com/svn/oss-31937/shared is at revision 12Ignored revision 12: Found only excluded paths: /project2/README, /shared/READMEhttps://subversion.assembla.com/svn/oss-31937/project1 is at revision 7Done. Took 24 secNo changes{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31937) Excluded Regions not applied if other changes in repository

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-31937 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Excluded Regions not applied if other changes in repository  
 
 
 
 
 
 
 
 
 
 
Alistair Haig, other option would be: 
For your project1 job use that in your Included Regions: 

 
/project1/.*
 

 
The result will be similar to: 

 
Started on Dec 30, 2015 6:13:00 PM
Received SCM poll call on master for OSS-31937-2 on Dec 30, 2015 6:13:05 PM
https://subversion.assembla.com/svn/oss-31937/shared is at revision 13
Ignored revision 13: Found no included paths
https://subversion.assembla.com/svn/oss-31937/project1 is at revision 7
Done. Took 12 sec
No changes
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [vsphere-cloud-plugin] (JENKINS-32096) Add option to leave VM powered off after creation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add option to leave VM powered off after creation  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jason Swager Path: src/main/java/org/jenkinsci/plugins/vSphereCloudSlaveTemplate.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Clone.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Deploy.java src/main/java/org/jenkinsci/plugins/vsphere/tools/VSphere.java src/main/resources/org/jenkinsci/plugins/vsphere/builders/Clone/config.jelly src/main/resources/org/jenkinsci/plugins/vsphere/builders/Clone/help-powerOn.html src/main/resources/org/jenkinsci/plugins/vsphere/builders/Deploy/config.jelly src/main/resources/org/jenkinsci/plugins/vsphere/builders/Deploy/help-powerOn.html http://jenkins-ci.org/commit/vsphere-cloud-plugin/90962f4ebaa776550ea8ce747cb3d213559fcb8a Log: Merge pull request #40 from eddyhub/JENKINS-32096 
Added option to set the power state after deployin a vm. 
Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/eec60218cef9...90962f4ebaa7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-26587 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Checkout fails with Multiple SCMs plugin on commit notification  
 
 
 
 
 
 
 
 
 
 
No, I didn't take any steps to reduce the number of calls to git rev-parse in the git plugin 2.4.1 release or the git client plugin 1.19.1 release. I am interested if you still see the problem, but a fix for that problem will need to wait for the next release of the plugins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-31937) Excluded Regions not applied if other changes in repository

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto edited a comment on  JENKINS-31937 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Excluded Regions not applied if other changes in repository  
 
 
 
 
 
 
 
 
 
 I've reproduced the  bug  behavior . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames

2015-12-30 Thread brian.b.l...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian L commented on  JENKINS-26493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use new EC2 API endpoint hostnames  
 
 
 
 
 
 
 
 
 
 
It would be really great to see a new release of this plugin. My team has seen a few issues working with the ec2-plugin, and we're hoping things will get smoother soon. On GitHub, there have been 14 commits to the master branch since the last release (August 2, 2015). One notable change (IMHO), is that the aws-java-sdk dependency has been upgraded from version 1.10.2 (used in the last release) to 1.10.26 (currently in the master branch). 
Can someone please comment as to when an update is expected, or if another plugin should be preferred? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-16711) Cannot process %20 in repository URL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-16711 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot process %20 in repository URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/SubversionChangeLogBuilder.java src/main/java/hudson/scm/SubversionEventHandlerImpl.java http://jenkins-ci.org/commit/subversion-plugin/ec10c72dd0a4a05add0f63733d36450ff7f2e7a1 Log: 

JENKINS-16711
 Encode the URLs when are shown in the logger 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-16711) Cannot process %20 in repository URL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-16711 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot process %20 in repository URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/SubversionSCM.java src/main/java/jenkins/scm/impl/subversion/SubversionSCMSource.java http://jenkins-ci.org/commit/subversion-plugin/94b8c22306c77acf7fd7c386d8bc708c350faba7 Log: Merge pull request #152 from recena/

JENKINS-16711
-PART2 


JENKINS-16711
 SVNPath must be built from a decoded path 
Compare: https://github.com/jenkinsci/subversion-plugin/compare/dd634079c9f9...94b8c22306c7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-16711) Cannot process %20 in repository URL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-16711 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot process %20 in repository URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/SubversionSCM.java src/main/java/jenkins/scm/impl/subversion/SubversionSCMSource.java http://jenkins-ci.org/commit/subversion-plugin/2b160a1ec3bc18224082141bf3683276d7aac6a8 Log: 

JENKINS-16711
 SVNPath must be built from a decoded path 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-16711) Cannot process %20 in repository URL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-16711 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot process %20 in repository URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/SubversionChangeLogBuilder.java src/main/java/hudson/scm/SubversionEventHandlerImpl.java http://jenkins-ci.org/commit/subversion-plugin/910139260fbcbf3d9fc6ab8d8251b73e41ebe935 Log: Merge pull request #153 from recena/

JENKINS-16711
-PART3 


JENKINS-16711
 Encode the URLs when are shown in the logger 
Compare: https://github.com/jenkinsci/subversion-plugin/compare/94b8c22306c7...910139260fbc 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-27718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/scm/listtagsparameter/ListSubversionTagsParameterValue.java http://jenkins-ci.org/commit/subversion-plugin/05aa7fc9b93c2cd6cef958a5b87603f8245e9ce8 Log: Merge pull request #151 from rodrigc/

JENKINS-27718
 


JENKINS-27718
 Override ParameterValue.buildEnvironment() 
Compare: https://github.com/jenkinsci/subversion-plugin/compare/910139260fbc...05aa7fc9b93c 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27718 
 
 
 
  Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multijob-plugin] (JENKINS-32230) Allow any subjob to be excluded from SCM polling for MultiJob projects

2015-12-30 Thread jclch...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Cheng created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32230 
 
 
 
  Allow any subjob to be excluded from SCM polling for MultiJob projects  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 multijob-plugin 
 
 
 

Created:
 

 30/Dec/15 8:23 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jeff Cheng 
 
 
 
 
 
 
 
 
 
 
If the "Poll subjobs in addition to multijob when polling" option is enabled for the parent MultiJob project, it would be nice to have the option to exclude any subjob from being polled. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [extended-choice-parameter-plugin] (JENKINS-31690) getGroovyBinding NPE

2015-12-30 Thread vi...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Gixed in version 0.56 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31690 
 
 
 
  getGroovyBinding NPE  
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [delivery-pipeline-plugin] (JENKINS-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery

2015-12-30 Thread pat...@diabol.se (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström commented on  JENKINS-30043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Step Jobs are placed after Post Build Action Jobs in delivery  
 
 
 
 
 
 
 
 
 
 
Created a PR with a proposed fix. https://github.com/Diabol/delivery-pipeline-plugin/pull/168 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-27718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Craig Rodrigues Path: src/main/java/hudson/scm/listtagsparameter/ListSubversionTagsParameterValue.java http://jenkins-ci.org/commit/subversion-plugin/e41bc73b66951f21e16dd96220b1b14b027f Log: JENKINS-27718 Override ParameterValue.buildEnvironment() 
ParameterValue.buildEnvVars() was deprecated. This fix is needed for the workflow plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-32199) Created a hidden job, but could not remove it

2015-12-30 Thread oo9...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chan reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Please reconsider this issue. Why would a non-exist job got kicked off by Jenkins?? Note: "list-jobs" doesn't return the non-existed job. 
thanks 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32199 
 
 
 
  Created a hidden job, but could not remove it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anthony Chan 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32251) Branch sync should wait for build to finish before deleting

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32251 
 
 
 
  Branch sync should wait for build to finish before deleting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Possibly related to #25  Original reporter https://github.com/unklphil   Our test suite creates a test database that is normally removed after tests are done, however when the branch is deleted before the tests finish, the branch sync immediately deletes everything and the tests stop. This causes the test databases to not be deleted.A possible solution would be to not delete a branch's job if it is currently building. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32250) Being able to edit project view as a fully dashboard view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32250 
 
 
 
  Being able to edit project view as a fully dashboard view  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/Nodashi Being able to edit project view as a fully dashboard view 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32252) Possible issue with how triggers are started

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32252 
 
 
 
  Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~pascalw] I noticed that when creating projects with this plugin the Github plugin doesn't create webhooks like it normally does on regular projects.I've debugged this issue a bit and noticed that on multi branch projects the Github trigger `start` method is always called with `newInstance = false` whereas on regular projects the it's called with newInstance = true. Looking at the code I think this could possibly originate from [here](https://github.com/mjdetullio/multi-branch-project-plugin/blob/54d7e5ebde04a13469d96b883cb81ce11351164f/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/FreeStyleMultiBranchProject.java#L964) where the start method is indeed called with `newInstance=false`.What I'm confused about however is whether the triggers should be started from the parent project at all or if they should be started on each child project. In any case the behavior of starting triggers seems to be different in multi branch projects vs regular projects. @mjdetullio can you help me understand this issue? If this is an actual issue I would like to fix it but I first want to make sure I fully understand the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

[JIRA] [multi-branch-project-plugin] (JENKINS-32254) Exclude "Merged" git branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32254 
 
 
 
  Exclude "Merged" git branches  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/billieblaze Loving this plugin.  Any way to exclude branches that have already been merged / closed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32253) Want an option to encode slashes in branch names differently

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32253 
 
 
 
  Want an option to encode slashes in branch names differently  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~kazssym] As issue #11 wrote, slashes in branch names are currently stored as %2F on the file system, but some application containers (I use GlassFish) do not like it in a URL. So I request an enhancement to add an option to encode slashes (or other special characters) differently, such as replacing with safe characters like '_' or something like that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32255 
 
 
 
  Multi-branch multi-configuration projects  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~derekdally] Is there a way to define several configurations (common across all branches)?  If not, would it be difficult to implement?Nice job with the plugin so far, it looks like it's going to make things a lot cleaner for this use case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/mrcarlosrendonConsider the following two entries found in the rssAll feed ``` {code: xml } nctnhbaseworker/trunk #19 (stable)tag:hudson.dev.java.net,2015:trunk:192015-12-22T00:02:26Z2015-12-22T00:02:26Z ``` {code}  ``` {code: xml } psclient/trunk #19 (1 test is still failing)tag:hudson.dev.java.net,2015:trunk:192015-12-22T00:04:24Z2015-12-22T00:04:24Z ``` {code} They are for two different projects, but the `` tag for them is identical which breaks RSS feed readers that are expecting each entry to have a unique id as is required by the ATOM specification (http://tools.ietf.org/html/rfc4287#section-4.2.6) that Jenkins uses. I think adding the project name in addition to the branch name in the id field would solve the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32256) Possible Features/Configs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32256 
 
 
 
  Possible Features/Configs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~lwhiteley]Features/Options that could be in future implementations: #  1. Bi-Directional Sync of branches and jobsThis would mean that if a developer deletes a branch then the jenkins job  will be deleted as well. The same would happen if a job is deleted, then the corresponding git branch would be deleted remotely as well. This would be optional based on the workflow of  a team. Suggested options would be:- Deleting branch triggers delete of job (One-Directional)- Deleting job triggers delete of branch (One-Directional)- Bi-Directional Delete  #  2. Delete Stale JobsThis would be the ability to delete/cleanup jobs that are considered `stale` by some logic. This may be if it was last run at a configurable amount of time (Days/Weeks?). #  3. Smart Creation of jobsWith the plugins/tools available, they will recreate a job after it is deleted even if the user did not push to the branch. The plugin should be smart enough to only recreate a job if the user pushed to the branch since the last sync cycle. This would help with not creating jobs that are `stale` but still needed to be picked up at a later date for development/building.***Note:***Features 2 and 3 may need to use the webhook instead of polling to not use up a lot of resources. (May be a good idea to allow folks to choose polling or webhook for all functionality though. Would be interesting). This will ensure only branches with changes are created and built.  #  4. Sub Configs for Each branchThis would mostly be overrides, like always keep this branch so that it is never deleted. Use case would be to keep artifacts etc.Another use case would be to add Build or Post-Build steps to a specific branch somehow for doing deploys as an example. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [multi-branch-project-plugin] (JENKINS-32256) Possible Features/Configs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32256 
 
 
 
  Possible Features/Configs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~lwhiteley] Features/Options that could be in future implementations:# 1. Bi-Directional Sync of branches and jobsThis would mean that if a developer deletes a branch then the jenkins job  will be deleted as well. The same would happen if a job is deleted, then the corresponding git branch would be deleted remotely as well. This would be optional based on the workflow of  a team. Suggested options would be:- Deleting branch triggers delete of job (One-Directional)- Deleting job triggers delete of branch (One-Directional)- Bi-Directional Delete # 2. Delete Stale JobsThis would be the ability to delete/cleanup jobs that are considered `stale` by some logic. This may be if it was last run at a configurable amount of time (Days/Weeks?).# 3. Smart Creation of jobsWith the plugins/tools available, they will recreate a job after it is deleted even if the user did not push to the branch. The plugin should be smart enough to only recreate a job if the user pushed to the branch since the last sync cycle. This would help with not creating jobs that are `stale` but still needed to be picked up at a later date for development/building.***Note:***Features 2 and 3 may need to use the webhook instead of polling to not use up a lot of resources. (May be a good idea to allow folks to choose polling or webhook for all functionality though. Would be interesting). This will ensure only branches with changes are created and built. # 4. Sub Configs for Each branchThis would mostly be overrides, like always keep this branch so that it is never deleted. Use case would be to keep artifacts etc.Another use case would be to add Build or Post-Build steps to a specific branch somehow for doing deploys as an example. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [multi-branch-project-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/mrcarlosrendon Consider the following two entries found in the rssAll feed```xmlnctnhbaseworker/trunk #19 (stable)tag:hudson.dev.java.net,2015:trunk:192015-12-22T00:02:26Z2015-12-22T00:02:26Z``xmlpsclient/trunk #19 (1 test is still failing)tag:hudson.dev.java.net,2015:trunk:192015-12-22T00:04:24Z2015-12-22T00:04:24Z```They are for two different projects, but the `` tag for them is identical which breaks RSS feed readers that are expecting each entry to have a unique id as is required by the ATOM specification (http://tools.ietf.org/html/rfc4287#section-4.2.6) that Jenkins uses. I think adding the project name in addition to the branch name in the id field would solve the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cloudbees-folder-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cloudbees-folder-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Labels:
 
 multibranch nested 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26309) Custom Commit message for git publisher

2015-12-30 Thread bba...@gfg-group.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bob Balli commented on  JENKINS-26309 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Custom Commit message for git publisher  
 
 
 
 
 
 
 
 
 
 
I was looking for same option for the Subversion commit. Specially Subversion merge plugin for rebasing the changes down to upstreaming project. We want to provide custom commits before performing rebase. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32233) Warnings Plugin not Configurable for Branch

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32233 
 
 
 
  Warnings Plugin not Configurable for Branch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~jwernerny] The Warnings Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) is not configurable through the GUI (web interface) for Branches.  When you go to add a console or workspace file log parser, it presents an empty drop down list instead of a list of parsers.A workaround is manually editing template/config.xml. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32234) Use branch-api

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32234 
 
 
 
  Use branch-api  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~jglick] https://github.com/mjdetullio/multi-branch-project-plugin/blob/master/README.md#why-not-use-the-branch-api-pluginIt is 1.0 and there has been a great deal of work on it recently. Used from _Workflow: Multibranch_, _Literate_, and _YAML Project_. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32236) Required tests don't play nicely with multi-branch-project-plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32236 
 
 
 
  Required tests don't play nicely with multi-branch-project-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32235) Git SCM web hook not triggering builds for branches that contain a forward slash '/'

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32235 
 
 
 
  Git SCM web hook not triggering builds for branches that contain a forward slash '/'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/jpeletier Hi,First of all, thank you for this great plug-inI have configured the multi-branch plug-in with my Stash Git repository with the following relevant parameters:* Sync Branches Schedule: H/5 * * * ** [x] Allow anonymous trigger of branch sync* Git* Include Branches  *  (a * wildcard)* Exclude Branches  I have configured Stash Git to trigger Jenkins every time a push is made to the repository, and it works. However, when the branch name contains a forward slash, such as "feature/new-cool-feature", the hook is ignored and the branch is not built. If I click the "Schedule Build", the build is scheduled and runs fine. So it is just the trigger that it is not working.I have read the plug-in has some issues with / in the names, but the issues described don't seem to match what is happening to us. My one and oly problem is the trigger coming from Stash being ignored.Does anybody know of a workaround?Thanks!/jpeletier 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32236) Required tests don't play nicely with multi-branch-project-plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32236 
 
 
 
  Required tests don't play nicely with multi-branch-project-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~nschloe] Reporting build statuses back to GitHub works fine for the multi-branch-project-plugin. We'd like to make use of it for GitHub's protected branches: Here, you require a specific test to pass before you can merge a PR into the protected branch. Which tests need passing is configurable, and with the multi-branch-project-plugin, I'm presented with all branches from the past:  ! [sc2](https://cloud.githubusercontent.com/assets/181628/10700735/175ca14c screenshot - 79c0-11e5-9adf-050d7f647f25 1 .png ) !   This isn't useful as a general configuration option, of course. Unfortunately, with multi-branch-project-plugin there's no general `frontend-dev` target (in the above example) that returns anything useful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32237) Exception when trying to add Build Promotion process

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32237 
 
 
 
  Exception when trying to add Build Promotion process  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/nabheet I am not really sure how I want this use case to work, but I figured that you might care to know that there was an exception. I was using the promoted-builds plugin from https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin. I could a also provide a list of all the plugins, but I think this was the one that cause the exeption.```Error while serving http://0.0.0.0:8090/job/Build_MyCode/configSubmitjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at

[JIRA] [multi-branch-project-plugin] (JENKINS-32239) job naming sould be configurable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32239 
 
 
 
  job naming sould be configurable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~vernyquartara] When creating a new multibranch job, the names of the subjobs are inferred from the repository path.For example, if the repo root is *http://mysvn.com/repo/* and the include branch _expression_ is _branches/*_, then all the subjobs will be named using the prefix _branches/_.This is not always wanted, for example in the case of a multi-project repository layout, such as* http://mysvn.com/repo/branches/branch1/project-name* http://mysvn.com/repo/branches/branch2/project-name* http://mysvn.com/repo/branches/branch3/project-namethe job will have 3 subjobs named _branches/branch1/project-name_, _branches/branch2/project-name_, _branches/branch3/project-name_.__IMHO The user should be able to configure the naming using a configuration option__, like a regular _expression_. For example in the above scenario, using a regex __branches/(.+)/.+__ the subjobs will be called simply _branch1_, _branch2_, _branch3_.This issue looks like an enanchement but I noticed that __subjobs defaults names cause an error into the downstream job that uses the copy-artifact plugin__, (the upstream artifact couldn't be found), so perhaps is more likely a bug.Verny 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

[JIRA] [github-pullrequest-plugin] (JENKINS-32238) Pull Request Branches Single view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32238 
 
 
 
  Pull Request Branches Single view  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~marcellodesales] Hi there,Have you thought about integrating this with the Pull Request Builder for GitHub??? I was thinking if this plugin could set a single branch called "pr" or "pull requests", that would be great to give users the view of the Pull Requests built for the job...https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+pluginBranch: `+refs/pull/*:refs/remotes/origin/pr/*`This is one of the most exciting plugins in a long time!!! Thanks a lot!!!Marcello 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-pullrequest-plugin] (JENKINS-32238) Pull Request Branches Single view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32238 
 
 
 
  Pull Request Branches Single view  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Component/s:
 
 github-pullrequest-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32242) push to scm triggering respective jenkins job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32242 
 
 
 
  push to scm triggering respective jenkins job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/kibotu As a developerwhen I to push to a specific branch on github/gitlab then the scm should trigger the respective jenkins jobso that jenkins actually builds the branch with changes.I tried JENKINS_URL/job/JOB_NAME/branch/BRANCH_NAME/build which only builds the scm default branch regardless to what branch has been pushedi tried JENKINS_URL/git/notifyCommit?url="" />how can i achieve this? thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32240) No test results in Maven multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32240 
 
 
 
  No test results in Maven multi-branch project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~dcendents] I created a Maven multi-branch project and I noticed that many of my branch builds did not record the junit test results, which seemed random. One build would work and the next would not.I found the problem: when a maven project branch builds "unhindered" then it works normally, however if the "master" project scans for branches  and sync the config to the branch projects while a build is in progress, then the junit reporter will not work and it will record 0 junit tests. I find this alarming as the build will pass even if one of my tests fails (should be unstable).It does not sound safe to systematically push (sync) the configuration to existing branches every time the master project scans the SCM. A perfect solution would be to delay the scan or the sync until all branch projects have finished building. An alternative solution could be to stop syncing the job config every time the project scans for branches and only do it when the master project configuration is modified, which comes down to the user to make sure he is not modifying the configuration while a branch project is building.Great project by the way, I've been using the lterate plugin for a while but I like that your plugin lets me create "real" jenkins projects with all the available options. Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are

[JIRA] [multi-branch-project-plugin] (JENKINS-32241) Job does not resolve {GIT_BRANCH} token on first job run. Need a branch env name for build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32241 
 
 
 
  Job does not resolve {GIT_BRANCH} token on first job run. Need a branch env name for build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~scaytrase] When branch job just created it does not resolve token `${GIT_BRANCH}` and (i.e. `origin/release/release_name`) and leaves it as `${GIT_BRANCH}` plaintext.I'm using tokens within template to separate job workspaces via custom workspace option (i.e. `\var\www\${GIT_BRANCH}`) to deploy branches on stagin env.As it leaves token plaintexted it performs first build in `/var/www/${GIT_BRANCH}` directory. But after git clone is finished it the `${GIT_BRANCH}` token is being expanded correctly and phing starts to use it to lookup build plan. And it expands to `/var/www/origin/release/release_name` which is correct but mismatched with the actual clone path.I really understand that problem is that workspace is resolved before cloning and it is not really the bug or problem of plugin. But I need the way to get fully qualified branch name (`origin/release/release_name`) as a token instead of ${GIT_BRANCH}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32243) Parameterization of "Restrict where this project can be run"

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32243 
 
 
 
  Parameterization of "Restrict where this project can be run"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~misery] We have some jobs than can be merged into one "multi branch" job. The only reason is that they need to run on another slave if it is branch "A" or branch "B". As this cannot be evaluated if the job started it needs to be "hardcoded" to the job configuration.Idea:Write in "global" job in "Restrict where this project can be run" field for example "Windows7_\$SUBJOB_BRANCH" and it will be "Windows7_stable" and "Windows7_master" in the sub projects. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32244) Environment variable for current branch

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32244 
 
 
 
  Environment variable for current branch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~misery] I need to know the current branch in generated job (see conditional step) but there is no $BRANCH variable or something like this I can use. $JOB_NAME does not contain only "branch name".Please add a $CURRENT_BRANCH or something like this.As a work-around I used Envinject plugin with the following groovy script.```def jobName = currentJob.getName()return [BRANCH: "${jobName}"]```It's weird that currentJob.getName() works instead of $JOB_NAME. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32245) Git publisher support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32245 
 
 
 
  Git publisher support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/kubajanda I was trying to configure git publisher as post-build action, but I can't as there is no option to set repository name under SCM and then specify it as Target remote name in git publisher. Also the git publisher complains about Project not currently configured to use Git; cannot check remote repository.Would it be possible to add git publisher support? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-32252) Possible issue with how triggers are started

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32252 
 
 
 
  Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~pascalw]I noticed that when creating projects with this plugin the Github plugin doesn't create webhooks like it normally does on regular projects.I've debugged this issue a bit and noticed that on multi branch projects the Github trigger `start` method is always called with `newInstance = false` whereas on regular projects the it's called with newInstance = true. Looking at the code I think this could possibly originate from  [here]( https://github.com/mjdetullio/multi-branch-project-plugin/blob/54d7e5ebde04a13469d96b883cb81ce11351164f/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/FreeStyleMultiBranchProject.java#L964 )  where the start method is indeed called with  `  {{ newInstance=false ` }} .What I'm confused about however is whether the triggers should be started from the parent project at all or if they should be started on each child project. In any case the behavior of starting triggers seems to be different in multi branch projects vs regular projects.  @  [~ mjdetullio ]  can you help me understand this issue? If this is an actual issue I would like to fix it but I first want to make sure I fully understand the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email

[JIRA] [github-plugin] (JENKINS-32252) Possible issue with how triggers are started

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32252 
 
 
 
  Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Component/s:
 
 github-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32249) Incorrect link inside mutlijob phase inside a view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32249 
 
 
 
  Incorrect link inside mutlijob phase inside a view  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~scaytrase]If one branch of multibranch project is used as a single phase of multijob project, multijob dashboard display incorrect link (and possibly name?) to multibranch subproject.I.e. given we have a view  `  {{ TestView ` }}  and Multibranch project branch  `  {{ MBTest > master ` }}  if we add this as a phase job to multijob project  `  {{ Pipeline ` }} , we will se a link to  `  {{ TestView/branch/master ` }}  instead of correct link to  `  {{ MBTest/branch/master ` }}  or so 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32248) Subversion tagging doesnt work with this plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32248 
 
 
 
  Subversion tagging doesnt work with this plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~mcastilla]When trying to tag an execution it throws this error: ``` {code} Tagging https://subversion.assembla.com/svn/tinsa-cl-sisgen/branches/fix-948 (rev.1534) to https://subversion.assembla.com/svn/tinsa-cl-sisgen/tags/branches/testERROR: Failed to tagorg.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:759) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryRoot(DAVRepository.java:127) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.copyReposToRepos(SVNCopyDriver.java:194) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.setupCopy(SVNCopyDriver.java:627) at org.tmatesoft.svn.core.internal.wc16.SVNCopyClient16.doCopy(SVNCopyClient16.java:440) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:65) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:23) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc2.SvnRemoteCopy.run(SvnRemoteCopy.java:227) at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:581) at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:307) at hudson.model.TaskThread.run(TaskThread.java:128)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:689) ... 19 moreCompleted ``` {code}

[JIRA] [multi-branch-project-plugin] (JENKINS-32246) Is it absolutely necessary to keep full .git repository in the sub-projects?

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32246 
 
 
 
  Is it absolutely necessary to keep full .git repository in the sub-projects?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~ivananishchuk]Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic.At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir. [ More info on SO ]( : http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32247) "Trigger builds remotely" hint shows wrong URL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32247 
 
 
 
  "Trigger builds remotely" hint shows wrong URL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 via @nszceta**"template"** in: ` {{ JENKINS_URL/job/JOB_NAME/branch/template/build?token=TOKEN_NAME ` }} should be replaced with **"BRANCH_NAME"** ` {{ JENKINS_URL/job/JOB_NAME/branch/BRANCH_NAME/build?token=TOKEN_NAME ` }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32244) Environment variable for current branch

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32244 
 
 
 
  Environment variable for current branch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~misery]I need to know the current branch in generated job (see conditional step) but there is no $BRANCH variable or something like this I can use. $JOB_NAME does not contain only "branch name".Please add a $CURRENT_BRANCH or something like this.As a work-around I used Envinject plugin with the following groovy script. ``` {code} def jobName = currentJob.getName()return [BRANCH: "${jobName}"] ``` {code}   It's weird that currentJob.getName() works instead of $JOB_NAME. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32237) Exception when trying to add Build Promotion process

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32237 
 
 
 
  Exception when trying to add Build Promotion process  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/nabheetI am not really sure how I want this use case to work, but I figured that you might care to know that there was an exception. I was using the promoted-builds plugin from https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin. I could a also provide a list of all the plugins, but I think this was the one that cause the exeption. ``` {code} Error while serving http://0.0.0.0:8090/job/Build_MyCode/configSubmitjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at

[JIRA] [multi-branch-project-plugin] (JENKINS-32237) Exception when trying to add Build Promotion process

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32237 
 
 
 
  Exception when trying to add Build Promotion process  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Component/s:
 
 promoted-builds-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32239) job naming sould be configurable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32239 
 
 
 
  job naming sould be configurable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~vernyquartara]When creating a new multibranch job, the names of the subjobs are inferred from the repository path.For example, if the repo root is *http://mysvn.com/repo/* and the include branch _expression_ is _branches/*_, then all the subjobs will be named using the prefix _branches/_.This is not always wanted, for example in the case of a multi-project repository layout, such as* http://mysvn.com/repo/branches/branch1/project-name* http://mysvn.com/repo/branches/branch2/project-name* http://mysvn.com/repo/branches/branch3/project-namethe job will have 3 subjobs named _branches/branch1/project-name_, _branches/branch2/project-name_, _branches/branch3/project-name_.__IMHO The user should be able to configure the naming using a configuration option__, like a regular _expression_. For example in the above scenario, using a regex __branches/(.+)/.+__ the subjobs will be called simply _branch1_, _branch2_, _branch3_.This issue looks like an enanchement but I noticed that __subjobs defaults names cause an error into the downstream job that uses the copy-artifact plugin__, (the upstream artifact couldn't be found), so perhaps is more likely a bug.Verny 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

[JIRA] [multi-branch-project-plugin] (JENKINS-32241) Job does not resolve {GIT_BRANCH} token on first job run. Need a branch env name for build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32241 
 
 
 
  Job does not resolve {GIT_BRANCH} token on first job run. Need a branch env name for build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~scaytrase]When branch job just created it does not resolve token `${GIT_BRANCH}` and (i.e.  `  {{ origin/release/release_name ` }} ) and leaves it as `${GIT_BRANCH}` plaintext.I'm using tokens within template to separate job workspaces via custom workspace option (i.e. `\var\www\${GIT_BRANCH}`) to deploy branches on stagin env.As it leaves token plaintexted it performs first build in `/var/www/${GIT_BRANCH}` directory. But after git clone is finished it the `${GIT_BRANCH}` token is being expanded correctly and phing starts to use it to lookup build plan. And it expands to  `  {{ /var/www/origin/release/release_name ` }}  which is correct but mismatched with the actual clone path.I really understand that problem is that workspace is resolved before cloning and it is not really the bug or problem of plugin. But I need the way to get fully qualified branch name ( ` {{ origin/release/release_name ` }} ) as a token instead of ${GIT_BRANCH}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32239) job naming sould be configurable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32239 
 
 
 
  job naming sould be configurable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~vernyquartara]When creating a new multibranch job, the names of the subjobs are inferred from the repository path.For example, if the repo root is *http://mysvn.com/repo/* and the include branch _expression_ is _branches/*_, then all the subjobs will be named using the prefix _branches/_.This is not always wanted, for example in the case of a multi-project repository layout, such as* http://mysvn.com/repo/branches/branch1/project-name* http://mysvn.com/repo/branches/branch2/project-name* http://mysvn.com/repo/branches/branch3/project-namethe job will have 3 subjobs named _branches/branch1/project-name_, _branches/branch2/project-name_, _branches/branch3/project-name_. __IMHO _IMHO  The user should be able to configure the naming using a configuration  option__  option_  , like a regular _expression_. For example in the above scenario, using a regex __branches/(.+)/.+__ the subjobs will be called simply _branch1_, _branch2_, _branch3_.This issue looks like an enanchement but I noticed that __subjobs defaults names cause an error into the downstream job that uses the copy-artifact plugin__, (the upstream artifact couldn't be found), so perhaps is more likely a bug.Verny 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send

[JIRA] [cloudbees-folder-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter https://github.com/mrcarlosrendonConsider the following two entries found in the rssAll feed{code:xml}nctnhbaseworker/trunk #19 (stable)tag:hudson.dev.java.net,2015:trunk:192015-12-22T00:02:26Z2015-12-22T00:02:26Z{code}{code:xml}psclient/trunk #19 (1 test is still failing)tag:hudson.dev.java.net,2015:trunk:192015-12-22T00:04:24Z2015-12-22T00:04:24Z{code}They are for two different projects, but the  ```  {{  ``` }}  tag for them is identical which breaks RSS feed readers that are expecting each entry to have a unique id as is required by the ATOM specification (http://tools.ietf.org/html/rfc4287#section-4.2.6) that Jenkins uses. I think adding the project name in addition to the branch name in the id field would solve the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-32199) Created a hidden job, but could not remove it

2015-12-30 Thread oo9...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chan commented on  JENKINS-32199 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Created a hidden job, but could not remove it  
 
 
 
 
 
 
 
 
 
 
There is only one Jenkins process running on the host. I suspect something was corrupted when I updated the job schedule. If that is the case, I will consider it is a bug because it shouldn't allow any corruption. Anyway, I will look for the answer from the #jenkins chanel. 
thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [packaging] (JENKINS-31583) windows installer ships with an insanley out of date JRE

2015-12-30 Thread jr...@glynlyon.com (JIRA)

Title: Message Title

Joel Reed commented on JENKINS-31583

Re: windows installer ships with an insanley out of date JRE

I wanted to add a "seconded" to this issue. I've been rapidly increasing the use of Jenkins in my largely Windows environment for the last 18 months or so and this has recently bubbled up as a "potential issue".
I have a single Jenkins master and a half dozen slaves, all Windows 2012R2. I deploy my slaves with the "Scheduled Task - At Startup" method. The slave.jar is kept in sync with the copy from master via external configuration management. The slaves jre is also deployed and maintained via external configuration management.
I have maintained the latest version of Jenkins via the web gui update functionality. What I have come to realize is that this is only maintaining the updated jenkins.war and not having any impact on the included jre which is the version that came with the msi I originally installed with, a year or so ago. However the latest and greatest msi which packages the jenkins.war (which I'm currently running) also packages the latest jre (1.8.0_66 vs my "original" 1.8.0_20).
Is there a "supported" way of maintaining this included jre? Can I rerun the latest .msi, if I do so what would I need to capture and potentially restore for job, plugin, history, and configuration preservation?
My short term workaround appears to be updating the jenkins.xml and utilizing a external jre maintained in similar fashion to my slaves. Is there documented guidance on which jre is currently supported for masters (as well as slaves)?
I think some wiki documentation might be the resolution here. What strategies exist and are supported. Can the msi be updated to provide a choice of included or external jre at the time of install? Can the msi be used to safely update an existing (but updated install)? Those kinds of things.
Thanks for a great product.

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30089 
 
 
 
  new config history created on each multibranch build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Component/s:
 
 multi-branch-project-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multi-branch-project-plugin] (JENKINS-32238) Pull Request Branches Single view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32238 
 
 
 
  Pull Request Branches Single view  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Hi there, 
Have you thought about integrating this with the Pull Request Builder for GitHub??? I was thinking if this plugin could set a single branch called "pr" or "pull requests", that would be great to give users the view of the Pull Requests built for the job... 
https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin Branch: `+refs/pull/:refs/remotes/origin/pr/` 
This is one of the most exciting plugins in a long time!!! Thanks a lot!!! 
Marcello 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32237) Exception when trying to add Build Promotion process

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32237 
 
 
 
  Exception when trying to add Build Promotion process  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
I am not really sure how I want this use case to work, but I figured that you might care to know that there was an exception. I was using the promoted-builds plugin from https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin. I could a also provide a list of all the plugins, but I think this was the one that cause the exeption. 
``` Error while serving http://0.0.0.0:8090/job/Build_MyCode/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at

[JIRA] [multi-branch-project-plugin] (JENKINS-32235) Git SCM web hook not triggering builds for branches that contain a forward slash '/'

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32235 
 
 
 
  Git SCM web hook not triggering builds for branches that contain a forward slash '/'  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Hi, 
First of all, thank you for this great plug-in 
I have configured the multi-branch plug-in with my Stash Git repository with the following relevant parameters: 
 

Sync Branches Schedule: H/5 * * * *
 

[x] Allow anonymous trigger of branch sync
 

Git
 

Include Branches * (a * wildcard)
 

Exclude Branches 
 
 
I have configured Stash Git to trigger Jenkins every time a push is made to the repository, and it works. However, when the branch name

[JIRA] [multi-branch-project-plugin] (JENKINS-32250) Being able to edit project view as a fully dashboard view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32250 
 
 
 
  Being able to edit project view as a fully dashboard view  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Being able to edit project view as a fully dashboard view 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [multi-branch-project-plugin] (JENKINS-32251) Branch sync should wait for build to finish before deleting

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32251 
 
 
 
  Branch sync should wait for build to finish before deleting  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Possibly related to #25  
Our test suite creates a test database that is normally removed after tests are done, however when the branch is deleted before the tests finish, the branch sync immediately deletes everything and the tests stop. This causes the test databases to not be deleted. 
A possible solution would be to not delete a branch's job if it is currently building. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32249) Incorrect link inside mutlijob phase inside a view

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32249 
 
 
 
  Incorrect link inside mutlijob phase inside a view  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
If one branch of multibranch project is used as a single phase of multijob project, multijob dashboard display incorrect link (and possibly name?) to multibranch subproject. 
I.e. given we have a view `TestView` and Multibranch project branch `MBTest > master` if we add this as a phase job to multijob project `Pipeline`, we will se a link to `TestView/branch/master` instead of correct link to `MBTest/branch/master` or so 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32246) Is it absolutely necessary to keep full .git repository in the sub-projects?

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32246 
 
 
 
  Is it absolutely necessary to keep full .git repository in the sub-projects?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic. 
At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir. 
[More info on SO](http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32236) Required tests don't play nicely with multi-branch-project-plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32236 
 
 
 
  Required tests don't play nicely with multi-branch-project-plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Reporting build statuses back to GitHub works fine for the multi-branch-project-plugin. We'd like to make use of it for GitHub's protected branches: Here, you require a specific test to pass before you can merge a PR into the protected branch. Which tests need passing is configurable, and with the multi-branch-project-plugin, I'm presented with all branches from the past: ![sc2](https://cloud.githubusercontent.com/assets/181628/10700735/175ca14c-79c0-11e5-9adf-050d7f647f25.png) This isn't useful as a general configuration option, of course. Unfortunately, with multi-branch-project-plugin there's no general `frontend-dev` target (in the above example) that returns anything useful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32255 
 
 
 
  Multi-branch multi-configuration projects  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:39 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Is there a way to define several configurations (common across all branches)? If not, would it be difficult to implement? 
Nice job with the plugin so far, it looks like it's going to make things a lot cleaner for this use case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32244) Environment variable for current branch

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32244 
 
 
 
  Environment variable for current branch  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
I need to know the current branch in generated job (see conditional step) but there is no $BRANCH variable or something like this I can use. $JOB_NAME does not contain only "branch name". 
Please add a $CURRENT_BRANCH or something like this. As a work-around I used Envinject plugin with the following groovy script. 
``` def jobName = currentJob.getName() return [BRANCH: "$ {jobName} 
"] ``` It's weird that currentJob.getName() works instead of $JOB_NAME. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32242) push to scm triggering respective jenkins job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32242 
 
 
 
  push to scm triggering respective jenkins job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
As a developer when I to push to a specific branch on github/gitlab  then the scm should trigger the respective jenkins job so that jenkins actually builds the branch with changes. 
I tried JENKINS_URL/job/JOB_NAME/branch/BRANCH_NAME/build which only builds the scm default branch regardless to what branch has been pushed 
i tried JENKINS_URL/git/notifyCommit?url="" where however gitlab didn't trigger any build whatsoever 
how can i achieve this? thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32245) Git publisher support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32245 
 
 
 
  Git publisher support  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
I was trying to configure git publisher as post-build action, but I can't as there is no option to set repository name under SCM and then specify it as Target remote name in git publisher.  
Also the git publisher complains about Project not currently configured to use Git; cannot check remote repository. 
Would it be possible to add git publisher support? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32234) Use branch-api

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32234 
 
 
 
  Use branch-api  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
https://github.com/mjdetullio/multi-branch-project-plugin/blob/master/README.md#why-not-use-the-branch-api-plugin 
It is 1.0 and there has been a great deal of work on it recently. Used from Workflow: Multibranch, Literate, and YAML Project. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32243) Parameterization of "Restrict where this project can be run"

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32243 
 
 
 
  Parameterization of "Restrict where this project can be run"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
We have some jobs than can be merged into one "multi branch" job. The only reason is that they need to run on another slave if it is branch "A" or branch "B". As this cannot be evaluated if the job started it needs to be "hardcoded" to the job configuration. 
Idea: Write in "global" job in "Restrict where this project can be run" field for example "Windows7_\$SUBJOB_BRANCH" and it will be "Windows7_stable" and "Windows7_master" in the sub projects. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32252) Possible issue with how triggers are started

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32252 
 
 
 
  Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:39 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
I noticed that when creating projects with this plugin the Github plugin doesn't create webhooks like it normally does on regular projects. 
I've debugged this issue a bit and noticed that on multi branch projects the Github trigger `start` method is always called with `newInstance = false` whereas on regular projects the it's called with newInstance = true. Looking at the code I think this could possibly originate from [here](https://github.com/mjdetullio/multi-branch-project-plugin/blob/54d7e5ebde04a13469d96b883cb81ce11351164f/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/FreeStyleMultiBranchProject.java#L964) where the start method is indeed called with `newInstance=false`. 
What I'm confused about however is whether the triggers should be started from the parent project at all or if they should be started on each child project. In any case the behavior of starting triggers seems to be different in multi branch projects vs regular projects. @mjdetullio can you help me understand this issue? If this is an actual issue I would like to fix it but I first want to make sure I fully understand the issue.

[JIRA] [multi-branch-project-plugin] (JENKINS-32240) No test results in Maven multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32240 
 
 
 
  No test results in Maven multi-branch project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
I created a Maven multi-branch project and I noticed that many of my branch builds did not record the junit test results, which seemed random. One build would work and the next would not. 
I found the problem: when a maven project branch builds "unhindered" then it works normally, however if the "master" project scans for branches and sync the config to the branch projects while a build is in progress, then the junit reporter will not work and it will record 0 junit tests. I find this alarming as the build will pass even if one of my tests fails (should be unstable). 
It does not sound safe to systematically push (sync) the configuration to existing branches every time the master project scans the SCM. A perfect solution would be to delay the scan or the sync until all branch projects have finished building. An alternative solution could be to stop syncing the job config every time the project scans for branches and only do it when the master project configuration is modified, which comes down to the user to make sure he is not modifying the configuration while a branch project is building. 
Great project by the way, I've been using the lterate plugin for a while but I like that your plugin lets me create "real" jenkins projects with all the available options.

[JIRA] [multi-branch-project-plugin] (JENKINS-32254) Exclude "Merged" git branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32254 
 
 
 
  Exclude "Merged" git branches  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:39 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Loving this plugin. Any way to exclude branches that have already been merged / closed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [multi-branch-project-plugin] (JENKINS-32239) job naming sould be configurable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32239 
 
 
 
  job naming sould be configurable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
When creating a new multibranch job, the names of the subjobs are inferred from the repository path. For example, if the repo root is http://mysvn.com/repo/* and the include branch _expression_ is branches/, then all the subjobs will be named using the prefix branches/. 
This is not always wanted, for example in the case of a multi-project repository layout, such as 
 

http://mysvn.com/repo/branches/branch1/project-name
 

http://mysvn.com/repo/branches/branch2/project-name
 

http://mysvn.com/repo/branches/branch3/project-name
 
 
the job will have 3 subjobs named branches/branch1/project-name, branches/branch2/project-name, branches/branch3/project-name. _IMHO The user should be able to configure the naming using a configuration option, like a regular _expression_. For example in the above scenario, using a regex __branches/(.

[JIRA] [multi-branch-project-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Consider the following two entries found in the rssAll feed 
```xml  nctnhbaseworker/trunk #19 (stable)  tag:hudson.dev.java.net,2015:trunk:19 2015-12-22T00:02:26Z 2015-12-22T00:02:26Z  ``` 
```xml  psclient/trunk #19 (1 test is still failing)  tag:hudson.dev.java.net,2015:trunk:19 2015-12-22T00:04:24Z 2015-12-22T00:04:24Z  ``` 
They are for two different projects, but the `` tag for them is identical which breaks RSS feed readers that are expecting each entry to have a unique id as is required by the ATOM specification (http://tools.ietf.org/html/rfc4287#section-4.2.6) that Jenkins uses.  
I think adding the project name in addition to the branch name in the id field would solve the issue.

[JIRA] [multi-branch-project-plugin] (JENKINS-32247) "Trigger builds remotely" hint shows wrong URL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32247 
 
 
 
  "Trigger builds remotely" hint shows wrong URL  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
via @nszceta 
*"template"* in: `JENKINS_URL/job/JOB_NAME/branch/template/build?token=TOKEN_NAME` 
should be replaced with *"BRANCH_NAME"* `JENKINS_URL/job/JOB_NAME/branch/BRANCH_NAME/build?token=TOKEN_NAME` 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32248) Subversion tagging doesnt work with this plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32248 
 
 
 
  Subversion tagging doesnt work with this plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
When trying to tag an execution it throws this error: 
``` Tagging https://subversion.assembla.com/svn/tinsa-cl-sisgen/branches/fix-948 (rev.1534) to https://subversion.assembla.com/svn/tinsa-cl-sisgen/tags/branches/test ERROR: Failed to tag org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:759) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032) at

[JIRA] [multi-branch-project-plugin] (JENKINS-32256) Possible Features/Configs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32256 
 
 
 
  Possible Features/Configs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:39 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
Features/Options that could be in future implementations: 
 
 
 
 
 
 
 
 
 

1. Bi-Directional Sync of branches and jobs This would mean that if a developer deletes a branch then the jenkins job will be deleted as well. The same would happen if a job is deleted, then the corresponding git branch would be deleted remotely as well. This would be optional based on the workflow of a team.

[JIRA] [multi-branch-project-plugin] (JENKINS-32253) Want an option to encode slashes in branch names differently

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32253 
 
 
 
  Want an option to encode slashes in branch names differently  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:39 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
As issue #11 wrote, slashes in branch names are currently stored as %2F on the file system, but some application containers (I use GlassFish) do not like it in a URL. So I request an enhancement to add an option to encode slashes (or other special characters) differently, such as replacing with safe characters like '_' or something like that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32233) Warnings Plugin not Configurable for Branch

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32233 
 
 
 
  Warnings Plugin not Configurable for Branch  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 30/Dec/15 11:38 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
The Warnings Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) is not configurable through the GUI (web interface) for Branches. When you go to add a console or workspace file log parser, it presents an empty drop down list instead of a list of parsers. 
A workaround is manually editing template/config.xml. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [multi-branch-project-plugin] (JENKINS-32241) Job does not resolve {GIT_BRANCH} token on first job run. Need a branch env name for build