[JIRA] [startup-trigger-plugin] (JENKINS-32659) Cannot start a job located in a Folder

2016-01-27 Thread geoffroy.jabou...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoffroy Jabouley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32659 
 
 
 
  Cannot start a job located in a Folder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 ashlux 
 
 
 

Components:
 

 startup-trigger-plugin 
 
 
 

Created:
 

 27/Jan/16 10:16 PM 
 
 
 

Environment:
 

 jenkins lts 1.596.3  startup-trigger-plugin 2.4 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Geoffroy Jabouley 
 
 
 
 
 
 
 
 
 
 
During Jenkins boot, if a job located in a Folder (Folder plugin) is configured to be executed, the startup-trigger-plugin does not "see" it, so nothing is executed. 
Would be glad to do the PR, if somebody can point me to some resources to support Folder plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
  

[JIRA] [tfs-plugin] (JENKINS-30703) Team System Web Access URL not saved

2016-01-27 Thread manf...@simpligility.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manfred Moser closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
PR with fixed merged. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30703 
 
 
 
  Team System Web Access URL not saved  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manfred Moser 
 
 
 

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] [core] (JENKINS-32660) Slave monitor for JNLP slaves using Launcher version lower than master

2016-01-27 Thread ow...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32660 
 
 
 
  Slave monitor for JNLP slaves using Launcher version lower than master  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Owen Wood 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 27/Jan/16 10:58 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Owen Wood 
 
 
 
 
 
 
 
 
 
 
Plugin feature. 
Requires new plugin to be created. See JENKINS-26466 and https://groups.google.com/forum/#!topic/jenkinsci-dev/WT8VLf5lZx4 for context. 
Add an `AdministrativeMonitor` that warns when slaves using launcher version lower than master are detected. Should only apply to JNLP slaves (TBC). 
Currently marking component as `core` while we wait for the new plugin to be created 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-32660) Slave monitor for JNLP slaves using Launcher version lower than master

2016-01-27 Thread ow...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood edited a comment on  JENKINS-32660 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slave monitor for JNLP slaves using Launcher version lower than master  
 
 
 
 
 
 
 
 
 
 Here is an example using core. This logic should be able to be mostly salvaged for new plugin:* [SlaveVersionMonitor ]( | https://github.com/Evildethow/jenkins/blob/feature/slave-version-monitor/core/src/main/java/jenkins/slaves/SlaveVersionMonitor.java ) ] * [SlaveVersionMonitorTest ]( | https://github.com/Evildethow/jenkins/blob/feature/slave-version-monitor/core/src/test/java/jenkins/slaves/SlaveVersionMonitorTest.java ) ] * [message ]( | https://github.com/Evildethow/jenkins/blob/feature/slave-version-monitor/core/src/main/resources/jenkins/slaves/SlaveVersionMonitor/message.jelly ) ] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-29156) Add the "Release Notes" functionality in TFS Plugin

2016-01-27 Thread rodrigolo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rodrigolopes assigned an issue to redsolo 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29156 
 
 
 
  Add the "Release Notes" functionality in TFS Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 rodrigolopes 
 
 
 

Assignee:
 
 rodrigolopes redsolo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-29310) Memory leak in progressive log

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-29310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Memory leak in progressive log  
 
 
 
 
 
 
 
 
 
 
So I'm probably out of my depth here but thought I'd try to understand what's happening. How are we not writing everything? I'm not clear on what the difference, in practice, is between what's being done in the completed case and what's being done otherwise... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26657) File context menu missing when installing Slave under windows with jnlp

2016-01-27 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-26657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File context menu missing when installing Slave under windows with jnlp  
 
 
 
 
 
 
 
 
 
 
If you check your logs, there should be errors looking a lot like this: 

1) Error injecting constructor, java.io.IOException: javax.crypto.BadPaddingException: Given final block not properly padded at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.(InstanceIdentity.java:38) while locating org.jenkinsci.main.modules.instance_identity.InstanceIdentity for field at org.jenkinsci.modules.upstart_slave_installer.SlaveInstallerFactoryImpl.id(SlaveInstallerFactoryImpl.java:23)
 
If that's the case, delete the files $JENKINS_HOME/identity.key.enc and $JENKINS_HOME/secrets/org.jenkinsci.main.modules.instance_identity.InstanceIdentity.KEY (and by "delete" I mean "move to a backup directory") and restart Jenkins.  
Please report whether that was the problem, and whether the proposed solution worked. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-pipeline-plugin] (JENKINS-32422) Job without poller triggering on SCM

2016-01-27 Thread abho...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Hobbs commented on  JENKINS-32422 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job without poller triggering on SCM  
 
 
 
 
 
 
 
 
 
 
Dan, I'm not able to get the failed poller job anymore as it was nuked by my job_dsl generation when I finished the feature branch. But here are the two triggered jobs, OK and FAIL states. I hope thats enough. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition

2016-01-27 Thread bc.fis...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brent Fisher commented on  JENKINS-28178 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to disable sandbox in CpsScmFlowDefinition  
 
 
 
 
 
 
 
 
 
 
FWIW, we are running into the same multibranch RejectedAccessExceptions from simple string manipulation. I almost think it could be useful to have the possibility of a whitelist extension file. I.e. methods that I feel are safe for my own Jenkins instance. And perhaps a way to mark which branches require sandboxing, or a way to not sandbox a pull request, if the script hasn't changed? Its pretty tricky, as you say. You mentioned that this is a unique issue. Is there already logged a ticket for this multibranch situation? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [script-security-plugin] (JENKINS-32661) workflow scripts can't use String.substring(int)

2016-01-27 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32661 
 
 
 
  workflow scripts can't use String.substring(int)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 

Priority:
 
 Major Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [svn-revert-plugin] (JENKINS-32308) NoSuchMethodError: hudson.scm.SubversionSCM.getLocations

2016-01-27 Thread anthony.mastr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Mastrean commented on  JENKINS-32308 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NoSuchMethodError: hudson.scm.SubversionSCM.getLocations  
 
 
 
 
 
 
 
 
 
 
Yikes, it is not trivial to upgrade the dependencies and jenkins-core version. So much has changed with the various APIs. I'm currently stuck on this HudsonTestCase vs. JenkinsRule nonsense. 
fork: https://github.com/AnthonyMastrean/svn-revert-plugin/ build: ttps://travis-ci.org/AnthonyMastrean/svn-revert-plugin docs: https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test#UnitTest-HudsonTestCase%28JUnit3%29 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-29156) Add the "Release Notes" functionality in TFS Plugin

2016-01-27 Thread manf...@simpligility.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manfred Moser commented on  JENKINS-29156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the "Release Notes" functionality in TFS Plugin  
 
 
 
 
 
 
 
 
 
 
Could you rebase to the latest master and test it and leave details about all that in the PR or here?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition

2016-01-27 Thread bc.fis...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brent Fisher edited a comment on  JENKINS-28178 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to disable sandbox in CpsScmFlowDefinition  
 
 
 
 
 
 
 
 
 
 FWIW, we are running into the same multibranch RejectedAccessExceptions from simple string manipulation. org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int   I almost think it could be useful to have the possibility of a whitelist extension file.  I.e. methods that I feel are safe for my own Jenkins instance.And perhaps a way to mark which branches require sandboxing, or a way to not sandbox a pull request, if the script hasn't changed?  Its pretty tricky, as you say.You mentioned that this is a unique issue.  Is there already logged a ticket for this multibranch situation? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32662) Unable to use versions with custom tool

2016-01-27 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32662 
 
 
 
  Unable to use versions with custom tool  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 customtools-plugin 
 
 
 

Created:
 

 28/Jan/16 12:46 AM 
 
 
 

Environment:
 

 Jenkins 1.646  Custom Tools Plugin 0.4.4 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Joshua Spence 
 
 
 
 
 
 
 
 
 
 
I am unable to use versioning for a custom tool. 
``` javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class com.cloudbees.jenkins.plugins.customtools.CustomTool from {"name":"phpenv","exportedPaths":"phpenv/bin,phpenv/shims","home":"","additionalVariables":"","toolVersion":{"versionsListSource":{"name":"PHP_VERSION","description":"The PHP version to use.","parameterGroup":{"value":"0","type":"PT_SINGLE_SELECT","visibleItemCount":"5","multiSelectDelimiter":",","quoteValue":false,"propertySource": {"value":"0","propertyValue":"5.3.29"} 
,"defaultPropertySource":{"value":"0","defaultPropertyValue":"5.3.29","properties":{"stapler-class-bag":"true","hudson-tools-InstallSourceProperty":{"installers":{"label":"","command":"export PHPENV_ROOT=$(pwd)/phpenv\nexport PATH=\"$PATH:$(pwd)/phpenv/bin\"\n\nif test -d $PHPENV_ROOT; then\n $PHPENV_ROOT/bin/phpenv update\nelse\n (curl -L http://git.io/phpenv-installer | bash)\nfi\n\nif ! test -d $PHPENV_ROOT/shims; 

[JIRA] [tfs-plugin] (JENKINS-29156) Add the "Release Notes" functionality in TFS Plugin

2016-01-27 Thread rodrigolo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rodrigolopes commented on  JENKINS-29156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the "Release Notes" functionality in TFS Plugin  
 
 
 
 
 
 
 
 
 
 
I submitted a pull request for this long ago, but I haven't heard anything back since then (https://github.com/jenkinsci/tfs-plugin/pull/40) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32662) Unable to use versions with custom tool

2016-01-27 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32662 
 
 
 
  Unable to use versions with custom tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joshua Spence 
 
 
 

Attachment:
 
 FireShot Capture 215 - Configure System [Jenkins] - https___ci.freelancer.com_configure.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] [tfs-plugin] (JENKINS-30443) Creating label no longer support build parameters

2016-01-27 Thread manf...@simpligility.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manfred Moser assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30443 
 
 
 
  Creating label no longer support build parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manfred Moser 
 
 
 

Assignee:
 
 Manfred Moser 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [script-security-plugin] (JENKINS-32661) workflow scripts can't use String.substring(int)

2016-01-27 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32661 
 
 
 
  workflow scripts can't use String.substring(int)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 script-security-plugin 
 
 
 

Created:
 

 28/Jan/16 12:31 AM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 
1.609.1, wf 1.8, secript-scurity 1.14 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int int 
same for gstring. 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.codehaus.groovy.runtime.GStringImpl substring java.lang.Integer java.lang.Integer) 
 
 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [tfs-plugin] (JENKINS-24593) Need a way to exclude commits done by the build itself from triggering another build

2016-01-27 Thread manf...@simpligility.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manfred Moser commented on  JENKINS-24593 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Need a way to exclude commits done by the build itself from triggering another build  
 
 
 
 
 
 
 
 
 
 
sandy thomas are you working on this issue or should we unassign it from you?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-26261) Unable to create the label in TFS using Jenkins.

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26261 
 
 
 
  Unable to create the label in TFS using Jenkins.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Olivier Dagenais Ganesh Mulimani 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-26375) Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26375 
 
 
 
  Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [s3-plugin] (JENKINS-21965) publishing to s3 bucket always failed authentication (us-east-1)

2016-01-27 Thread lsbw...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 lsb want commented on  JENKINS-21965 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: publishing to s3 bucket always failed authentication (us-east-1)  
 
 
 
 
 
 
 
 
 
 
I got this error too 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-29408) Support building shelvesets

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29408 
 
 
 
  Support building shelvesets  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-25586) getAffectedFiles() is not implemented

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25586 
 
 
 
  getAffectedFiles() is not implemented  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Summary:
 
 Build Failed when triggered from VisualStudio.com Web Hooks getAffectedFiles() is not implemented 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28729 
 
 
 
  Exception raised during template rendering: getAffectedFiles() is not implemented  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Santosh Akuthota 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27371) Parent builds sometimes hang on successful child builds of same type

2016-01-27 Thread si...@simonmweber.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Simon Weber commented on  JENKINS-27371 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parent builds sometimes hang on successful child builds of same type  
 
 
 
 
 
 
 
 
 
 
Tony Bridges I don't think this was solved for us until I upgraded Jenkins. I'm not sure what combination of the jenkins, trigger plugin, and multijob plugin upgrades is necessary to solve it, but the environment I described earlier has been rock solid for months now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [reverse-proxy-auth-plugin] (JENKINS-32663) Jenkins instance is not loading after patch upgrade

2016-01-27 Thread verma_vija...@rediffmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vijay Kumar Verma assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32663 
 
 
 
  Jenkins instance is not loading after patch upgrade  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vijay Kumar Verma 
 
 
 

Assignee:
 
 Vijay Kumar Verma 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [reverse-proxy-auth-plugin] (JENKINS-32663) Jenkins instance is not loading after patch upgrade

2016-01-27 Thread verma_vija...@rediffmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vijay Kumar Verma created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32663 
 
 
 
  Jenkins instance is not loading after patch upgrade  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Vijay Kumar Verma 
 
 
 

Attachments:
 

 error page.JPG 
 
 
 

Components:
 

 reverse-proxy-auth-plugin 
 
 
 

Created:
 

 28/Jan/16 4:31 AM 
 
 
 

Environment:
 

 Production 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Vijay Kumar Verma 
 
 
 
 
 
 
 
 
 
 
I have updated version of reverse-proxy-auth-plugin to latest version 1.5, after update it tried to restart Jenkins via UI and is throwing error as mentioned in attachment. 
I tried to restart Jenkins instance via http:// 
Even, I tried to remove reverse-proxy-auth-plugin related files from #[jenkins-home]/plugins/reverse-proxy-auth-plugin and restart but it didn't worked. 
 
 
 
 
 
 
 
 
 

[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters

2016-01-27 Thread andrew.hamm...@mobileembrace.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Hammett commented on  JENKINS-29031 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Current Build Parameters doesn't pass custom job parameters  
 
 
 
 
 
 
 
 
 
 
it appears that only server-side environment variables are being parsed as parameters and all other values are being passed as literals. 
As an example if I were set the following "predefined variables" for any given job ``` FOO=$BAR GIT_COMMIT=$GIT_COMMIT ``` 
The $GIT_COMMIT value would be evaluated with $FOO being treated as literal $BAR. 
I have tried: ``` foo=baz export FOO=foo ``` 
using each of the above separately ultimately results in the same. the job being triggered will receive FOO=$BAR where $BAR is not evaluated (and does not show baz or foo). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-25720) Refactor the TFS Plugin to support Credentials API

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25720 
 
 
 
  Refactor the TFS Plugin to support Credentials API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Andy Pemberton 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-26449) Team Foundation Server Plugin: Team System Web Access repository browser links broken for TFS 2012 and 2013

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26449 
 
 
 
  Team Foundation Server Plugin: Team System Web Access repository browser links broken for TFS 2012 and 2013  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Jesse Jacob 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-29006) Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29006 
 
 
 
  Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-26089) Repository browser doesn't work for "Visual studio team foundation server 2013"

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26089 
 
 
 
  Repository browser doesn't work for "Visual studio team foundation server 2013"   
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Thomas Scheyvaerts 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-25368) Add an option to hide the long list of files checked out by TFS

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25368 
 
 
 
  Add an option to hide the long list of files checked out by TFS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-29200) Executing tf using the TFS Plugin throws an IO exception

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29200 
 
 
 
  Executing tf using the TFS Plugin throws an IO exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Lakshmi Jaganathan 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-29156) Add the "Release Notes" functionality in TFS Plugin

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29156 
 
 
 
  Add the "Release Notes" functionality in TFS Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-3636) Request to make retrieving sourcecode a configurable option when using SCM to poll for changes

2016-01-27 Thread manf...@simpligility.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manfred Moser closed an issue as Won't Do 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This issue is probably beyond the scope of the plugin and also over 6 years old. As such are closing this issue. Please file a new issue if some feature like this is desired after testing your scenario with the latest version of the tfs plugin. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-3636 
 
 
 
  Request to make retrieving sourcecode a configurable option when using SCM to poll for changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manfred Moser 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Won't Do 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-12543 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CliAuthenticator (username/password) called too late to parse arguments (like job names)  
 
 
 
 
 
 
 
 
 
 
Jesse Glick - I'd lean towards the second approach, pulling the credentials from the argument list and authenticating using those if necessary.  
That said, I'm confused. Aren't we already populating the authenticator at https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CLICommand.java#L228? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32660) Slave monitor for JNLP slaves using Launcher version lower than master

2016-01-27 Thread ow...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood commented on  JENKINS-32660 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slave monitor for JNLP slaves using Launcher version lower than master  
 
 
 
 
 
 
 
 
 
 
Here is an example using core. This logic should be able to be mostly salvaged for new plugin: 
 

[SlaveVersionMonitor](https://github.com/Evildethow/jenkins/blob/feature/slave-version-monitor/core/src/main/java/jenkins/slaves/SlaveVersionMonitor.java)
 

[SlaveVersionMonitorTest](https://github.com/Evildethow/jenkins/blob/feature/slave-version-monitor/core/src/test/java/jenkins/slaves/SlaveVersionMonitorTest.java)
 

[message](https://github.com/Evildethow/jenkins/blob/feature/slave-version-monitor/core/src/main/resources/jenkins/slaves/SlaveVersionMonitor/message.jelly)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-pipeline-plugin] (JENKINS-32422) Job without poller triggering on SCM

2016-01-27 Thread abho...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Hobbs updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32422 
 
 
 
  Job without poller triggering on SCM  
 
 
 
 
 
 
 
 
 
 
Correct service build job, and ghost service build job. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Anthony Hobbs 
 
 
 

Attachment:
 
 service_build_ok_build.xml 
 
 
 

Attachment:
 
 service_build_fail_build.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] [core] (JENKINS-21017) CLI update-job and POSTing config.xml cannot remove properties

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-21017 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CLI update-job and POSTing config.xml cannot remove properties  
 
 
 
 
 
 
 
 
 
 
So I probably have no idea what I'm talking about and my brain is oozing out my ears from trying to figure this out, but could we do some special-casing in RobustReflectionConverter to specifically grab any JobPropertys (when deserializing a Job descendant) or immediate class fields (for anything descending from AbstractItem) that show up in the deserialization process, and remove any that are set in the original but don't show up in the deserialization?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [script-security-plugin] (JENKINS-32661) workflow scripts can't use String.substring(int)

2016-01-27 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32661 
 
 
 
  workflow scripts can't use String.substring(int)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 script-security 1.18{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int}}eg:  {{someString.substring( 10 );}}workaround: {{someString.substring( 10, someString.length() );}}which is slightly annoying and makes the Jenkinsfile more verbose than necessary. Related to: https://issues.jenkins-ci.org/browse/JENKINS-29541 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [script-security-plugin] (JENKINS-32661) workflow scripts can't use String.substring(int)

2016-01-27 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32661 
 
 
 
  workflow scripts can't use String.substring(int)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 1.609.1, wf 1.8, secript script - scurity security  1. 14 18 {{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int  int }} same for gstring eg:  {{someString . substring( 10 );}}  workaround: {{ org someString . jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object substring  ( org  10, someString . codehaus.groovy.runtime.GStringImpl substring java.lang.Integer java.lang.Integer length( )  ); }} which is slightly annoying and makes the Jenkinsfile more verbose than necessary. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32662) Unable to use versions with custom tool

2016-01-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32662 
 
 
 
  Unable to use versions with custom tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Component/s:
 
 extended-choice-parameter-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] [customtools-plugin] (JENKINS-32662) Unable to use versions with custom tool

2016-01-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-32662 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use versions with custom tool  
 
 
 
 
 
 
 
 
 
 
From what I see it's a compatibility issue caused by changes in the Extended Choice plugin. Please specify it's version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Inv

2016-01-27 Thread ty...@monkeypox.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy deleted an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32638 
 
 
 
  how to contact facebook management  
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 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-32639) Github commit status doesn't work

2016-01-27 Thread a.belayt...@smart-crowd.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Belaytzev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32639 
 
 
 
  Github commit status doesn't work  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kirill Merkushev 
 
 
 

Components:
 

 github-plugin 
 
 
 

Created:
 

 27/Jan/16 8:07 AM 
 
 
 

Environment:
 

 Debian GNU/Linux 7  Linux 3.13.0-74 2015 x86_64  java -version  java version "1.7.0_75"  OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~deb7u1)  OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)   Jenkins 1.646  GitHub plugin 1.17.0  Nginx reverse proxy   Github Private Repository 
 
 
 

Labels:
 

 plugins 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Alexey Belaytzev 
 
 
 
 
 
 
 
 
 
 
Problem with set build status on github. Build log: ... Setting commit status on GitHub for https://github.com/Company/Project/commit/39357a7cd3fb42296d29a00c07caa7f81aa79363 ... 
But build status not set on Github:  https://s3-eu-west-1.amazonaws.com/uploads-eu.hipchat.com/113102/841991/ruCMoRTyQqI3Hiv/Screen%20Shot%202016-01-27%20at%2011.04.48.png 
 
 
  

[JIRA] [ansicolor-plugin] (JENKINS-30528) Add ANSI colour support to workflow log output

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-30528 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add ANSI colour support to workflow log output  
 
 
 
 
 
 
 
 
 
 
Are we sure this actually works? It's still referencing AbstractBuild - https://github.com/dblock/jenkins-ansicolor-plugin/blob/master/src/main/java/hudson/plugins/ansicolor/AnsiColorBuildWrapper.java#L202 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [rebuild-plugin] (JENKINS-32645) Rebuild Plugin triggering same job multiple times on slaves simultaneously

2016-01-27 Thread dun...@duncanbell.co.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Duncan Bell updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32645 
 
 
 
  Rebuild Plugin triggering same job multiple times on slaves simultaneously  
 
 
 
 
 
 
 
 
 

Change By:
 
 Duncan Bell 
 
 
 

Labels:
 
 jenkins plugin rebuild rebuild-last slave slave-agent slaves  ssh-slave 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [msbuild-plugin] (JENKINS-32654) Build Fails when PreBuildEvent has "REM" comments

2016-01-27 Thread larryeisenst...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Larry Eisenstein created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32654 
 
 
 
  Build Fails when PreBuildEvent has "REM" comments  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 kdsweeney 
 
 
 

Components:
 

 msbuild-plugin 
 
 
 

Created:
 

 27/Jan/16 3:44 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Larry Eisenstein 
 
 
 
 
 
 
 
 
 
 
My Visual Studio project has PreBuildEvents. I get errors when I have comments in the PreBuildEvent. 


Error Message
  

 

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets(1063,5): error MSB3073: The command "REM  [C:\Jenkins\jobs\Test Git\workspace\Snap.csproj]
 

 
If I remove these comments from the PreBuild event, it works. 
If I build the project directly from Visual Studio (with PreBuild event comments), it works. 
 
 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [rebuild-plugin] (JENKINS-32645) Rebuild Plugin triggering same job multiple times on slaves simultaneously

2016-01-27 Thread dun...@duncanbell.co.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Duncan Bell commented on  JENKINS-32645 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rebuild Plugin triggering same job multiple times on slaves simultaneously  
 
 
 
 
 
 
 
 
 
 
Trying my older version of ssh-slaves plugin (1.9) has the same behaviour as 1.10. 
The job starts off with... 
(pending—Waiting for next available executor on all) 
Then spawns to all slaves instead of just one... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-31322) Parallel maven jobs run out of order

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-31322 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parallel maven jobs run out of order  
 
 
 
 
 
 
 
 
 
 
I'm guessing this is because of the weirdness of MavenModule within MavenModuleSet being actual AbstractProject objects themselves and having independent build numbering from the parent. The parent will end up setting its next build number to one higher than any of the child modules have for their highest build number. There's got to be some race condition somewhere. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable

2016-01-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-28821 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable  
 
 
 
 
 
 
 
 
 
 
Stopped the progress since Jesse Glick didn't like https://github.com/jenkinsci/docker-workflow-plugin/pull/7 . I have not implemented anything else 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-pipeline-plugin] (JENKINS-31012) Jenkins Build Pipeline Plugin and using HTTP tunnels to load the Jenkins instance

2016-01-27 Thread alv...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  JENKINS-31012 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins Build Pipeline Plugin and using HTTP tunnels to load the Jenkins instance  
 
 
 
 
 
 
 
 
 
 
Thanks Bill Hurt 
Tony Xynidakis I misread your original issue where you can't update the Jenkins URL. Is it possible to configure your http tunnel to rewrite content and update the URL that way? 
The issue you describe will be an issue with a number of other plugins: 
https://github.com/search?utf8=%E2%9C%93=%22app.rootUrl%22+%22jelly%22=Code=searchresults 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.

2016-01-27 Thread rpoc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robby Pocase commented on  JENKINS-32523 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.  
 
 
 
 
 
 
 
 
 
 
I've seen this issue on and off for months now across various jobs. I'm not sure if its specifically related to pending changelists, though. I have a job now that doesn't have any pending changelists (unless there are some in default) that is in the constant queuing state. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cli] (JENKINS-32622) deadlock due to support-core use of classloading during logging

2016-01-27 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32622 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: deadlock due to support-core use of classloading during logging  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Steven Christou Path: src/main/java/com/cloudbees/jenkins/support/SupportLogFormatter.java http://jenkins-ci.org/commit/support-core-plugin/d0c2ec7b8acd28f088483e3d6ffec5fb3a157db7 Log: Merge pull request #55 from jtnord/JENKINS-32622 
JENKINS-32622 Switch to a ThreadLocal DateFormatter 
Compare: https://github.com/jenkinsci/support-core-plugin/compare/751b73fdff61...d0c2ec7b8acd 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cli] (JENKINS-32622) deadlock due to support-core use of classloading during logging

2016-01-27 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32622 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: deadlock due to support-core use of classloading during logging  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: James Nord Path: src/main/java/com/cloudbees/jenkins/support/SupportLogFormatter.java http://jenkins-ci.org/commit/support-core-plugin/bf508eb6535d3d907839f924062772fd9aa6cba7 Log: JENKINS-32622 Switch to a ThreadLocal DateFormatter 
Attempt to avoid a deadlock observed in remoting by not causing any remote classes to be loaded when we are logging. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-blocker-plugin] (JENKINS-32531) Missing default value for configure block level setting

2016-01-27 Thread michal.sevce...@etnetera.cz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ševčenko commented on  JENKINS-32531 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing default value for configure block level setting  
 
 
 
 
 
 
 
 
 
 
I just found out that this is problem not only by migration to new version, but also of the UI itself. The UI does neither preset any value for the option, nor validates that some option is set. So if the user only checks that job should be blocking, without setting the parameter, job does not block. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked

2016-01-27 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-28466 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked   
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Javier Palacios Path: work/jenkins.model.JenkinsLocationConfiguration.xml http://jenkins-ci.org/commit/gitlab-hook-plugin/1bb034f5d5c7a449b733758af056441668e75853 Log: Add jenkins_url variable (JENKINS-28466) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-blocker-plugin] (JENKINS-32653) Should the job be blocking even if it is only queued, not actually running?

2016-01-27 Thread michal.sevce...@etnetera.cz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ševčenko created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32653 
 
 
 
  Should the job be blocking even if it is only queued, not actually running?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 build-blocker-plugin 
 
 
 

Created:
 

 27/Jan/16 3:30 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michal Ševčenko 
 
 
 
 
 
 
 
 
 
 
I wonder it would make more sense that job would be blocking other jobs not only if it is running, but if it is queued (blocked for instance, or waiting for empty slot). 
If I set that job A blocks job B and B blocks C, and run A, then B, and then C, I would expect that job C would execute only after B unblocks itself, and finishes. The job C however starts immediately because job B does not run at the time (is blocked by A). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
  

[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-32655) Add support for Pipeline job types

2016-01-27 Thread peteha...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Hayes created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32655 
 
 
 
  Add support for Pipeline job types  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 nathan m 
 
 
 

Components:
 

 stash-pullrequest-builder-plugin 
 
 
 

Created:
 

 27/Jan/16 4:19 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Peter Hayes 
 
 
 
 
 
 
 
 
 
 
I attempted to use this plugin with the Pipeline (previously called Workflow) plugin and, although you can configure the plugin parameters on the job page, saving the job configuration fails with the following error: 
javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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) 
It would be great to add support for the Pipeline plugin so pipeline builds can be triggered when Pull Requests are created and / or approved.  
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [scm-sync-configuration-plugin] (JENKINS-32656) Cannot configure password for ssh-key used for git remote

2016-01-27 Thread argr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alberto Gallardo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32656 
 
 
 
  Cannot configure password for ssh-key used for git remote  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Frédéric Camblor 
 
 
 

Components:
 

 scm-sync-configuration-plugin 
 
 
 

Created:
 

 27/Jan/16 4:32 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.644  SCM Sync Configuration Plugin ver. 0.9 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Alberto Gallardo 
 
 
 
 
 
 
 
 
 
 
Cannot use a git repository with ssh, if the key is password-protected. 
Example: {{$# Set password for ssh key: $ ssh-keygen -p -f ~/.ssh/id_rsa Key has comment '/var/lib/jenkins/.ssh/id_rsa' Enter new passphrase (empty for no passphrase): *** Enter same passphrase again: *** Your identification has been saved with the new passphrase. 
$git remote -v origin ssh://git@git.server/repo (fetch) origin ssh://git@git.server/repo (push) }} 
Trying to save any config change: {{SCM Sync status :  Wed Jan 27 17:22:04 CET 2016 : Error while checking in file to scm repository }} 
In log: SEVERE: [checkinFiles] Problem during SCM commit : Permission denied (publickey). fatal: Could not read from remote repository. 
 
 
 
 
 

[JIRA] [scm-sync-configuration-plugin] (JENKINS-32656) Cannot configure password for ssh-key used for git remote

2016-01-27 Thread argr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alberto Gallardo commented on  JENKINS-32656 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot configure password for ssh-key used for git remote  
 
 
 
 
 
 
 
 
 
 
This issue could be presumibly solved if #18129 were implemented? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [claim-plugin] (JENKINS-27206) Enable claim support from workflow

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-27206 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable claim support from workflow  
 
 
 
 
 
 
 
 
 
 
Hmm, yeah. I guess we could change that to if (build.getResult() == null || build.getResult().isWorseThan(Result.SUCCESS)) { to get it to work when called from a Pipeline job but still behave like normal outside...but then all Pipeline builds will show up eligible to be claimed, not just failed ones. This is one of those cases where the Pipeline design doesn't fit right with Publishers... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [timestamper-plugin] (JENKINS-30143) logs for individual workflow steps do not contain timestamps

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-30143 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: logs for individual workflow steps do not contain timestamps  
 
 
 
 
 
 
 
 
 
 
Is it as simple as https://github.com/jenkinsci/timestamper-plugin/blob/master/src/main/java/hudson/plugins/timestamper/annotator/TimestampAnnotator.java#L77-L79? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22300) Need ability to associate public ip address for slave nodes

2016-01-27 Thread mferra...@dataxu.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Ferrante commented on  JENKINS-22300 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Need ability to associate public ip address for slave nodes  
 
 
 
 
 
 
 
 
 
 
Yesss, helped close a 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] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable

2016-01-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev stopped work on  JENKINS-28821 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [performance-plugin] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep

2016-01-27 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32650 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make PerformancePublisher a SimpleBuildStep  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Cyrille Le Clerc Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/5e78bc99b7150961f165a8bdce7e95b6335b3686 Log: Add PerformancePublisher 
Add PerformancePublisher https://issues.jenkins-ci.org/browse/JENKINS-32650 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [msbuild-plugin] (JENKINS-32654) Build Fails when PreBuildEvent has "REM" comments

2016-01-27 Thread larryeisenst...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Larry Eisenstein updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32654 
 
 
 
  Build Fails when PreBuildEvent has "REM" comments  
 
 
 
 
 
 
 
 
 

Change By:
 
 Larry Eisenstein 
 
 
 
 
 
 
 
 
 
 My Visual Studio project has PreBuildEvents.  I get errors when I have comments in the PreBuildEvent.*+Error Message+*  {code:java}C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets(1063,5): error MSB3073: The command "REM  [C:\Jenkins\jobs\Test Git\workspace\Snap.csproj] C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets(1063,5): error MSB3073: " exited with code 4. [C:\Jenkins\jobs\Test Git\workspace\Snap.csproj] {code}If I remove these comments from the PreBuild event, it works.If I build the project directly from Visual Studio (with PreBuild event comments), it works. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [scm-sync-configuration-plugin] (JENKINS-32656) Cannot configure password for ssh-key used for git remote

2016-01-27 Thread argr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alberto Gallardo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32656 
 
 
 
  Cannot configure password for ssh-key used for git remote  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alberto Gallardo 
 
 
 
 
 
 
 
 
 
 Cannot use a git repository with ssh, if the key is password-protected.Example:{{$# Set password for ssh key:$ ssh-keygen -p -f ~/.ssh/id_rsaKey has comment '/var/lib/jenkins/.ssh/id_rsa'Enter new passphrase (empty for no passphrase): ***Enter same passphrase again: ***Your identification has been saved with the new passphrase.$git remote -vorigin ssh://git@git.server/repo (fetch)origin ssh://git@git.server/repo (push)}}Trying to save any config change:{{SCM Sync status :  Wed Jan 27 17:22:04 CET 2016 : Error while checking in file to scm repository}}In log: {{ SEVERE: [checkinFiles] Problem during SCM commit : Permission denied (publickey).fatal: Could not read from remote repository. }}  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [integrity-plugin] (JENKINS-32665) Test bug

2016-01-27 Thread integrity_jenkins_plu...@ptc.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 PTC ALM created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32665 
 
 
 
  Test bug  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 PTC ALM 
 
 
 

Components:
 

 integrity-plugin 
 
 
 

Created:
 

 28/Jan/16 7:53 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 PTC ALM 
 
 
 
 
 
 
 
 
 
 
Test Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [integrity-plugin] (JENKINS-32665) Test bug

2016-01-27 Thread integrity_jenkins_plu...@ptc.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 PTC ALM closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32665 
 
 
 
  Test bug  
 
 
 
 
 
 
 
 
 

Change By:
 
 PTC ALM 
 
 
 

Status:
 
 Open Closed 
 
 
 

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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated

2016-01-27 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ commented on  JENKINS-11176 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Promotion criteria "If the build is a release build" is broken and displays duplicated  
 
 
 
 
 
 
 
 
 
 
This still happens in latest release of the plugin 2.5.4. Can we re-open this 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] [github-plugin] (JENKINS-32639) Github commit status doesn't work

2016-01-27 Thread a.belayt...@smart-crowd.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Belaytzev reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Sorry my mistake. Github plugin in "Console Output" displays link to merge on github instead of github commit. 
Console Output: ... Setting commit status on GitHub for https://github.com/SmartCrowd/Monitoring/commit/30b42207656fd2341276e916cad73b9181b4f9cc ... 
Merge on github: 
 
Commit in this merge on github: 
 
System Log Jenkins: 
jan 28, 2016 10:00:02 AM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent Received POST for https://github.com/Company/Repository jan 28, 2016 10:00:02 AM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run Poked Jenkins-Build-Name jan 28, 2016 10:00:02 AM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run Poked Server-Name jan 28, 2016 10:01:40 AM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent Received POST for https://github.com/Company/Repository jan 28, 2016 10:01:40 AM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run Poked Jenkins-Build-Name jan 28, 2016 10:01:40 AM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run Poked Server-Name jan 28, 2016 10:01:42 AM INFO com.cloudbees.jenkins.GitHubPushTrigger$1 run SCM changes detected in Jenkins-Build-Name. Triggering #53 jan 28, 2016 10:02:12 AM INFO hudson.model.Run execute Jenkins-Build-Name #53 main build action completed: SUCCESS 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32639 
 
 
 
  Github commit status doesn't work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexey Belaytzev 
 
 
 

Resolution:
 
 Incomplete 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[JIRA] [s3-plugin] (JENKINS-21965) publishing to s3 bucket always failed authentication (us-east-1)

2016-01-27 Thread lsbw...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 lsb want commented on  JENKINS-21965 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: publishing to s3 bucket always failed authentication (us-east-1)  
 
 
 
 
 
 
 
 
 
 
I found the causing is maybe have more '/' before your bucket 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] [s3-plugin] (JENKINS-21965) publishing to s3 bucket always failed authentication (us-east-1)

2016-01-27 Thread lsbw...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 lsb want edited a comment on  JENKINS-21965 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: publishing to s3 bucket always failed authentication (us-east-1)  
 
 
 
 
 
 
 
 
 
 I found the causing is maybe have more '/' before your bucket name. You should like this jenkins/xxx/${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] [_unsorted] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception

2016-01-27 Thread abines...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Abinesh Subburayalu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32664 
 
 
 
  Copy Artifact plugin parameter passing via curl throws exception  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 _unsorted 
 
 
 

Created:
 

 28/Jan/16 7:38 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Abinesh Subburayalu 
 
 
 
 
 
 
 
 
 
 
I am trying to execute a Jenkins Job using curl command and my job uses Copy Artifact plugin and I am trying to pass the parameter. But it fails. Here is the complete stacktrace 
Here is the curl url, 
curl --user abinesh:x http://jenkinsurl/job/job.name/build --data-urlencode json='{"parameter":[ {"name":"DEPLOY_TO_SERVER", "value":"target.server"} 
, {"name":"BUILD_SELECTION","default selector":"latest successful build","stableOnly":false} 
]}' 
 might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class hudson.plugins.copyartifact.BuildSelector from  {"name":"BUILD_SELECTION","default selector":"latest successful build","stableOnly":false} 
 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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 

[JIRA] [_unsorted] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception

2016-01-27 Thread abines...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Abinesh Subburayalu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32664 
 
 
 
  Copy Artifact plugin parameter passing via curl throws exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Abinesh Subburayalu 
 
 
 
 
 
 
 
 
 
 I am trying to execute a Jenkins Job using curl command and my job uses Copy Artifact plugin and I am trying to pass the parameter. But it fails.  Here is the complete stacktrace     Here is the curl url,curl --user abinesh:x http://jenkinsurl/job/job.name/build --data-urlencode json='{"parameter":[  {"name":"DEPLOY_TO_SERVER", "value":"target.server"},  {"name":"BUILD_SELECTION","default selector":"latest successful build","stableOnly":false}  ]}' Here is the complete stacktrace  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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 org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.success(BasicHeaderProcessor.java:140) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:82) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at 

[JIRA] [cobertura-plugin] (JENKINS-32573) Cobertura misconfiguration destroys 'publishers' node

2016-01-27 Thread t...@praqma.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thierry Lacour commented on  JENKINS-32573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cobertura misconfiguration destroys 'publishers' node  
 
 
 
 
 
 
 
 
 
 
That's understandable. I just wanted to get this out in the open since it's a pain to find out what's going wrong in bigger scripts. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-32133) Polish and expose auto-generated Workflow step documentation

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32133 
 
 
 
  Polish and expose auto-generated Workflow step documentation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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] [maven-plugin] (JENKINS-7441) Move from Maven 2.0.4 embedder to something more modern - i.e., 3.x

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-7441 
 
 
 
  Move from Maven 2.0.4 embedder to something more modern - i.e., 3.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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] [core] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-11149 
 
 
 
  JNLP slave fails to connect if Anonymous has not permission READ  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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] [matrix-auth-plugin] (JENKINS-30495) Add 'authenticated' user group to the Matrix UI

2016-01-27 Thread drrobpl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Platt commented on  JENKINS-30495 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add 'authenticated' user group to the Matrix UI  
 
 
 
 
 
 
 
 
 
 
+1 
Given that adding the row works (I tested with builtin DB security) it is just the view/initial matrix that needs changing. It's only through trawling the internet that I figured out I could use this special "authenticated" SID. I suspect there are people out there thinking this isn't possible and going through a hassle setting up permissions on every user. It is a usability thing. I suspect that 

JENKINS-13029
 was created because this feature wasn't visible to the user. 
Resolving this may reduce the amount of queries/stackoverflow/questions and is especially relevant for working around JENKINS-28132, where the release but disappears even if you are saying that logged in users can do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [release-plugin] (JENKINS-28132) Release button disappears after upgrading Release Plugin from 2.4.1 to 2.5.3

2016-01-27 Thread drrobpl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Platt commented on  JENKINS-28132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Release button disappears after upgrading Release Plugin from 2.4.1 to 2.5.3  
 
 
 
 
 
 
 
 
 
 
In case it is helpful to others, I've confirmed Andreas' workaround for "logged-in users can do anything" via the matrix "authenticated" mechanism, on a system using jenkins builtin user database. 
(I wasn't sure whether it was an LDAP group until I researched it – but "authenticated" is built into Jenkins specially) 
If the "authenticated" matrix feature is news to you as much as me, then you may wish to vote on JENKINS-30495  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4535) The ability to clone from multiple repositories into separate directories would be useful

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The Multiple SCMs plugin is the solution here. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-4535 
 
 
 
  The ability to clone from multiple repositories into separate directories would be useful  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting

2016-01-27 Thread jorg.zieg...@fotonic.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jörg Ziegler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32657 
 
 
 
  cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 cmakebuilder-plugin 
 
 
 

Created:
 

 27/Jan/16 5:40 PM 
 
 
 

Environment:
 

 all 
 
 
 

Labels:
 

 configuration plugin jenkins 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jörg Ziegler 
 
 
 
 
 
 
 
 
 
 
it would be desirable for full cross-platform scripting of bigger cmake-projects to be able to run cmake scripts (cmake -P 

[JIRA] [tfs-plugin] (JENKINS-21938) TF14044: Access Denied: User XXX needs the AdminWorkspaces global permission(s).

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21938 
 
 
 
  TF14044: Access Denied: User XXX needs the AdminWorkspaces global permission(s).  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-22046) TFS plugin won't get changeset information from VisualStudio.com, fails with Access Denied

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
visualstudio.com, a.k.a. Visual Studio Team Services (previously Visual Studio Online) is supported since version 4.0.0. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-22046 
 
 
 
  TFS plugin won't get changeset information from VisualStudio.com, fails with Access Denied  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Arnoud Berendsen 
 
 
 

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 

[JIRA] [matrix-auth-plugin] (JENKINS-30495) Add 'authenticated' user group to the Matrix UI

2016-01-27 Thread drrobpl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Platt edited a comment on  JENKINS-30495 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add 'authenticated' user group to the Matrix UI  
 
 
 
 
 
 
 
 
 
 +1Given that adding the row works (I tested with builtin DB security) it is just the view/initial matrix that needs changing. It's only through trawling the internet that I figured out I could use this special "authenticated" SID , and that it wasn't an LDAP group . I suspect there are people out there thinking this isn't possible and going through a hassle setting up permissions on every user. It is a usability thing. I suspect that JENKINS-13029 was created because this feature wasn't visible to the user.Resolving this may reduce the amount of queries/stackoverflow/questions and is especially relevant for working around JENKINS-28132, where the release  but  button  disappears even if you are saying that logged in users can do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-22446) Get the branch name into environment variable.

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais commented on  JENKINS-22446 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Get the branch name into environment variable.  
 
 
 
 
 
 
 
 
 
 
How would this work? 
If you mean a parameterized build, you can (with version 4.0.0) add a parameter in the Project path field, as I did when I tested the new Cloaked paths field. See comment 171974422 on pull requeust #68. 
Otherwise I'm not sure how the branch name could be detected from, say, the Project 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] [tfs-plugin] (JENKINS-22446) Get the branch name into environment variable.

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22446 
 
 
 
  Get the branch name into environment variable.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable

2016-01-27 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow commented on  JENKINS-28821 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable  
 
 
 
 
 
 
 
 
 
 
I was able to work around this without modifying the container by explicitly specifying the uid to match the mounted filesystem (uid: 1000, gid: 50). 
Like this: 

 

docker.image('maven:3.3.3-jdk-8').inside('-u 1000:50') {
  git '...'
  sh 'mvn -B clean install'
}
 

 
Less than ideal, as the uid is specified twice in the command line... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [build-failure-analyzer-plugin] (JENKINS-17651) Allow more than 1 line as indicator

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17651 
 
 
 
  Allow more than 1 line as indicator  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

Status:
 
 Reopened 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] [git-plugin] (JENKINS-12430) Git change trigger generate duplicate build

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer assigned an issue to Mark Waite 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-12430 
 
 
 
  Git change trigger generate duplicate build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

Assignee:
 
 Andrew Bayer Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25930) Race condition creating build links during concurrent builds causes build failures

2016-01-27 Thread as_kuml...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ali Sadik Kumlali commented on  JENKINS-25930 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Race condition creating build links during concurrent builds causes build failures  
 
 
 
 
 
 
 
 
 
 
It seems the problem only occurs when the job triggered by MultiJob Plug-in. The job can run parallel if I trigger it manually.  
The other thing is the problem does not occur on Windows. I can reproduce it in Linux. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-22387) Default workspace name is not configurable

2016-01-27 Thread oliv...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22387 
 
 
 
  Default workspace name is not configurable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [release-plugin] (JENKINS-28132) Release button disappears after upgrading Release Plugin from 2.4.1 to 2.5.3

2016-01-27 Thread drrobpl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Platt edited a comment on  JENKINS-28132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Release button disappears after upgrading Release Plugin from 2.4.1 to 2.5.3  
 
 
 
 
 
 
 
 
 
 In case it is helpful to others, I've confirmed Andreas' workaround for "logged-in users can do anything" via the matrix "authenticated" mechanism, on a system using jenkins builtin user database , on LTS 1 . 642.1. (I wasn't sure whether it was an LDAP group until I researched it -- but "authenticated" is built into Jenkins specially)If the "authenticated" matrix feature is news to you as much as me, then you may wish to vote on JENKINS-30495 ;-) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-4152) Incremental builds should include previous builds' modules if previous build failed

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The Maven plugin is kinda awful, so I'd generally advise not to use it, and definitely don't use the incremental build option. =) 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-4152 
 
 
 
  Incremental builds should include previous builds' modules if previous build failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-16208) TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset

2016-01-27 Thread j...@olsonzoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jeffolson commented on  JENKINS-16208 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset  
 
 
 
 
 
 
 
 
 
 
Thank you! I no longer work on a project that uses TFS, but I will pass this on to some of my colleagues on my old team. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jclouds-plugin] (JENKINS-14397) create jenkins user with full name

2016-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-14397 
 
 
 
  create jenkins user with full name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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.


  1   2   3   >