date:20161019

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39125  
 
 
  Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39125  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
 Owen legitimately mentioned that there is "com.cloudbees.jenkins.plugins.customtools.CustomToolInstallWrapper.decorateLauncher()" in the call. This call implements installation of tools on the master, which runs a as a part if the build step and require the environment. This behavior is compliant with Jenkins core API. The Custom Tool Plugin's behavior is correct. So the problem is with File locking. It may be self-locking of the installer or a conflict/bug somewhere. Or just an antivirus/whatever locking the file. Owen Wood I need the following info: 1) File usage by processes stats. E.g. ProcessExcplorer can provide it 2) If the file is locked by Jenkins itself, use http://file-leak-detector.kohsuke.org/ to triangulate the original lock cause   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev edited a comment on  JENKINS-39125  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
 Maven Tool Installer is a MavenToolInstallation and MavenInstaller  are the  part of  Maven plugin  the Jenkins core , not Custom Tools Plugin .https://github.com/jenkinsci/jenkins/blob/2311ae8a5e7afd550b13909b4b1c4ae3338274dd/core/src/main/java/hudson/tasks/Maven.java  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39125  
 
 
  Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 
 
Component/s: 
 maven-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39125  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
 Maven Tool Installer is a part of Maven plugin, not Custom Tools Plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39125  
 
 
  Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39125  
 
 
  Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 maven-plugin  
 
 
Component/s: 
 customtools-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39130) Jenkins JNLP agents should not connect/schedule builds if the workspace cannot be created

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39130  
 
 
  Jenkins JNLP agents should not connect/schedule builds if the workspace cannot be created   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core, remoting  
 
 
Created: 
 2016/Oct/20 5:08 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 It's a pretty old behavior, but I think it makes sense to fix it at some point: 1) Setup the non-existent folder as a workspace for JNLP slaves 2) Start slave from the user who has no permissions to create folders in the path 3) Start JNLP slave Expected result: 1) Slave startup fails (like in SSH slaves) Actual result: 1) Slave starts 2) Slaves accepts the builds 3) The builds fail  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39129) We are not able to delete few jobs .. A problem occurred while processing the request.

2016-10-19 Thread sreejith.pulik...@socgen.com (JIRA)

Title: Message Title

sreejith pulikkal created an issue

Jenkins / JENKINS-39129

We are not able to delete few jobs .. A problem occurred while processing the request.

Issue Type:
Bug

Assignee:
Unassigned

Components:
core

Created:
2016/Oct/20 4:48 AM

Environment:
Linux

Priority:
Major

Reporter:
sreejith pulikkal

We are not able to delete few jobs in jenkins,While we deleting the jobs we are getting below error. Please help us to solve the same. We tried deleting the job after restarting jenkins instance also still the issue persist. 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. javax.servlet.ServletException: java.lang.NullPointerException 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

[JIRA] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page

2016-10-19 Thread mdono...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 mdonohue commented on  JENKINS-38581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins auto linkification for Bugzilla is broken on the build page   
 

  
 
 
 
 

 
 I am still not able to reproduce with the subversion plugin, alongside Fisheye integration. It's very difficult to guess what the root cause is without a way to reproduce the problem. Can you try building a test Jenkins setup, and add one plugin at a time, until the problem reproduces there?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39128) Not able to sent email from SMTP setup in Jenkins

2016-10-19 Thread prashanth.ti...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Prashanth Aedulapuram created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39128  
 
 
  Not able to sent email from SMTP setup in Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2016/Oct/20 4:15 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Prashanth Aedulapuram  
 

  
 
 
 
 

 
 Unable to configure and send email by configuring SMTP Failed to send out e-mail javax.mail.AuthenticationFailedException: 534-5.7.14  Please log in via your web browser and 534-5.7.14 then try again. 534-5.7.14  Learn more at 534 5.7.14  https://support.google.com/mail/answer/78754 y77sm36100116pfi.69 - gsmtp  at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:809)  at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:752)  at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:669)  at javax.mail.Service.connect(Service.java:317)  at javax.mail.Service.connect(Service.java:176)  at javax.mail.Service.connect(Service.java:125)  at javax.mail.Transport.send0(Transport.java:194)  at javax.mail.Transport.send(Transport.java:124)  at hudson.tasks.Mailer$DescriptorImpl.doSendTestMail(Mailer.java:581)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)  at java.lang.reflect.Method.invoke(Unknown Source)  at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324)  at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167)  at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100)  at

[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Collect browser logs and publish via support-core   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 To enable better tracing of errors in blueocean, client side web console errors need to be collected and reported, via the server, to the support core plugin.In scope: * Trap all js errors on the client side* Publish errors to server side endpoint (jenkins under /blue/rest)* A support core "Component" to publish client side logs/data to their own file as needed (similar to browser.md now)* Capture additional information (like headers/response payloads) for failures and publish them to server side endpointNice to have scope: * Client side component may not need be blueocean generic - if possible make it work with classic* Server side collection point may best live outside of blueocean if possible* support-core component may actually be able to be contributed to the support core plugin itself, meaning that there is no blueocean specific code in all thishttps://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Some interesting reading: http://jsnlog.com/ https://scotch.io/tutorials/how-to-log-client-side-_javascript_-errors  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-39127) Report on slow UI components or routes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39127  
 
 
  Report on slow UI components or routes   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Labels: 
 supportability  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39127) Report on slow UI components or routes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39127  
 
 
  Report on slow UI components or routes   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Oct/20 3:41 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 The https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin automatically tracks slow requests (eg if a request takes > 10s, it will take threadumps and do other diagnostic things). The benefit is that when someone is having a bad time, the evidence is already recorded to point to the culprit.  In a SPA like blue ocean, this works nicely for the REST endpoints (which are a source of problems, but not alone). What we lose is the ability to map slowness in the support bundle to what the user is seeing.  In scope:  
 
Investigate if there are ways to track time taken by react components (render time?) 
Investigate if there are ways to track time used in routes (render time?) 
Collect profiling data, and publish to (new) endpoint

[JIRA] (JENKINS-39098) Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39098  
 
 
  Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39098) Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please don't use bug reports to ask questions. The Jenkins user mailing list includes many people who can assist with your questions, while individual plugins are usually maintained by a much smaller group of people.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39098  
 
 
  Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message

[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39126  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Collect browser logs and publish via support-core   
 

  
 
 
 
 

 
 NOTE: split this into server/client components if it makes sense for implementation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Collect browser logs and publish via support-core   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 To enable better tracing of errors in blueocean,  collection of logs from the  client side  if required  web console errors need to be collected and reported, via the server, to the support core plugin .For In scope: * Trap all js errors on  the client side * Publish errors  to  work, a  server side  component is required to collect the logs  endpoint  ( so the client side js can publish them jenkins under /blue/rest ) .   The * A  support - core  plugin can be extended by implementing a  "Component"  extension point. This can then be used  to  write out the  publish  client side logs /data  to their own file  ( as  an alternative  needed (similar  to  inserting  browser.md now)* Capture additional information (like headers/response payloads) for failures and publish  them  in the normal serverside log  to server side endpointNice to have scope: * Client side component may not need be blueocean generic  -  which is  if  possible , but preferable to keep them separate)  make it work with classic  * Server side collection point may best live outside of blueocean if possible  Support * support-  core  component may actually be able to be contributed to the support core  plugin :  itself, meaning that there is no blueocean specific code in all this  https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin  (this should be an optional dependency only)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Collect browser logs and publish via support-core   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Summary: 
 Endpoint to collect Collect  browser logs and  publish via  support -  core  component to publish them  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39126) Endpoint to collect browser logs and support core component to publish them

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Endpoint to collect browser logs and support core component to publish them   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 To enable better tracing of errors in blueocean, collection of logs from the client side if required. For the client side to work, a server side component is required to collect the logs (so the client side js can publish them). The support-core plugin can be extended by implementing a "Component" extension point. This can then be used to write out the client side logs to their own file (as an alternative to inserting them in the normal serverside log - which is possible, but preferable to keep them separate) Support core plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39126) Endpoint to collect browser logs and support core component to publish them

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Endpoint to collect browser logs and support core component to publish them   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 To enable better tracing of errors in blueocean, collection of logs from the client side if required. For the client side to work, a server side component is required to collect the logs (so the client side js can publish them). The support-core plugin can be extended by implementing a "Component" extension point. This can then be used to write out the client side logs to their own file (as an alternative to inserting them in the normal serverside log - which is possible, but preferable to keep them separate)Support core plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin  (this should be an optional dependency only)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39126) Endpoint to collect browser logs and support core component to publish them

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Endpoint to collect browser logs and support core component to publish them   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Oct/20 3:17 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 To enable better tracing of errors in blueocean, collection of logs from the client side if required.  For the client side to work, a server side component is required to collect the logs (so the client side js can publish them).  The support-core plugin can be extended by implementing a "Component" extension point. This can then be used to write out the client side logs to their own file (as an alternative to inserting them in the normal serverside log - which is possible, but preferable to keep them separate)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39126) Endpoint to collect browser logs and support core component to publish them

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39126  
 
 
  Endpoint to collect browser logs and support core component to publish them   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Labels: 
 supportability  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking

2016-10-19 Thread ow...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Wood created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39125  
 
 
  Windows: Cannot change Maven custom tool installer due to slave file locking   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 customtools-plugin  
 
 
Created: 
 2016/Oct/20 3:09 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Owen Wood  
 

  
 
 
 
 

 
 Unable to update Maven Custom Tool on Windows slaves due to file lock on Maven process. Cause: 

 

18:53:36 Caused by: java.io.IOException (http://stacktrace.jenkins-ci.org/search?query=java.io.IOException) : remote file operation failed: C:\JENKINS_HOME\tools\hudson.tasks.Maven_MavenInstallation\Maven3-3-3-lockfix at hudson.remoting.Channel@2b1d2861:bld2k8-03: java.nio.file.FileSystemException: C:\JENKINS_HOME\tools\hudson.tasks.Maven_MavenInstallation\Maven3-3-3-lockfix\lib\maven-core-3.3.9.jar: The process cannot access the file because it is being used by another process.
 

 Full Output (job logs): Replaced: 
 
JENKINS_HOME location with C:\JENKINS_HOME (windows) 
Nexus URL with NEXUS_URL 
 

 

18:53:36 [JDK_8u91_JCEP] $ cmd /c call C:\JENKINS_HOME\tools\hudson.model.JDK\JDK_8u91_JCEP\hudson7143384717113035922.bat

18:53:36 FATAL: Failed to install NEXUS_URL/nexus/content/repositories/ebu-tools/org/apache/maven/apache-maven/3.3.3/apache-maven-3.3.3-corefix-lockfix.zip

[JIRA] (JENKINS-39124) SSE ping check to confirm operational (diagnostic helper)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39124  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSE ping check to confirm operational (diagnostic helper)   
 

  
 
 
 
 

 
 Tom FENNELLY I thought this might be up your alley at some point. I am not sure what I am describing is reasonable, but worth thinking about IMO.  If this looks too likely to generate false alerts, maybe we dont do it (but its output should only be in the console log - at least until we are 100% confident - if we were, we could politely tell the user to ask for help).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39124) SSE ping check to confirm operational (diagnostic helper)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Tom FENNELLY  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39124  
 
 
  SSE ping check to confirm operational (diagnostic helper)   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Tom FENNELLY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39124) SSE ping check to confirm operational (diagnostic helper)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39124  
 
 
  SSE ping check to confirm operational (diagnostic helper)   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Labels: 
 supportability  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39124) SSE ping check to confirm operational (diagnostic helper)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39124  
 
 
  SSE ping check to confirm operational (diagnostic helper)   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Oct/20 3:07 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 SSE is a core requirement for good operation of blueocean.  It makes sense to have a check in the background at some point that triggers an SSE callback that the front end can expect to arrive in a certain amount of time. Should this fail to arrive, the client could log a console error saying "SSE appears to not be supported". This would flush out incompatible proxies or at least eliminate SSE push events as a problem for supportability.  Needs exploration. Should SSE fail to work we can then look at the network/proxy config (but this means we don't need to guess).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-39098) Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone

2016-10-19 Thread saifulfai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 saiful faizee commented on  JENKINS-39098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone   
 

  
 
 
 
 

 
 Hi, Thanks for your reply. Actually i just want to know what/how to put in the Git > Repository Url as per attached ? From the attachment, you can see that url which i always used to clone the branch in my project, but when i put there, the error always appeared. FYI, my git repo was in AWS server.Please advise and thanks in advance.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39117) NPE at git SCM polling

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-39117  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPE at git SCM polling   
 

  
 
 
 
 

 
 The stack trace seems to point to a problem in the checkmarx plugin and its EnvVarAction.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39117) NPE at git SCM polling

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39117  
 
 
  NPE at git SCM polling   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Component/s: 
 checkmarx-plugin  
 
 
Component/s: 
 git-client-plugin  
 
 
Component/s: 
 git-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39117) NPE at git SCM polling

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39117  
 
 
  NPE at git SCM polling   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39123) Fix the HTML Report security problem in Jenkins plugin

2016-10-19 Thread xiwen.z...@hpe.com (JIRA)

Title: Message Title

xiwen zhao created an issue

Jenkins / JENKINS-39123

Fix the HTML Report security problem in Jenkins plugin

Issue Type:
New Feature

Assignee:
Ofir Shaked

Components:
hp-application-automation-tools-plugin

Created:
2016/Oct/20 2:30 AM

Priority:
Major

Reporter:
xiwen zhao

current Jenkins version cannot display the HTML report because of Content Security Policy. https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy The policy bans JS, CSS, etc, affecting a lot of report plugin. Currently the workaround is to disable this Content Security Policy in Jenkins script console by executing this script: System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "") The Jenkins script console can be accessed from the "manage Jenkins" link, typically at your http://server/jenkins/script. You can see the https://wiki.jenkins-ci.org/display/JENKINS/Jenkins%20Script%20Console for details about Jenkins script console. About the issue - It’s due to use of Iframes, Inline JS, inline CSS and other minor issues that lead to our reports being blocked on Jenkins. Current solution (workaround for LR and UFT) – published on the plugin page on jenkins.io - https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-ContentSecurityPolicyHeader Long term solution – • on LR side were working on two solutions – 1. Planned new LR report for 14.00. 2. New JS reporting engine to present a jenkins made report for LR. • On overall plugin side – no overall solution is possible due to difference in reports.

[JIRA] (JENKINS-39087) Add ability to mark a multibranch pipeline as a favourite - NOT a branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-39087  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ability to mark a multibranch pipeline as a favourite - NOT a branch   
 

  
 
 
 
 

 
 [~jamesdumay] we should think on this more. Having a favourite as a shortcut is not unreasonable, and may solve the related issue of what to do when there is no default branch...My thoughts: If a user fav's a MB pipeline that has a master branch, fav the master branch. If they fav a MB that doesn't have a master branch, fav just the MB itself, show now branch status or ability to run (the fav just becomes a short cut to the activity screen for that MB pipeline).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39087) Add ability to mark a multibranch pipeline as a favourite - NOT a branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39087  
 
 
  Add ability to mark a multibranch pipeline as a favourite - NOT a branch   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Sprint: 
 indian  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38223) FlowNode.isRunning is not very useful

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FlowNode.isRunning is not very useful   
 

  
 
 
 
 

 
 Agree Jesse - if that is the spec, that is the spec. Perhaps a clearer name would help, but this is much needed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39017) archiveArtifacts produces an empty/erroneous log for Blue Ocean

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39017  
 
 
  archiveArtifacts produces an empty/erroneous log for Blue Ocean   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Michael Neale  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39122) Certain Groovy expressions cause Global Library loading to Silently Fail

2016-10-19 Thread d...@baltrinic.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenneth Baltrinic updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39122  
 
 
  Certain Groovy expressions cause Global Library loading to Silently Fail   
 

  
 
 
 
 

 
Change By: 
 Kenneth Baltrinic  
 

  
 
 
 
 

 
 h2. SummaryCertain legitimate groovy expressions, when present in a groovy global shared library will cause any pipeline job that attempts to load the library to hang at the point immediately after the library is loaded.  This occurs with no errors in the job console nor any errors in the jenkins logs, effectively leaving the user to have to start guessing at possible causes.h2. Steps to ReproduceI don't know if there are other scenarios that will cause this but here is a reproducible one that I have come up with.h3. Step 1Create a repo in git and configure it to be loaded on demand.  In our case we are loading under the name 'pipeline- libs utils '.h3. Step 2Create the following file in that library:{ { quote} /src/examples/Bug.groovy {quote } } with conntent: {code: groovy java }package examplesimport groovy.transform.Field// This is the line that seems to be the real cause of the problem.  A final static field that invokes a function to get its value.@Field def static final API_BASE_URL = absolutizeUrl("api")def static absolutizeUrl(relativeUrl) { return "http://myserver/${relativeUrl}" }{code}h3. Step 3Now create a pipeline job with the following DSL:{code: groovy java }@Library('pipeline-utils')import examples.Bug//Though the bug seems to be triggered by the field declaration, it isn't activated if we don't invoke a function from the class in question.println Bug.absolutizeUrl('ui'){code}h3. Step 4Run this job and you will get output similar to the following:{code}Started by user Baltrinic, KennethLoading library pipeline-utils@master > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://git@stash:7999/jenkins/pipeline-utils.git # timeout=10Fetching upstream changes from ssh://git@stash:7999/jenkins/pipeline-utils.git > git --version # timeout=10 > git fetch --tags --progress ssh://git@stash:7999/jenkins/pipeline-utils.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10Checking out Revision 164a989ac7555e33541894d966075819c3e66143 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 164a989ac7555e33541894d966075819c3e66143 > git rev-list 395d5408a41619030e2855f01bb55a7103ce6b10 # timeout=10{code}At this point  the job  there  will be  no further console output and the job is  hung and must be forcibly aborted.h2. RecommendationsThis is admittedly an esoteric scenario.  I am not so concerned that a fix be implemented to allow this code to load correctly.  My main concern is that the failure must not be silent.  It may be impossible to account for all the ways in which things might fail to load or be processed by the CPS system, etc.  But better error reporting that clearly identifies the offending file and line number should be possible.  This took me the

[JIRA] (JENKINS-39122) Certain Groovy expressions cause Global Library loading to Silently Fail

2016-10-19 Thread d...@baltrinic.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenneth Baltrinic updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39122  
 
 
  Certain Groovy expressions cause Global Library loading to Silently Fail   
 

  
 
 
 
 

 
Change By: 
 Kenneth Baltrinic  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39122) Certain Groovy expressions cause Global Library loading to Silently Fail

2016-10-19 Thread d...@baltrinic.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenneth Baltrinic created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39122  
 
 
  Certain Groovy expressions cause Global Library loading to Silently Fail   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Oct/20 1:17 AM  
 
 
Environment: 
 Jenkins 2.7.1 with Pipeline 2.4 and Pipeline Shared Groovy Libraries 2.4  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kenneth Baltrinic  
 

  
 
 
 
 

 
 Summary Certain legitimate groovy expressions, when present in a groovy global shared library will cause any pipeline job that attempts to load the library to hang at the point immediately after the library is loaded. This occurs with no errors in the job console nor any errors in the jenkins logs, effectively leaving the user to have to start guessing at possible causes. Steps to Reproduce I don't know if there are other scenarios that will cause this but here is a reproducible one that I have come up with. Step 1 Create a repo in git and configure it to be loaded on demand. In our case we are loading under the name 'pipeline-libs'. Step 2 Create the following file in that library: {{ /src/examples/Bug.groovy}} with conntent:  

 

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


package examples
import groovy.transform.Field

// This is the line that seems to be the real cause of the problem.  A final static field that invokes

[JIRA] (JENKINS-36288) JDL component for Popover

2016-10-19 Thread jmcdon...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald updated  JENKINS-36288  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Merged to trunk. Ideally I'd prefer a new issue for tweaking the layout rules once everybody has had a chance to play with it.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36288  
 
 
  JDL component for Popover   
 

  
 
 
 
 

 
Change By: 
 Josh McDonald  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alastair D'Silva edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 The technique that I proposed when I added a configurable encoding to the branch names is as follows:    { quote code:java }  /** * Create a clean version of the name, suitable for use as file paths * @return the cleaned name */private String stripName() {String name = getName().replaceAll("_", "___"); // Escape all underscoresreturn Util.rawEncode(name).replaceAll("%2F", "_"). // Replace forward slash with underscorereplaceAll("%", "__"); // Replace remaining % with double underscore}{ quote code }  This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alastair D'Silva edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 The technique that I proposed when I added a configurable encoding to the branch names is as follows: {{ /** * Create a clean version of the name, suitable for use as file paths * @return the cleaned name */private String stripName() {String name = getName().replaceAll("_", "___"); // Escape all underscoresreturn Util.rawEncode(name).replaceAll("%2F", "_"). // Replace forward slash with underscorereplaceAll("%", "__"); // Replace remaining % with double underscore} }} This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alastair D'Silva edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 The technique that I proposed when I added a configurable encoding to the branch names is as follows:{ { quote} /** * Create a clean version of the name, suitable for use as file paths * @return the cleaned name */private String stripName() {String name = getName().replaceAll("_", "___"); // Escape all underscoresreturn Util.rawEncode(name).replaceAll("%2F", "_"). // Replace forward slash with underscorereplaceAll("%", "__"); // Replace remaining % with double underscore} {quote } }   This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alastair D'Silva commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 The technique that I proposed when I added a configurable encoding to the branch names is as follows: /** 
 
Create a clean version of the name, suitable for use as file paths 
@return the cleaned name */ private String stripName() { String name = getName().replaceAll("_", "___"); // Escape all underscores return Util.rawEncode(name). replaceAll("%2F", "_"). // Replace forward slash with underscore replaceAll("%", "__"); // Replace remaining % with double underscore } 
 This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can click "Create Pipeline" and open the creation flow process   
 

  
 
 
 
 

 
 As discussed - we want the inverse of the logic that decides if the login button should be shown. If the login button is shown then create should not be shown. If the login is not shown, the create should be shown.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39116) JDK auto installation doesn't occur

2016-10-19 Thread fukusuke.takaha...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fukusuke Takahashi edited a comment on  JENKINS-39116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK auto installation doesn't occur   
 

  
 
 
 
 

 
 Than you for reply.I added build step(Invoke Gradle script) but JDK auto installation never occer.Although JDK auto installation  installation  doesn't occer, Gradle instalaltion work correctly.(also Ant)Is threre anything else to check ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39116) JDK auto installation doesn't occur

2016-10-19 Thread fukusuke.takaha...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fukusuke Takahashi edited a comment on  JENKINS-39116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK auto installation doesn't occur   
 

  
 
 
 
 

 
 Than you for reply.I added build step(Invoke Gradle script) but JDK auto installation  still  never occer.Although JDK auto installation installation doesn't occer, Gradle instalaltion work correctly.(also Ant)Is threre anything else to check ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39116) JDK auto installation doesn't occur

2016-10-19 Thread fukusuke.takaha...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fukusuke Takahashi commented on  JENKINS-39116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK auto installation doesn't occur   
 

  
 
 
 
 

 
 Than you for reply. I added build step(Invoke Gradle script) but JDK auto installation still never occer. Although JDK auto installation installation doesn't occer, Gradle instalaltion work correctly.(also Ant) Is threre anything else to check ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34223) Add configuration field to set additional config options

2016-10-19 Thread daniel.bl...@au.ibm.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Black commented on  JENKINS-34223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add configuration field to set additional config options   
 

  
 
 
 
 

 
 I'd like to set submodule.common.url I have git mirror of a github repo that is being built in numerous ways. This upstream git repo has a large submodule which I've also mirrored. I don't want to pollute the mirror by changing its submodule configuration.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36885) AVD not being created

2016-10-19 Thread amil...@fd-software.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Arie Miller commented on  JENKINS-36885  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AVD not being created   
 

  
 
 
 
 

 
 I ended up figuring out that this was due to the avd config file not having proper line breaks in my scenario.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

2016-10-19 Thread sorin.sbar...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 I find ironic the fact that this fix that was supposed to help is creating more issues. Let's face it: the probability of causing build failures due to path limitations is 1000... times bigger than the one of getting checksum collisions. I have seen LOTS of build failing due to PATH length related issues (for both job and workspace) but never a checksum collision, even for very short ones. 
 
I am sure that someone with more time could compute the real probabilities  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-33761) Ability to disable "resume" build.

2016-10-19 Thread cgro...@fitbit.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Groves commented on  JENKINS-33761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to disable "resume" build.   
 

  
 
 
 
 

 
 Not really. While the build is running normally, we don't want anyone to have to confirm proceeding to the next step. It's only when the build is interrupted by a restart that we don't want it to automatically continue. Whenever Jenkins goes down, it's generally a larger failure with a variable amount of time before service is restored. We can't guarantee that the person watching it will be there when Jenkins comes back without making the normal case worse.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Watkins commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 You could just use a UUID. The canonical form is 36 characters long, and you can express one in Base32 in just 16 characters.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Watkins edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 bq. This is using SHA-256 encoded in Base32So  optionally  use SHA-256 encoded in [RFC-4648|https://en.wikipedia.org/wiki/Base64#RFC_4648]-flavoured Base64 - it'll be half the length. Hmm. No, you'll have potential problems with case-insensitive file systems.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Watkins edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 bq. This is using SHA-256 encoded in Base32So use SHA-256 encoded in  [  RFC-4648 |https://en.wikipedia.org/wiki/Base64#RFC_4648] -flavoured Base64 - it'll be half the length.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Watkins commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 

This is using SHA-256 encoded in Base32
 So use SHA-256 encoded in RFC-4648-flavoured Base64 - it'll be half the length.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections

2016-10-19 Thread nickolay.rumyant...@emc.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nickolay Rumyantsev commented on  JENKINS-27421  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unserializable iterator & entry classes from Java Collections   
 

  
 
 
 
 

 
 A little addition to Jesse Glick's comment: the pain point about looping over Map is that standard Map.entrySet() returns list of non-serializable entry objects, i.e. LinkedHashMap.Entry. Despite the Map itself is indeed Serializable. If talking about values() then I am not so sure because new ArrayList(someMap.values()) is Serializable whereas someMap.values() is not. Jesse Glick, am I in danger of getting NonSerializable Exception if I don't use any intermediate variable to store someMap.values() and immediately pass it into ArrayList constructor?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick edited a comment on  JENKINS-30244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stash command with includes: '**' fails due to "unclosed entries"   
 

  
 
 
 
 

 
 Hmm, will have to see if this can be reproduced using a stock Docker image, or if it needs VirtualBox etc. Do you happen to know how to reproduce from scratch? Does it work on some platforms and fail on others? I was not able to reproduce using a trimmed version of your script in a functional test  on Ubuntu (4 . 4.0-43 x86_64).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-30244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stash command with includes: '**' fails due to "unclosed entries"   
 

  
 
 
 
 

 
 Hmm, will have to see if this can be reproduced using a stock Docker image, or if it needs VirtualBox etc. Do you happen to know how to reproduce from scratch? Does it work on some platforms and fail on others? I was not able to reproduce using a trimmed version of your script in a functional test.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-25508) Git plugin doesn't parse changelog (false "First time build")

2016-10-19 Thread danito8...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Nuss edited a comment on  JENKINS-25508  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin doesn't parse changelog (false "First time build")   
 

  
 
 
 
 

 
 Hi, I had the same problem. I solve it, making a new job copying the existing one and remove then the original.In the new copied job, the changelog work correctly.I hope this helps. Jenkins 1.651.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-25508) Git plugin doesn't parse changelog (false "First time build")

2016-10-19 Thread danito8...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Nuss commented on  JENKINS-25508  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin doesn't parse changelog (false "First time build")   
 

  
 
 
 
 

 
 Hi, I had the same problem.  I solve it, making a new job copying the existing one and remove then the original. In the new copied job, the changelog work correctly. I hope this helps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36288) JDL component for Popover

2016-10-19 Thread jmcdon...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald updated  JENKINS-36288  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36288  
 
 
  JDL component for Popover   
 

  
 
 
 
 

 
Change By: 
 Josh McDonald  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-33761) Ability to disable "resume" build.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-33761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to disable "resume" build.   
 

  
 
 
 
 

 
 I think what you are looking for is an input step between stages. Whether Jenkins happened to be restarted in the middle of the build is not relevant to that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 This is using SHA-256 encoded in Base32, it is different.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34637  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipeline DSL: timeout() does not work if withEnv() is enclosed   
 

  
 
 
 
 

 
 That is an unrelated issue: JENKINS-38380  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-27421  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unserializable iterator & entry classes from Java Collections   
 

  
 
 
 
 

 
 

is there going to be a better way to do that?
 If and when I can figure out how to resolve this issue. 

I'm not seeing the point of us having the have a bunch of helper methods to turn all Collection into ArrayList
 Every usage of an intermediary value which does not implement java.io.Serializable must be encapsulated in a method marked with the @NonCPS annotation in order to run in Pipeline Script. Your safeArray example will not work, since it is both receiving and returning nonserializable values. The point of entries is that it takes a serializable Map, and returns a serializable List. You could probably also have something like (untested): 

 

@NonCPS def entrySet(m) {m.collect {k, v -> [key: k, value: v]}}
for (def e in entrySet(map)) {
  echo "got ${e.key} → ${e.value}"
}
 

 which at least looks more like the standard looping using 

 

for (def e in map.entrySet()) {
  echo "got ${e.key} → ${e.value}"
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process

2016-10-19 Thread vivek (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-38594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can click "Create Pipeline" and open the creation flow process   
 

  
 
 
 
 

 
 Michael Neale Nothing that serves permission outside of pipeline api. Backend can check if user has create permission (anonymous or logged in).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36970) Log api 500 errors to server console

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36970  
 
 
  Log api 500 errors to server console   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Trivial Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39089) ansicolor plugin 0.4.2 is not working with Jenkins ver. 1.651.2

2016-10-19 Thread sammi....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sammi SINGH assigned an issue to Daniel Doubrovkine  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39089  
 
 
  ansicolor plugin 0.4.2 is not working with Jenkins ver. 1.651.2   
 

  
 
 
 
 

 
Change By: 
 Sammi SINGH  
 
 
Assignee: 
 Daniel Doubrovkine  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38867) Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories

2016-10-19 Thread svano...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-38867  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released as workflow-api plugin v 2.5  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38867  
 
 
  Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37455) parameter expansion not done on depotPath in p4Sync Pipeline DSL

2016-10-19 Thread jenk...@richardlee.name (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Lee commented on  JENKINS-37455  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: parameter expansion not done on depotPath in p4Sync Pipeline DSL   
 

  
 
 
 
 

 
 This is actually a higher priority than 'minor', and is a regression from the legacy 'perforce' plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-25549) FlowNode doConfigDotXml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-25549  
 
 
  FlowNode doConfigDotXml   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Summary: 
 FlowNode  should have transient action integration  doConfigDotXml  
 
 
Labels: 
 REST diagnostics  
 

  
 
 
 
 

 
 Long since got {{TransientActionFactory}} integration (cf. JENKINS-38867). Keeping open for the diagnostic RFE.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38476) Always use "-usenonexclusivelock" option

2016-10-19 Thread mustafaulu....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mustafa Ulu closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Not that useful.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38476  
 
 
  Always use "-usenonexclusivelock" option   
 

  
 
 
 
 

 
Change By: 
 Mustafa Ulu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38223) FlowNode.isRunning is not very useful

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38223  
 
 
  FlowNode.isRunning is not very useful   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Summary: 
 Incorrect state of completed parallel branch FlowNode.isRunning is not very useful  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38223) Incorrect state of completed parallel branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Incorrect state of completed parallel branch   
 

  
 
 
 
 

 
 I still think the method is behaving according to spec—it is just not a useful spec. When the branch has completed, a BlockEndNode is created and becomes one of the heads of the flow graph. Thus it isRunning() according to the definition. The spec will not be changed (that would not be compatible), so the most that would be done is to deprecate the method, and possibly introduce a new method with a different semantics: example  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-38594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can click "Create Pipeline" and open the creation flow process   
 

  
 
 
 
 

 
 [~cliffmeyers] well per pipeline permissions won't work here as we are creating a new pipeline. I would say for starters as long as they aren't read only we can at least offer to let them try to create a pipeline. If the permissions are more fine grained than we realise at the backend, we will see errors, and can adjust course ;) Would [~vivek] do you know of any existing permissions in jenkins, perhaps  that  work  blue ocean already exposes via the API, that could be used to decide if the create pipeline link should be shown or not ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections

2016-10-19 Thread ben.d...@ontariosystems.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Dean commented on  JENKINS-27421  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unserializable iterator & entry classes from Java Collections   
 

  
 
 
 
 

 
 Jesse Glick, is there going to be a better way to do that? Because it seems a little silly to have my Jenkinsfile scripts littered with stuff like 

 

@NonCPS def safeArray(c) {
c.collect { v -> v }
}

// ...
def someMap = [a: 1, b:2]
for (def thing in safeArray(someMap.values())) {
  echo "do something with $thing"
}
 

 in fact, why bother with .collect, it just needs to be an ArrayList 

 

def someMap = [a: 1, b:2]
for (def thing in new ArrayList(someMap.values())) {
  echo "do something with $thing"
}
 

 which needs script security approval, But that's basically what .collect is doing. I guess I'm not seeing the point of us having the have a bunch of helper methods to turn all Collection into ArrayList.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36885) AVD not being created

2016-10-19 Thread oldel...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Mortimer commented on  JENKINS-36885  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AVD not being created   
 

  
 
 
 
 

 
 I came across a similar failure earlier today. In my case it was due to having specified an invalid display configuration for the emulator. This resulted in the "create avd" command failing. Having looked at the code the emulator plugin only reports the output (either stderr or stdout) in very specific cases. This hides the cause of the failure. In addition the "Failed to parse AVD config file" failure is just a symptom of the problem because there is no configuration file to parse. I have prepared a patch that improves error logging. See https://github.com/jenkinsci/android-emulator-plugin/pull/62  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34488) Failing 'assert' hangs the pipeline

2016-10-19 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-34488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failing 'assert' hangs the pipeline   
 

  
 
 
 
 

 
 Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/workflow/actions/ErrorAction.java src/test/java/org/jenkinsci/plugins/workflow/actions/ErrorActionTest.java http://jenkins-ci.org/commit/workflow-api-plugin/9892fdffe0c3dfd34ba02b1edb0960f4c724b04d Log: [FIXED JENKINS-34488] Use ProxyException for exceptions that aren't serialized by XStream for security reasons  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34488) Failing 'assert' hangs the pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-34488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34488  
 
 
  Failing 'assert' hangs the pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38769) Pipeline job hangs when agent loses network connectivity

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38769  
 
 
  Pipeline job hangs when agent loses network connectivity   
 

  
 
 
 
 

 
 The failure to abort when the agent is hung—the summary issue—is a known limitation that I would like to improve. The exceptions are probably all duplicates of JENKINS-34488, though the surface symptoms are different.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Priority: 
 Critical Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38769) Pipeline job hangs when agent loses network connectivity

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38769  
 
 
  Pipeline job hangs when agent loses network connectivity   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 workflow-durable-task-step-plugin  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 workflow-support-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38605) Conflict with withMaven plugin, serialization error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38605  
 
 
  Conflict with withMaven plugin, serialization error   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can click "Create Pipeline" and open the creation flow process   
 

  
 
 
 
 

 
 Cliff Meyers well per pipeline permissions won't work here as we are creating a new pipeline. I would say for starters as long as they aren't read only we can at least offer to let them try to create a pipeline. If the permissions are more fine grained than we realise at the backend, we will see errors, and can adjust course  Would that work?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed

2016-10-19 Thread steveprent...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Prentice commented on  JENKINS-34637  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipeline DSL: timeout() does not work if withEnv() is enclosed   
 

  
 
 
 
 

 
 Not sure if this is a different issue or another manifestation of the issue with CpsBodyExecution, but passing a submitter into input is enough to trigger this issue with timeout for me. 

 

timeout(time: 3, unit: 'SECONDS') {
// input will hang forever.
input submitter: 'user'
}
 

 

 

timeout(time: 3, unit: 'SECONDS') {
// will timeout as expected
input()
}
 

 If this is a different issue, let me know and I'll submit a new issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38457) FlowGraphTable shows parallel branches out of order

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-38457  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 IIUC this is now fixed.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38457  
 
 
  FlowGraphTable shows parallel branches out of order   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In Review Resolved  
 
 
Assignee: 
 Jesse Glick Sam Van Oort  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the

[JIRA] (JENKINS-38847) API for creating a multibranch pipeline once all data gathered from user

2016-10-19 Thread vivek (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-38847  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

2016-10-19 Thread lebreton.gabr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Le Breton edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 Is the  lenght  length  limit documented somewhere?There's usually no collision with git sha hash and it's 41 characters long. Jenkins seems to use a 53  character  characters  long  hash .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

2016-10-19 Thread lebreton.gabr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Le Breton commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 Is the lenght limit documented somewhere? There's usually no collision with git sha hash and it's 41 characters long. Jenkins seems to use a 53 character long.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27906) Fail to read NUnit3 output xml

2016-10-19 Thread ten...@yahoo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Hicks commented on  JENKINS-27906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fail to read NUnit3 output xml   
 

  
 
 
 
 

 
 Until it is updated, you can use the JUnit plugin and the NUnit3-JUnit.xslt file that comes with nunit. You can find it on https://github.com/nunit/nunit-transforms/tree/master/nunit3-junit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

2016-10-19 Thread jenk...@beakerware.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kingsbury commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 My apologies, I misunderstood the intent of the patch.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-33761) Ability to disable "resume" build.

2016-10-19 Thread cgro...@fitbit.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Groves commented on  JENKINS-33761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to disable "resume" build.   
 

  
 
 
 
 

 
 Ahh, well what we want is for it not to continue without someone being there to monitor it. Automatically continuing to the next step means that if the person previously monitoring it left after Jenkins went down, they wouldn't be there when it comes back. We'd like to not have it resume for those builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 

you're missing the point
 I do not think I am missing anything. Hence my suggested patch above. (The ArtifactArchiver.NoMatchFound text should probably also suggest enabling the allowEmptyArchive mode—a later addition—if the lack of a match is not a bug.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-33761) Ability to disable "resume" build.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-33761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to disable "resume" build.   
 

  
 
 
 
 

 
 

maybe the problem is with finding the process again, or handling it not being there
 Perhaps. 

Should it handle bat() and sh()?
 Yes, this is the principle use case. 

Is the assumption that the slave keeps track of the process output, return value etc.?
 Yes. 

Will a job always resume to the same slave?
 Yes. 

Maybe the build finished before Jenkins came back?
 The external process I suppose you mean. Should be fine, the sh/bat step should then simply print any final output, and exit according to the process’ exit code. 

it'd continue to the next step after that?
 Exactly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-39076) Stack Overflow when trying to save system configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Wisen Tanasa  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Possibly a bug in Groovy. I would not recommend src/main/groovy/ for production code. At any rate, the super call should be deleted I think.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39076  
 
 
  Stack Overflow when trying to save system configuration   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 core  
 
 
Labels: 
 groovy  
 
 
Assignee: 
 Wisen Tanasa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

2016-10-19 Thread jenk...@beakerware.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kingsbury commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 Jesse, you're missing the point. Yes, once someone recognizes the problem, it can be worked around. Until that point, they are left with a failed build and no useful information as to its cause. Hence the request for additional output from archiveArtifacts.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 

Why cant the hash just be shortened?
 It is already as short as it can be while guaranteeing that there is no collision between jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 From a script, it would probably also work to run 

 

currentBuild.result = 'STABLE'
 

 prior to running the archiver. (The result can only get worse, never better, but it can become nonnull.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build