date:20180313

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44785  
 
 
  Add Built-in Request timeout support in Remoting   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 robustness  stalled  timeout  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-44785) Add Built-in Request timeout support in Remoting

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev stopped work on  JENKINS-44785  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-31050) Slave goes offline during the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev stopped work on  JENKINS-31050  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace

2018-03-13 Thread captresp...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Roberts commented on  JENKINS-2111  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace   
 

  
 
 
 
 

 
 As a workaround for this had to write a cron job that scans the get branches, matches them up with the workspace folders, then removes them.  An option that would just do then whenever the job is removed would be fantastic.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev edited a comment on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 JEP-200 is not a bug FYI. It is an intentional security hardening  at it was announced 2 months ago .  No plan to whitelist the date formatter classes in the core.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 JEP-200 is not a bug FYI. It is an intentional security hardening.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49022  
 
 
  Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 JEP-200  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 Artem Fedorov JEP-200 lands in LTS on this Wednesday. I recommend to not release the proposed patch until the compatibility is fixed. CC Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

2018-03-13 Thread senthilkumar.ra...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Senthilkumar Rasan commented on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38833) Remoting - Agent Stability improvements

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev stopped work on  JENKINS-38833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38833) Remoting - Agent Stability improvements

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-38833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remoting - Agent Stability improvements   
 

  
 
 
 
 

 
 The EPIC is almost done, nut it needs a hero to finish it. No capacity to work on it anytime soon  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38833) Remoting - Agent Stability improvements

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38833  
 
 
  Remoting - Agent Stability improvements   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-23709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make the internal Plugin API accessible for System Groovy Scripts   
 

  
 
 
 
 

 
 Rafael Pestano Maybe you want to consider https://github.com/jenkinsci/ownership-plugin/blob/master/doc/OwnershipBasedSecurity.md You can find some samples about permission management with scripts here:  
 
https://github.com/oleg-nenashev/demo-jenkins-config-as-code/blob/master/init_scripts/src/main/groovy/io/jenkins/systemgroovy/plugins/OwnershipBasedSecurityHelper.groovy 
https://github.com/oleg-nenashev/demo-jenkins-config-as-code/blob/master/init_scripts/src/main/groovy/scripts/Auth.groovy#L25-L33 
 Also there is support in the CasC plugin now: 
 
https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/casc/integrations/rolebasedauth/RoleStrategy1.yml 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS

2018-03-13 Thread eric.lemaniss...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Lemanissier commented on  JENKINS-49211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build gets stuck on Publish Over CIFS   
 

  
 
 
 
 

 
 same problem #2 under v0.9 here  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50151) Jenkins does not start if the content of the folder pointed by--webroot is deleted

2018-03-13 Thread fbelz...@gmail.com (JIRA)

Title: Message Title

Félix Belzunce Arcos updated an issue

Jenkins / JENKINS-50151

Jenkins does not start if the content of the folder pointed by--webroot is deleted

Change By:
Félix Belzunce Arcos

h3. What is the incorrect behaviour?Jenkins can't start - and it does not provide anything meaningful in the logsh3. What is the expected behaviour?Jenkins should be able to start and if not something meaningful should appear in the logsh3. Step by step to reproduce1. Download Jenkins OSS 2.89. 4 3 2. Run the .war with `java -DJENKINS_HOME= -jar jenkins.war --webroot=` - you can check the permissions of the folder here3. Jenkins starts correctly4. Kill the Jenkins process and remove the content of `rm -rf /*` - Notice that I am not removing the folder, but just the content!5. Try to start Jenkins again and you will see it does not start `java -DJENKINS_HOME= -jar jenkins.war --webroot=`The last thing in the logs is:{code:java}INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled{code}h3. Business ImpactIn case you clean up the content of , then Jenkins does not start.h3. WorkaroundDelete , not the content `rm -rf `h3. RegressionYes, it is. In 2.60 this is working._If so, what versions did this previously work in?_No idea.

Add Comment

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

[JIRA] (JENKINS-49050) Sequential stage groups UX and editor support

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49050  
 
 
  Sequential stage groups UX and editor support   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-42314) Timing reported for branches is 1ms

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42314  
 
 
  Timing reported for branches is 1ms   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-47428) Problems with the new ArgumentsAction.getResolvedArguments

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47428  
 
 
  Problems with the new ArgumentsAction.getResolvedArguments   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46889) Plugin in post step doesn't see injected environment

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46889  
 
 
  Plugin in post step doesn't see injected environment   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-43336) Allow locking multiple stages in declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43336  
 
 
  Allow locking multiple stages in declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Declarative - 1.2 , Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-43857) PasswordParameterDefinition should be filtered from InputSubmittedAction

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43857  
 
 
  PasswordParameterDefinition should be filtered from InputSubmittedAction   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41164) Input in parallel does not show up on stage view

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41164  
 
 
  Input in parallel does not show up on stage view   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40109  
 
 
  Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41239) Error during always block skips execution of remaining steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41239  
 
 
  Error during always block skips execution of remaining steps   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46898) Github Api Events Produce Error If Branch Name Contains #

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46898  
 
 
  Github Api Events Produce Error If Branch Name Contains #   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38765  
 
 
  Stage view renders incorrectly with stages appearing multiple times.   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40096) Stage View is missing after Plugin update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40096  
 
 
  Stage View is missing after Plugin update   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46415) Either function parameters or variables from withCredentials plugin don't work correctly

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46415  
 
 
  Either function parameters or variables from withCredentials plugin don't work correctly   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-48361) ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48361  
 
 
  ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-45579) Step to set stage or parallel status

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45579  
 
 
  Step to set stage or parallel status   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36956) Pipeline hangs on JUnitResultArchiver step with test publishers

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36956  
 
 
  Pipeline hangs on JUnitResultArchiver step with test publishers   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46336) Sidecar docker containers for declarative

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46336  
 
 
  Sidecar docker containers for declarative   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43194  
 
 
  Lightweight checkout for PR merge jobs   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates,  Blue Ocean 1.4 - beta 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-48138) filexist('') return an incorrect result in windows machines

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48138  
 
 
  filexist('') return an incorrect result in windows machines   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38181) withCredentials variables that are extracted are not masked outside of block

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38181  
 
 
  withCredentials variables that are extracted are not masked outside of block   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-48421) Support kubernetes in Declarative Pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48421  
 
 
  Support kubernetes in Declarative Pipeline
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Pipeline - Candidates  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts

2018-03-13 Thread rmpest...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rafael Pestano commented on  JENKINS-23709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make the internal Plugin API accessible for System Groovy Scripts   
 

  
 
 
 
 

 
 Hi guys, There is a way to pass parameters to the groovy script? We need to automate the Jenkins grant access in our company because the project-role matrix is unmanageable (100 users per 300 projects).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50151) Jenkins does not start if the content of the folder pointed by--webroot is deleted

2018-03-13 Thread fbelz...@gmail.com (JIRA)

Title: Message Title

Félix Belzunce Arcos created an issue

Jenkins / JENKINS-50151

Jenkins does not start if the content of the folder pointed by--webroot is deleted

Issue Type:
Bug

Assignee:
Unassigned

Components:
core

Created:
2018-03-13 16:05

Priority:
Critical

Reporter:
Félix Belzunce Arcos

What is the incorrect behaviour? Jenkins can't start - and it does not provide anything meaningful in the logs What is the expected behaviour? Jenkins should be able to start and if not something meaningful should appear in the logs Step by step to reproduce 1. Download Jenkins OSS 2.89.4 2. Run the .war with `java -DJENKINS_HOME= -jar jenkins.war --webroot=` - you can check the permissions of the folder here 3. Jenkins starts correctly 4. Kill the Jenkins process and remove the content of `rm -rf /*` - Notice that I am not removing the folder, but just the content! 5. Try to start Jenkins again and you will see it does not start `java -DJENKINS_HOME= -jar jenkins.war --webroot=` The last thing in the logs is:

INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled

Business Impact In case you clean up the content of , then Jenkins does not start. Workaround Delete , not the content `rm -rf ` Regression Yes, it is. In 2.60 this is working. If so, what versions did this previously work in? No idea.

[JIRA] (JENKINS-46255) Windows Slave Plugin to support SMB Version 2 or greater

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-46255  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows Slave Plugin to support SMB Version 2 or greater   
 

  
 
 
 
 

 
 Generally everybody is welcome to contribute to this and other issues  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46255) Windows Slave Plugin to support SMB Version 2 or greater

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-46255  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows Slave Plugin to support SMB Version 2 or greater   
 

  
 
 
 
 

 
 As you may see, the ticket is not assigned to anybody. This plugin is not being actively developed, and there is no ETA so far. CC Emilio Escobar   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49678) Pipeline lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file

2018-03-13 Thread esc...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Emilio Escobar  updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49678  
 
 
  Pipeline lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file   
 

  
 
 
 
 

 
Change By: 
 Emilio Escobar   
 
 
Summary: 
 Pipleine Pipeline  lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-47977) Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47977  
 
 
  Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-47977) Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-47977  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message   
 

  
 
 
 
 

 
 I do not anticipate to get any Remoting maintenance time in foreseeable future, so I have decided to unassign myself from this ticket. Sorry about this regression. It should be a newbie-friendly ticket, and everybody is welcome to contribute.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-47977) Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47977  
 
 
  Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49383) Env variables help: also list HUDSON_CHANGELOG_FILE

2018-03-13 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Env variables help: also list HUDSON_CHANGELOG_FILE   
 

  
 
 
 
 

 
 Code changed in jenkins User: pasasap Path: .gitignore http://jenkins-ci.org/commit/p4-plugin/160592ad625bc18a16548ea124ad81e39baa94e5 Log: Ignore VIM swap files. JENKINS-49383 Signed-off-by: pasasap   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40103) Jenkins: JUnit Plugin: publish results doesn't show trend report until successful build

2018-03-13 Thread marcello.romani.e...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcello Romani commented on  JENKINS-40103  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins: JUnit Plugin: publish results doesn't show trend report until successful build   
 

  
 
 
 
 

 
 Thanks for reporting this, I still see the issue with these versions: Jenkins ver. 2.89.4 JUnit Plugin 1.24  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

2018-03-13 Thread artem.fedo...@blazemeter.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 Sorry, not yet. Maybe in the next week I'll have time for reproduce and fix it. Maybe you can use jenkins LTS version, that have not such bug?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49801) TFS Plugin fails getting sources when Team project name contains spaces

2018-03-13 Thread kellie....@microsoft.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kellie Jos commented on  JENKINS-49801  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: TFS Plugin fails getting sources when Team project name contains spaces   
 

  
 
 
 
 

 
 Hello Sharon. I'm looking into this issue but have been unable to reproduce it so far.  Could you provide me with some additional information to help me debug the issue? It appears you are using a Jenkins Pipelines project, is this correct? What version of TFS do you have? Can you provide the exact error that you are seeing as well as logs? You can find information on how to capture logs here:  https://wiki.jenkins.io/display/JENKINS/Logging.    Thanks, Kellie  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

2018-03-13 Thread senthilkumar.ra...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Senthilkumar Rasan commented on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 Any update?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-47977) Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47977  
 
 
  Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-47977) Jenkins build fails with Root directory not writable: /usr/share/tomcat/.jenkins/cache/jars message

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev stopped work on  JENKINS-47977  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36453) Replay does not reuse commit on non-multibranch pipeline jobs

2018-03-13 Thread nicos.ma...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicos Maris updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36453  
 
 
  Replay does not reuse commit on non-multibranch pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Nicos Maris  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50150) Parallel stage with when shown as ran, but it haven't

2018-03-13 Thread leandro.naro...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Leandro Narosky created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50150  
 
 
  Parallel stage with when shown as ran, but it haven't   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-03-13-12-14-21-339.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-03-13 15:19  
 
 
Environment: 
 Last version Jenkins with blue ocean  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Leandro Narosky  
 

  
 
 
 
 

 
    Those steps are shown as ran, but it haven't. Clicking them just says "this stage has no steps" 

 

stage('Deploy release') {
environment{
ARTIFACT_VERSION = xxx
}
when {
anyOf {
branch 'RC'
branch 'HOTFIX_*'
branch 'HOTFIX-*'
}
}
parallel{
stage('Deploy to RC') {
when {
anyOf {
branch 'RC'
branch 'HOTFIX_*'
branch 'HOTFIX-*'
}
}
steps {
deploy(xxx)
}
}

stage('Deploy to CERT') {
when {
anyOf {
branch 'RC'
branch 'HOTFIX_*'
branch 'HOTFIX-*'
}
}
steps {
deploy(xxx)
}
}
}
 

  I've added "when" everywhere to try to fix it, but it doesn't work. It's clearly using the condition since it doesn't run the deploy script. The error seems to be only in the GUI This code is in a shared library, I'm not sure if that could be the reason of the error.

[JIRA] (JENKINS-50124) restore class compatibility for AbstractTaskListener

2018-03-13 Thread jn...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-50124  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: restore class compatibility for AbstractTaskListener   
 

  
 
 
 
 

 
 Manuel Recena Soto is there a need to backport this to 2.107.2? if not can you remove the "lts-candidate" label  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-30271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins job hangs and cannot be killed after aborting DSL job   
 

  
 
 
 
 

 
 Groovy has been updated from 2.4.8 to 2.4.11 in Jenkins 2.61. The issue should be fixed, see https://issues.apache.org/jira/browse/GROOVY-8067. Can anyone reproduce the problem in 2.61 or later? If not, I'm going to close this ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-33651) Support GitHub Display Name

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Display name is supported by the Dynamic DSL: 

 

job(String name) {
  properties {
githubProjectProperty {
  projectUrlStr(String value)
  displayName(String value)
}
  }
} 
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-33651  
 
 
  Support GitHub Display Name   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-45202) Regenerating job definition via job dsl clears state

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45202  
 
 
  Regenerating job definition via job dsl clears state   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-48202) User able to create jobs via job DSL plugin on Jenkins top level

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48202  
 
 
  User able to create jobs via job DSL plugin on Jenkins top level   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-44543) Don't force --batch-mode to benefit of Maven 3.5 colorized output

2018-03-13 Thread dcende...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beland edited a comment on  JENKINS-44543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Don't force --batch-mode to benefit of Maven 3.5 colorized output   
 

  
 
 
 
 

 
  I can confirm it works with maven 3.5.3 but it requires -Dstyle.color=always on the command line and -Djansi.force=true in the mavenOpts.e.g. :{code:java}withMaven(mavenOpts: '-Djansi.force=true') {sh "mvn clean verify -Dstyle.color= true always "}{code}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50149) Unable to find Jira Id from commit using jira ext plugin

2018-03-13 Thread posto...@yahoo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marian Postole created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50149  
 
 
  Unable to find Jira Id from commit using jira ext plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Dan Alvizu  
 
 
Attachments: 
 jiraext.jpg, jiraextjob.jpg  
 
 
Components: 
 jira-ext-plugin  
 
 
Created: 
 2018-03-13 14:43  
 
 
Environment: 
 Jenkins - 2.73.2  Jira ext plugin - 0.7  Jira version - 7.5.2  
 
 
Labels: 
 jenkins plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marian Postole  
 

  
 
 
 
 

 
 Hello, I've set up the plugin on a test Jenkins, the job is triggered by a commit in Gerrit and the scope is to use the JIRA id from the commit message and transition the issue from one status to another. At this moment it only works when I choose: Manually specifying it. Trying to use First word of commit or Mentioned somewhere in commit leads to this ouput: Updating JIRA tickets ChangeLogSet class: class hudson.scm.EmptyChangeLogSet Operation: Transition tickets Operation: Add a comment Finish updating JIRA tickets and no update is done in Jira. I've used the same id each time. I've attached the configuration for the plugin and also from the job. On the other hand if I use a Github repo as trigger the job manages to make the update.  Is it something wrong in the plugin config or in the job? Regards, Marian

[JIRA] (JENKINS-48907) Job DSL job generation results in java.nio.file.NoSuchFileException for config.xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please re-open if the problem persists.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48907  
 
 
  Job DSL job generation results in java.nio.file.NoSuchFileException for config.xml   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49591) Jenkins DSL Script lightweight() method is ignored

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I can not reproduce this. You need to install version 2.29 or later of the "Pipeline: Groovy" plugin to use the lightweight option, see https://jenkinsci.github.io/job-dsl-plugin/#path/pipelineJob-definition-cpsScm-lightweight. Job DSL should print a warning to the seed job output if a plugin needs to be installed or updated.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49591  
 
 
  Jenkins DSL Script lightweight() method is ignored   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file

2018-03-13 Thread pal...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-49678  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file   
 

  
 
 
 
 

 
 We can't fix the behaviour in the p4-plugin as Jenkins tells us to sync by calling SCM.checkout, the skipDefaultCheckout() is a workaround.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50148) Unable to edit pipeline in blueocean when Jenkinsfile contains "withSonarQubeEnv"

2018-03-13 Thread rciaccaf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Romain Ciaccafava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50148  
 
 
  Unable to edit pipeline in blueocean when Jenkinsfile contains "withSonarQubeEnv"   
 

  
 
 
 
 

 
Change By: 
 Romain Ciaccafava  
 

  
 
 
 
 

 
 Everything is fine until I switch to edit mode. Then, OceanBlue layout is displayed but the stages are not.In chrome console, this error message appears :   {code:java}blueocean.js:58253 Unhandled Rejection: "Error: No parameters for: withSonarQubeEnv\n at convertStepFromJson (https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63287:27)\n at convertStageFromJson (https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63239:28)\n at convertJsonToInternalModel (https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63195:28)\n at https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:57251:96\n at https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63513:13\n at https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:64335:17\n at "logUnhandledPromiseRejection @ blueocean.js:58253{code}In case it helps, this is the Jenkinsfile : {code:java}pipeline {  agent any  stages {stage('Server build (Java 8)') {  agent {docker {  image 'openjdk:8'  args '-v /srv/docker/jenkins-containers/cache/gradle-java8:/root/.gradle'}  }  steps {sh 'cd server && ./gradlew clean && ./gradlew build'  }}stage('Client build') {  agent {docker {  image 'node:9'  args '--network jenkinscontainers_default --link sonarqube -v /srv/docker/jenkins-containers/cache/npm-node9:/root/.npm'}  }  steps {withSonarQubeEnv('sonar') {  sh 'cd ./client && npm install'}  }}stage('Server SonarQube analysis') {  agent {docker {  image 'openjdk:8'  args '--network jenkinscontainers_default --link sonarqube -v /srv/docker/jenkins-containers/cache/gradle-java8:/root/.gradle'}  }  steps {withSonarQubeEnv('sonar') {  sh 'cd ./server && ./gradlew --info sonarqube'}  }}stage('Server SonarQube QG') {  agent {docker {  image 'openjdk:8'  args '--network jenkinscontainers_default --link sonarqube -v /srv/docker/jenkins-containers/cache/gradle-java8:/root/.gradle'}  }  steps {timeout(time: 1, unit: 'HOURS') {  waitForQualityGate()}  }}stage('Client SonarQube analysis') {  agent {docker {  image 'node:9'  args '--network jenkinscontainers_default --link sonarqube -v /srv/docker/jenkins-containers/cache/npm-node9:/root/.npm'

[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49797  
 
 
  IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50148) Unable to edit pipeline in blueocean when Jenkinsfile contains "withSonarQubeEnv"

2018-03-13 Thread rciaccaf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Romain Ciaccafava created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50148  
 
 
  Unable to edit pipeline in blueocean when Jenkinsfile contains "withSonarQubeEnv"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-pipeline-editor-plugin  
 
 
Created: 
 2018-03-13 14:35  
 
 
Environment: 
 Jenkins 2.89.4 run in Docker container (jenkins:lts image).  BlueOcean plugin 1.4.2  
 
 
Labels: 
 pipeline blueocean _javascript_  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Romain Ciaccafava  
 

  
 
 
 
 

 
 Everything is fine until I switch to edit mode. Then, OceanBlue layout is displayed but the stages are not. In chrome console, this error message appears :   

 

blueocean.js:58253 Unhandled Rejection: "Error: No parameters for: withSonarQubeEnv\n at convertStepFromJson (https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63287:27)\n at convertStageFromJson (https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63239:28)\n at convertJsonToInternalModel (https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:63195:28)\n at https://app.jaguards.com:4433/adjuncts/e896cb23/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:57251:96\n at

[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker assigned an issue to Daniel Spilker  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49797  
 
 
  IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Assignee: 
 PTC ALM Daniel Spilker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46573) Jira Version Parameter always null

2018-03-13 Thread grim_toas...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Turner commented on  JENKINS-46573  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira Version Parameter always null   
 

  
 
 
 
 

 
 Had the same issue this morning, simplest change is just to override the getValue() method - PR raised at https://github.com/jenkinsci/jira-plugin/pull/143.  The linked issue above JENKINS-45293 if you follow through to the original stackoverflow question is actually the same issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49787) Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49787  
 
 
  Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49696) Delete and re-create view if type changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Will be released in 1.69.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49696  
 
 
  Delete and re-create view if type changes   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49820) 'Do not allow concurrent builds' in pipeline sometimes fails

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49820  
 
 
  'Do not allow concurrent builds' in pipeline sometimes fails   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50024) Cannot run CIFs plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This scripts works for me: 

 

job('example') {
  publishers {
cifsPublisher {
  continueOnError(false)
  failOnError(true)
  alwaysPublishFromMaster(false)
  masterNodeName('master')
  publishers {
cifsPublisher {
  configName('nl1fs02.mydomain.com')
  verbose(false)
  useWorkspaceInPromotion(false)
  usePromotionTimestamp(false)
  retry {
retries(5)
retryDelay(15)
  }
  label {
label('Publishing to nl1fs02')
  }
  transfers {
cifsTransfer {
  sourceFiles('**/build/**')
  excludes('')
  remoteDirectory('$RELEASE_VERSION')
  removePrefix('build')
  remoteDirectorySDF(false)
  flatten(false)
  cleanRemote(true)
  noDefaultExcludes(false)
  makeEmptyDirs(true)
  patternSeparator('[, ]+')
}
  }
}
  }
}
  }
}
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50024  
 
 
  Cannot run CIFs plugin   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-50141) Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"

2018-03-13 Thread franc...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50141  
 
 
  Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50141) Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"

2018-03-13 Thread franc...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50141  
 
 
  Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50141) Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"

2018-03-13 Thread franc...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50141  
 
 
  Unable to launch slave in AWS due to " Security groups must all be VPC security groups to work in a VPC context"   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50133) Update sdk version & improving code quality/style

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-50133  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49766) SVN support for uft inegration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-49766  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50147) UFT svn support - fixing test connection for existing credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-50147  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50146) if slave name contains spaces - no restriction (of slave) is added to job and execution job is executed on master and not on slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-50146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49765) defect #574013 : UTF Discovery Job does not add to octane localized tests

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49765  
 
 
  defect #574013 : UTF Discovery Job does not add to octane localized tests   
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Labels: 
 5.3.4-beta  octane  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50145) UFT integration - jenkins might clone not "master" branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-50145  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49765) defect #574013 : UTF Discovery Job does not add to octane localized tests

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-49765  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49766) SVN support for uft inegration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49766  
 
 
  SVN support for uft inegration   
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Labels: 
 5.3.4-beta  octane  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50147) UFT svn support - fixing test connection for existing credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin stopped work on  JENKINS-50147  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50131) git parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 guillermo casco commented on  JENKINS-50131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git parameter   
 

  
 
 
 
 

 
 I configure it like you said, but now it can´t find the branch (even though is showed in the drop down menu) chek images that I just updated.  thanks for your help Budy.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50131) git parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 guillermo casco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50131  
 
 
  git parameter   
 

  
 
 
 
 

 
Change By: 
 guillermo casco  
 
 
Attachment: 
 Capture1.JPG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50131) git parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 guillermo casco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50131  
 
 
  git parameter   
 

  
 
 
 
 

 
Change By: 
 guillermo casco  
 
 
Attachment: 
 Capture3.JPG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50131) git parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 guillermo casco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50131  
 
 
  git parameter   
 

  
 
 
 
 

 
Change By: 
 guillermo casco  
 
 
Attachment: 
 Capture2.JPG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50131) git parameter

Title: Message Title


 
 
 
 

 
 
 

 
   
 guillermo casco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50131  
 
 
  git parameter   
 

  
 
 
 
 

 
Change By: 
 guillermo casco  
 
 
Attachment: 
 Capture4.JPG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41318) Publisher Over CIFS(CifsBuilderPlugin) seems not to be working when configuring the plugin using groovy DSL script

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41318  
 
 
  Publisher Over CIFS(CifsBuilderPlugin) seems not to be working when configuring the plugin using groovy DSL script   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-48854) P4 sync code and display 'change' more than once.

2018-03-13 Thread pal...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-48854  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4 sync code and display 'change' more than once.   
 

  
 
 
 
 

 
 If there is more than one sync in the Jenkins Job and the sync contains one or more of the same files, then the change will get reported twice. For example, on a Pipeline build the Jenkinsfile is sync'ed by the script then again as it is within the workspace view of the 'checkout' or 'p4sync' stage.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50147) UFT svn support - fixing test connection for existing credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50147  
 
 
  UFT svn support - fixing test connection for existing credentials
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 

  
 
 
 
 

 
 user story #522126  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50145) UFT integration - jenkins might clone not "master" branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50145  
 
 
   UFT integration - jenkins might clone not "master" branch   
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 

  
 
 
 
 

 
 defect #588037  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50146) if slave name contains spaces - no restriction (of slave) is added to job and execution job is executed on master and not on slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50146  
 
 
  if slave name contains spaces - no restriction (of slave) is added to job and execution job is executed on master and not on slave   
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 

  
 
 
 
 

 
 defect #587053  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50147) UFT svn support - fixing test connection for existing credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50147  
 
 
  UFT svn support - fixing test connection for existing credentials
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Michael Seldin  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-03-13 14:18  
 
 
Labels: 
 octane 5.3.4-beta uft-integration  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Seldin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-50145) UFT integration - jenkins might clone not "master" branch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50145  
 
 
   UFT integration - jenkins might clone not "master" branch   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Michael Seldin  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-03-13 14:17  
 
 
Labels: 
 octane 5.3.4-beta  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Seldin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-50146) if slave name contains spaces - no restriction (of slave) is added to job and execution job is executed on master and not on slave