[JIRA] (JENKINS-41067) NullPointerException when using InfluxDB Plugin in Pipeline script

2017-03-10 Thread aleksi.sim...@eficode.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksi Simell commented on  JENKINS-41067  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when using InfluxDB Plugin in Pipeline script   
 

  
 
 
 
 

 
 That configuration looks fine. When you write a pipeline script, you need to specify target as  

 

step([$class: 'InfluxDbPublisher', target: 'http://influxdb-develop.demandbase.com:8086,jenkins_db',...]) 

    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Adding following to gitconfig file resolved the issue. {{[http] }} sslVerify = false  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
Change By: 
 Ravi Singareddy  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
 Adding following to gitconfig file resolved the issue. {{[http] }} sslVerify = false  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42018) Bitbucket Server projects are being disabled in Jenkins when you trigger from Bitbucket commit

2017-03-10 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ commented on  JENKINS-42018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Server projects are being disabled in Jenkins when you trigger from Bitbucket commit   
 

  
 
 
 
 

 
 This behavior with Dead branch is fixed in branch-api 2.0.7: --JENKINS-42234--. Branch API does not process such event anymore.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-34268) Lock multiple resources using the Pipeline lock step

2017-03-10 Thread dafal...@akamai.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Falcone commented on  JENKINS-34268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lock multiple resources using the Pipeline lock step   
 

  
 
 
 
 

 
 After implementing Anton Lundin's suggestion, I received the following error in my build (followed by a stacktrace): 

 

org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method 

 To fix it, I went to Manage Jenkins > In process Script Approval, clicked Approve on the pending signature approval, and reran the build.  I had to repeat the process 4-5 times to approve all the required signatures.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-34268) Lock multiple resources using the Pipeline lock step

2017-03-10 Thread dafal...@akamai.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Falcone edited a comment on  JENKINS-34268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lock multiple resources using the Pipeline lock step   
 

  
 
 
 
 

 
 After implementing Anton Lundin's suggestion, I received the following error in my build (followed by a stacktrace):{code:java}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method{code}To fix it, I went to Manage Jenkins > In process Script Approval, clicked Approve on the pending signature approval, and reran the build.  I had to repeat the process 4-5 times to approve all the required signatures , but it worked great after that .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42685) Remove custom stapler proxy as we can now use assync requests

2017-03-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42685  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove custom stapler proxy as we can now use assync requests   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/resources/org/biouno/unochoice/CascadeChoiceParameter/index.jelly src/main/resources/org/biouno/unochoice/DynamicReferenceParameter/index.jelly src/main/resources/org/biouno/unochoice/stapler/unochoice/unochoice.js http://jenkins-ci.org/commit/active-choices-plugin/8ccd7fcdec84e3cb6272115662632fa2542ce945 Log: JENKINS-42685 Remove stapler proxy as we can now use assync requests  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42685) Remove custom stapler proxy as we can now use assync requests

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42685  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove custom stapler proxy as we can now use assync requests   
 

  
 
 
 
 

 
 Local tests worked fine. Pushed to a branch in git, and will merge it once 1.5.3 is released.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42685) Remove custom stapler proxy as we can now use assync requests

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42685  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove custom stapler proxy as we can now use assync requests   
 

  
 
 
 
 

 
 Ioannis, all requests from the plug-in are synchronous. (warning, this is one of those long comments, come back with coffee when you have time / patience to read it with calm  ) Jenkins supports automagically creating a proxy to Java objects. In the UI, _javascript_ code can call Java methods. It is not a standard way. In Java, we annotate classes with @ _javascript_Method. These methods are then exposed by Stapler (Jenkins' web framework) to the UI. This annotation is used to create proxy objects. The UI _javascript_ code talks to this proxy, and in our case, when you change something in one field, the plug-in _javascript_ code retrieves the referenced parameter values, then calls the proxy method "doUpdate" to update the list of values reactively. Now, this all used to happen asynchronously in uno-choice-0.something. We changed it after realising that it could take a while to retrieve values and render the UI. During that big refactor we did together some time ago, I added a *hack*. Right now, jst before calling the doUpdate method of the proxy, we "replace" the proxy by a custom proxy, that is synchronous. This is bad for the UI. As we lock the main thread (you see some warnings in Firefox console some times). Now that we have a "Loading..." message in 1.5.3 (to be released), I believe we can use Jenkins' default _javascript_ proxy. Which is good for a number of reasons. And then simply call asynchronously the doUpdate method, display the loading overlay, that will disappear once the proxy is done.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

   

[JIRA] (JENKINS-42685) Remove custom stapler proxy as we can now use assync requests

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42685  
 
 
  Remove custom stapler proxy as we can now use assync requests   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Summary: 
 Remove  custom  stapler proxy as we can now use assync requests  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42685) Remove stapler proxy as we can now use assync requests

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42685  
 
 
  Remove stapler proxy as we can now use assync requests   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Bruno P. Kinoshita  
 
 
Components: 
 active-choices-plugin  
 
 
Created: 
 2017/Mar/11 5:13 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bruno P. Kinoshita  
 

  
 
 
 
 

 
 Thanks to the new spinning loader, introduced in 1.5.3, I believe we can now drop the custom hack in the plug-in to have synchronous requests. Initial tests locally showed that it worked with no problems. Will ask Ioannis Moutsatsos to test it too before releasing 1.5.4.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
  

[JIRA] (JENKINS-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita assigned an issue to Ioannis Moutsatsos  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42034  
 
 
  Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Assignee: 
 Bruno P. Kinoshita Ioannis Moutsatsos  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42034  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters   
 

  
 
 
 
 

 
 I'm not sure referencing the parameter is the problem. Your script is returning HTML with a 

[JIRA] (JENKINS-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
 The message "unable to get local issuer certificate" is not one that I've ever seen.  You may want to consider the stackoverflow article.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
 Yes. I am using credentials while connecting to git in jenkins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
Change By: 
 Ravi Singareddy  
 
 
Attachment: 
 gitcommandline.PNG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
Change By: 
 Ravi Singareddy  
 
 
Attachment: 
 git.PNG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
 Add a username / password credential in the Jenkins credentials store, and use that credential from the job definition.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
 Hi Mark, If I am able to clone  https://myrepository/myproject.git  using git command; But Jenkins Source Code Management not able to execute same git command. What is the standard procedure for accessing https git URLs from jenkins? Thanks   Ravi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42034  
 
 
  Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 

  
 
 
 
 

 
 Using an Active Choices Reactive Reference Parameter and having it return Formatted HTML with a script portion (onchange, etc...) works great unless the groovy script references other dependent build parameters such as strings, Active Choice parameters, etc...  The returned HTML renders properly, just without the script.  Attached is a (hopefully) very simple job configuration to demonstrate.  The groovy script for generating the sample test is as follows (DummyVar is a string parameter defined just above this parameter): --- {code} //Uncomment this line, causing DummyVar to be referenced, and the script will be lost at runtime.//def a = DummyVardef FullHTML = ""FullHTML += ""FullHTML += " jQuery(document).on('ready', function() { function updateOutputValue()  { jQuery('#value').val('Booya!'); };"
FullHTML += " updateOutputValue();"
FullHTML += "});"
FullHTML += ""FullHTML += ""FullHTML += " "return FullHTML --- {code} Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-39593) Performance slow in 1.5 release

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-39593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance slow in 1.5 release   
 

  
 
 
 
 

 
 Acknowledged. Let's aim at getting this fixed for 1.5.4. Plus, it sounds like fun to debug and fix this kind of problems  1.5.3 released in a few hours, available on Monday UTC. Working on 1.5.4 right after that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-39593) Performance slow in 1.5 release

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita started work on  JENKINS-39593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42222) On Rebuilding jenkins job, Active choice reactive reference parameter values are editable by user.

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-4  
 
 
  On Rebuilding jenkins job, Active choice reactive reference parameter values are editable by user.   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42665) Git BuildData caches remoteUrls without trimming strings

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42665  
 
 
  Git BuildData caches remoteUrls without trimming strings   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) Git clone fails https://repo/project.git using a downloaded certificate

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  Git clone fails https://repo/project.git using a downloaded certificate   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 GIT Fail to connect Git clone fails  https:// myrepository repo / myproject project .git  using a downloaded certificate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) GIT Fail to connect https://myrepository/myproject.git

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-42684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GIT Fail to connect https://myrepository/myproject.git   
 

  
 
 
 
 

 
 I've never used certificates with git in that way, so I don't know if they will work with the plugin.  There are no automated tests or acceptance tests of that form of authentication.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) GIT Fail to connect https://myrepository/myproject.git

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  GIT Fail to connect https://myrepository/myproject.git   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 |Failed to connect to repository : Command "git.exe ls-remote -h [https://abc...@myserver.com/scm/tess/testing.git] HEAD" returned status code 128: stdout:  stderr: fatal: unable to access 'https://abc...@myserver.com/scm/tess/testing.git/': SSL certificate problem: unable to get local issuer certificate     I have downloaded certificate and added to gitconfig.       [http]    sslCAPath = c:\ \ jenkins  \ abcdef.crt   I have also added this certificate to the jre cacerts keystore     {{  c:\jenkins>"c:\Program Files\Java\jdk1.8.0_111\bin\keytool.exe"  -import -noprompt -trustcacerts -alias abcdef -file c:\jenkins\abcedef.crt -keystore c:"\Program Files\Java\jre1.8.0_111\lib\security\cacerts" -storepass changeit  }}{{    }}    I have successfully clone from this git using following command.git clone [https://abc...@myserver.com/scm/tess/testing.git]But I am not able to connect to this repository from jenkins source code management . Thanks Ravi   |  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

 

[JIRA] (JENKINS-42684) GIT Fail to connect https://myrepository/myproject.git

2017-03-10 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  GIT Fail to connect https://myrepository/myproject.git   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42629) Github Issues plugin not working in pipeline

2017-03-10 Thread sites+jenk...@dan.cx (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Lo Nigro commented on  JENKINS-42629  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Issues plugin not working in pipeline   
 

  
 
 
 
 

 
 Thanks for the bug report. I'm not very familiar with pipeline  so I'll try to investigate and determine how to fix this. The code for the plugin is on GitHub so feel free to take a look if you're familiar with how pipelines work   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) GIT Fail to connect https://myrepository/myproject.git

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  GIT Fail to connect https://myrepository/myproject.git   
 

  
 
 
 
 

 
Change By: 
 Ravi Singareddy  
 

  
 
 
 
 

 
 |Failed to connect to repository : Command "git.exe ls-remote -h  [  https://abc...@myserver.com/scm/tess/testing.git ]  HEAD" returned status code 128:stdout: stderr: fatal: unable to access 'https://abc...@myserver.com/scm/tess/testing.git/': SSL certificate problem: unable to get local issuer certificate  I have downloaded certificate and added to gitconfig. [http] sslCAPath = c:\\jenkins \\  abcdef.crt I have also added this certificate to the jre cacerts keystore  c:\jenkins>"c:\Program Files\Java\jdk1.8.0_111\bin\keytool.exe"  -import -noprompt -trustcacerts -alias abcdef -file c:\jenkins\abcedef.crt -keystore c:"\Program Files\Java\jre1.8.0_111\lib\security\cacerts" -storepass changeit I have successfully clone from this git using  following  command  but .git clone [https://abc...@myserver.com/scm/tess/testing.git]But I am  not able to connect  to this repository  from  the  jenkins  source code management .    Thanks   Ravi    |  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

 

[JIRA] (JENKINS-42636) During pipeline stage build time reported incorrectly

2017-03-10 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey edited a comment on  JENKINS-42636  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: During pipeline stage build time reported incorrectly   
 

  
 
 
 
 

 
 [~jamesdumay] I tried fetching 'General SCM' step using step API, its returning correct duration, while General SCM step is going on, it shows that steps duration as running/unknown, and it fetch of that API shows correct incrementing duration. Once its finished/success this number doesn't change. Someone from UI should take a look to see if there is some logic and for some reason its failing to update the duration, because it doesn't happen in all cases. It will also help to capture steps API output when it shows such ever increasing duration. I don't see this behavior in API.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42636) During pipeline stage build time reported incorrectly

2017-03-10 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-42636  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: During pipeline stage build time reported incorrectly   
 

  
 
 
 
 

 
 James Dumay I tried fetching 'General SCM' step using step API, its returning correct duration, while General SCM step is going on, it shows that steps duration as running/unknown, and it fetch of that API shows correct incrementing duration. Once its finished/success this number doesn't change. Someone from UI should take a look to see if there is some logic and for some reason its failing to update the duration, because it doesn't happen in all cases.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42684) GIT Fail to connect https://myrepository/myproject.git

2017-03-10 Thread singare...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ravi Singareddy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42684  
 
 
  GIT Fail to connect https://myrepository/myproject.git   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2017/Mar/10 11:51 PM  
 
 
Environment: 
 git plugin 3.1.0, git client plugin 2.3.0, jenkins 2.32.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ravi Singareddy  
 

  
 
 
 
 

 
 
 

 
 
Failed to connect to repository : Command "git.exe ls-remote -h https://abc...@myserver.com/scm/tess/testing.git HEAD" returned status code 128: stdout:  stderr: fatal: unable to access 'https://abc...@myserver.com/scm/tess/testing.git/': SSL certificate problem: unable to get local issuer certificate     I have downloaded certificate and added to gitconfig.   [http] sslCAPath = c:\\jenkinsabcdef.crt   I have also added this certificate to the jre cacerts keystore    c:\jenkins>"c:\Program Files\Java\jdk1.8.0_111\bin\keytool.exe"  -import -noprompt -trustcacerts -alias abcdef -file c:\jenkins\abcedef.crt -keystore c:"\Program Files\Java\jre1.8.0_111\lib\security\cacerts" -storepass changeit   I have successfully clone from this git using command but not able to connect from the jenkins     
 

 
  
 
 

[JIRA] (JENKINS-42650) Pipeline Editor Tweaks

2017-03-10 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-42650  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42650  
 
 
  Pipeline Editor Tweaks   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita started work on  JENKINS-38893  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-32461) jenkinsProject variable is not available in Multi-configuration project

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-32461  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jenkinsProject variable is not available in Multi-configuration project   
 

  
 
 
 
 

 
 Hi Kevin Yu, triaged this issue for 1.5.4 release. Will spend some time looking into how to fix this issue, but cannot promise including it in the release. I remember it was a bit tricky due to the way we retrieve the project name.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-24274) New DB-based choice provider

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-24274  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New DB-based choice provider   
 

  
 
 
 
 

 
 Triaging issues for active-choices-plugin today and found this issue linked to another one (JENKINS-28736). Will look at implementing it for active-choices, using the pull request as reference. If there's nothing that break compatibility, and it makes sense to add this parameter type, this should be shipped with active-choices-plugin 1.5.4 (probably in one or two weeks).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-41709) Blue Ocean doesnt render Active Choices parameters

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-41709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean doesnt render Active Choices parameters   
 

  
 
 
 
 

 
 Acknowledged, watching the issue that is blocking this one. We can cut a release as soon as that issue is fixed and we have tested the behaviour of active-choices-plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42646) Unable to save Jenkinsfile for totally blank github repo

2017-03-10 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-42646  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42646  
 
 
  Unable to save Jenkinsfile for totally blank github repo   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-40501  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter   
 

  
 
 
 
 

 
 Closing as Not a Defect Christoph Obermair, as this is working as expected, given the current features of the plug-in. From the String value, you will have to use Jenkins API in Groovy and navigate through the objects in Jenkins to reach your ListSubversionTagsParameterValue. We are working in the next months to make the Scriptler integration better. So hopefully in the future we will be able to point users with similar issues to existing Scriptler scripts that can, at least, simplify this task. Cheers Bruno  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40501  
 
 
  Reactive Reference Parameter not working with "List Subversion Tags" parameter   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade

2017-03-10 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert commented on  JENKINS-42676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade   
 

  
 
 
 
 

 
 Do you know of a way to get a free trial account at rackspace? If yes, then I could test all that stuff myself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-41111) click build bottom would crash when Active Choices Plugin conjunction with Dynamic Parameter Plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-4  
 
 
  click build bottom would crash when Active Choices Plugin conjunction with Dynamic Parameter Plugin   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-41111) click build bottom would crash when Active Choices Plugin conjunction with Dynamic Parameter Plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-4  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: click build bottom would crash when Active Choices Plugin conjunction with Dynamic Parameter Plugin   
 

  
 
 
 
 

 
 Hi xiaoyu wang, closing as cannot reproduce due to the lack of a test case. I checked the source code in the GitHub master. The plug-in used to be hosted under a user account, but has been moved under the GitHub jenkinsci organisation. If you look at the code, other changes have been made since 0.20 and since this move to jenkinsci org. The method mentioned in the exception (checkParameterValue) is not available in the ChoiceParameterDefinition parameter any more. Feel free to re-open the ticket including the exception stack trace as you did, plus steps to reproduce, such as example parameters used, config.xml files, screen shots, or whatever you can imagine that will be helpful for the developers to reproduce this issue. Thank you! Bruno  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade

2017-03-10 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert commented on  JENKINS-42676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade   
 

  
 
 
 
 

 
 If both the admin username and the admin password were empty before, Set the admin credential to None If the admin username was set and the admin password was empty before, then the admin credential should be a SSH-credential with the same username and a copy of the global cloud-key as private key. If both admin user and admin password were set before, then the admin credential should be a Username/Password credential using this username and password.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-41111) click build bottom would crash when Active Choices Plugin conjunction with Dynamic Parameter Plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-4  
 
 
  click build bottom would crash when Active Choices Plugin conjunction with Dynamic Parameter Plugin   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 

  
 
 
 
 

 
 {noformat} javax.servlet.ServletException: java.lang.IllegalArgumentException: Illegal choice: java/kuk-config-https.git at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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.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:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:134) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:125) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 

[JIRA] (JENKINS-32965) Issues with active Choice plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Hi, closing this as cannot reproduce. This could be a core issue, or perhaps a dependency problem. Feel free to re-open the issue, including detailed environment information, and preferably using the latest version of the plug-in with the matching Jenkins LTS version to confirm the issue persists. Thanks Bruno  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32965  
 
 
  Issues with active Choice plugin   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You 

[JIRA] (JENKINS-32965) Issues with active Choice plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32965  
 
 
  Issues with active Choice plugin   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Comment: 
 Hmm, was about to close as cannot reproduce, but first started looking at JIRA and found similar issues. I suspect it is some incompatibility with classes from other plug-ins, or maybe a slave with an outdated jar. Linking similar issues here for now anyway. Let's see what we can find about this exception.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-32965) Issues with active Choice plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-32965  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Issues with active Choice plugin   
 

  
 
 
 
 

 
 Hmm, was about to close as cannot reproduce, but first started looking at JIRA and found similar issues. I suspect it is some incompatibility with classes from other plug-ins, or maybe a slave with an outdated jar. Linking similar issues here for now anyway. Let's see what we can find about this exception.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Are the messages the same for the  other  working  builds? The warnings plugin should report a line that shows the actual number of warnings...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Are the messages the same for the other builds? The warnings plugin should report a line that shows the actual number of warnings...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42683) ci-game-plugin shall be usable from pipelines

2017-03-10 Thread martin.pe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 m perzl created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42683  
 
 
  ci-game-plugin shall be usable from pipelines   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 redsolo  
 
 
Components: 
 ci-game-plugin  
 
 
Created: 
 2017/Mar/10 10:42 PM  
 
 
Environment: 
 Jenkins 2.49  ci-game 1.26  
 
 
Labels: 
 plugin pipeline jenkins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 m perzl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

[JIRA] (JENKINS-32965) Issues with active Choice plugin

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32965  
 
 
  Issues with active Choice plugin   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 

  
 
 
 
 

 
 Hi I am trying to use active choice parameter , with the sample groovy script provided in the link : https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+PluginI am receiving following exceptions while executing the job , could you please help .  Release : 1.3 A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack trace {noformat} javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tonldevops/data/jenkins-home/plugins/uno-choice/WEB-INF/lib/uno-choice.jar!/org/biouno/unochoice/common/selectContent.jelly:4:52:  org/jenkinsci/remoting/RoleSensitive at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at 

[JIRA] (JENKINS-33473) Groovy script with default values when job is started by timer

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-33473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Groovy script with default values when job is started by timer   
 

  
 
 
 
 

 
 Triaging issues, had already no idea what this issue was about. Love that I know myself and leave this notes to myself in the comments  triaging 1.5.3, but only including minor issues, as there are other unreleased changes waiting to be published. Look forward to 1.5.4. The next development cycle starts immediately after 1.5.3 is released, due to extremely ugly weather here   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade

2017-03-10 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert edited a comment on  JENKINS-42676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade   
 

  
 
 
 
 

 
 Did you literally used those double curly braces? If yes, that's completely wrong. Where did you get that from?Contact me via the email listed in my github-profile and I can send you some working examples.BTW: cloud-init is quite picky about indentation.Edit:Did the cloud-init log file exist at least? If not: Maybe your specific image does not have cloud-init incuded? Just seen: In that blog, they mention using a config-drive. You should probably ask them if this works with regular metadata as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42557) Reactive reference value not available to downstream AC parameter

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42557  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Reactive reference value not available to downstream AC parameter   
 

  
 
 
 
 

 
 The fix is already in 1.5.3-alpha (released some time ago). Will triage other issues, and if there is any very simple issues to include, they will be all released tomorrow Sunday NZ time, as 1.5.3. Remember to use a test bed server when installing the new plug-in, before updating it your production servers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42643) Conditional application of triggers in Declarative

2017-03-10 Thread docw...@gerf.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-42643  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Conditional application of triggers in Declarative   
 

  
 
 
 
 

 
 ❤️ Maybe allow with to work anyplace? Or at least most places? e.g. the properties section (or options or whatever it is called) as well as inside a stage?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade

2017-03-10 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert edited a comment on  JENKINS-42676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade   
 

  
 
 
 
 

 
 Did you literally used those double curly braces? If yes, that's completely wrong. Where did you get that from?Contact me via the email listed in my github-profile and I can send you some working examples.BTW: cloud-init is quite picky about indentation. Edit:Did the cloud-init log file exist at least? If not: Maybe your specific image does not have cloud-init incuded?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42655) Active choices parameters not rendering after dsl generation

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active choices parameters not rendering after dsl generation   
 

  
 
 
 
 

 
 Hopefully not related to JENKINS-39760 as you reported (thanks for providing detailed environment settings!!) 1.5.2. Will keep that in mind anyway.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42677) AC Reactive Reference value returns null when contains an = sign

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42677  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AC Reactive Reference value returns null when contains an = sign   
 

  
 
 
 
 

 
 1.5.3. will be released tomorrow NZ TIME, should be available as update on Monday GMT. Remember to use a test bed before updating a production installation   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade

2017-03-10 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert commented on  JENKINS-42676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade   
 

  
 
 
 
 

 
 Did you literally used those double curly braces? If yes, that's completely wrong. Where did you get that from? Contact me via the email listed in my github-profile and I can send you some working examples. BTW: cloud-init is quite picky about indentation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42677) AC Reactive Reference value returns null when contains an = sign

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42677  
 
 
  AC Reactive Reference value returns null when contains an = sign   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42677) AC Reactive Reference value returns null when contains an = sign

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita stopped work on  JENKINS-42677  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42677) AC Reactive Reference value returns null when contains an = sign

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-42677  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AC Reactive Reference value returns null when contains an = sign   
 

  
 
 
 
 

 
 Ioannis Moutsatsos cannot reproduce it locally. Fixed in 1.5.3-alpha. Will cut a release this weekend with the fixes we have so far since the last release (see Wiki for complete list). Tested locally, importing the config.xml (thanks a ton for that, saved me a lot of time), works fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42573) Possibly incorrect quoting logic for system properties passed to gradle cli

2017-03-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42573  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Possibly incorrect quoting logic for system properties passed to gradle cli   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stefan Wolf Path: README.md src/main/java/hudson/plugins/gradle/Gradle.java src/test/groovy/hudson/plugins/gradle/GradlePluginIntegrationTest.groovy http://jenkins-ci.org/commit/gradle-plugin/7752876638cc371cb7dfaf81e35cb5644e8f10e4 Log: Drop custom parameter escaping Escaping done by `addKeyValuePairs` is already enough. [FIXED JENKINS-42573]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42573) Possibly incorrect quoting logic for system properties passed to gradle cli

2017-03-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42573  
 
 
  Possibly incorrect quoting logic for system properties passed to gradle cli   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42677) AC Reactive Reference value returns null when contains an = sign

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita started work on  JENKINS-42677  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread vladd...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vlad Dumitrescu edited a comment on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Oops, exactly when I said that I got a "no warnings" run...    So a three seconds delay doesn't help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-22346) CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-22346  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean   
 

  
 
 
 
 

 
 Whatever was “fixed”, this exception is still thrown under some conditions. As best I can make out, SshCliAuthenticator will write a boolean zero or more times. Typically once, I guess, but it is in a loop of some kind (cannot understand what it is looping over), and maybe zero if a CLI authentication failure is thrown. Then CliManagerImpl.authenticate runs every CliTransportAuthenticator in parallel (?!). Finally CLI.authenticate expects to read a boolean for every private key, and sometimes there is nothing to read so it throws this EOFException instead of explaining what is going on. I think I can reproduce this when you have multiple private keys (say, both DSA and RSA) are not using -i, and none of them match.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42646) Unable to save Jenkinsfile for totally blank github repo

2017-03-10 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-42646  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42646  
 
 
  Unable to save Jenkinsfile for totally blank github repo   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-37220) Job DSL analogue of multibranch projects & organization folders

2017-03-10 Thread docw...@gerf.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-37220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job DSL analogue of multibranch projects & organization folders   
 

  
 
 
 
 

 
 Use case: 

Joe creates a GitHub Org Folder.  His repos foo and bar are scanned and picked up because they have a Jenkinsfile in each. 
foo is a huge repository (2gb) and he only wants the last 10 commits when building (a shallow clone with depth 10) and without any tags. 
bar uses lots of submodules, but isn't big.  He wants the submodule extensions turned on and to use the GitHub Org credentials.
 This could be done by allow adding extensions at the GitHub Org Folder level, but that would mean forcing all builds to have a depth of 10, no tags, and submodules turned on.  This could cause people to split the GitHub Orgs up just to accommodate Jenkins (which may not be possible, if they are paying for the Orgs, etc.) An idea is we could change the scm from an Object to the list form (I don't know what it is called) that looks like [$class:GitSCM, extensions: ... ] I have some code I run in a trusted pipeline via the src/ directory that almost does this... 

 

 class ScmEditablizer {
 static def makeScmEditable(scm, env) {
Integer i

def branches = []
for (i = 0; i < scm.branches.size(); i++) {
def it = scm.branches.get(i)
branches.add([name: it.getName()])
}

def userRemoteConfigs = []
for (i = 0; i < scm.userRemoteConfigs.size(); i++) {
def it = scm.userRemoteConfigs.get(i)
userRemoteConfigs.add([
name:  it.getName(),
url:   it.getUrl(),
credentialsId: it.getCredentialsId(),
refspec:   it.getRefspec()
])
}

return [ $class: 'GitSCM', extensions: [], branches: branches, userRemoteConfigs: userRemoteConfigs ]
}
}
 

 But this doesn't work because the extensions are missing and it doesn't understand Pull Requests (I don't know why exactly). This allows getting an "editable" scm object that can have extensions, etc. added to it.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
   

[JIRA] (JENKINS-40179) Stray comma at end of HTML value passed to build step

2017-03-10 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40179  
 
 
  Stray comma at end of HTML  value passed to build step   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42650) Pipeline Editor Tweaks

2017-03-10 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42650  
 
 
  Pipeline Editor Tweaks   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 

  
 
 
 
 

 
 A few outstanding tasks: * provide a popup that they'll lose their work when leaving the page *  swap buttons with load/export if go directly to editor *  sort extension points somehow - alphabetically? (do this last; already solved with new extension mechanism)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-36521) Newline characters in commit logs not parsed correctly

2017-03-10 Thread ljader...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Łukasz Jąder commented on  JENKINS-36521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Newline characters in commit logs not parsed correctly   
 

  
 
 
 
 

 
 Hi Reinhold Füreder, Honestly I'm with Jesse on having this reported as a separate issue. I've ran an initial analysis and I think parsing commit message should be implemented as in Git Plugin. The git-plugin checks if there is a blank 2nd line (commit message with format http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) and displays only this line on main job page and each build page, but it displays full commit message on "Changes" section (job/test-git-repo/4/changes). Just for reference, please checkout usage of "msgAnnotated" and "commentAnnotated" here: https://github.com/jenkinsci/git-plugin/blob/master/src/main/resources/hudson/plugins/git/GitChangeSetList/index.jelly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread vladd...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vlad Dumitrescu commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Oops, exactly when I said that I got a "no warnings" run...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread vladd...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vlad Dumitrescu commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Yep, a sleep seems to fix it, so I guess it's a duplicate of  JENKINS-32191. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-7470) hudson-cli.jar login does not work with ActiveDirectory authentication

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7470  
 
 
  hudson-cli.jar login does not work with ActiveDirectory authentication   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 cli  
 
 
Labels: 
 cli  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-41745) Remoting-free CLI

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-41745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remoting-free CLI   
 

  
 
 
 
 

 
 Linking any issues I could find that might be related, affected, or obsoleted.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-10305) when using Active Directory Authentication, all CLI commands can only be run as Annonymous

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-10305  
 
 
  when using Active Directory Authentication, all CLI commands can only be run as Annonymous   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 cli  
 
 
Labels: 
 cli  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-10727) hudson-cli.jar login does not work together with Collabnet TeamForge

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-10727  
 
 
  hudson-cli.jar login does not work together with Collabnet TeamForge   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 cli  
 
 
Labels: 
 cli  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-26183) Unable to delete a workflow-like build using jenkins-cli

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26183  
 
 
  Unable to delete a workflow-like build using jenkins-cli   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-32705) install-plugin command can leave behind broken files

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32705  
 
 
  install-plugin command can leave behind broken files   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 robustness  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-32705) install-plugin command can leave behind broken files

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32705  
 
 
  install-plugin command can leave behind broken files   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Summary: 
 jenkins install - cli.jar should not use PWD for temporary plugin command can leave behind broken  files  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42676) Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade

2017-03-10 Thread manuel.vace...@enalean.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Vacelet commented on  JENKINS-42676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to ssh provisionned node on openstack (rackspace) after 2.8 -> 2.14 upgrade   
 

  
 
 
 
 

 
 Thanks for the follow-up 

It should all have been automatically migrated. Didn't it do that?
 Sort of, the elements related to rackspace APIs seems to have been properly migrated (as I can see server beeing created) but for the rest it's unclear. 

The admin credentials are used for provisioning resp. running the init-script and can be either SSH-credentials or Username/Password credentials (depends on Provider, I don't have a rackspace account so I don't know the specifics there)
 Maybe there is an issue there because I either tried to: 
 
Leave it blank (as it was before upgrade) 
Set root + private key 
 And none of these worked. So I gave a try to cloud-init, it seems to work better (at least the node is not terminated because jenkins cannot ssh it) but I didn't manage to got it right. Here was I now have in the logs: Mar 10, 2017 9:08:11 PM org.jclouds.logging.jdk.JDKLogger logInfo INFO: >> creating new server region(IAD) name(stuff-ba2) image(9ab07706-4b9f-41ad-a8f5-8b4fda2e40f7) flavor(general1-1) options(CreateServerOptions{keyName=null, metadata={Name=stuff, jclouds-group=stuff}, userData=#cloud-config users: - name: jenkins {{ homedir: /jenkins}} {{ ssh-authorized-keys:}} {{ - ssh-rsa B}} {{ sudo: ['ALL=(ALL) NOPASSWD:ALL']}} {{ groups: sudo}} {{ shell: /bin/bash}} phone_home: {{ url: https://ci.tuleap.org/jenkins/jclouds-phonehome/}} {{ tries: 3}} {{ , availabilityZone=null, configDrive=false})}} Mar 10, 2017 9:08:14 PM org.jclouds.logging.jdk.JDKLogger logInfo INFO: << PENDING node(IAD/7429c130-a6f9-4820-84d1-03e86418a847) Mar 10, 2017 9:08:37 PM org.jclouds.logging.jdk.JDKLogger logInfo INFO: << customized node(IAD/7429c130-a6f9-4820-84d1-03e86418a847) Mar 10, 2017 9:08:37 PM jenkins.plugins.jclouds.compute.JCloudsSlave createComputer INFO: Creating a new JClouds Slave Mar 10, 2017 9:08:37 PM jenkins.plugins.jclouds.compute.PhoneHomeMonitor waitForPhoneHome INFO: Waiting for stuff-ba2 to phone home. 900 seconds until timeout. As I was not able to ssh the node, I imaged it and spawn a new node based on the image but I didn't find a reference to my cloud-init setting on this debug image (I looked in /var/lib/cloud/instance/cloud-config.txt as well as /var/log/cloud-init.log). How can I know if I did my config correctly ?{{}}  
 

  
 
 
 
 

 
 
 

 
  

[JIRA] (JENKINS-41085) jenkins-cli quiet-down -block does not block with pipeline jobs

2017-03-10 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41085  
 
 
  jenkins-cli quiet-down -block does not block with pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 documentation pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Are the messages the same for the other builds? The warnings plugin should report a line that shows the actual number of warnings... Maybe this is related to JENKINS-32191. Can you please add a sleep after your erlang build step?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42642  
 
 
  Warnings reported intermittently   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Resolution: 
 Incomplete  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread vladd...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vlad Dumitrescu commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 Do you mean this? It is identical to the other jobs' (except for the reference build for deltas) ===> Compiling erlide_ide _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused [Pipeline] step [WARNINGS] Parsing warnings in console log with parser Erlang Compiler (erlc) [WARNINGS] Parsing warnings in console log with parser Maven [WARNINGS] Computing warning deltas based on reference build #26 [Pipeline] step  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42095) Checkstyle plugin not working in pipeline

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-42095  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Checkstyle plugin not working in pipeline   
 

  
 
 
 
 

 
 Is it ok to close this issue? I think that using the checkstyle plugin right after  the  creating of the checkstyle.xml file should do the trick. (Creating and reading the checkstyle results must be within the same *node*)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42095) Checkstyle plugin not working in pipeline

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-42095  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Checkstyle plugin not working in pipeline   
 

  
 
 
 
 

 
 Is it ok to close this issue? I think that using the checkstyle plugin right after creating of the checkstyle.xml file should do the trick. (Creating and reading the checkstyle results must be within the same *node*  block in the Jenkinsfile )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42095) Checkstyle plugin not working in pipeline

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Is it ok to close this issue? I think that using the checkstyle plugin right after the creating of the checkstyle.xml file should do the trick. (Creating and reading the checkstyle results must be within the same node)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42095  
 
 
  Checkstyle plugin not working in pipeline   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe 

[JIRA] (JENKINS-41067) NullPointerException when using InfluxDB Plugin in Pipeline script

2017-03-10 Thread kneppe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Knepper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41067  
 
 
  NullPointerException when using InfluxDB Plugin in Pipeline script   
 

  
 
 
 
 

 
Change By: 
 John Knepper  
 
 
Attachment: 
 Screen Shot 2017-03-10 at 12.59.22 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-41067) NullPointerException when using InfluxDB Plugin in Pipeline script

2017-03-10 Thread kneppe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Knepper commented on  JENKINS-41067  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when using InfluxDB Plugin in Pipeline script   
 

  
 
 
 
 

 
 Aleksi Simell I apologize I do not have much familiarity with this pipeline.  This is what I have:     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-32809) SCM workspace being flushed to 0 when old builds are discarded in Matrix Builds

2017-03-10 Thread vik...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikram Parthasarathy commented on  JENKINS-32809  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM workspace being flushed to 0 when old builds are discarded in Matrix Builds   
 

  
 
 
 
 

 
 I'm running into the same issue as well. Any updates? Thanks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 What are the [WARNINGS] messages in the console log for job 27 .  ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 What are the [WARNINGS] messages in the console log for job 27.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42682) parameters values should be able to expand values of ther parameters

2017-03-10 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42682  
 
 
  parameters values should be able to expand values of ther parameters   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Jenkins 2017-03-10 20-45-05.png  
 
 
Components: 
 core  
 
 
Created: 
 2017/Mar/10 8:53 PM  
 
 
Labels: 
 parameters  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sorin Sbarnea  
 

  
 
 
 
 

 
 Is seem that currently it is impossible to user values of already defined parameters in order to simplify parameter usage and avoid repetition (DRY principle). I will give this bash example in order to explain value expansions as they work in bash (probably the most known syntax. 

 

#!/bin/bash
PARAM1="AAA"
PARAM2="Some $AAA text"
PARAM3="Other ${AAA} text"
PARAM4="3th example which resolves ${AAA:-ZZZ} as ZZZ when AAA is not defined"
 

 If we want to put these 4 parameters in Jenkins we have no option for allowing the user to than only the value of PARAM1, because Jenkins does not perform variable expansion of the default values. You may wonder why this is so important because sounds like a really weird use case. For this reason I will provide one screenshot from our current build parameters.  As you can imagine we do have other branches for other numeric values than "11.0". At this moment if a user wants to build a specific branch 

[JIRA] (JENKINS-42642) Warnings reported intermittently

2017-03-10 Thread vladd...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vlad Dumitrescu edited a comment on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 As you can see, builds 24 to 30 are for the same commit. #27 reports no warnings  (not only the graph) . The logs for each run are identical (except timestamps and such). The relevant lines are below the image, as well as the excerpt from the Jenkinsfile calling the reporter.!jenkins_error.png!===> Compiling erlide_ide _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused  step([$class: 'WarningsPublisher', canComputeNew: false, canResolveRelativePaths: true, canRunOnFailed: true, consoleParsers: [[parserName: 'Erlang Compiler (erlc)'], [parserName: 'Maven']], excludePattern: '', healthy: '', includePattern: '', messagesPattern: '', unHealthy: ''])    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42642) Warnings reported intermittently

2017-03-10 Thread vladd...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vlad Dumitrescu commented on  JENKINS-42642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings reported intermittently   
 

  
 
 
 
 

 
 As you can see, builds 24 to 30 are for the same commit. #27 reports no warnings. The logs for each run are identical (except timestamps and such). The relevant lines are below the image, as well as the excerpt from the Jenkinsfile calling the reporter.  ===> Compiling erlide_ide _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused   step([$class: 'WarningsPublisher', canComputeNew: false, canResolveRelativePaths: true, canRunOnFailed: true, consoleParsers: [[parserName: 'Erlang Compiler (erlc)'], [parserName: 'Maven']], excludePattern: '', healthy: '', includePattern: '', messagesPattern: '', unHealthy: ''])    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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


  1   2   3   4   >