[JIRA] (JENKINS-36465) Unable to determine Maven version

2016-07-06 Thread srijin...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 srijini s created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36465  
 
 
  Unable to determine Maven version   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Eyal Ben Moshe  
 
 
Components: 
 artifactory-plugin  
 
 
Created: 
 2016/Jul/06 7:42 AM  
 
 
Environment: 
 centos 6  Jenkins 1.651.3  Artifactory plugin 2.5.1  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 srijini s  
 

  
 
 
 
 

 
 Building in workspace /var/lib/jenkins/workspace/JFrog sample > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/JFrogDev/project-examples.git # timeout=10 Fetching upstream changes from https://github.com/JFrogDev/project-examples.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/JFrogDev/project-examples.git +refs/heads/:refs/remotes/origin/ > git rev-parse refs/remotes/origin/master^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit}  # timeout=10 Checking out Revision 8b6c06a4bb903bdfb831f740da364dedf82adb75 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 8b6c06a4bb903bdfb831f740da364dedf82adb75 > git rev-list 8b6c06a4bb903bdfb831f740da364dedf82adb75 # timeout=10 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.RuntimeException: Unable to determine Maven version at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:167) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:100) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModu

[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config

2016-07-06 Thread croesusk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Croesus Kall commented on  JENKINS-27548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sporadic IOException: Failed to persist config   
 

  
 
 
 
 

 
 How does one go about finding which plugin alters the property? I tried this in the plugin folder for jenkins: 

 

grep -ir 'org.xml.sax.driver' *
 

 And got this: 

 

Binary file analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar matches
Binary file build-pipeline-plugin/WEB-INF/lib/xercesImpl-2.9.1.jar matches
Binary file findbugs/WEB-INF/lib/library-2.0.4.jar matches
Binary file selenium/WEB-INF/lib/selenium-server-standalone-2.41.0.jar matches
 

 I am guessing the 'xercedImpl' dependencies are ok, but perhaps findbugs or selenium might be the culprits ?  
 

  
 
 
 
 

 
 
 

 
 
 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-35024) Parametrized build doesn't set environment variables in Mutli-configuration projects

2016-07-06 Thread ashish_b...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashish Behl resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Thanks. the problem was definitely with credentials plugin. But after upgrading the credentials plugin, now passing credentials to shell script as job parameters does not work. crashes when adding "use secret texts -> bindings" Marking this issue as resolved.  Thanks for the help and a quick answer.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35024  
 
 
  Parametrized build doesn't set environment variables in Mutli-configuration projects   
 

  
 
 
 
 

 
Change By: 
 Ashish Behl  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 

[JIRA] (JENKINS-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Open Closed  
 
 
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-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed 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-29716) Incorrect Execution Results when using TestNG class name results seeking strategy

2016-07-06 Thread arnewohl...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arne Wohletz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29716  
 
 
  Incorrect Execution Results when using TestNG class name results seeking strategy   
 

  
 
 
 
 

 
Change By: 
 Arne Wohletz  
 
 
Attachment: 
 TestingResultsXml.png  
 
 
Attachment: 
 Testlink_Java Class.png  
 

  
 
 
 
 

 
 
 

 
 
 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-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Reopened Closed  
 
 
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-35991) Control of BB PR behavior on multi-branch pipelines

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Let's keep this feature described in JENKINS-36283. Closing this.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35991  
 
 
  Control of BB PR behavior on multi-branch pipelines   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Open Closed  
 
 
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://gro

[JIRA] (JENKINS-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Reopened 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-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed 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-29716) Incorrect Execution Results when using TestNG class name results seeking strategy

2016-07-06 Thread arnewohl...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arne Wohletz commented on  JENKINS-29716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Incorrect Execution Results when using TestNG class name results seeking strategy   
 

  
 
 
 
 

 
 Hello Bruno, thanks for for quick response. I found the solution which works for me - the class name that is used in the example is actually 'jenkins.plugins.testlink.examples.TestCurrentTime' whereas in TestLink I used 'hudson.plugins.testlink.examples.TestCurrentTime' as it said in the tutorial PDF (page 15). Now it works perfectly!Maybe that also helps voss qa.  
 

  
 
 
 
 

 
 
 

 
 
 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-33865) Double Build on Multibranch Pipeline with open PR

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33865  
 
 
  Double Build on Multibranch Pipeline with open PR   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-35991) Control of BB PR behavior on multi-branch pipelines

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35991  
 
 
  Control of BB PR behavior on multi-branch pipelines   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Resolution: 
 Fixed  
 
 
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-35991) Control of BB PR behavior on multi-branch pipelines

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35991  
 
 
  Control of BB PR behavior on multi-branch pipelines   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed 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-35991) Control of BB PR behavior on multi-branch pipelines

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35991  
 
 
  Control of BB PR behavior on multi-branch pipelines   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Reopened 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-35991) Control of BB PR behavior on multi-branch pipelines

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35991  
 
 
  Control of BB PR behavior on multi-branch pipelines   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-34931) Build merge commit instead of PR head

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34931  
 
 
  Build merge commit instead of PR head   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Resolution: 
 Fixed  
 
 
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-36283) PR builds customization

2016-07-06 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz commented on  JENKINS-36283  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PR builds customization   
 

  
 
 
 
 

 
 All cleared up 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-36466) Update env-inject-lib to 1.24

2016-07-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36466  
 
 
  Update env-inject-lib to 1.24   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 envinject-plugin  
 
 
Created: 
 2016/Jul/06 8:21 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Félix Belzunce Arcos  
 

  
 
 
 
 

 
 Env-inject-lib 1.23 was using hudson.matrix.MatrixRun directly, but with a recent jenkins-core matrix plugin is not anymore in the jenkins-core but on a separate plugin. See: https://github.com/jenkinsci/envinject-lib/pull/7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-36466) Update env-inject-lib to 1.24

2016-07-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos started work on  JENKINS-36466  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Félix Belzunce Arcos  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-36458) Support shared system groovy script

2016-07-06 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36458  
 
 
  Support shared system groovy script   
 

  
 
 
 
 

 
Change By: 
 Dominik Bartholdi  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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-36467) Update env-inject-lib to 1.24

2016-07-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos started work on  JENKINS-36467  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Félix Belzunce Arcos  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-36467) Update env-inject-lib to 1.24

2016-07-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36467  
 
 
  Update env-inject-lib to 1.24   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 buildcontext-capture-plugin  
 
 
Created: 
 2016/Jul/06 8:26 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Félix Belzunce Arcos  
 

  
 
 
 
 

 
 Env-inject-lib 1.23 was using hudson.matrix.MatrixRun directly, but with a recent jenkins-core matrix plugin is not anymore in the jenkins-core but on a separate plugin. See: https://github.com/jenkinsci/envinject-lib/pull/7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-36239) StackOverflowError in plugin manager on 1.596.1

2016-07-06 Thread i...@ncipher.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Norton commented on  JENKINS-36239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StackOverflowError in plugin manager on 1.596.1   
 

  
 
 
 
 

 
 I get this on 1.596.3 with the SVN plugin fully updated and no workflow plugins at 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-36211) Karaoke mode: User should follow along with stages when watching a pipeline result execute

2016-07-06 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler commented on  JENKINS-36211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Karaoke mode: User should follow along with stages when watching a pipeline result execute   
 

  
 
 
 
 

 
 Michael Neale yeah kind of, the problem is when you want to view e.g an earlier node you request something like http://localhost:8080/jenkins/blue/organizations/jenkins/steps/detail/steps/63/pipeline/5  the 5 on the end is the "node" id, now to be able to follow alone even on that url, is we test whether the url param node is smaller then nodeReducer and if so use the nodeReducer for the steps. Anyway if we not following but have a running job  
 

  
 
 
 
 

 
 
 

 
 
 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-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs

2016-07-06 Thread outtierb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bert Outtier commented on  JENKINS-36375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs   
 

  
 
 
 
 

 
 Same issue here. change-assembly-version-plugin 1.5.1 Linux jenkins master Windows 8.1 build node.  
 

  
 
 
 
 

 
 
 

 
 
 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-36439) Evolve more composable redux store code patterns

2016-07-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY started work on  JENKINS-36439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-36409) Support Email Extension Plugin

2016-07-06 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Slated for next week.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36409  
 
 
  Support Email Extension Plugin   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
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-36468) Tasks fail to run on ECS after upgrade to 1.4

2016-07-06 Thread l...@vvoosh.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Silva created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36468  
 
 
  Tasks fail to run on ECS after upgrade to 1.4   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jan Roehrich  
 
 
Components: 
 amazon-ecs-plugin  
 
 
Created: 
 2016/Jul/06 8:55 AM  
 
 
Environment: 
 Jenkins 2.11  ECS-plugin 1.4  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Luis Silva  
 

  
 
 
 
 

 
 With the latest plugin version (1.4) my tasks fail to run on the ecs slaves. They sit waiting for executors forever. I made sure I had two servers with plenty of resources connected to ECS.  It looks like the task is assigned to a node but they immediately disconnects. After downgrading to version 1.3 is all started working perfectly again. I tested it with the same number of servers, same tasks, same jenkins versions, etc. See the logs below for both versions. Version 1.4 failures: 
 
Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 3,767mb of free memory. 3,000mb are required Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 1,024 units of free cpu. 512 units are required Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback call INFO: Created Slave: JenkinsSlavesECS-16e94238750e85 Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTask WARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure to run task with definition arn:aws:ecs:eu-west-1:AWS_ACC:task-definition/je

[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4

2016-07-06 Thread l...@vvoosh.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Silva updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36468  
 
 
  Tasks fail to run on ECS after upgrade to 1.4   
 

  
 
 
 
 

 
Change By: 
 Luis Silva  
 

  
 
 
 
 

 
 With the latest plugin version (1.4) my tasks fail to run on the ecs slaves. They sit waiting for executors forever. I made sure I had two servers with plenty of resources connected to ECS. It looks like the task is assigned to a node but then immediately disconnects.After downgrading to version 1.3  is  it  all started working perfectly again.I tested it with the same number of servers, same tasks, same jenkins versions, etc.See the logs below for both versions.Version 1.4 failures:{quote}Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 3,767mb of free memory. 3,000mb are requiredJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 1,024 units of free cpu. 512 units are requiredJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Created Slave: JenkinsSlavesECS-16e94238750e85Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTaskWARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure to run task with definition arn:aws:ecs:eu-west-1:AWS_ACC:task-definition/jenkins-slave:78 on ECS cluster arn:aws:ecs:eu-west-1:AWS_ACC:cluster/JenkinsSlavesJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTaskWARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure reason=RESOURCE:MEMORY, arn=arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/e949c164-1e0c-4e9c-85c3-36b035b5b601Jul 06, 2016 8:37:43 AM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave BackendTests failed to launchjava.lang.IllegalStateException: ECS Slave JenkinsSlavesECS-16e9422efc9bc3 (ecs task arn:aws:ecs:eu-west-1:AWS_ACC:task/b6621ca4-b397-46ad-9659-9c6fe1633b32) not connected since 7/6/16 8:37 AM secondsat com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:219)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)at java.util.concurrent.FutureTask.run(FutureTask.java:262)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Jul 06, 2016 8:37:43 AM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave BackendTests failed to launchhudson.AbortException: Failed to run slave container JenkinsSlavesECS-16e94238750e85at com.cloudbees.jenkins.plugins.amazonecs

[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4

2016-07-06 Thread l...@vvoosh.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Silva updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36468  
 
 
  Tasks fail to run on ECS after upgrade to 1.4   
 

  
 
 
 
 

 
Change By: 
 Luis Silva  
 

  
 
 
 
 

 
 With the latest plugin version (1.4) my tasks fail to run on the ecs slaves. They sit waiting for executors forever. I made sure I had two servers with plenty of resources connected to ECS. It looks like the task is assigned to a node but  they  then  immediately disconnects.After downgrading to version 1.3 is all started working perfectly again.I tested it with the same number of servers, same tasks, same jenkins versions, etc.See the logs below for both versions.Version 1.4 failures:{quote}Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 3,767mb of free memory. 3,000mb are requiredJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 1,024 units of free cpu. 512 units are requiredJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Created Slave: JenkinsSlavesECS-16e94238750e85Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTaskWARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure to run task with definition arn:aws:ecs:eu-west-1:AWS_ACC:task-definition/jenkins-slave:78 on ECS cluster arn:aws:ecs:eu-west-1:AWS_ACC:cluster/JenkinsSlavesJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTaskWARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure reason=RESOURCE:MEMORY, arn=arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/e949c164-1e0c-4e9c-85c3-36b035b5b601Jul 06, 2016 8:37:43 AM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave BackendTests failed to launchjava.lang.IllegalStateException: ECS Slave JenkinsSlavesECS-16e9422efc9bc3 (ecs task arn:aws:ecs:eu-west-1:AWS_ACC:task/b6621ca4-b397-46ad-9659-9c6fe1633b32) not connected since 7/6/16 8:37 AM secondsat com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:219)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)at java.util.concurrent.FutureTask.run(FutureTask.java:262)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Jul 06, 2016 8:37:43 AM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave BackendTests failed to launchhudson.AbortException: Failed to run slave container JenkinsSlavesECS-16e94238750e85at com.cloudbees.jenkins.plugins.amazone

[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4

2016-07-06 Thread l...@vvoosh.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Silva updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36468  
 
 
  Tasks fail to run on ECS after upgrade to 1.4   
 

  
 
 
 
 

 
Change By: 
 Luis Silva  
 

  
 
 
 
 

 
 With the latest plugin version (1.4) my tasks fail to run on the ecs slaves. They sit waiting for executors forever. I made sure I had two servers with plenty of resources connected to ECS. It looks like the task is assigned to a node but then immediately disconnects.After downgrading to version 1.3 it all started working perfectly again.I tested it with the same number of servers, same tasks, same jenkins versions, etc.See the logs below for both versions.Version 1.4 failures:{quote}Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 3,767mb of free memory. 3,000mb are requiredJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/ceb4eece-2abe-4f19-aad3-8d3cbd18a7ee has 1,024 units of free cpu. 512 units are requiredJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Created Slave: JenkinsSlavesECS-16e94238750e85Jul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTaskWARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure to run task with definition arn:aws:ecs:eu-west-1:AWS_ACC:task-definition/jenkins-slave:78 on ECS cluster arn:aws:ecs:eu-west-1:AWS_ACC:cluster/JenkinsSlavesJul 06, 2016 8:37:33 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService runEcsTaskWARNING: Slave JenkinsSlavesECS-16e94238750e85 - Failure reason=RESOURCE:MEMORY, arn=arn:aws:ecs:eu-west-1:AWS_ACC:container-instance/e949c164-1e0c-4e9c-85c3-36b035b5b601Jul 06, 2016 8:37:43 AM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave BackendTests failed to launchjava.lang.IllegalStateException: ECS Slave JenkinsSlavesECS-16e9422efc9bc3 (ecs task arn:aws:ecs:eu-west-1:AWS_ACC:task/b6621ca4-b397-46ad-9659-9c6fe1633b32) not connected since 7/6/16 8:37 AM secondsat com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:219)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)at java.util.concurrent.FutureTask.run(FutureTask.java:262)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Jul 06, 2016 8:37:43 AM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave BackendTests failed to launchhudson.AbortException: Failed to run slave container JenkinsSlavesECS-16e94238750e85at com.cloudbees.jenkins.plugins.amazonecs.ECSSe

[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza assigned an issue to Raul Arabaolaza  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31738  
 
 
  Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Assignee: 
 Andres Rodriguez Raul Arabaolaza  
 

  
 
 
 
 

 
 
 

 
 
 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-34880) When using multiple updateSites, tool installer download fails if one UC is missing installers

2016-07-06 Thread thomas.wikst...@tieto.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Wikström commented on  JENKINS-34880  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When using multiple updateSites, tool installer download fails if one UC is missing installers   
 

  
 
 
 
 

 
 We experience the same problem in version 1.651.3, could the solution (JENKINS-34880) be implemented there as well? Regards /Thomas  
 

  
 
 
 
 

 
 
 

 
 
 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-36211) Karaoke mode: User should follow along with stages when watching a pipeline result execute

2016-07-06 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler commented on  JENKINS-36211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Karaoke mode: User should follow along with stages when watching a pipeline result execute   
 

  
 
 
 
 

 
 Talking to Michael Neale in the weekly I will try to change the onClick behaviour of the pipelineGraph in case of running nodes. In that case we do not point to a url like pipeline/$ {id}  but remove the id  
 

  
 
 
 
 

 
 
 

 
 
 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-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36469  
 
 
  CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Raul Arabaolaza  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2016/Jul/06 9:06 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Raul Arabaolaza  
 

  
 
 
 
 

 
 ```CapybaraPortingLayerImpl.clickButton()``` Randomly fails to click sticky buttons when there is vertical scroll in the page. The actual implementation scrolls down to the button by means of the ```org.jenkinsci.test.acceptance.selenium.Scroller``` class which internally uses scrolljs. For some reason this scrolling and YUI sticky buttons (where the button itself is replaced by some YUI generated markup) makes the default ```click()``` method of Selenium fail sometimes without throwing any error against FF 46. The result is that some PO are not working as expected and random errors appears in the test harness due to jobs not being created or configurations not being saved like https://issues.jenkins-ci.org/browse/JENKINS-31738 Environment: 
 
OS: Mac OSX, Ubuntu 14.04 
Jenkins Version: 1.651.3 LTS 
JDK version: JDK7 
  
 

  
 
 
 
 

 
 
 

   

[JIRA] (JENKINS-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza commented on  JENKINS-36469  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
 One of the problems with #JENKINS-31738 is just this, sometimes the needed jobs are not created or configurations are not saved  
 

  
 
 
 
 

 
 
 

 
 
 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-34880) When using multiple updateSites, tool installer download fails if one UC is missing installers

2016-07-06 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-34880  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When using multiple updateSites, tool installer download fails if one UC is missing installers   
 

  
 
 
 
 

 
 Hi Thomas Wikström Due to whatever reason this fix has not been backported to 1.651.3 Currently this stabilization branch is closed. The next LTS release is 2.7.1, which is expected to be published today or tomorrow. This release will contain the fix.  
 

  
 
 
 
 

 
 
 

 
 
 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-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.

2016-07-06 Thread necrofi...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 yauhen f commented on  JENKINS-36132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.   
 

  
 
 
 
 

 
 03 Is the file 'pdf.js' contained more than once in your workspace? No 04 Is the file 'WebProject/Plugins/pdfjs/build/pdf.js' a valid filename? yes 05 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/Plugins/pdfjs/build/pdf.js' not applyable - master 06 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/Plugins/pdfjs/build/pdf.js' it looses somehow one folder level from svn, so file is available but WebProject was lost inside of message  
 

  
 
 
 
 

 
 
 

 
 
 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-36439) Evolve more composable redux store code patterns

2016-07-06 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36439  
 
 
  Evolve more composable redux store code patterns   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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-36439) Evolve more composable redux store code patterns

2016-07-06 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-36439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Evolve more composable redux store code patterns   
 

  
 
 
 
 

 
 After talking to Michael Neale and he was asking if anything else was depending on this. So, more-or-less all features are depending on redux in some way. We could keep going with redux as we have it today, so from that point of view one could say that this is not a "blocker". Otoh, we know that how we're doing redux now needs to evolve/change and is one of the areas where we are building up most tech-debt, so from my pov, I'd prefer for us to look at this sooner rather than later and see can we start the process of improving it Vs continuing to leave the "sh1t pile up in the back room"  Of course in the end, others might consider that it's better to keep pushing forward with more features and show more visual progress.  
 

  
 
 
 
 

 
 
 

 
 
 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-36470) Parameter Expression always throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ always throws CredentialNotFoundException   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 credentials-binding-plugin, credentials-plugin  
 
 
Created: 
 2016/Jul/06 9:33 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Erik The Other Wizzard  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received 

[JIRA] (JENKINS-35310) "Trigger builds remotely" doesn't save authToken

2016-07-06 Thread knsk.m...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kensuke Matsuzaki commented on  JENKINS-35310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Trigger builds remotely" doesn't save authToken   
 

  
 
 
 
 

 
 As a workaround, I created a simple project 'multibranch-project-trigger' that receive build trigger events, and run indexer by calling "curl -X POST -u me:xx http://jenkins/job/multibranch-project/build?delay=0"  
 

  
 
 
 
 

 
 
 

 
 
 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-36470) Parameter Expression throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ throws CredentialNotFoundException   
 

  
 
 
 
 

 
Change By: 
 Erik The Other Wizzard  
 
 
Summary: 
 Parameter _expression_  always  throws CredentialNotFoundException  
 
 
Environment: 
 Jenkins ver. 1.648os.arch amd64os.name Linuxos.version 4.2.0-38-genericjava.runtime.name OpenJDK Runtime Environmentjava.runtime.version 1.7.0_101-b00java.vm.name OpenJDK 64-Bit Server VMPlugins:plain-credentials 1.2 true falsecredentials 2.1.4 true falsecredentials-binding 1.8 true false  
 

  
 
 
 
 

 
 When configuring a job with credentials binding the 'specific credentials' do work but when I try to use the 'parameter _expression_' it always fails with the following message:```[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluation the following Groovy script content: println "secret_file_id:" + secret_file_idsecret_file_id:keystore[EnvInject] - Injecting contributions.Building on master in workspace /var/lib/jenkins/workspace/Credential-binding-parameter-_expression_FATAL: ${secret_file_id}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${secret_file_id} at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124) at org.jenkinsci.plugins.credentialsbinding.impl.FileBinding.bindSingle(FileBinding.java:52) at org.jenkinsci.plugins.credentialsbinding.Binding.bind(Binding.java:133) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper.setUp(SecretBuildWrapper.java:58) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE```  
 

  
 
 
 
 

 
 
 


[JIRA] (JENKINS-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36469  
 
 
  CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 

  
 
 
 
 

 
 ``` {code} CapybaraPortingLayerImpl.clickButton() ``` {code}  Randomly fails to click sticky buttons when there is vertical scroll in the page.The actual implementation scrolls down to the button by means of the  ```  {code} org.jenkinsci.test.acceptance.selenium.Scroller ``` {code}  class which internally uses scrolljs.For some reason this scrolling and YUI sticky buttons (where the button itself is replaced by some YUI generated markup) makes the default  ```  {code} click() ``` {code}  method of Selenium fail sometimes without throwing any error against FF 46. The result is that some PO are not working as expected and random errors appears in the test harness due to jobs not being created or configurations not being saved like https://issues.jenkins-ci.org/browse/JENKINS-31738*Environment:** OS: Mac OSX, Ubuntu 14.04* Jenkins Version: 1.651.3 LTS* JDK version: JDK7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  

[JIRA] (JENKINS-36470) Parameter Expression throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ throws CredentialNotFoundException   
 

  
 
 
 
 

 
Change By: 
 Erik The Other Wizzard  
 

  
 
 
 
 

 
 When configuring a job with credentials binding the 'specific credentials' do work but when I try to use the 'parameter _expression_' it always fails with the following message: ``` {code} [EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluation the following Groovy script content: println "secret_file_id:" + secret_file_idsecret_file_id:keystore[EnvInject] - Injecting contributions.Building on master in workspace /var/lib/jenkins/workspace/Credential-binding-parameter-_expression_FATAL: ${secret_file_id}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${secret_file_id} at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124) at org.jenkinsci.plugins.credentialsbinding.impl.FileBinding.bindSingle(FileBinding.java:52) at org.jenkinsci.plugins.credentialsbinding.Binding.bind(Binding.java:133) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper.setUp(SecretBuildWrapper.java:58) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE ``` {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-36471) Branch Indexing is failing when tries to recompute children

2016-07-06 Thread esc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Emilio Escobar  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36471  
 
 
  Branch Indexing is failing when tries to recompute children   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 subversion-plugin  
 
 
Created: 
 2016/Jul/06 9:46 AM  
 
 
Environment: 
 subversion plugin 2.6  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Emilio Escobar   
 

  
 
 
 
 

 
 Hello, all the Multibranch Pipeline jobs are failing when try to recompute children.  In the indexing logs:  

 

FATAL: Failed to recompute children of Branch Indexing
java.io.IOException: failed to make/load /var/jenkins/caches/svn-627ad516-79f6-4613-97d6-39456a59c664.db: java.io.IOError: java.io.IOException: File too large
at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:118)
at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:267)
at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:216)
at jenkins.scm.api.SCMSource.fetch(SCMSource.java:143)
at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:295)
at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:151)
at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:106)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: java.io.IOError: java.io.IOException: File too large
at org.mapdb.Volume$FileChannelVol.putData(Volume.java:799)
at org.mapdb.StoreWAL.replayLogFile(StoreWAL.java:852)
at org.mapdb.StoreWAL.(StoreWA

[JIRA] (JENKINS-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36469  
 
 
  CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 

  
 
 
 
 

 
 { code} { CapybaraPortingLayerImpl.clickButton() {code } }  Randomly fails to click sticky buttons when there is vertical scroll in the page.The actual implementation scrolls down to the button by means of the { code} { org.jenkinsci.test.acceptance.selenium.Scroller {code } }  class which internally uses scrolljs.For some reason this scrolling and YUI sticky buttons (where the button itself is replaced by some YUI generated markup) makes the default {code}click(){code} method of Selenium fail sometimes without throwing any error against FF 46. The result is that some PO are not working as expected and random errors appears in the test harness due to jobs not being created or configurations not being saved like https://issues.jenkins-ci.org/browse/JENKINS-31738*Environment:** OS: Mac OSX, Ubuntu 14.04* Jenkins Version: 1.651.3 LTS* JDK version: JDK7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
   

[JIRA] (JENKINS-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36469  
 
 
  CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 

  
 
 
 
 

 
 {{CapybaraPortingLayerImpl.clickButton()}} Randomly fails to click sticky buttons when there is vertical scroll in the page.The actual implementation scrolls down to the button by means of the {{org.jenkinsci.test.acceptance.selenium.Scroller}} class which internally uses scrolljs.For some reason this scrolling and YUI sticky buttons (where the button itself is replaced by some YUI generated markup) makes the default { code} { click() {code } }  method of Selenium fail sometimes without throwing any error against FF 46. The result is that some PO are not working as expected and random errors appears in the test harness due to jobs not being created or configurations not being saved like https://issues.jenkins-ci.org/browse/JENKINS-31738*Environment:** OS: Mac OSX, Ubuntu 14.04* Jenkins Version: 1.651.3 LTS* JDK version: JDK7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
  

[JIRA] (JENKINS-36471) Branch Indexing is failing when tries to recompute children

2016-07-06 Thread rec...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto assigned an issue to Manuel Recena Soto  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36471  
 
 
  Branch Indexing is failing when tries to recompute children   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Assignee: 
 Manuel Recena Soto  
 

  
 
 
 
 

 
 
 

 
 
 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-36215) Weblogic Deployer plugin 3.3 issue

2016-07-06 Thread r...@orange.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael CHAUMIER commented on  JENKINS-36215  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Weblogic Deployer plugin 3.3 issue   
 

  
 
 
 
 

 
 Hi Bharath Natarajan Good news for you.  I will add to the wiki more details about the classpath. What was the problem with the key authentication ? "But we are able to run this deploy job from Jenkins node. Is there anyway we can do that" : So you can or cannot deploy from a node? "We are getting "No JDK error" whenever trying to use JDK installed in Jenkins node". Do you mean : "if we set the JDK installed on the jenkins node in the jenkins global configuration there's no problem."? In the node configuration (you can see on your jenkins master instance (http://://computer//configure)) did you try to override JDK installation with the jdk installation node path ?  
 

  
 
 
 
 

 
 
 

 
 
 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-32046) Rounding error on aggregated throughput in case of different uri report

2016-07-06 Thread a...@ya.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrey Pokhilko resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32046  
 
 
  Rounding error on aggregated throughput in case of different uri report   
 

  
 
 
 
 

 
Change By: 
 Andrey Pokhilko  
 
 
Status: 
 In Progress 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-28733) Performance Plugin not showing URI's details in Graph

2016-07-06 Thread a...@ya.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrey Pokhilko resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-28733  
 
 
  Performance Plugin not showing URI's details in Graph   
 

  
 
 
 
 

 
Change By: 
 Andrey Pokhilko  
 
 
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-36470) Parameter Expression throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ throws CredentialNotFoundException   
 

  
 
 
 
 

 
Change By: 
 Erik The Other Wizzard  
 
 
Attachment: 
 bot-config.xml  
 
 
Attachment: 
 environment-variables.png  
 

  
 
 
 
 

 
 
 

 
 
 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-36470) Parameter Expression throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ throws CredentialNotFoundException   
 

  
 
 
 
 

 
Change By: 
 Erik The Other Wizzard  
 
 
Attachment: 
 config.png  
 

  
 
 
 
 

 
 
 

 
 
 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-36470) Parameter Expression throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ throws CredentialNotFoundException   
 

  
 
 
 
 

 
Change By: 
 Erik The Other Wizzard  
 

  
 
 
 
 

 
 When configuring a job with credentials binding the 'specific credentials' do work but when I try to use the 'parameter _expression_' it always fails with the following message:{code}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluation the following Groovy script content: println "secret_file_id:" + secret_file_idsecret_file_id:keystore[EnvInject] - Injecting contributions.Building on master in workspace /var/lib/jenkins/workspace/Credential-binding-parameter-_expression_FATAL: ${secret_file_id}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${secret_file_id} at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124) at org.jenkinsci.plugins.credentialsbinding.impl.FileBinding.bindSingle(FileBinding.java:52) at org.jenkinsci.plugins.credentialsbinding.Binding.bind(Binding.java:133) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper.setUp(SecretBuildWrapper.java:58) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code} As shown in config-attachment the referenced secret file (ID: 'keystore') is found when using the specific credentials option. When I try to load it dynamically with the parameter _expression_ using ${secret_file_id} the exception is thrown.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-36430) S3 plugin - Unable to load AWS credentials from any provider in the chain

2016-07-06 Thread ajit.jogle...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ajit Joglekar commented on  JENKINS-36430  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: S3 plugin - Unable to load AWS credentials from any provider in the chain   
 

  
 
 
 
 

 
 On the same jenkins instance as Anand has mentioned above, I get following exception while trying to save the S3 bucket access keys. It seems the keys are not written to the disk and when a login check is attempted it fails with the following exception: (actual host name replaced with ) WARNING: Error while serving http:///publisher/S3BucketPublisher/loginCheck java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilte

[JIRA] (JENKINS-36465) Unable to determine Maven version

2016-07-06 Thread ey...@jfrog.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Ben Moshe commented on  JENKINS-36465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to determine Maven version   
 

  
 
 
 
 

 
 This looks like a duplication of this issue: https://www.jfrog.com/jira/browse/HAP-771 Version 2.5.1 of the plugin should resolve it. Can you please make sure you're using 2.5.1 and that jars from previous version are not cached on the .jenkins/plugins or .jenkins/cache?  
 

  
 
 
 
 

 
 
 

 
 
 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-30600) git isn't ran inside build container

2016-07-06 Thread nicolas.del...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas De Loof commented on  JENKINS-30600  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git isn't ran inside build container   
 

  
 
 
 
 

 
 see https://github.com/jenkinsci/git-client-plugin/pull/211  
 

  
 
 
 
 

 
 
 

 
 
 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-36330) Make It possible to limit number of jobs in a view

2016-07-06 Thread tommy.ty...@diabol.se (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tommy Tynjä commented on  JENKINS-36330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make It possible to limit number of jobs in a view   
 

  
 
 
 
 

 
 Mikael Sundberg No worries!  
 

  
 
 
 
 

 
 
 

 
 
 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-36430) S3 plugin - Unable to load AWS credentials from any provider in the chain

2016-07-06 Thread mr.akbas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander A commented on  JENKINS-36430  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: S3 plugin - Unable to load AWS credentials from any provider in the chain   
 

  
 
 
 
 

 
 It looks like you have issue with read-write access to  

 
.aws/ 

  on local or remote node.  
 

  
 
 
 
 

 
 
 

 
 
 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-36465) Unable to determine Maven version

2016-07-06 Thread srijin...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 srijini s commented on  JENKINS-36465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to determine Maven version   
 

  
 
 
 
 

 
 I resolved it by place the maven folder in inside jenkins's home.  
 

  
 
 
 
 

 
 
 

 
 
 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-36471) Branch Indexing is failing when tries to recompute children

2016-07-06 Thread esc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Emilio Escobar  closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 There were other two db files corrupted: svn-627ad516-79f6-4613-97d6-39456a59c664.db.p  svn-627ad516-79f6-4613-97d6-39456a59c664.db.t After deleting those files the indexing start working as expected.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36471  
 
 
  Branch Indexing is failing when tries to recompute children   
 

  
 
 
 
 

 
Change By: 
 Emilio Escobar   
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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 u

[JIRA] (JENKINS-34310) Delivery pipeline show most active pipelines

2016-07-06 Thread tommy.ty...@diabol.se (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tommy Tynjä commented on  JENKINS-34310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Delivery pipeline show most active pipelines   
 

  
 
 
 
 

 
 Per Lundholm Thank you for this future request!  A work around would be to reconfigure the pipelines in the view when focus changes, e.g. through JobDSL and then sort the pipelines on last activity. Duplicated by JENKINS-36330.  
 

  
 
 
 
 

 
 
 

 
 
 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-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza started work on  JENKINS-31738  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza commented on  JENKINS-31738  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view   
 

  
 
 
 
 

 
 Many of the problems are related to jobs not being created or configurations not being saved because of JENKINS-36469  
 

  
 
 
 
 

 
 
 

 
 
 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-35645) ATH: XvncPluginTest.workflow failure

2016-07-06 Thread mfra...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Franco closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I wasn't able to reproduce the error with current versions of the ATH. If I check out any commit previous to the PR-134 merge, then I get it. So it seems like this has been solved as a side effect of the JENKINS-36048.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35645  
 
 
  ATH: XvncPluginTest.workflow failure   
 

  
 
 
 
 

 
Change By: 
 Manuel Franco  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-36470) Parameter Expression throws CredentialNotFoundException

2016-07-06 Thread e...@theothersonline.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik The Other Wizzard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36470  
 
 
  Parameter _expression_ throws CredentialNotFoundException   
 

  
 
 
 
 

 
Change By: 
 Erik The Other Wizzard  
 

  
 
 
 
 

 
 When configuring a job with credentials binding the 'specific credentials' do work but when I try to use the 'parameter _expression_' it always fails with the following message:{code}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluation the following Groovy script content: println "secret_file_id:" + secret_file_idsecret_file_id:keystore[EnvInject] - Injecting contributions.Building on master in workspace /var/lib/jenkins/workspace/Credential-binding-parameter-_expression_FATAL: ${secret_file_id}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${secret_file_id} at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124) at org.jenkinsci.plugins.credentialsbinding.impl.FileBinding.bindSingle(FileBinding.java:52) at org.jenkinsci.plugins.credentialsbinding.Binding.bind(Binding.java:133) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper.setUp(SecretBuildWrapper.java:58) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code}As shown in config-attachment the referenced secret file (ID: 'keystore') is found when using the specific credentials option. When I try to load it dynamically with the parameter _expression_ using ${secret_file_id} the exception is thrown. I've spend a fair amount of time testing with different settings for credentials and plugin versions but none fixed my issue. I've attached an example job configuration that mimics my issue. Basically the one I'm trying to achieve is a job that based upon a parameter builds and signs an Android app. The parameter is either supplied through a properties file inside a git repo or by making the build 'parameterized'. Any help would be appreciated!Cheers, Erik  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-33708) Invocation of 'sh' on Windows should provide a more helpful error

2016-07-06 Thread 3...@gmx.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 peschmae peschmae commented on  JENKINS-33708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invocation of 'sh' on Windows should provide a more helpful error   
 

  
 
 
 
 

 
 I got it working on my system with the shell from git-bash. 
 
C:\Program Files\Git\bin is in the global search path, such that Jenkins finds sh.exe 
Jenkins also needs nohup (as the error message suggests). Git-bash has a nohup in /usr/bin. I just symlinked that (along with the shared libraries it needs) int /bin: 
 

 

Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


mklink "C:\Program Files\Git\bin\nohup.exe" "C:\Program Files\git\usr\bin\nohup.exe"
mklink "C:\Program Files\Git\bin\msys-2.0.dll" "C:\Program Files\git\usr\bin\msys-2.0.dll"
mklink "C:\Program Files\Git\bin\msys-iconv-2.dll" "C:\Program Files\git\usr\bin\msys-iconv-2.dll"
mklink "C:\Program Files\Git\bin\msys-intl-8.dll" "C:\Program Files\git\usr\bin\msys-intl-8.dll"
 

 With that setup it's working just fine on my machines.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 


[JIRA] (JENKINS-33708) Invocation of 'sh' on Windows should provide a more helpful error

2016-07-06 Thread 3...@gmx.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 peschmae peschmae edited a comment on  JENKINS-33708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invocation of 'sh' on Windows should provide a more helpful error   
 

  
 
 
 
 

 
 I got it working on my system with the shell from git-bash.# C:\Program Files\Git\bin is in the global search path, such that Jenkins finds _sh.exe_# Jenkins *also* needs _nohup.exe_ (as the error message suggests, see also [BourneshellScript.java|https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java]). Git-bash has a _nohup.exe_ in /usr/bin. I just symlinked that (along with the shared libraries it needs) into /bin by running from a Windows cmd shell:{code: bash java }mklink "C:\Program Files\Git\bin\nohup.exe" "C:\Program Files\git\usr\bin\nohup.exe"mklink "C:\Program Files\Git\bin\msys-2.0.dll" "C:\Program Files\git\usr\bin\msys-2.0.dll"mklink "C:\Program Files\Git\bin\msys-iconv-2.dll" "C:\Program Files\git\usr\bin\msys-iconv-2.dll"mklink "C:\Program Files\Git\bin\msys-intl-8.dll" "C:\Program Files\git\usr\bin\msys-intl-8.dll"{code}With that setup it's working just fine on my machines.  
 

  
 
 
 
 

 
 
 

 
 
 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-33708) Invocation of 'sh' on Windows should provide a more helpful error

2016-07-06 Thread 3...@gmx.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 peschmae peschmae edited a comment on  JENKINS-33708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invocation of 'sh' on Windows should provide a more helpful error   
 

  
 
 
 
 

 
 I got it working on my system with the shell from git-bash.# C:\Program Files\Git\bin is in the global search path, such that Jenkins finds  sh  _sh . exe exe_ # Jenkins *also* needs  nohup  _nohup.exe_  (as the error message suggests , see also [BourneshellScript.java|https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java] ). Git-bash has a  nohup  _nohup.exe_  in /usr/bin. I just symlinked that (along with the shared libraries it needs) int /bin:{code:bash}mklink "C:\Program Files\Git\bin\nohup.exe" "C:\Program Files\git\usr\bin\nohup.exe"mklink "C:\Program Files\Git\bin\msys-2.0.dll" "C:\Program Files\git\usr\bin\msys-2.0.dll"mklink "C:\Program Files\Git\bin\msys-iconv-2.dll" "C:\Program Files\git\usr\bin\msys-iconv-2.dll"mklink "C:\Program Files\Git\bin\msys-intl-8.dll" "C:\Program Files\git\usr\bin\msys-intl-8.dll"{code}With that setup it's working just fine on my machines.  
 

  
 
 
 
 

 
 
 

 
 
 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-33708) Invocation of 'sh' on Windows should provide a more helpful error

2016-07-06 Thread 3...@gmx.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 peschmae peschmae edited a comment on  JENKINS-33708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invocation of 'sh' on Windows should provide a more helpful error   
 

  
 
 
 
 

 
 I got it working on my system with the shell from git-bash.# C:\Program Files\Git\bin is in the global search path, such that Jenkins finds _sh.exe_# Jenkins *also* needs _nohup.exe_ (as the error message suggests, see also [BourneshellScript.java|https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java]). Git-bash has a _nohup.exe_ in /usr/bin. I just symlinked that (along with the shared libraries it needs)  int  into  /bin  by running from a Windows cmd shell :  {code:bash}mklink "C:\Program Files\Git\bin\nohup.exe" "C:\Program Files\git\usr\bin\nohup.exe"mklink "C:\Program Files\Git\bin\msys-2.0.dll" "C:\Program Files\git\usr\bin\msys-2.0.dll"mklink "C:\Program Files\Git\bin\msys-iconv-2.dll" "C:\Program Files\git\usr\bin\msys-iconv-2.dll"mklink "C:\Program Files\Git\bin\msys-intl-8.dll" "C:\Program Files\git\usr\bin\msys-intl-8.dll"{code}With that setup it's working just fine on my machines.  
 

  
 
 
 
 

 
 
 

 
 
 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-30327) Failed to scout MultiJobBuildSelector - ClassNotFoundException: hudson.plugins.copyartifact.BuildSelector

2016-07-06 Thread dotheb...@citadel.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wilfried Goesgens commented on  JENKINS-30327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to scout MultiJobBuildSelector - ClassNotFoundException: hudson.plugins.copyartifact.BuildSelector   
 

  
 
 
 
 

 
 this occured to me with the jenkins 2.11 debian package.  
 

  
 
 
 
 

 
 
 

 
 
 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-36472) Depend on Icon Shim Plugin

2016-07-06 Thread christian.poeni...@tracetronic.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 TraceTronic GmbH created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36472  
 
 
  Depend on Icon Shim Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 TraceTronic GmbH  
 
 
Components: 
 ecutest-plugin  
 
 
Created: 
 2016/Jul/06 12:35 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 TraceTronic GmbH  
 

  
 
 
 
 

 
 Take advantages of the Icon Shim Plugin that allows to make use of the core  tag, while still remaining backward compatible with older versions of Jenkins core that do not have the icon tag.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA

[JIRA] (JENKINS-31047) Incorrect Behaviour on WarningsPluginTest

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza started work on  JENKINS-31047  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza started work on  JENKINS-36469  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-36473) New Metric: Load assessment for required nodes

2016-07-06 Thread it.carlosrod...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Lopez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36473  
 
 
  New Metric: Load assessment for required nodes   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 metrics-plugin  
 
 
Created: 
 2016/Jul/06 12:45 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Carlos Lopez  
 

  
 
 
 
 

 
 Include in the metrics parameters list: load assessment for required nodes.  Similar behaviour of "jenkins.job.scheduled" but for nodes and not for the master. Node label would be introduced as parameter as it does on `jenkins.node._XXX.builds` _(timer)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-07-06 Thread fernando.ros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fernando Rosado Altamirano edited a comment on  JENKINS-35347  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to test connection when using keystone V3 API   
 

  
 
 
 
 

 
 We  also  are  also  suffering the same issue. We needed upgrade openstack auth api and the jenkins plugin stop working. Are there any workaround? Do you have any estimation about when it will be solved?Thanks a lot.  
 

  
 
 
 
 

 
 
 

 
 
 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-35347) unable to test connection when using keystone V3 API

2016-07-06 Thread fernando.ros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fernando Rosado Altamirano commented on  JENKINS-35347  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to test connection when using keystone V3 API   
 

  
 
 
 
 

 
 We also are suffering the same issue. We needed upgrade openstack auth api and the jenkins plugin stop working. Are there any workaround? Do you have any estimation about when it will be solved? Thanks a lot.  
 

  
 
 
 
 

 
 
 

 
 
 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-34614) ATH ftpd container doesn't seem to be opening port 21 (or running?)

2016-07-06 Thread rec...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The PR was merged.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-34614  
 
 
  ATH ftpd container doesn't seem to be opening port 21 (or running?)   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Status: 
 In Progress 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/op

[JIRA] (JENKINS-31047) Incorrect Behaviour on WarningsPluginTest

2016-07-06 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza assigned an issue to Raul Arabaolaza  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31047  
 
 
  Incorrect Behaviour on WarningsPluginTest   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Assignee: 
 Oliver Gondža Raul Arabaolaza  
 

  
 
 
 
 

 
 
 

 
 
 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-36430) S3 plugin - Unable to load AWS credentials from any provider in the chain

2016-07-06 Thread anand.krish...@telegraph.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anand Krishnan commented on  JENKINS-36430  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: S3 plugin - Unable to load AWS credentials from any provider in the chain   
 

  
 
 
 
 

 
 Hi , I am not sure what you mean I am running the docker instance as:   docker run -d -u 1000 -p 8080:8080 -p 5:5 -v /var/lib/jenkins:/var/jenkins_home jenkinsci/jenkins:2.11 do you mean the .aws in jenkins_home ?  
 

  
 
 
 
 

 
 
 

 
 
 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-33021) trilead ssh MAC and key exchange algorithms severely outdated

2016-07-06 Thread biog...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan An commented on  JENKINS-33021  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: trilead ssh MAC and key exchange algorithms severely outdated   
 

  
 
 
 
 

 
 I used another fork of Trilead ssh2 instead which has sha256 implemented. it's called ConnectBot sshlib. available on GitHub. https://github.com/connectbot/sshlib  
 

  
 
 
 
 

 
 
 

 
 
 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-34644) Stage View Shows Excessively Long Full Run Time Figures

2016-07-06 Thread jenkins-ci....@cowsgomoo.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Coltrey Mather commented on  JENKINS-34644  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stage View Shows Excessively Long Full Run Time Figures   
 

  
 
 
 
 

 
 Sam Van Oort This is a multibranch pipeline, so maybe it's different ... but this just gives me an NPE...I've verified that this is a build number with a negative durationMillis and pauseDurationMillis Jenkins.instance.getItem('p-j-d/master').getBuildByNumber(25).execution.currentHeads.get(0).actions 

 

java.lang.NullPointerException: Cannot invoke method getBuildByNumber() on null object
	at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
	at Script1.run(Script1.groovy:1)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:585)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:623)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:594)
	at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142)
	at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114)
	at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
	at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:111)
	at jenkins.model.Jenkins._doScript(Jenkins.java:4043)
	at jenkins.model.Jenkins.doScript(Jenkins.java:4015)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServ

[JIRA] (JENKINS-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rec...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36469  
 
 
  CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 

  
 
 
 
 

 
 {{CapybaraPortingLayerImpl.clickButton()}} Randomly fails to click sticky buttons when there is vertical scroll in the page.The actual implementation scrolls down to the button by means of the {{org.jenkinsci.test.acceptance.selenium.Scroller}} class which internally uses scrolljs.For some reason this scrolling and YUI sticky buttons (where the button itself is replaced by some YUI generated markup) makes the default {{click()}} method of Selenium fail sometimes without throwing any error against FF 46. The result is that some PO are not working as expected and random errors appears in the test harness due to jobs not being created or configurations not being saved like [JENKINS-31738|https://issues.jenkins-ci.org/browse/JENKINS-31738]. . *Environment:*.* OS: Mac OSX, Ubuntu 14.04* Jenkins Version: 1.651.3 LTS* JDK version: JDK7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

[JIRA] (JENKINS-36469) CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons

2016-07-06 Thread rec...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36469  
 
 
  CapybaraPortingLayerImpl.clickButton() has problems with vertical scroll and sticky buttons   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 

  
 
 
 
 

 
 {{CapybaraPortingLayerImpl.clickButton()}} Randomly fails to click sticky buttons when there is vertical scroll in the page.The actual implementation scrolls down to the button by means of the {{org.jenkinsci.test.acceptance.selenium.Scroller}} class which internally uses scrolljs.For some reason this scrolling and YUI sticky buttons (where the button itself is replaced by some YUI generated markup) makes the default {{click()}} method of Selenium fail sometimes without throwing any error against FF 46. The result is that some PO are not working as expected and random errors appears in the test harness due to jobs not being created or configurations not being saved like  [JENKINS-31738|  https://issues.jenkins-ci.org/browse/JENKINS-31738 ].  . *Environment:* . * OS: Mac OSX, Ubuntu 14.04* Jenkins Version: 1.651.3 LTS* JDK version: JDK7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
 

[JIRA] (JENKINS-36474) Copy Artifacts - Cloudbees folder issue

2016-07-06 Thread bob.lio...@kuehne-nagel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Liotta created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36474  
 
 
  Copy Artifacts - Cloudbees folder issue   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 copyartifact-plugin  
 
 
Created: 
 2016/Jul/06 2:02 PM  
 
 
Environment: 
 plugin version 1.38  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Robert Liotta  
 

  
 
 
 
 

 
 Hello I have an issue that is described almost the same as this issue: JENKINS-32512 that was closed. The issue is as follows: Create a job in a folder. Call it testfolder/sourcebuild. Have this folder save an artifact. Case #1 - Works now create a job at the root, not in a folder. Call it getArt. Use the copyartifacts plugin. set the project name to testfolder/sourcebuild set the job# accordingly. Run job, works Case#2 - Does not work edit getArt Add a string variable bad - set it to testfolder/sourcebuild get the job# accordingly set the projectname to $bad or $ {bad} . Run job. Cannot find source project. I also tried adding it as /testfolder/sourcebuild.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-36475) Pipeline script editor is unusable when Theme is enabled

2016-07-06 Thread m...@herbert.cc (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Benjamin Herbert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36475  
 
 
  Pipeline script editor is unusable when Theme is enabled   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 simple-theme-plugin  
 
 
Created: 
 2016/Jul/06 2:14 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Benjamin Herbert  
 

  
 
 
 
 

 
 Having the simple theme plugin enabled, the pipeline script editor is hard to use. The cursor in the editor field is shown further right as it actually inputs text.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1

[JIRA] (JENKINS-36361) javax.servlet.ServletException in pluginmanager

2016-07-06 Thread it...@clear2pay.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 C2PA IT commented on  JENKINS-36361  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: javax.servlet.ServletException in pluginmanager   
 

  
 
 
 
 

 
 Same issue here, Jenkins 1.583 & SVN Plugin 2.4.5. Not sure what happened, but I didn't upgrade/downgrade my subversion plugin at all in the past 3 months.  
 

  
 
 
 
 

 
 
 

 
 
 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-33655) blank page after login, log says: java.lang.RuntimeException: Header>6144

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-33655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blank page after login, log says: java.lang.RuntimeException: Header>6144   
 

  
 
 
 
 

 
 Do you send a giant cookie header to Jenkins?  
 

  
 
 
 
 

 
 
 

 
 
 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-36354) Distributed job with sync to central server

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36354  
 
 
  Distributed job with sync to central server   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-36323) Problems on reading computer/(master)/config.xml

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is by design. We removed this API in the May security update, see SECURITY-281 / CVE-2016-3727 here: https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36323  
 
 
  Problems on reading computer/(master)/config.xml   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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 r

[JIRA] (JENKINS-36191) NullPointerException when saving project on Jenkins ver. 2.10

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Duplicates an issue that was fixed towards 2.12.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36191  
 
 
  NullPointerException when saving project on Jenkins ver. 2.10   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-36249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen   
 

  
 
 
 
 

 
 Please do this and look for deadlocks: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump   
 

  
 
 
 
 

 
 
 

 
 
 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-27350) "Performance Report" on each job don't have link text and the graph picture is missing.

2016-07-06 Thread a...@ya.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrey Pokhilko resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27350  
 
 
  "Performance Report" on each job don't have link text and the graph picture is missing.   
 

  
 
 
 
 

 
Change By: 
 Andrey Pokhilko  
 
 
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-36019) No one can serve two masters

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-36019  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No one can serve two masters   
 

  
 
 
 
 

 
 So, what's the major bug here? That Jenkins allows you to do something obviously stupid and fall on your face as soon as there's a conflict?  
 

  
 
 
 
 

 
 
 

 
 
 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-36378) Jenkins Server caught Blue Dump Screen and crashed

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36378  
 
 
  Jenkins Server caught Blue Dump Screen and crashed   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 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-36009) configure node not possible

2016-07-06 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-36009  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: configure node not possible   
 

  
 
 
 
 

 
 While it's loading, do this: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump May help to update the Credentials plugin, IIRC there was a 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.


[JIRA] (JENKINS-36474) Copy Artifacts - Cloudbees folder issue

2016-07-06 Thread bob.lio...@kuehne-nagel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Liotta closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I found the issue and it WAS permissions.. You might want to mention in the docs that in this case, the permission would need to allow /jobname  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36474  
 
 
  Copy Artifacts - Cloudbees folder issue   
 

  
 
 
 
 

 
Change By: 
 Robert Liotta  
 
 
Status: 
 Open Closed  
 
 
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

  1   2   3   >