[JIRA] (JENKINS-49446) Regression with 1.15 and WithContainerStep

2018-02-16 Thread nicolas.del...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas De Loof commented on  JENKINS-49446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression with 1.15 and WithContainerStep   
 

  
 
 
 
 

 
 @myoung34 you're perfectly right, this is not a requirement but a convention on official image (it's required to get official image approved), and many custom image don't follow this. Our issue here is we are abusing the container lifecycle : an arbitrary docker image is not designed to run arbitrary command like we use them for. One option is to override entrypoint to run a custom command. But then we disable the initial entrypoint designed by image author, which in many cases is required for the image to make any sense. Typically, Selenium images do use it to run a X11 server. This option has been adopted in the past, introducing https://issues.jenkins-ci.org/browse/JENKINS-41316 regression. The other is to assume newcomers mostly will try docker pipeline using official images. So we offer a solution which works out-of-the box, and can't report issue with target image if detected not to match our requirements. Those who are already used with docker-pipeline then get a documented direction on how to fix their image or update their pipeline. I welcome any suggestion for a 3rd option. As one can't "docker exec" in a stopped container, we have to find some way for the container to run a "pause" command, and this is definitively not part of docker spec to support this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-43119) Monitor Swam client on some port ?

2018-02-16 Thread vi...@reachvikas.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Kumar commented on  JENKINS-43119  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Monitor Swam client on some port ?   
 

  
 
 
 
 

 
 Michael Greco Maybe it is too late now. I ended up monitoring count of java processes using CloudWatch and then terminate the instance if the count is less than the desired value.  
 

  
 
 
 
 

 
 
 

 
 
 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-49609) Feature Request - Support SAML too

2018-02-16 Thread vi...@reachvikas.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Kumar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49609  
 
 
  Feature Request - Support SAML too   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 D. Lauer  
 
 
Components: 
 keycloak-plugin  
 
 
Created: 
 2018-02-17 05:58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vikas Kumar  
 

  
 
 
 
 

 
 It would be great if you can support SAML protocol too   Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-49608) Feature Request - Add some documentation for Keycloak SAML Integration

2018-02-16 Thread vi...@reachvikas.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Kumar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49608  
 
 
  Feature Request - Add some documentation for Keycloak SAML Integration   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 saml-plugin  
 
 
Created: 
 2018-02-17 05:56  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vikas Kumar  
 

  
 
 
 
 

 
 Hello Team, I am not sure if it is too much to ask to include some documentation to integrate Jenkins with Keycloak. Something like an exported JSON would be awesome so that one can import it, change a couple of values and it would just work. Thanks in advance! Regards, Vikas  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
  

[JIRA] (JENKINS-49446) Regression with 1.15 and WithContainerStep

2018-02-16 Thread 3a835...@opayq.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 marc young edited a comment on  JENKINS-49446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression with 1.15 and WithContainerStep   
 

  
 
 
 
 

 
 I'd also like to point out (aside from breaking everything at 3 of my contracts): you've  based everything on "requirements" that are actually suggestions.The error I'm now facing in dozens of builds:{code}04:11:59 ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).{code}Youve stated *as required by* . However those docs clearly say:{code}All official images should provide a consistent interface. {code}Should != require. Your use-case and assumptions are not  a standard to hold an entire community to Please remember: I'm using *other* peoples *official*  containers to run in jenkins. I cannot (and will not) fork every single one of these to meet your guidelines.  
 

  
 
 
 
 

 
 
 

 
 
 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-49446) Regression with 1.15 and WithContainerStep

2018-02-16 Thread 3a835...@opayq.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 marc young commented on  JENKINS-49446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression with 1.15 and WithContainerStep   
 

  
 
 
 
 

 
 I'd also like to point out (aside from breaking everything at 3 of my contracts): you've based everything on "requirements" that are actually suggestions. The error I'm now facing in dozens of builds: 

 

04:11:59 ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).
 

 Youve stated as required by . However those docs clearly say: 

 

All official images should provide a consistent interface. 
 

 Should != require. Your use-case and assumptions are not a standard to hold an entire community to  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

2018-02-16 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 ugh this sounds bad. I have a server that I update every day and have not seen this, but tyler has similar and has..   
 

  
 
 
 
 

 
 
 

 
 
 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

2018-02-16 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48571  
 
 
  checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Minor Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-17494) Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer

2018-02-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-17494  
 
 
  Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 copyartifact-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-32444) Proposal: Move build logs off of Jenkins master

2018-02-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32444  
 
 
  Proposal: Move build logs off of Jenkins master   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49561) FSSCM Does Not Update File Modifiers

2018-02-16 Thread jens.roga...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jens Rogalli commented on  JENKINS-49561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM Does Not Update File Modifiers   
 

  
 
 
 
 

 
 Oleg Nenashev Ok then  I will implement it as an extra option.     
 

  
 
 
 
 

 
 
 

 
 
 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-49561) FSSCM Does Not Update File Modifiers

2018-02-16 Thread jens.roga...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jens Rogalli commented on  JENKINS-49561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM Does Not Update File Modifiers   
 

  
 
 
 
 

 
 That does not make any difference. The implementation would be that simple anyway.  The problems arise by the underlying implementations see: https://stackoverflow.com/questions/10783677/how-to-check-file-permissions-in-java-os-independently just as one example.     
 

  
 
 
 
 

 
 
 

 
 
 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-48490) Intermittently slow docker provisioning with no errors

2018-02-16 Thread matt.lud...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Ludlum commented on  JENKINS-48490  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittently slow docker provisioning with no errors   
 

  
 
 
 
 

 
 I've been trying to reproduce this issue on my local box using SSH executors with both 1.1.2 and 1.1.3 to no avail. We are still seeing it on other instances. In the short term, I've thrown together  a quick and dirty script job to "unstick" the jobs. https://gist.github.com/MattLud/1f8a56fcce933f7e97c366de54c85ba9      
 

  
 
 
 
 

 
 
 

 
 
 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-38877) Build History by Node doesn't work with Pipeline

2018-02-16 Thread dam...@addepar.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Jiang commented on  JENKINS-38877  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build History by Node doesn't work with Pipeline   
 

  
 
 
 
 

 
 It's been over a year since  

There are various longer-term plans for analytic capabilities.
 Are there any updates on this? There are two annoyance with pipeline builds on multiple nodes: 1. It's hard to tell which nodes were used for which pipeline steps (addressed by the "setting build display name" idea in the comments here) 2. It's hard to tell which jobs/pipeline steps were run on a node, which is what this ticket was originally about.   Are there any workarounds for the latter?  
 

  
 
 
 
 

 
 
 

 
 
 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-47022) DropDown is loosing focus on selection of an option

2018-02-16 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-47022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DropDown is loosing focus on selection of an option   
 

  
 
 
 
 

 
 Alvaro Lobato Ported and 1.4.2 released.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-02-16 Thread m...@basilcrow.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Sam Van Oort Thanks! I'll start following JENKINS-37575 now. Glad to hear there's a long-term solution in the works. I did see the PERFORMANCE-OPTIMIZED pipeline mode and am looking forward to trying it out 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-49561) FSSCM Does Not Update File Modifiers

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan commented on  JENKINS-49561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM Does Not Update File Modifiers   
 

  
 
 
 
 

 
 Would it make sense to just implement something very simple, like this: 
 
if the permissions are different, just copy the whole file again 
 Would that cause potential regression / defects?  
 

  
 
 
 
 

 
 
 

 
 
 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Basil Crow #2 has been addressed – there is separate work in the proposed solution to https://issues.jenkins-ci.org/browse/JENKINS-37575 (PRs from Jesse that I am reviewing) that should address your issue, so I'm trying to avoid double-tracking the same cluster of issues.   The issues are phrased differently (resending output vs. timing out) but the root cause is the same (timing in the communication). So, that means there's a more comprehensive long-term solution in the works. Oh, and if you're by any chance using NFS for your master too: the parts of JENKINS-47170 that I've released already will probably benefit you a lot (particularly the PERFORMANCE-OPTIMIZED pipeline mode) – docs are up at https://jenkins.io/doc/book/pipeline/scaling-pipeline/  Should greatly reduce the IO needs of your master when running Pipelines.  
 

  
 
 
 
 

 
 
 

 
 
 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

2018-02-16 Thread ygo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ygor Almeida edited a comment on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 I'm in the same boat, [~alexsuter]. My team is already talking about a possible migration to GoCD. Like you, we are always updating Jenkins and its plugins  and this problem . This issue  is causing a series of unexpected deployments. Anyways, total chaos in my environment right now. At this point, even a workaround is very welcome.  
 

  
 
 
 
 

 
 
 

 
 
 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

2018-02-16 Thread ygo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ygor Almeida edited a comment on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 I'm in the same boat, [~alexsuter]. My team is already talking about a possible migration to GoCD. Like you, we are always updating Jenkins and its plugins and this problem is causing a series of unexpected deployments. Anyways, total chaos in my environment right now.  At this point, even a workaround is very welcome.  
 

  
 
 
 
 

 
 
 

 
 
 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

2018-02-16 Thread ygo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ygor Almeida commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 I'm in the same boat, Alex Suter. My team is already talking about a possible migration to GoCD. Like you, we are always updating Jenkins and its plugins and this problem is causing a series of unexpected deployments. Anyways, total chaos in my environment right now.  
 

  
 
 
 
 

 
 
 

 
 
 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-49561) FSSCM Does Not Update File Modifiers

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM Does Not Update File Modifiers   
 

  
 
 
 
 

 
 I agree that fixing this bug is regression-prone. OTOH it is always possible the behavior changes opt-in and configurable via advanced options. If you do so, jt will be safe to experiment with behaviors. You could even mark the new flag as experinental so that theee will be a room for breaking changes before it gets fully fixed P.S: Personally I use the plugin only for read-only data  
 

  
 
 
 
 

 
 
 

 
 
 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

2018-02-16 Thread alexander.su...@axonivy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Suter commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 This problem is really annoying. After jenkins master restart, we have to rescan all builds, which builds all branches! And we quite often restart jenkins to update jenkins itself and also the system on which jenkins is running. The closed PR would at least solve the problem for the moment. In the meantime, can we work on a better solution?  
 

  
 
 
 
 

 
 
 

 
 
 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-49561) FSSCM Does Not Update File Modifiers

2018-02-16 Thread jens.roga...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jens Rogalli edited a comment on  JENKINS-49561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM Does Not Update File Modifiers   
 

  
 
 
 
 

 
 I checked the code and yes you are right this will happen.Why is it happening: The code checks for modification dates, but changing file Permissions / modifiers does not change the date.File permissions seem to be be a troublesome topic, especially in Windows. So any code modification to achieve the desired behavior, will lead, in my opinion to more bug reports. Or to an exclusion list like File Permissions will be checked but,  under windows x with Java y it might not work.Maybe this topic should be  rest  rested  as a known bug and be documented. Lets ask [~oleg_nenashev]. I could implement it if he approves the topic to be worthwhile implementing.  
 

  
 
 
 
 

 
 
 

 
 
 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-49561) FSSCM Does Not Update File Modifiers

2018-02-16 Thread jens.roga...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jens Rogalli commented on  JENKINS-49561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM Does Not Update File Modifiers   
 

  
 
 
 
 

 
 I checked the code and yes you are right this will happen. Why is it happening: The code checks for modification dates, but changing file Permissions / modifiers does not change the date. File permissions seem to be be a troublesome topic, especially in Windows. So any code modification to achieve the desired behavior, will lead, in my opinion to more bug reports. Or to an exclusion list like File Permissions will be checked but,  under windows x with Java y it might not work. Maybe this topic should be rest as a known bug and be documented.  Lets ask Oleg Nenashev. I could implement it if he approves the topic to be worthwhile implementing.  
 

  
 
 
 
 

 
 
 

 
 
 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-49607) ssh-slaves-plugin should report the required java version when none found

2018-02-16 Thread dchs...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Hsueh created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49607  
 
 
  ssh-slaves-plugin should report the required java version when none found   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 ssh-slaves-plugin  
 
 
Created: 
 2018-02-16 20:20  
 
 
Environment: 
 jenkins 2.98  ssh-slaves-plugin 1.25.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Hsueh  
 

  
 
 
 
 

 
 when the ssh-slaves-plugin cannot find a supported version of java (or cannot find any version of java as per JENKINS-18767) it should report what version is needed: 

 
[02/16/18 18:15:19] [SSH] Checking java version of java
[02/16/18 18:15:19] [SSH] java -version returned 1.7.0_80.
[02/16/18 18:15:19] [SSH] Checking java version of /usr/bin/java
[02/16/18 18:15:19] [SSH] /usr/bin/java -version returned 1.7.0_80.
[02/16/18 18:15:19] [SSH] Checking java version of /usr/java/default/bin/java
[02/16/18 18:15:19] [SSH] /usr/java/default/bin/java -version returned 1.7.0_80.
[02/16/18 18:15:19] [SSH] Checking java version of /usr/java/latest/bin/java
[02/16/18 18:15:20] [SSH] /usr/java/latest/bin/java -version returned 1.7.0_80.
[02/16/18 18:15:20] [SSH] Checking java version of /usr/local/bin/java
Couldn't figure out the Java version of /usr/local/bin/java
bash: /usr/local/bin/java: No such file or directory

[02/16/18 18:15:20] [SSH] Checking java version of /usr/local/java/bin/java
Couldn't figure out the Java version of /usr/local/java/bin/java
bash: /usr/local/java/bin/java: No such file or directory

[02/16/18 18:15:20] [SSH] Checking java version of /var/lib/jenkins/jdk/bin/java
Couldn't figure out the Java version of /var/lib/jenkins/jdk/bin/java

[JIRA] (JENKINS-49560) FSSCM does not work with “checkout scm” on agent

2018-02-16 Thread jens.roga...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jens Rogalli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49560  
 
 
  FSSCM does not work with “checkout scm” on agent   
 

  
 
 
 
 

 
Change By: 
 Jens Rogalli  
 
 
Comment: 
 Very good description of the issue. Better than Jenkins-48769.  
 

  
 
 
 
 

 
 
 

 
 
 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-49560) FSSCM does not work with “checkout scm” on agent

2018-02-16 Thread jens.roga...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jens Rogalli commented on  JENKINS-49560  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FSSCM does not work with “checkout scm” on agent   
 

  
 
 
 
 

 
 Very good description of the issue. Better than Jenkins-48769.  
 

  
 
 
 
 

 
 
 

 
 
 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-02-16 Thread m...@basilcrow.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 I see that this bug has been closed as fixed, but I'm not sure I'd consider it fixed. I guess that depends on what the scope of this bug is. There were two problems identified in the bug: 
 
JENKINS-47791 introduced a new failure mode that only manifests when using NFS-based workspaces. 
This new failure mode having a poor error message. 
 If the scope of this bug is both of these issues, then only the second has been fixed. The first issue remains, and this bug shouldn't be marked as fixed. If the scope of this bug is only the second issue, then a new bug should be filed covering the first issue. Which of the two is the case?  
 

  
 
 
 
 

 
 
 

 
 
 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released to the wild now  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48300  
 
 
  Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49559) Document: How to raise issues in FSSCM Plugin

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Usually we leave tickets in Resolved forever  Not exactly the best practice  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49559  
 
 
  Document: How to raise issues in FSSCM Plugin   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-49559) Document: How to raise issues in FSSCM Plugin

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan commented on  JENKINS-49559  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document: How to raise issues in FSSCM Plugin   
 

  
 
 
 
 

 
 Oleg Nenashev: Am I expected to Close this ticket, since I raised it? Or does the process work differently? ( I didn't see this question answered in How to report an 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-49044) DescriptorVisibilityFilters are not applied to SecurityRealm and AuthorizationStrategy

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49044  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DescriptorVisibilityFilters are not applied to SecurityRealm and AuthorizationStrategy   
 

  
 
 
 
 

 
 Code changed in jenkins User: Antonio Muniz Path: core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy test/src/test/java/hudson/model/DescriptorVisibilityFilterTest.java http://jenkins-ci.org/commit/jenkins/0e51e36023d0533f099226ba7a0035dae7b02a84 Log: JENKINS-49044 Apply visibility filters to SecurityRealm and AuthorizationStrategy (#3246) 
 
JENKINS-49044 Honor DescriptorVisibilityFilter for SecurityRealm and AuthorizationStrategy 
 
 
JENKINS-49044 The test 
  
 

  
 
 
 
 

 
 
 

 
 
 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-47142) archiveArtifacts step failure is not displayed

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-47142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: archiveArtifacts step failure is not displayed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/Messages.properties core/src/main/resources/hudson/tasks/Messages_bg.properties core/src/main/resources/hudson/tasks/Messages_da.properties core/src/main/resources/hudson/tasks/Messages_de.properties core/src/main/resources/hudson/tasks/Messages_es.properties core/src/main/resources/hudson/tasks/Messages_fr.properties core/src/main/resources/hudson/tasks/Messages_it.properties core/src/main/resources/hudson/tasks/Messages_ja.properties core/src/main/resources/hudson/tasks/Messages_nl.properties core/src/main/resources/hudson/tasks/Messages_pt_BR.properties core/src/main/resources/hudson/tasks/Messages_ru.properties core/src/main/resources/hudson/tasks/Messages_sr.properties core/src/main/resources/hudson/tasks/Messages_tr.properties core/src/main/resources/hudson/tasks/Messages_zh_TW.properties http://jenkins-ci.org/commit/jenkins/193855d1fb82e980e93f0c9ce3c15c459d448fab Log: JENKINS-47142 Simplifying the logic of ArtifactArchiver.perform, making it friendlier to Pipeline.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-47142) archiveArtifacts step failure is not displayed

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-47142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: archiveArtifacts step failure is not displayed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/Messages.properties core/src/main/resources/hudson/tasks/Messages_bg.properties core/src/main/resources/hudson/tasks/Messages_da.properties core/src/main/resources/hudson/tasks/Messages_de.properties core/src/main/resources/hudson/tasks/Messages_es.properties core/src/main/resources/hudson/tasks/Messages_fr.properties core/src/main/resources/hudson/tasks/Messages_it.properties core/src/main/resources/hudson/tasks/Messages_ja.properties core/src/main/resources/hudson/tasks/Messages_nl.properties core/src/main/resources/hudson/tasks/Messages_pt_BR.properties core/src/main/resources/hudson/tasks/Messages_ru.properties core/src/main/resources/hudson/tasks/Messages_sr.properties core/src/main/resources/hudson/tasks/Messages_tr.properties core/src/main/resources/hudson/tasks/Messages_zh_TW.properties http://jenkins-ci.org/commit/jenkins/e5fd7b7c90077e681454723bb952acc7067e4443 Log: Merge pull request #3265 from jglick/simple-build-steps-should-be-simple-JENKINS-47142 JENKINS-47142 Simplifying the logic of ArtifactArchiver.perform, making it friendlier to Pipeline Compare: https://github.com/jenkinsci/jenkins/compare/b4dc44806119...e5fd7b7c9007  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-48711) Create a Docker image for running PCT for plugins

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-48711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create a Docker image for running PCT for plugins   
 

  
 
 
 
 

 
 With https://github.com/jenkinsci/plugin-compat-tester/pull/67 we can build PCT Docker image just from Dockerfile  
 

  
 
 
 
 

 
 
 

 
 
 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-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan commented on  JENKINS-49593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document FSSCM License   
 

  
 
 
 
 

 
 Oleg Nenashev: Two topics you may want to comment on: 
 
I've set the years to 2009-2018 (first commit I found was from 2009. 
I've set the copyright owner to “Various contributors.” 
  
 

  
 
 
 
 

 
 
 

 
 
 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-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan updated  JENKINS-49593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49593  
 
 
  Document FSSCM License   
 

  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan updated  JENKINS-49593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49593  
 
 
  Document FSSCM License   
 

  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl

2018-02-16 Thread timothy.mcna...@build.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim McNally commented on  JENKINS-49543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl   
 

  
 
 
 
 

 
 I agree that updating Tomcat is the correct mitigation route. This is reinforced by the fact that Tomcat 8.0.x line is officially entering EOL soon. (announcement)  Thanks for your help in resolving this.  
 

  
 
 
 
 

 
 
 

 
 
 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-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Oleg Nenashev: Filed PR #7.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49593  
 
 
  Document FSSCM License   
 

  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 
 
Assignee: 
 Ernst de Haan 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-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan updated  JENKINS-49593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49593  
 
 
  Document FSSCM License   
 

  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 
 
Status: 
 In  Review  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-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49593  
 
 
  Document FSSCM License   
 

  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 

  
 
 
 
 

 
 Please document which license is applicable to the FileSystem SCM plugin.E.g. as follows:- copy the Jenkins {{LICENSE.md}} file into the repository- reference the {{LICENSE.md}} file from the  `  {{ README.md ` }}  file- copy the contents of the {{LICENSE.md}} file into the {{README.md}} fileThen the approach would be fully in line with the main Jenkins repository [jenkinsci/jenkins|https://github.com/jenkinsci/jenkins].  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49593  
 
 
  Document FSSCM License   
 

  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 

  
 
 
 
 

 
 Please document which license is applicable to the FileSystem SCM plugin.E.g. as follows:- copy the Jenkins {{LICENSE. md txt }} file into the repository- reference the {{LICENSE. md txt }} file from the {{README.md}} file- copy the contents of the {{LICENSE. md txt }} file into the {{README.md}} fileThen the approach would be fully in line with the main Jenkins repository [jenkinsci/jenkins|https://github.com/jenkinsci/jenkins].  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49593) Document FSSCM License

2018-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan started work on  JENKINS-49593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ernst de Haan  
 
 
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-28010) Use Google Apps group for Authorization

2018-02-16 Thread flor...@ramillien.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florian Ramillien edited a comment on  JENKINS-28010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use Google Apps group for Authorization   
 

  
 
 
 
 

 
 Same problems for us, we  like in a first time  want  to split admin role (credentials, main configuration, ...) from jobs  roles  management .For this we think about two Google API options: Groups (already discussed here) and Roles API:[https://developers.google.com/admin-sdk/directory/v1/reference/groups ]   [ https://developers.google.com/admin-sdk/directory/v1/reference/roles |https://developers.google.com/admin-sdk/directory/v1/reference/roles ] I think that most entreprise Most enterprise  using Google  authent  OAuth  already use 'Groups' that can be matched with Jenkins rights. Groups would be the easy way for many.The 'Roles' way may offer more controls on rights, but could be more complexe to operate.  
 

  
 
 
 
 

 
 
 

 
 
 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-49602) hudson.model.Queue$BuildableItem missing Data

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49602  
 
 
  hudson.model.Queue$BuildableItem missing Data   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49602) hudson.model.Queue$BuildableItem missing Data

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.model.Queue$BuildableItem missing Data   
 

  
 
 
 
 

 
 Nothing to do on the Pipeline side. Stash Pull Request Builder needs to resolve subtasks correctly  
 

  
 
 
 
 

 
 
 

 
 
 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-49559) Document: How to raise issues in FSSCM Plugin

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It has been integrated into the master. No need to release to consider as Fixed  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49559  
 
 
  Document: How to raise issues in FSSCM Plugin   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress 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 

[JIRA] (JENKINS-28010) Use Google Apps group for Authorization

2018-02-16 Thread flor...@ramillien.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florian Ramillien commented on  JENKINS-28010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use Google Apps group for Authorization   
 

  
 
 
 
 

 
 Same problems for us, we like in a first time to split admin role (credentials, main configuration, ...) from jobs roles. For this we think about two Google API options: Groups (already discussed here) and Roles API: [https://developers.google.com/admin-sdk/directory/v1/reference/groups https://developers.google.com/admin-sdk/directory/v1/reference/roles|https://developers.google.com/admin-sdk/directory/v1/reference/roles] I think that most entreprise using Google authent already use 'Groups' that can be matched with Jenkins rights. Groups would be the easy way for many. The 'Roles' way may offer more controls on rights, but could be more complexe to operate.  
 

  
 
 
 
 

 
 
 

 
 
 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-49559) Document: How to raise issues in FSSCM Plugin

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49559  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document: How to raise issues in FSSCM Plugin   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: README.md http://jenkins-ci.org/commit/filesystem_scm-plugin/78341c0048f94b8800f88a0eec57fdc0d3ce1488 Log: Merge pull request #6 from znerd/JENKINS-49559 JENKINS-49559: Initial version of README.md file. Compare: https://github.com/jenkinsci/filesystem_scm-plugin/compare/1378a5228929...78341c0048f9  
 

  
 
 
 
 

 
 
 

 
 
 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-49559) Document: How to raise issues in FSSCM Plugin

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49559  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document: How to raise issues in FSSCM Plugin   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ernst de Haan Path: README.md http://jenkins-ci.org/commit/filesystem_scm-plugin/f6e83baff30c909d775fda9d973963deb1a192cf Log: JENKINS-49559: Incorporated review comments.  
 

  
 
 
 
 

 
 
 

 
 
 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-49559) Document: How to raise issues in FSSCM Plugin

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49559  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document: How to raise issues in FSSCM Plugin   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ernst de Haan Path: README.md http://jenkins-ci.org/commit/filesystem_scm-plugin/8b188b26cd4c99f4399660207c74841fd00cec66 Log: JENKINS-49559: Initial version of README.md 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-49393) Broken symlinks in reused workspaces

2018-02-16 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-49393  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Broken symlinks in reused workspaces   
 

  
 
 
 
 

 
 Thanks to Simon easily reproduced the problem. Think it may be a bug in P4Java because the command in the log is correct: 

 

p4 reconcile -w -f FILEPATH
 

 With P4 client synlinks are correctly cleaned up using this command.   Reproductions steps: 
 
Create a freestyle job using 'Auto cleanup and sync' setting. 
Submit a file called f1 to path. 
Manually run job 
Go to build slave workspace and create following files and symlinks: 
 

 

echo A > A
echo B > B
echo C > C
ln -s A Alink
ln -s B ABlink
ln -s A XAlink

 

 
 
Edit and submit f1 from own workspace. 
Manually run job. 
No error is seen but following files are left behind: 
   

 

drwxr-xr-x  2 jenkins jenkins 4096 Feb 16 16:55 .
drwxr-xr-x 13 jenkins jenkins 4096 Feb 16 16:44 ..
lrwxrwxrwx  1 jenkins jenkins    1 Feb 16 16:49 Alink -> A
-r--r--r--  1 jenkins jenkins  275 Feb 16 16:55 f1
lrwxrwxrwx  1 jenkins jenkins    1 Feb 16 16:49 XAlink -> A

 

      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-49393) Broken symlinks in reused workspaces

2018-02-16 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49393  
 
 
  Broken symlinks in reused workspaces   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Labels: 
 P4_SUPPORT P4_VERIFY  
 

  
 
 
 
 

 
 
 

 
 
 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view

2018-02-16 Thread pmatig...@successfactors.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Matignon commented on  JENKINS-47286  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view   
 

  
 
 
 
 

 
 I find unfortunate that the ticket be rejected wholesale. I think it had 2 things potentially in its scope that could be considered independently, and both of them are pretty common sense IMHO. The first part is adding support for skipped stages (i.e. add an _expression_ to the stage to determine whether to skip or not), which was shutdown, sadly. The second part is concerned solely on rendering a skipped stage in a pipeline visualization (classic or blue ocean). This applies to declarative pipelines right now, and I can't think there would be anyone arguing against it. IF skipped stages are one day available  on scripted pipelines, the same rendering would apply as well. Would there be support for splitting this ticket maybe ?  
 

  
 
 
 
 

 
 
 

 
 
 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-49606) Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49606  
 
 
  Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 JEP-200  lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-49606) Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-49606  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49606  
 
 
  Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49606) Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49606  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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-48057) Durable Task 1.16 breaks PowerShell live output

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-48057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released with 1.18  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48057  
 
 
  Durable Task 1.16 breaks PowerShell live output   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-47797) Powershell Step Always Returns Success

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-47797  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released with 1.18  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47797  
 
 
  Powershell Step Always Returns Success   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-46496) Powershell step in pipeline job outputs UTF-8 BOM

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-46496  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released with 1.18  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46496  
 
 
  Powershell step in pipeline job outputs UTF-8 BOM   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-46876) PowerShell: incorrect handling of $LASTEXITCODE can cause broken script to not abort pipeline

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-46876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released with version 1.18  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46876  
 
 
  PowerShell: incorrect handling of $LASTEXITCODE can cause broken script to not abort pipeline   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46508) Powershell Pipeline Step hangs if capturing Stdout and output is null

2018-02-16 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-46508  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released with 1.18  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46508  
 
 
  Powershell Pipeline Step hangs if capturing Stdout and output is null   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49606) Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49606  
 
 
  Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList
 

  
 
 
 
 

 
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-49606) Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-49606  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view

2018-02-16 Thread pmatig...@successfactors.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Matignon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47286  
 
 
  Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view   
 

  
 
 
 
 

 
Change By: 
 Patrice Matignon  
 

  
 
 
 
 

 
 Created as response to comments of https://issues.jenkins-ci.org/browse/JENKINS-37781 as the visualization of skipped stages is very, very nice for declarative pipelines in Blue Ocean. # Allow to skip stages in scripted pipelines leading to equally nice visualization in Blue Ocean: The current approaches mentioned by [~mkobit] in https://issues.jenkins-ci.org/browse/JENKINS-37781?focusedCommentId=294965=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-294965 and [~jamesdumay] in https://issues.jenkins-ci.org/browse/JENKINS-37781?focusedCommentId=294966=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-294966 lead to either misleading or just less obvious visualization... # Improve visualization of stage view: instead of showing skipped stages (declarative pipelines) as always being green and allegedly executed, make them e.g. gray. ** Stage "skipped" is actually skipped, but stage view shows:  !classic-ui-stage-view-1.png|thumbnail! ** This is IMHO also  an IMHO  a  major enhancement and valid fix for the other problem reported by [~mkobit] in https://issues.jenkins-ci.org/browse/JENKINS-37781?focusedCommentId=294965=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-294965: "[The Pipeline Stage View Plugin] has some weird display issues if new pipelines have different stage executions than previous ones."  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-49606) Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49606  
 
 
  Jenkins core should whitelist com.google.common.collect.Lists$TransformingRandomAccessList
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-02-16 17:11  
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 It is a follow-up to JENKINS-49573. com.google.common.collect.Lists$TransformingRandomAccessList may be produced by Lists.transform() in Guava, which seems to be a valid use-case. 

 

public ResultShortcut(String name, boolean exact, Result... results) {
this(name, exact, Lists.transform(
Arrays.asList(results),
new Function() {
public String apply(Result result) {
return result.toString();
}
}));
}
 

 Keeping it as Bug so that it becomes an LTS candidate for 2.107.1  
 

  
 
 
 
 

 
 
 

   

[JIRA] (JENKINS-47022) DropDown is loosing focus on selection of an option

2018-02-16 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-47022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DropDown is loosing focus on selection of an option   
 

  
 
 
 
 

 
 Alvaro Lobato Sorry, somehow I missed it. PR is opened, https://github.com/jenkinsci/blueocean-plugin/pull/1660 for back port. I should be able to cut 1.4.2 release today after its merged.  
 

  
 
 
 
 

 
 
 

 
 
 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-49596) User session memory leak

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User session memory leak   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/winstone/pull/44 pulls in newer relese of Jetty. Let's see what olamy responds about 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-49586) JDepend plugin classes not in JEP-200 whitelist

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49586  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDepend plugin classes not in JEP-200 whitelist   
 

  
 
 
 
 

 
 Created https://github.com/jenkinsci/jdepend-plugin/pull/2. Would it be possible to test the snapshot?  
 

  
 
 
 
 

 
 
 

 
 
 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-49586) JDepend plugin classes not in JEP-200 whitelist

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-49586  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49586  
 
 
  JDepend plugin classes not in JEP-200 whitelist   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49605) Add BLUE_OCEAN_BUILD_URL environment variable to builds

2018-02-16 Thread adamwdou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Dougal updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49605  
 
 
  Add BLUE_OCEAN_BUILD_URL environment variable to builds   
 

  
 
 
 
 

 
Change By: 
 Adam Dougal  
 
 
Labels: 
 blueocean  
 
 
Environment: 
 Jenkins 2.89.4Blue Ocean 1.4.0  
 

  
 
 
 
 

 
 
 

 
 
 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-49605) Add BLUE_OCEAN_BUILD_URL environment variable to builds

2018-02-16 Thread adamwdou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Dougal created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49605  
 
 
  Add BLUE_OCEAN_BUILD_URL environment variable to builds   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-02-16 16:19  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Adam Dougal  
 

  
 
 
 
 

 
 When a build fails we'd like to send a slack notification containing a link to the Blue Ocean view of the job. We can construct this using the existing environment variables: 

 

BLUE_OCEAN_BUILD_URL = $HUDSON_URL + "blue/organizations/jenkins/" + urlEncoded($JOB_NAME) + "/detail/" + $JOB_BASE_NAME + "/" + $BUILD_NUMBER
 

 But obviously this may break if Blue Ocean changes it's urls.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-47206) Guess at buckets for initial build via filesystem scan

2018-02-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-47206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Guess at buckets for initial build via filesystem scan   
 

  
 
 
 
 

 
 Interesting, will take a look. I suspect we will need something more careful going forward, but so long as no new user option or API is introduced, it could be a stopgap.  
 

  
 
 
 
 

 
 
 

 
 
 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-49586) JDepend plugin classes not in JEP-200 whitelist

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49586  
 
 
  JDepend plugin classes not in JEP-200 whitelist   
 

  
 
 
 
 

 
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-49586) JDepend plugin classes not in JEP-200 whitelist

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-49586  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-47206) Guess at buckets for initial build via filesystem scan

2018-02-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Lucie Votypkova  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47206  
 
 
  Guess at buckets for initial build via filesystem scan   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Lucie Votypkova  
 

  
 
 
 
 

 
 
 

 
 
 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-47206) Guess at buckets for initial build via filesystem scan

2018-02-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-47206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-47206) Guess at buckets for initial build via filesystem scan

2018-02-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-47206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47206  
 
 
  Guess at buckets for initial build via filesystem scan   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-26107) Allow stage to operate as a labelled block

2018-02-16 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-26107  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow stage to operate as a labelled block   
 

  
 
 
 
 

 
 Yes, possibly. But you generally wouldn't "label a command", probably more a couple of them to produce not just a serie of staged named after the called commands, but that stage is actually doing ("checking code coverage" or whatever).  
 

  
 
 
 
 

 
 
 

 
 
 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-48434) Perforce based Pipelines with polling can Delete Jenkins Home directory

2018-02-16 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Ready for release.  Test build: https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/171/  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48434  
 
 
  Perforce based Pipelines with polling can Delete Jenkins Home directory   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In Progress Resolved  
 
 
Assignee: 
 Paul Allen  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   
 

[JIRA] (JENKINS-48434) Perforce based Pipelines with polling can Delete Jenkins Home directory

2018-02-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-48434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Perforce based Pipelines with polling can Delete Jenkins Home directory   
 

  
 
 
 
 

 
 Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java http://jenkins-ci.org/commit/p4-plugin/2ec2dccaa9e6ff318ccada47f2af691170aaa7be Log: Do not change the workspace root during polling. JENKINS-48434  
 

  
 
 
 
 

 
 
 

 
 
 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-40518) Give the unzip step a parameter to suppress verbose output

2018-02-16 Thread matthew.bren...@lenel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Brenner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 A boolean parameter 'quiet' was added to the unzip step to address this issue in pull request 40. This was released in version 2.0, on February 14th, 2018.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40518  
 
 
  Give the unzip step a parameter to suppress verbose output   
 

  
 
 
 
 

 
Change By: 
 Matthew Brenner  
 
 
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, 

[JIRA] (JENKINS-49461) Publish test results

2018-02-16 Thread dhara.ghodas...@infostretch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dhara Ghodasara assigned an issue to Dhara Ghodasara  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49461  
 
 
  Publish test results   
 

  
 
 
 
 

 
Change By: 
 Dhara Ghodasara  
 
 
Assignee: 
 priya swami Dhara Ghodasara  
 

  
 
 
 
 

 
 
 

 
 
 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-49461) Publish test results

2018-02-16 Thread dhara.ghodas...@infostretch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dhara Ghodasara assigned an issue to priya swami  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49461  
 
 
  Publish test results   
 

  
 
 
 
 

 
Change By: 
 Dhara Ghodasara  
 
 
Assignee: 
 Dhara Ghodasara priya swami  
 

  
 
 
 
 

 
 
 

 
 
 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-34071) Allow filtering by BitBucket Cloud projects

2018-02-16 Thread rene.gre...@ida-analytics.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rene Greuel commented on  JENKINS-34071  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow filtering by BitBucket Cloud projects   
 

  
 
 
 
 

 
 This is a really annoying problem. We have a lot of repositories and grouped them into projects. Why can we create project based Bitbucket folders in Jenkins when using Bitbucket server, but when using Bitbucket cloud  we must use the whole team? Actually we are using  a workaround by prefixing the Jenkinsfiles with _ and filter the repos in a team folder config by matching the Jenkinsfile name. This is obviously lame because every folder scan anyhow scans all repos of the team. But it's the only way to get more structure and oversight in huge team configurations.  
 

  
 
 
 
 

 
 
 

 
 
 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-49574) [JEP-200] java.lang.SecurityException: Rejected: java.util.Calendar

2018-02-16 Thread adrien.cl...@gls-france.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien CLERC commented on  JENKINS-49574  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [JEP-200] java.lang.SecurityException: Rejected: java.util.Calendar   
 

  
 
 
 
 

 
 Not before monday. But yes, I think I can manage to test it. Where would it be available for download?  
 

  
 
 
 
 

 
 
 

 
 
 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-49604) Wrong cleaning generated files in overlaying multiple depot directories

2018-02-16 Thread alexey.lar...@jeppesen.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexey Larsky created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49604  
 
 
  Wrong cleaning generated files in overlaying multiple depot directories   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-02-16 15:58  
 
 
Environment: 
 Jenkins 2.89.4  P4 plugin 1.8.5  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Alexey Larsky  
 

  
 
 
 
 

 
   The folder 'Project_1' has sub-folder 'folder' with some files. When I overlaying it by another folder with '//' syntax and enable 'DELETE generated files' - all files from original 'Project_1/folder/...' are removing and stays only '//' mapped files. 

 

 //depot/Project_1/...//joe/...
+//depot/Project_2/folder/... //joe/folder/... 

   PS. The explicit mapping 'Project_1/folder' works OK.   

 

 //depot/Project_1/...//joe/...
 //depot/Project_1/folder/... //joe/folder/...
+//depot/Project_2/folder/... //joe/folder/... 

      
 

  
 
 
 
 

 

[JIRA] (JENKINS-49574) [JEP-200] java.lang.SecurityException: Rejected: java.util.Calendar

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49574  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [JEP-200] java.lang.SecurityException: Rejected: java.util.Calendar   
 

  
 
 
 
 

 
 I have created https://github.com/jenkinsci/cvs-plugin/pull/45 Adrien CLERC would it be possible to test it if the snapshot build passes?  
 

  
 
 
 
 

 
 
 

 
 
 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-40518) Give the unzip step a parameter to suppress verbose output

2018-02-16 Thread matthew.bren...@lenel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Brenner commented on  JENKINS-40518  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the unzip step a parameter to suppress verbose output   
 

  
 
 
 
 

 
 Roman Baeriswyl thanks for pointing that out! I can confirm the parameter is available and working after updating the plugin to 2.0.  
 

  
 
 
 
 

 
 
 

 
 
 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-49574) [JEP-200] java.lang.SecurityException: Rejected: java.util.Calendar

2018-02-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-49574  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49574  
 
 
  [JEP-200] java.lang.SecurityException: Rejected: java.util.Calendar   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49594) Add extension points to contribute and filter Pod Templates

2018-02-16 Thread vinc...@latombe.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated  JENKINS-49594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49594  
 
 
  Add extension points to contribute and filter Pod Templates   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}

2018-02-16 Thread jpe...@veritone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Perez commented on  JENKINS-49485  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}   
 

  
 
 
 
 

 
 I am not using GitHub Enterprise.  
 

  
 
 
 
 

 
 
 

 
 
 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-47434) Differing status checks (pr-merge vs. branch) prevents making one required in GitHub

2018-02-16 Thread median...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47434  
 
 
  Differing status checks (pr-merge vs. branch) prevents making one required in GitHub   
 

  
 
 
 
 

 
Change By: 
 Nick Jones  
 
 
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-47434) Differing status checks (pr-merge vs. branch) prevents making one required in GitHub

2018-02-16 Thread median...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47434  
 
 
  Differing status checks (pr-merge vs. branch) prevents making one required in GitHub   
 

  
 
 
 
 

 
Change By: 
 Nick Jones  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-47434) Differing status checks (pr-merge vs. branch) prevents making one required in GitHub

2018-02-16 Thread median...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones commented on  JENKINS-47434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Differing status checks (pr-merge vs. branch) prevents making one required in GitHub   
 

  
 
 
 
 

 
 The best answer (also posted on StackOverflow) seems to be to configure the Multibranch Pipeline job to "Discover pull requests from origin" and "Discover pull requests from forks", in both cases with the setting of "merging the pull request with the current target branch revision". That strategy will consistently post the "continuous-integration/jenkins/pr-merge" status to GitHub, which can then be made required.  
 

  
 
 
 
 

 
 
 

 
 
 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-40518) Give the unzip step a parameter to suppress verbose output

2018-02-16 Thread r.baeris...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Baeriswyl commented on  JENKINS-40518  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the unzip step a parameter to suppress verbose output   
 

  
 
 
 
 

 
 Seems to be released: https://github.com/jenkinsci/pipeline-utility-steps-plugin/blob/master/CHANGES.md  
 

  
 
 
 
 

 
 
 

 
 
 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-49603) Configuration slicer does not work on groovy scripts - NoSuchFieldError: DESCRIPTOR

2018-02-16 Thread mrich...@paychex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark R created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49603  
 
 
  Configuration slicer does not work on groovy scripts - NoSuchFieldError: DESCRIPTOR   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Mikael Gaunin  
 
 
Components: 
 configurationslicing-plugin  
 
 
Created: 
 2018-02-16 14:44  
 
 
Environment: 
 Jenkins 2.7.1  Configuration Slicing Plugin 1.47  Groovy 1.24   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark R  
 

  
 
 
 
 

 
 Field Groovy.DESCRIPTOR was removed in 1.16. https://github.com/jenkinsci/groovy-plugin/blob/groovy-1.15/src/main/java/hudson/plugins/groovy/Groovy.java#L136 https://github.com/jenkinsci/groovy-plugin/blob/groovy-1.16/src/main/java/hudson/plugins/groovy/Groovy.java#L136 

 
Caused by: java.lang.NoSuchFieldError: DESCRIPTOR
	at configurationslicing.tools.GroovySlicer$GroovySlicerSpec.getToolInstallations(GroovySlicer.java:57)
	at configurationslicing.tools.AbstractToolSlicerSpec.getInstallations(AbstractToolSlicerSpec.java:109)
	at configurationslicing.tools.AbstractToolSlicerSpec.setValues(AbstractToolSlicerSpec.java:87)
	at configurationslicing.tools.AbstractToolSlicerSpec.setValues(AbstractToolSlicerSpec.java:24)
	at configurationslicing.UnorderedStringSlicer.transform(UnorderedStringSlicer.java:100)
	at configurationslicing.UnorderedStringSlicer.transform(UnorderedStringSlicer.java:6)
	at configurationslicing.ConfigurationSlicing$SliceExecutor.transform(ConfigurationSlicing.java:136)
	at configurationslicing.ConfigurationSlicing$SliceExecutor.doSliceconfigSubmit(ConfigurationSlicing.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 

[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes

2018-02-16 Thread w.male...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Waldek M commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes   
 

  
 
 
 
 

 
 I took the liberty to link JENKINS-38331 - per-stage `agent` declarations are also affected.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


  1   2   3   >