[JIRA] (JENKINS-40271) Update module names for update center

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40271  
 
 
  Update module names for update center   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 frank  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40271) Update module names for update center

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40271  
 
 
  Update module names for update center   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 James Dumay  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Dec/07 7:30 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 
 
 Daniel Beck yo i386 around? 10:08 AM Could we maybe get some consistency between Blue Ocean and Pipeline, the two big polluters of the plugin manager, re the naming of things? 10:08 AM Pipeline: Thing 10:08 AM Blue Ocean :: Module :: Thing 10:09 AM FWIW I'd prefer the former, because BO's looks like a 15 year old's online gaming tag 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-39676) Cannot populate servers via groovy script

[fbelz...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos commented on  JENKINS-39676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot populate servers via groovy script   
 

  
 
 
 
 

 
 Meanwhile this is not released, please migrate to the new Descriptor. 

 

@DataBoundConstructor
// as Java signature, this binding doesn't make sense, so please don't use this constructor
public ActiveDirectorySecurityRealm(String domain, List domains, String site, String bindName,
String bindPassword, String server, GroupLookupStrategy groupLookupStrategy, boolean removeIrrelevantGroups, Boolean customDomain, CacheConfiguration cache) {
 

 

 

import hudson.plugins.active_directory.* 
import jenkins.model.*

def instance = Jenkins.getInstance();
def ActiveDirectoryDomain adDomain = new ActiveDirectoryDomain("Example_Domain_Name_2", "Example_Domain_Controller_2");
def domains = new ArrayList();
domains.add(adDomain);

def securityRealm = new ActiveDirectorySecurityRealm( 
"", 
domains,
"", 
"",
"",  
"", 
GroupLookupStrategy.RECURSIVE,
false,
true,
null)
println(securityRealm.domains)

instance.setSecurityRealm(securityRealm) 
instance.save()
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
   

[JIRA] (JENKINS-40270) Unable to create new jenkins job - Blank page issue

[utkarshred...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 utkarsh sharma created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40270  
 
 
  Unable to create new jenkins job - Blank page issue   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Attachments: 
 Screen Shot 2016-12-07 at 12.23.43 PM.png  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2016/Dec/07 6:56 AM  
 
 
Labels: 
 jenkins  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 utkarsh sharma  
 

  
 
 
 
 

 
 Hi Team, I am unable to create new jenkins job as it throws blank page. I tried inspect element and it gave me this :  *jquery2.js:998 GET http://10.40.162.72/jenkins/view/All/itemCategories?depth=3 500 (Internal Server Error)* Please help us resolving this issue asap as this is blocker for our major release. Jenkins version : Jenkins ver. 2.7.4 Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

[JIRA] (JENKINS-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error

[inbarajan.pra...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Prabhu Inbarajan edited a comment on  JENKINS-39695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error   
 

  
 
 
 
 

 
 [~iocanel] - Can you please clarify the comment , my setup is somewhat similar. I am running my jenkins master in docker swarm, but have configured it to run my slave workloads on remote kubernetes.i have looked at the kubernetes-plugin code somewhat superficially , but dont see how the stack trace above correlates with any logic from the kubernetes-client plugin. Interestingly enough, this problem seems to impact all the shell commands in pipeline DSL , the other jvm calls seems okay. {code:java}https://github.com/jenkinsci/kubernetes-plugin/blob/52c0af572ef091399fa76657be34471c033d1464/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L92{code} " if you use the kubernetes-plugin outside of kubernetes, you need to properlly configure it to talk to the remote kubernetes." what configuration are you referring to?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error

[inbarajan.pra...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Prabhu Inbarajan commented on  JENKINS-39695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error   
 

  
 
 
 
 

 
 Ioannis Canellos - Can you please clarify the comment , my setup is somewhat similar. I am running my jenkins master in docker swarm, but have configured it to run my slave workloads on remote kubernetes. i have looked at the kubernetes-plugin code somewhat superficially , but dont see how the stack trace above correlates with any logic from the kubernetes-client plugin. Interestingly enough, this problem seems to impact all the shell commands in pipeline DSL , the other jvm calls seems okay. " if you use the kubernetes-plugin outside of kubernetes, you need to properlly configure it to talk to the remote kubernetes."  what configuration are you referring to?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40269) Unit test CoverageObjectGraphTest fails on Fedora 24

[s...@flanigan.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40269  
 
 
  Unit test CoverageObjectGraphTest fails on Fedora 24   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ognjen Bubalo  
 
 
Attachments: 
 baseStroke.png, crop100.png, crop5.png, multiple.png, simple.png, skipzero.png  
 
 
Components: 
 jacoco-plugin  
 
 
Created: 
 2016/Dec/07 6:30 AM  
 
 
Environment: 
 Fedora 24, openjdk 1.8.0_111  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sean Flanigan  
 

  
 
 
 
 

 
 Six tests in hudson.plugins.jacoco.model.CoverageObjectGraphTest fail when built from master (commit a35ce7309), apparently due to minor font rendering differences. The erroneous charts are attached.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong

[m...@jochen-fuerbacher.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jochen A. Fürbacher commented on  JENKINS-38536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Execution time of parallel blocks of in-flight jobs wrong   
 

  
 
 
 
 

 
 

 

node() {

stage('Stage 1') {

parallel (
el1: { sleep 20 },
el2: { sleep 10 }
)
}
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-31824) Users with project create credentials permission are unable to add new credentials

[fbelz...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos commented on  JENKINS-31824  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Users with project create credentials permission are unable to add new credentials   
 

  
 
 
 
 

 
 I am NOT able to reproduce this issue with version Jenkins ver. 1.609, neither 1.651 This issue needs the version of Jenkins core used and a bit more of information for reproduction.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40193) Upgrade plugin parent pom

[kingzzm1...@sina.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 zhaoz zhiming commented on  JENKINS-40193  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade plugin parent pom   
 

  
 
 
 
 

 
 @escoem It seems something wrong. When I upload files it report error message: 401, ReasonPhrase: Unauthorized.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39955) REGRESSION: Re-running a failed build via re-run button from results screen breaks karaoke mode

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39955  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: Re-running a failed build via re-run button from results screen breaks karaoke mode   
 

  
 
 
 
 

 
 I am pretty sure this wasn't broken when running not via hpi:run. I was able to re-run the same pipeline from both hpi:run and the production way - and one didn't work, the other did.  The ATH obviously tests the production way... anyway. This is done now once merged.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 Patrick Wolf from conversations with KK, it wasn't relised at first how hard it would be to implement. As the saying goes "we do these things not because they are easy, but because we thought they would be easy"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38339) Unable to browse to externally launched builds [missing log decoration]

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to browse to externally launched builds [missing log decoration]   
 

  
 
 
 
 

 
 Yes I think there needs to either be log decorations of affordances for when other jobs are invoked  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly   
 

  
 
 
 
 

 
 cc James Dumay what is the plugin to disable to stop this? Is it the BlueOcean Display URL plugin?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-33765) Configure S3 at folder level

[ow...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Wood commented on  JENKINS-33765  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configure S3 at folder level   
 

  
 
 
 
 

 
 Advised that extension points are required on the https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin to make this work but the main implementation is required here. Maybe Stephen Connolly can provide some insight?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-33762) Per-folder tool installations

[ow...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Wood assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33762  
 
 
  Per-folder tool installations   
 

  
 
 
 
 

 
Change By: 
 Owen Wood  
 
 
Assignee: 
 Owen Wood  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40224  
 
 
  Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Component/s: 
 blueocean-display-url-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40227) blueocean site cannot be reached

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-40227  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blueocean site cannot be reached   
 

  
 
 
 
 

 
 Hi Matt Westlake, Sorry to hear that you ran into troubles. How did you determine that "it caused a plugin to stop responding" - would be great to know what symptoms you saw Jenkins exhibiting at the time and what page you tried to access. As for the server not starting up correctly, would you be able to: 
 
Restart your Jenkins server 
Wait for it to start up 
Visit the Jenkins home screen 
Copy the logs and email them to me jdu...@cloudbees.com 
 That should help us diagnose what is going on here.  Thanks James  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay edited a comment on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 [~hrmpw] if the {{archive}} step fails because there are no inputs that fails terribly too (with a stack trace) . There are many steps that exhibit similar behaviour. If we can have beautiful error reports like JENKINS-35308 for all the steps I would sleep better at night :)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 Patrick Wolf if the archive step fails because there are no inputs that fails terribly too (with a stack trace)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40268) Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`

[guc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 gu cong updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40268  
 
 
  Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`   
 

  
 
 
 
 

 
Change By: 
 gu cong  
 

  
 
 
 
 

 
 ``` bash |># echo $NVM_NODEJS_ORG_MIRRORhttp://npm.taobao.org/mirrors/node`` console 1:49:25 curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 10411:49:25 Binary download from https://nodejs.org/dist/v6.9.2/node-v6.9.2.tar.xz failed, trying source.11:49:25 grep: /root/.nvm/.cache/src/node-v6.9.2/node-v6.9.2.tar.xz: No such file or directory11:49:25 Provided file to checksum does not exist.11:49:25 nvm: install v6.9.2 failed!```I need to download node from mirror, but Jenkins still download from the official website.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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 

[JIRA] (JENKINS-40268) Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`

[guc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 gu cong updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40268  
 
 
  Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`   
 

  
 
 
 
 

 
Change By: 
 gu cong  
 

  
 
 
 
 

 
 ```bash |># $  echo $NVM_NODEJS_ORG_MIRRORhttp://npm.taobao.org/mirrors/node`` console1:49:25 curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 10411:49:25 Binary download from https://nodejs.org/dist/v6.9.2/node-v6.9.2.tar.xz failed, trying source.11:49:25 grep: /root/.nvm/.cache/src/node-v6.9.2/node-v6.9.2.tar.xz: No such file or directory11:49:25 Provided file to checksum does not exist.11:49:25 nvm: install v6.9.2 failed!```I need to download node from mirror, but Jenkins still download from the official website.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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, 

[JIRA] (JENKINS-40268) Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`

[guc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 gu cong created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40268  
 
 
  Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Tomas Salazar  
 
 
Components: 
 nvm-wrapper-plugin  
 
 
Created: 
 2016/Dec/07 3:58 AM  
 
 
Environment: 
 NVM_IOJS_ORG_MIRROR  https://npm.taobao.org/mirrors/iojs   NVM_NODEJS_ORG_MIRROR  https://npm.taobao.org/mirrors/node   PHANTOMJS_CDNURL  https://npm.taobao.org/mirrors/phantomjs   SASS_BINARY_SITE  https://npm.taobao.org/mirrors/node-sass  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 gu cong  
 

  
 
 
 
 

 
 ``` bash 1:49:25 curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 11:49:25 Binary download from https://nodejs.org/dist/v6.9.2/node-v6.9.2.tar.xz failed, trying source. 11:49:25 grep: /root/.nvm/.cache/src/node-v6.9.2/node-v6.9.2.tar.xz: No such file or directory 11:49:25 Provided file to checksum does not exist. 11:49:25 nvm: install v6.9.2 failed! ``` I need to download node from mirror, but Jenkins still download from the official website.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  

[JIRA] (JENKINS-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)

[li...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-40071  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)   
 

  
 
 
 
 

 
 Hi [~lhostec], You mean no test in the project? Then what I suggest  you 've built in your job? What test result did  to contact HPE support to report a case, cause  the  upload step tried  issue seems goes into ALM side, need  to  upload?What build steps have you configured in your job? Where did  analyze  the  junit result xml file came from?  ALM log.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC

[li...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-32004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HP Automation Tools Unable to Export Job Results to QC   
 

  
 
 
 
 

 
 Your issue seems goes into ALM side, need to analyze the QC log to find out why. I suggest you to contact HPE support to report a case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-23271) Intermittent Invalid Object ID in remoting module

[andrew.paul.g...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray commented on  JENKINS-23271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent Invalid Object ID in remoting module   
 

  
 
 
 
 

 
 Should this now be resolved with release of 2.35?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)

[li...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-40071  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)   
 

  
 
 
 
 

 
 Hi LHoste Cedric, You mean no test in the project? Then what you've built in your job? What test result did the upload step tried to upload? What build steps have you configured in your job? Where did the junit result xml file came from?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39861) Jenkinsfile path of Multibranch pipeline

[jenk...@johnnado.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee commented on  JENKINS-39861  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile path of Multibranch pipeline
 

  
 
 
 
 

 
 Users, watch out for the problem I reported in JENKINS-40267.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory

[jenk...@johnnado.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40267  
 
 
  Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory   
 

  
 
 
 
 

 
Change By: 
 John McGehee  
 

  
 
 
 
 

 
 Without _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins does clone in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace.  That's all for the bug report.  I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.If you first do *not* use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory.  Pretty darn hard to diagnose...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  

[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory

[jenk...@johnnado.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40267  
 
 
  Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Dec/07 1:44 AM  
 
 
Environment: 
 Jenkins ver. 2.19.2  Pipeline 2.4  Pipeline: Multibranch 2.9  Ubuntu 16 LTS  
 
 
Priority: 
  Major  
 
 
Reporter: 
 John McGehee  
 

  
 
 
 
 

 
 Without Additional Behaviors > Check out to a sub-directory, Jenkins can find my Jenkinsfile. If I add Additional Behaviors > Check out to a sub-directory, Jenkins does clone in the specified directory, but it still looks for Jenkinsfile at the top of the workspace. That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation. If you first do not use Additional Behaviors > Check out to a sub-directory a Jenkinsfile will be placed at the top of the workspace, and everything will work as expected. Then if you start using Additional Behaviors > Check out to a sub-directory, Jenkins will forever use your old Jenkinsfile that remains at the top of the workspace--Jenkins will not see any updates to the Jenkinsfile that now appears in the sub-directory. Pretty darn hard to diagnose...  
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-36795) pipeline support for UFT

[jackze...@msn.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 jack zhao commented on  JENKINS-36795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipeline support for UFT   
 

  
 
 
 
 

 
 we are going through last QA cycle, new plugin version with pipeline support will be released once it is done.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline

[derek...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 DEREK LU commented on  JENKINS-38670  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ability to enter build notes/parameters for a Manual step in the pipeline   
 

  
 
 
 
 

 
 I did uploaded three screenshots from my workaround when I open this request. Please see the attachment of the  One is to configure the ability;  Another one is a button/link in the pipeline job to popup a window (job as work around) to enter a note The third one is the job to create the note. I put the links of the screenshots here: https://issues.jenkins-ci.org/secure/attachment/34222/Build_note_config_option.jpg https://issues.jenkins-ci.org/secure/attachment/34218/Build_note_for_manual_build.jpg https://issues.jenkins-ci.org/secure/attachment/34221/popup_from_build_note_link.jpg It would be nice if the entering note feature is part of the job itself rather than a separated job like I did in the workaround. Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40158) Open Blue Ocean button is shown even after uninstalling the blueocean-beta plugin from jenkins

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please re-open if you are able to provide more information  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40158  
 
 
  Open Blue Ocean button is shown even after uninstalling the blueocean-beta plugin from jenkins   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39907) Github pull requests gets unproper statuses url link

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39907  
 
 
  Github pull requests gets unproper statuses url link   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 frank  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) API to list available tools for the Editor

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  API to list available tools for the Editor   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Component/s: 
 pipeline-model-definition-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) API to list available tools for the Editor

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Keith Zantow  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  API to list available tools for the Editor   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Andrew Bayer Keith Zantow  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) API to list available tools for the Editor

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  API to list available tools for the Editor   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 As a user of a visual editor, I would like to be offered a list of tools that are available to be used with the tool installer.  *In Scope** New REST endpoint in the editor that allows configured tools to be enumerated over.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) API to list available tools for the Editor

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  API to list available tools for the Editor   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Issue Type: 
 New Feature Task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) API to list available tools for the Editor

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  API to list available tools for the Editor   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Summary: 
 Provide API to  list  of installable  available  tools  for the Editor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[pw...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf commented on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 Why do you say it's a long shot, Michael Neale? It's something we flagged to do for improving Pipeline and I think this one is pretty important, even with PMD. If any step fails on the backend we need to make sure the error reporting is good.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)

[ebrahim.mosh...@cognitoiq.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ebrahim Moshaya commented on  JENKINS-37599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)   
 

  
 
 
 
 

 
 I have the same issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline

[alv...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Alvizu commented on  JENKINS-38670  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ability to enter build notes/parameters for a Manual step in the pipeline   
 

  
 
 
 
 

 
 I'm not sure I follow specifically where. Can you include a screenshot with a red X or whatever of what screen / UI you'd like to see them under  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline

[derek...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 DEREK LU commented on  JENKINS-38670  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ability to enter build notes/parameters for a Manual step in the pipeline   
 

  
 
 
 
 

 
 Dan, Thanks for looking into this. As long as the notes can be accessed in the job at run/build time, it should be good enough, as we can add steps in the job to store the notes.  In my workaround (with a separated job), I wrote scripts to save the notes/comments into files then compose them into an HTML file, then move the html file under user Content for viewing. I downloaded https://github.com/jenkinsci/build-pipeline-plugin/tree/JENKINS-38670. after buit and installed, I didn't see note entering ability in the build pipeline, so I guess the change for the feature is not in yet. Thanks. Derek  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40266) Allow override UserProperty.setUser(User)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40266  
 
 
  Allow override UserProperty.setUser(User)   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40266) Allow override UserProperty.setUser(User)

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40266  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow override UserProperty.setUser(User)   
 

  
 
 
 
 

 
 Code changed in jenkins User: Kanstantsin Shautsou Path: core/src/main/java/hudson/model/UserProperty.java test/src/test/java/hudson/model/UserPropertyTest.java test/src/test/resources/hudson/model/UserPropertyTest/SetUserUserProperty/config.jelly test/src/test/resources/hudson/model/UserPropertyTest/nestedUserReference/config.xml test/src/test/resources/hudson/model/UserPropertyTest/nestedUserReference/users/nestedUserReference/config.xml http://jenkins-ci.org/commit/jenkins/9172bca30fbdfc2478ccb60458dd397ba6b1df55 Log: [FIX JENKINS-40266] Allow override UserProperty.setUser(User) (#2655) UserProperty may contain nested objects that depend on User.  On User reconfiguration setUser(User) is called so it should be non-final to have ability override it and update references in nested objects. Signed-off-by: Kanstantsin Shautsou   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-17340) Environment variables fail to get translated when encountered as part of a command execution.

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-17340  
 
 
  Environment variables fail to get translated when encountered as part of a command execution.   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Hi,I am using Jenkins(v1.506) to create a build automation for Tivoli Omnibus Netcool v7.1 on a Solaris v10 machine.When I try to execute the Probe rules syntax check command '/opt/netcool/omnibus/probes/nco_p_syntax -rulesfile $NC_RULES_HOME/snmptrap.rules -server WAOSCV1', in which $NC_RULES_HOME is an environment variable '/opt/netcool/etc/rules/'. This enviroment variable is set using 'envinject' plugin. The command is executed using publish-over-ssh pluginsThe enviorment variable $NC_RULES_HOME is converted as '/opt/netcool/etc/rules/' in the given command, but when the files are read as part of the 'nco_p_syntax' command, the $NC_RULES_HOME is not decoded to '/opt/netcool/etc/rules/'. PFB the console output.Started by user anonymous[EnvInject] - Loading node environment variables.Building in workspace C:\Program Files\Jenkins\workspace\sytaxcheck2[EnvInject] - Executing scripts and injecting environment variables after the SCM step.[EnvInject] - Injecting as environment variables the properties content NC_RULES_HOME=/opt/netcool/etc/rules[EnvInject] - Variables injected successfully.SSH: Connecting from host  [TVMATP230977D]  HOST SSH: Connecting with configuration  [ssweb0034  SERVER . nsatest . in . telstra.com.au] ... SSH: EXEC: STDOUT/STDERR from command [/opt/netcool/omnibus/probes/nco_p_syntax -rulesfile /opt/netcool/etc/rules/snmptrap.rules -server WAOSCV1] ...03/25/13 19:41:28: Warning: Failed to load properties file : No such file or directory03/25/13 19:41:28: Information: Connecting ...03/25/13 19:41:28: Information: Checking rules file ...03/25/13 19:41:28: Debug: Reading /opt/netcool/etc/rules/snmptrap.rules03/25/13 19:41:28: Debug: Plain text rules file detected.03/25/13 19:41:28: Error: Rules file '/opt/netcool/etc/rules/snmptrap.rules' line 98: Failed to read lookup table file '$NC_RULES_HOME/include-snmptrap/CorrScore.snmptrap.lookup'03/25/13 19:41:28: Information: Falling back to previous rules file.03/25/13 19:41:28: Error: Error(s) in rules file03/25/13 19:41:28: Information: Disconnecting ...03/25/13 19:41:28: Warning: Disconnect malfunction - continuing shutdown anywaySSH: EXEC: completed after 811 msSSH: Disconnecting configuration  [ssweb0034  SERVER . nsatest . in . telstra.com.au] ... ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [2]]Build step 'Send files or execute commands over SSH' changed build result to UNSTABLEFinished: UNSTABLE  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-40266) Allow override UserProperty.setUser(User)

[gentoo.inte...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kanstantsin Shautsou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40266  
 
 
  Allow override UserProperty.setUser(User)   
 

  
 
 
 
 

 
Change By: 
 Kanstantsin Shautsou  
 

  
 
 
 
 

 
 UserProperty may contain nested objects that depend on User.On User reconfiguration setUser(User) is called so it should be non-final to have ability override it and update references in nested objects.I want store some configs in nested classes without messing all logic in UserProperty class. https://github.com/jenkinsci/jenkins/pull/2655  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40266) Allow override UserProperty.setUser(User)

[gentoo.inte...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kanstantsin Shautsou created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40266  
 
 
  Allow override UserProperty.setUser(User)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kanstantsin Shautsou  
 
 
Components: 
 core  
 
 
Created: 
 2016/Dec/06 11:47 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kanstantsin Shautsou  
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/2655  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

[JIRA] (JENKINS-40265) Promotion badge icon not showing after jenkins latest update

[sgabr...@brainfuse.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Gabriel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40265  
 
 
  Promotion badge icon not showing after jenkins latest update   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 promoted-builds-plugin  
 
 
Created: 
 2016/Dec/06 11:47 PM  
 
 
Environment: 
 Jenkins 2.35  
 
 
Labels: 
 plugin promoted-builds  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Samuel Gabriel  
 

  
 
 
 
 

 
 Stack trace from the logs java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at 

[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-39407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use system default Maven, Maven Settings if not specified   
 

  
 
 
 
 

 
 Yes we would need to do that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 Patrick Wolf yeah JENKINS-35308 seems a bit of a long shot right now.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40264) Add filter build queue / executors options to folders

[ow...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Wood created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40264  
 
 
  Add filter build queue / executors options to folders   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 view-filters.png  
 
 
Components: 
 cloudbees-folder-plugin  
 
 
Created: 
 2016/Dec/06 11:27 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Owen Wood  
 

  
 
 
 
 

 
 "Dashboard", "Groovy Script View", "List View" and "My View" include "Filter build queue" and the "Filter build executors" features. It would be great to see this feature in folders.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-40256) Enhancements to form controls

[cmey...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-40256  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enhancements to form controls   
 

  
 
 
 
 

 
 WIP PR: https://github.com/jenkinsci/jenkins-design-language/pull/121 Still has a little way to go but posting the PR for early feedback while I'm out this week.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) Provide list of installable tools

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide list of installable tools   
 

  
 
 
 
 

 
 James Dumay yes this is just to provide an api to enumerate them for now (this doesnt' cover the scope of the editor supporting it)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40256) Enhancements to form controls

[cmey...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40256  
 
 
  Enhancements to form controls   
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 

  
 
 
 
 

 
 Implement finalized style guide...* (x) States for Text Input, Text Area, Radio Button, Checkbox, Dropdown** Focus**  Hover**  Active** Disabled* * "Destructive"*  (x) New button styles (primary and inverted)* (x) Error states for Text Input, Text Area* (x) Sizes for Text Area, Text Input* (x) Restyle dropdown  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) Provide list of installable tools

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-40199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide list of installable tools   
 

  
 
 
 
 

 
 Michael Neale actually this is just a REST endpoint in the editor now, right? There isn't a dependency on Declarative to provide this info except what tools are configured in the model.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) Provide list of installable tools

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sounds good.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  Provide list of installable tools   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Resolution: 
 Postponed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[ashutoshmit...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashutosh Mittal commented on  JENKINS-40261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
 I will test that part. I have tried it multiple times and it is the same thing every time.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[halk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-40261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
 I'll try to look into it more, do you know if your server restarted or anything in the middle of the test? I havn't really tested that. I'll try to come up with a test case. Can you confirm your protractor tests are completing by adding another echo statement afterwards? 

 

node {
  stage "Prep Server"
  git url: '', branch: 'ashutosh-dev'
  stage "Test"
  echo 'Starting Sauce Connect...'
  sauce('452bedf5-7158-441c-bdb3-ac36d65a8704') { 
sauceconnect(options: '', useGeneratedTunnelIdentifier: false, verboseLogging: true) {
  echo 'Starting testing with Protractor...'
  sh "/usr/bin/protractor cucumberSauceConf.js --cucumberOpts.tags='@oaoSmoke'" 
  echo 'Finished testing with Protractor...'
}
  }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40199) Provide list of installable tools

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide list of installable tools   
 

  
 
 
 
 

 
 James Dumay after discussion - do we want to bring this back for future? (eg as alt config when agent isn't docker)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"

[gust...@gnustavo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gustavo Chaves commented on  JENKINS-31455  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build instability with "ISVNAuthentication provider did not provide credentials"   
 

  
 
 
 
 

 
 Isn't this related to JENKINS-29340? The simptoms seem to be the same and that issue was considered fixed on version 2.5.7 of the Subversion Plugin.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[ashutoshmit...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashutosh Mittal edited a comment on  JENKINS-40261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
 Hi [~halkeye]Below is the sample script i am usingnode {stage "Prep Server"git url: '', branch: 'ashutosh-dev'   stage "Test"echo 'Starting Sauce Connect...'sauce('452bedf5-7158-441c-bdb3-ac36d65a8704') { sauceconnect(options: '', useGeneratedTunnelIdentifier: false, verboseLogging: true) { echo 'Starting testing with Protractor...'  sh "/usr/bin/protractor cucumberSauceConf.js --cucumberOpts.tags='@oaoSmoke'"}}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[ashutoshmit...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashutosh Mittal edited a comment on  JENKINS-40261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
 Hi [~halkeye]Below is the sample script i am using node {stage "Prep Server"git url: '', branch: 'ashutosh-dev'   stage "Test"echo 'Starting Sauce Connect...'sauce('452bedf5-7158-441c-bdb3-ac36d65a8704') { sauceconnect(options: '', useGeneratedTunnelIdentifier: false, verboseLogging: true) { echo 'Starting testing with Protractor...'sh "/usr/bin/protractor cucumberSauceConf.js --cucumberOpts.tags='@oaoSmoke'"}}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[ashutoshmit...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashutosh Mittal commented on  JENKINS-40261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
 node { stage "Prep Server" git url: '', branch: 'ashutosh-dev'  stage "Test" echo 'Starting Sauce Connect...' sauce('452bedf5-7158-441c-bdb3-ac36d65a8704') {  sauceconnect(options: '', useGeneratedTunnelIdentifier: false, verboseLogging: true)  { echo 'Starting testing with Protractor...' sh "/usr/bin/protractor cucumberSauceConf.js --cucumberOpts.tags='@oaoSmoke'" }  } }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40263) Could not find credentials matching during docker build

[nikol...@nikolaus-demmel.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolaus Demmel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40263  
 
 
  Could not find credentials matching during docker build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-commons-plugin  
 
 
Created: 
 2016/Dec/06 9:05 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nikolaus Demmel  
 

  
 
 
 
 

 
 We have a jenkins job that builds a docker image from docker file using the build and publish and then pushes it to a private docker registry. It used to work fine. Now there were some updates to the DTR. We didn't touch the Jenkins job configuration, but I now get the following error when running the builds: {{ERROR: Could not find credentials matching test-docker hudson.AbortException: Could not find credentials matching test-docker at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:217) at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:204) at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:196) at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:455) at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:431) at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:373) at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311) at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:291) at com.cloudbees.dockerpublish.DockerBuilder.perform(DockerBuilder.java:262) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at 

[JIRA] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[halk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-40261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
 hi Ashutosh Mittal Can you give me a sample script that reproduces this? Reading your error log it seems like your sh/script step doesn't exit, but i'm not sure  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40262) Promotions created with job DSL are not visible

[imriz...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Imri Zvik commented on  JENKINS-40262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Promotions created with job DSL are not visible   
 

  
 
 
 
 

 
 It seems like https://github.com/jenkinsci/promoted-builds-plugin/pull/76 and https://github.com/jenkinsci/promoted-builds-plugin/pull/82 didn't take each other into account.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40237) provide a list of suitable credentials available to a pipeline

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Duplicates JENKINS-38848. We already have this in the Blue Ocean REST API.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40237  
 
 
  provide a list of suitable credentials available to a pipeline   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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 

[JIRA] (JENKINS-40199) Provide list of installable tools

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Postponed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Tools are something we don't want to encourage in the new world with the Editor for the time being.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  Provide list of installable tools   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Postponed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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, 

[JIRA] (JENKINS-40199) Provide list of installable tools

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40199  
 
 
  Provide list of installable tools   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Minor Trivial  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40262) Promotions created with job DSL are not visible

[imriz...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Imri Zvik updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40262  
 
 
  Promotions created with job DSL are not visible   
 

  
 
 
 
 

 
Change By: 
 Imri Zvik  
 

  
 
 
 
 

 
 I have a very simple promotion:{code}  promotion {  name('Production')  icon("star-gold")   visible(true)   conditions {  manual('teamA,teamB')  }  actions {copyArtifacts('$PROMOTED_JOB_NAME') {  includePatterns('envInject.properties')  buildSelector { buildNumber('$PROMOTED_NUMBER')  } }  downstreamParameterized {trigger("Dist-To-Prod"){ block { buildStepFailure('never') failure('FAILURE') unstable('UNSTABLE') } parameters { propertiesFile('envInject.properties',true) }}  }  }  }{code}When I go to the generated job promotion status, I don't see anything.If I go to the job configuration, and without changing anything, click on "Save", the promotions become visible.Looking the promotion XML, it seems like the isVisible element is missing.Am I missing something?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 
   

[JIRA] (JENKINS-40262) Promotions created with job DSL are not visible

[imriz...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Imri Zvik created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40262  
 
 
  Promotions created with job DSL are not visible   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin, promoted-builds-plugin  
 
 
Created: 
 2016/Dec/06 8:33 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Imri Zvik  
 

  
 
 
 
 

 
 I have a very simple promotion: 

 

  promotion {
  name('Production')
  icon("star-gold")
  visible(true)
  conditions {
  manual('teamA,teamB')
  }
  actions {
copyArtifacts('$PROMOTED_JOB_NAME') {
  includePatterns('envInject.properties')
  buildSelector {
  buildNumber('$PROMOTED_NUMBER')
  }
 }
  downstreamParameterized {
trigger("Dist-To-Prod"){
  block {
  buildStepFailure('never')
  failure('FAILURE')
  unstable('UNSTABLE')
  }
  parameters {
propertiesFile('envInject.properties',true)
  }
}
  }
  }
  }
 

 When I go to the generated job promotion status, I don't see anything. If I go to the job configuration, and without changing anything, click on "Save", the promotions become visible. Looking the promotion XML, it seems like the isVisible element is missing. Am I missing something?  
 

  
   

[JIRA] (JENKINS-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline

[roguishmount...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Schwarz commented on  JENKINS-26660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline   
 

  
 
 
 
 

 
 Hi all, I created two PRs for the git-client-plugin and the git-plugin that I believe address the issues outlined in this bug report and PR163. They are https://github.com/jenkinsci/git-plugin/pull/449 and https://github.com/jenkinsci/git-client-plugin/pull/222, Feel free to review and/or test them and comment on the PRs. The git-plugin PR is dependent on the git-client-PR so make sure to update the pom file in the git-plugin.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline

[roguishmount...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Schwarz edited a comment on  JENKINS-26660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline   
 

  
 
 
 
 

 
 Hi all,I created two PRs for the git-client-plugin and the git-plugin that I believe address the issues outlined in this bug report and [PR163|https://github.com/jenkinsci/git-client-plugin/pull/163]. They are https://github.com/jenkinsci/git-plugin/pull/449 and https://github.com/jenkinsci/git-client-plugin/pull/222, Feel free to review and/or test them and comment on the PRs. The git-plugin PR is dependent on the git-client - PR so make sure to update the pom file in the git-plugin.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39647) Failed to write defaultParameterValue

[sheib...@bizstream.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sterling Heibeck commented on  JENKINS-39647  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to write defaultParameterValue   
 

  
 
 
 
 

 
 Thanks! And yes, that PermaGen error has been my been. I'm in a windows environment and I have a ton of jobs and the thing keeps running into that issue. I'm working on moving everything over to pipelines, which hopefully will fix that!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39647) Failed to write defaultParameterValue

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39647  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to write defaultParameterValue   
 

  
 
 
 
 

 
 Sterling Heibeck ahh thanks for that. I think we're going to not serialize invalid actions as part of JENKINS-40088. This problem shouldn't happen in the future.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39647) Failed to write defaultParameterValue

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39647  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to write defaultParameterValue   
 

  
 
 
 
 

 
 Sterling Heibeck unrelated - looks like you need to increase your servers permgen BTW java.lang.OutOfMemoryError: PermGen space  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline

[ashutoshmit...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashutosh Mittal created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40261  
 
 
  Sauce connect process not stopping as part of Jenkins pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Gavin Mogan  
 
 
Components: 
 sauce-ondemand-plugin  
 
 
Created: 
 2016/Dec/06 8:02 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ashutosh Mittal  
 

  
 
 
 
 

 
 Hi We have Jenkins setup with no slaves and configured a job with using Jenkins pipeline but after protractor test case execution ends, sauce connect process is not stopping and it just simply hangs at that step We have to manually stop the job to close the process - eport created successfully! Aborted by anonymous Sending interrupt signal to process sh: line 1: 16950 Terminated JENKINS_SERVER_COOKIE=$jsc '/var/lib/jenkins/jobs/OAO_SauceLabs/workspace@tmp/durable-d1230cf0/script.sh' > '/var/lib/jenkins/jobs/OAO_SauceLabs/workspace@tmp/durable-d1230cf0/jenkins-log.txt' 2>&1 Aborted by anonymous Aborted by anonymous Aborted by anonymous Aborted by anonymous Aborted by anonymous Click here to forcibly terminate running steps Click here to forcibly terminate running steps Click here to forcibly terminate running steps Click here to forcibly terminate running steps Click here to forcibly terminate running steps Click here to forcibly terminate running steps [Pipeline] } Decremented process count for NSB_team, now 0 Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process Sauce Connect stopped for: NSB_team [Pipeline] // sauceconnect [Pipeline] } [Pipeline] // sauce [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Below is version information - Jenkins 1.651.3 Sauce OnDemand plugin 1.158 Pipeline: Groovy 2.4  
 

  
 
 
 
 

 

[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-38536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Execution time of parallel blocks of in-flight jobs wrong   
 

  
 
 
 
 

 
 Jochen A. Fürbacher would you be able to provide a sample Jenkinsfile that exercises the behaviour?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay edited a comment on  JENKINS-38536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Execution time of parallel blocks of in-flight jobs wrong   
 

  
 
 
 
 

 
 [~jochenafuerbacher] would you be able to provide a sample {{Jenkinsfile}} that exercises the behaviour  you are seeing ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2

[stef...@earthlingsoft.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steffen Kamp commented on  JENKINS-38608  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Null value not allowed as an environment variable: GIT_URL_2
 

  
 
 
 
 

 
 I have just encountered the same issue and found that I had erroneously configured two Git repositories and left the URL of the second one empty (probably because I clicked the "Add Repository" button after entering the URL, assuming that I had to confirm the setting). Just go to the configuration page for the project and have a look at the source code management section. I suspect you have configured two "Repositories" where one of them does not have an URL. Remove this repository and initiate the build again using a git push (or by resending the commit hook from the Bitbucket site).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[pw...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf commented on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 Do we have some negative tests that can fail a build more disastrously than an error step? At least until we have JENKINS-35308 implemetend  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-30870) Reload Configuration from Disk - does not reload job config.xml

[asha...@linkedin.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Shafer commented on  JENKINS-30870  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Reload Configuration from Disk - does not reload job config.xml   
 

  
 
 
 
 

 
 I'm also seeing that jobs within folders are not getting reloaded. 2.19.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39335) If a failure happens outside of parallel branch it isn't shown in a stage

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If a failure happens outside of parallel branch it isn't shown in a stage   
 

  
 
 
 
 

 
 Patrick Wolf depends where the exception is thrown. For example, if its before the first stage we would attribute the failure to the first stage.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40260) Active JNLP Sessions are maintained if the JNLP Port is disabled or changed

[jh...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Hill updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40260  
 
 
  Active JNLP Sessions are maintained if the JNLP Port is disabled or changed   
 

  
 
 
 
 

 
Change By: 
 John Hill  
 
 
Summary: 
 Active JNLP Sessions are maintained if the JNLP Port is disabled  or changed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC

[lance.weit...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lance Weitzel commented on  JENKINS-32004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HP Automation Tools Unable to Export Job Results to QC   
 

  
 
 
 
 

 
 I checked and we are on version 12.50  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40260) Active JNLP Sessions are maintained if the JNLP Port is disabled

[jh...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Hill updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40260  
 
 
  Active JNLP Sessions are maintained if the JNLP Port is disabled   
 

  
 
 
 
 

 
Change By: 
 John Hill  
 
 
Summary: 
 Active JNLP Sessions are maintained if the JNLP Port is disabled  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40260) JNLP Sessions are maintained if the JNLP Port is disabled

[jh...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Hill created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40260  
 
 
  JNLP Sessions are maintained if the JNLP Port is disabled   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Dec/06 6:50 PM  
 
 
Environment: 
 2.19  Ubuntu-15.04   
 
 
Labels: 
 jenkins jnlp  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 John Hill  
 

  
 
 
 
 

 
 If a JNLP Session is active and the JNLP Port is disabled by setting "Manage Jenkins->Global Security->TCP port for JNLP agents." to 'Disable', the TCP session is maintained. Subsequent sessions no longer connect, but the active ones remain open.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-39955) REGRESSION: Re-running a failed build via re-run button from results screen breaks karaoke mode

[kzan...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow commented on  JENKINS-39955  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION: Re-running a failed build via re-run button from results screen breaks karaoke mode   
 

  
 
 
 
 

 
 FYI, using a pipeline with this script to test: 

 

def lines = """
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Pellentesque porttitor dui eget ante congue blandit.
Nullam vel purus a leo luctus accumsan nec nec risus.
Vestibulum varius mauris vel odio malesuada scelerisque.
Vivamus sed ligula ac tortor cursus faucibus elementum sit amet est.
""".split('\n');
echo "First... "
for (def i = 0; i < 30; i++) {
if (i % 5 == 0) {
stage "Stage ${i}"
}
echo lines[i%lines.length];
Thread.sleep(500);
}

throw new Exception('Oh noes, this failed so I can click re-run')
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-30011) Allow multiple instances of Post Build Scripts as a post build action

[nittanymount...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David D commented on  JENKINS-30011  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow multiple instances of Post Build Scripts as a post build action   
 

  
 
 
 
 

 
 +1 really need to be able to execute different scripts in case failure or success.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

[mmit...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Mitchell commented on  JENKINS-28492  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.   
 

  
 
 
 
 

 
 This also appears to perhaps happen "near" a failure https://issues.jenkins-ci.org/browse/JENKINS-33358  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40092) slave.jar copy via SCP fails in 2.33+

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40092  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: slave.jar copy via SCP fails in 2.33+   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/test/acceptance/plugins/ssh_slaves/SshSlaveLauncher.java src/test/java/plugins/SshSlavesPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/4c7a364b881a082ca7e715f9e15416ee93704fb4 Log: Merge pull request #234 from jglick/SshSlavesPluginTest-JENKINS-40092 JENKINS-40092 Ensuring SshSlavesPluginTest can be run Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/97a28168c585...4c7a364b881a  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38307) ATH erroneously installs detached plugins, causing needless restarts

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38307  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ATH erroneously installs detached plugins, causing needless restarts   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: src/test/java/plugins/SshSlavesPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/a5ae9dc40e32dfd8847c3d63efa9a315a1fe21e9 Log: JENKINS-38307 Pending #191, make sure we are installing recent versions of plugins, not whatever old stuff happened to be in the detached list.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40259) The plugin stop working at unity 5.5

[silve...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 axx silvera created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40259  
 
 
  The plugin stop working at unity 5.5   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 lacostej  
 
 
Components: 
 unity3d-plugin  
 
 
Created: 
 2016/Dec/06 5:59 PM  
 
 
Environment: 
 Jenkins ver. 2.35   Unity3d plugin 1.3  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 axx silvera  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

 

[JIRA] (JENKINS-39220) ECS Cluster drop-down does not show more than 100 ecs clusters

[nicolas.del...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas De Loof commented on  JENKINS-39220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ECS Cluster drop-down does not show more than 100 ecs clusters   
 

  
 
 
 
 

 
 I assume the ECS API only return a limited number of values. But I wonder you really need this to list 260 clusters ! Don't you use fine grained IAM profile to access your AWS ressources ? Sounds a security issue you have a single account configured in Jenkins that can access them all.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39594) Frequent, intermittent "Failed to deploy artifacts: Could not transfer artifact" errors when uploading to Nexus 3

[pskumar...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Suresh Kumar edited a comment on  JENKINS-39594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Frequent, intermittent "Failed to deploy artifacts: Could not transfer artifact" errors when uploading to Nexus 3   
 

  
 
 
 
 

 
 I was able to replicate the issue, when continuously trying to upload artifacts, in some cases with no reason failing to upload artifacts.And now changed the connector, given a trail run with artifact size 50MB and uploading artifacts every 2 mins, didn't failed. Will keep on some more time observation.Mean time the code fix is available in the below commit, please give a try and let me know the feedback.https://github.com/jenkinsci/nexus-artifact-uploader-plugin/commit/65aa6da1290ddc396adb2317c3b9744ad66d5c23https://jenkins.ci.cloudbees.com/job/plugins/job/nexus-artifact-uploader-plugin/sp.sd$nexus-artifact-uploader/lastSuccessfulBuild/artifact/sp.sd/nexus-artifact-uploader/2.9-SNAPSHOT/nexus-artifact-uploader-2.9-SNAPSHOT.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39355) API improvements based on real-world implementation and usage

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: API improvements based on real-world implementation and usage   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephen Connolly Path: README.md docs/consumer.adoc docs/implementation.adoc pom.xml src/main/java/jenkins/scm/api/MethodUtils.java src/main/java/jenkins/scm/api/SCM2.java src/main/java/jenkins/scm/api/SCMCategory.java src/main/java/jenkins/scm/api/SCMEvent.java src/main/java/jenkins/scm/api/SCMEventListener.java src/main/java/jenkins/scm/api/SCMFile.java src/main/java/jenkins/scm/api/SCMFileSystem.java src/main/java/jenkins/scm/api/SCMHead.java src/main/java/jenkins/scm/api/SCMHeadCategory.java src/main/java/jenkins/scm/api/SCMHeadEvent.java src/main/java/jenkins/scm/api/SCMHeadMixinEqualityGenerator.java src/main/java/jenkins/scm/api/SCMHeadObserver.java src/main/java/jenkins/scm/api/SCMNavigator.java src/main/java/jenkins/scm/api/SCMNavigatorDescriptor.java src/main/java/jenkins/scm/api/SCMNavigatorEvent.java src/main/java/jenkins/scm/api/SCMNavigatorOwner.java src/main/java/jenkins/scm/api/SCMNavigatorOwners.java src/main/java/jenkins/scm/api/SCMProbe.java src/main/java/jenkins/scm/api/SCMProbeStat.java src/main/java/jenkins/scm/api/SCMRevisionAction.java src/main/java/jenkins/scm/api/SCMSource.java src/main/java/jenkins/scm/api/SCMSourceCategory.java src/main/java/jenkins/scm/api/SCMSourceCriteria.java src/main/java/jenkins/scm/api/SCMSourceDescriptor.java src/main/java/jenkins/scm/api/SCMSourceEvent.java src/main/java/jenkins/scm/api/SCMSourceObserver.java src/main/java/jenkins/scm/api/SCMSourceOwner.java src/main/java/jenkins/scm/api/SCMSourceOwners.java src/main/java/jenkins/scm/api/actions/ChangeRequestAction.java src/main/java/jenkins/scm/api/actions/package-info.java src/main/java/jenkins/scm/api/metadata/AvatarMetadataAction.java src/main/java/jenkins/scm/api/metadata/ContributorMetadataAction.java src/main/java/jenkins/scm/api/metadata/ObjectMetadataAction.java src/main/java/jenkins/scm/api/metadata/package-info.java src/main/java/jenkins/scm/api/mixin/ChangeRequestSCMHead.java src/main/java/jenkins/scm/api/mixin/SCMHeadMixin.java src/main/java/jenkins/scm/api/mixin/TagSCMHead.java src/main/java/jenkins/scm/api/mixin/package-info.java src/main/java/jenkins/scm/api/package-info.java src/main/java/jenkins/scm/impl/ChangeRequestSCMHeadCategory.java src/main/java/jenkins/scm/impl/NoOpProjectObserver.java src/main/java/jenkins/scm/impl/NullSCMSource.java src/main/java/jenkins/scm/impl/SCM2Notifier.java src/main/java/jenkins/scm/impl/SCM2TransientActionFactory.java src/main/java/jenkins/scm/impl/SCMTriggerListener.java src/main/java/jenkins/scm/impl/SingleSCMNavigator.java src/main/java/jenkins/scm/impl/SingleSCMSource.java src/main/java/jenkins/scm/impl/TagSCMHeadCategory.java src/main/java/jenkins/scm/impl/UncategorizedSCMHeadCategory.java src/main/java/jenkins/scm/impl/UncategorizedSCMSourceCategory.java src/main/java/jenkins/scm/impl/package-info.java src/main/resources/jenkins/scm/api/Messages.properties src/main/resources/jenkins/scm/impl/Messages.properties src/test/java/jenkins/scm/api/MessagesTest.java src/test/java/jenkins/scm/api/SCMCategoryTest.java src/test/java/jenkins/scm/api/SCMEventTest.java src/test/java/jenkins/scm/api/SCMHeadObserverTest.java src/test/java/jenkins/scm/api/SCMHeadTest.java src/test/java/jenkins/scm/impl/ChangeRequestSCMHeadCategoryTest.java src/test/java/jenkins/scm/impl/MessagesTest.java src/test/java/jenkins/scm/impl/NoOpProjectObserverTest.java src/test/java/jenkins/scm/impl/NullSCMSourceTest.java src/test/java/jenkins/scm/impl/SingleSCMNavigatorTest.java src/test/java/jenkins/scm/impl/SingleSCMSourceTest.java 

[JIRA] (JENKINS-39594) Frequent, intermittent "Failed to deploy artifacts: Could not transfer artifact" errors when uploading to Nexus 3

[pskumar...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Suresh Kumar commented on  JENKINS-39594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Frequent, intermittent "Failed to deploy artifacts: Could not transfer artifact" errors when uploading to Nexus 3   
 

  
 
 
 
 

 
 I was able to replicate the issue, when continuously trying to upload artifacts, in some cases with no reason failing to upload artifacts. And now changed the connector, given a trail run with artifact size 50MB and uploading artifacts every 2 mins, didn't failed. Will keep on some more time observation. Mean time the code fix is available in the below commit, please give a try and let me know the feedback. https://github.com/jenkinsci/nexus-artifact-uploader-plugin/commit/65aa6da1290ddc396adb2317c3b9744ad66d5c23   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-30058) Support Maven Core Extensions

[bochenski.kuba+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski commented on  JENKINS-30058  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support Maven Core Extensions   
 

  
 
 
 
 

 
 This is a core maven feature – another one that is missing. Is the Maven integration completely useless? https://javaadventure.blogspot.com/2013/11/jenkins-maven-job-type-considered-evil.html  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-30058) Support Maven Core Extensions

[bochenski.kuba+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30058  
 
 
  Support Maven Core Extensions   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 
 
Issue Type: 
 New Feature Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.