[JIRA] (JENKINS-33238) GitPlugin | Concurrent builds are serialized when publishing

2016-09-26 Thread rejeeshchandran...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rejeesh Chandran commented on  JENKINS-33238  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitPlugin | Concurrent builds are serialized when publishing   
 

  
 
 
 
 

 
 We are getting the same issue but with Memory Map Publisher plugin. 

 

Memory Map Publisher is waiting for a checkpoint on  #
 

 If the previous job is taking too much time or stuck then then next job will also be taking time or stuck at this point.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38523) Stage listing flashes "no steps" when loading a stage for the first time

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38523  
 
 
  Stage listing flashes "no steps" when loading a stage for the first time   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/27 5:58 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 Some times if the step listing takes a while to show, the pipeline results screen can show "no steps" empty state incorrectly, before being replaced with the step listing...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-38522) Long stage names overflow poorly on stage graph

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38522  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Long stage names overflow poorly on stage graph   
 

  
 
 
 
 

 
 cc James Dumay - I thought there could be a little bit of design thought over this. My suggestion is sensible truncation with a hover state - can it be that simple?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38522) Long stage names overflow poorly on stage graph

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38522  
 
 
  Long stage names overflow poorly on stage graph   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2016-09-27 at 2.24.00 pm.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/27 5:52 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 If you are creative with words, you end up with stage names that don't play nice with stage graph.  This perhaps should be truncated more elegantly with a hover state to show the full name...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
   

[JIRA] (JENKINS-38522) Long stage names overflow poorly on stage graph

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Brody Maclean  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38522  
 
 
  Long stage names overflow poorly on stage graph   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Brody Maclean  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-38442  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support nested stages in the Pipeline Graph   
 

  
 
 
 
 

 
 [~mbadran] well, some slight good news: there is a proposal that more information about scripts is returned so instead of saying "shell script" it can show a snippet of the script itself (just a little bit) or the output if run (that isn't being done as part of blue ocean project though, as deeper changes are needed) - so that helps a bit. But to clarify, this is clearer. So you are happy with a stage graph at a high level, up the top, but need ways to group multiple steps into one, and label them (down the bottom). Maybe nested stage is useful for that, but not sure. To me nested stage implies a nesting of the visual graph, but we will see...  [~jamesdumay] perhaps this is a case for labelled steps of some kind?
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38442  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support nested stages in the Pipeline Graph   
 

  
 
 
 
 

 
 mohamed badran well, some slight good news: there is a proposal that more information about scripts is returned so instead of saying "shell script" it can show a snippet of the script itself (just a little bit) or the output if run (that isn't being done as part of blue ocean project though, as deeper changes are needed) - so that helps a bit.  But to clarify, this is clearer. So you are happy with a stage graph at a high level, up the top, but need ways to group multiple steps into one, and label them (down the bottom). Maybe nested stage is useful for that, but not sure. To me nested stage implies a nesting of the visual graph, but we will see...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38493) Add a new status indicator for "waiting for input"

2016-09-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38493  
 
 
  Add a new status indicator for "waiting for input"   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope* Add a new status indicator for "waiting for input"  in the JDL  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38482) Documentation of ExtensionPoints and their binding attributes they fill pass through

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Documentation of ExtensionPoints and their binding attributes they fill pass through   
 

  
 
 
 
 

 
 @thorsten it does yes. - where would that documentation live - where the extension point is defined? could it be generated somehow? It seems ideally to belong where the extension point itself is defined in (say) jsx, and then a tool could extract it? or else (as keith has suggested) have the UI show it up sometimes with clickable docs?  There is this ticket: https://issues.jenkins-ci.org/browse/JENKINS-35842 - which I think this should be combined with. Thoughts?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36795) hp automation tools - pipeline enabled

2016-09-26 Thread xiwen.z...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 xiwen zhao started work on  JENKINS-36795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 xiwen zhao  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


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

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Christian Höltje ha - no I think its just as this was referred to in a commit message in a pull request, and JIRA automatically picks it up (not directly related to this issue, but was impacted by it).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


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

2016-09-26 Thread docw...@gerf.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 I was trying to figure out if it was some weird spam or what...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38515) Get the output from git client for debugging

2016-09-26 Thread jwstr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Strickland closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 See last comment; you have to hit an error condition to see the full logs which is thrown up in the GitException. A good path will not show the logs.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38515  
 
 
  Get the output from git client for debugging
 

  
 
 
 
 

 
Change By: 
 Jonathan Strickland  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38515) Get the output from git client for debugging

2016-09-26 Thread jwstr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Strickland commented on  JENKINS-38515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Get the output from git client for debugging
 

  
 
 
 
 

 
 Mark Waite Ok so I feel like I wasted a lot of resources time on this; definitely apologize in advance. After looking at the code (https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1752) I found that its only going to give the stderr and stdout output if an actual error occurs. Thus, my testing of good path we were not seeing the full dumps. After testing with an error condition (simulate bad credentials which is really easy) we saw the complete curl dumps. In case someone else hits this issue and needs debug tracing, this is what we did: 1. Inject the following into your environment. We did it using puppet to orchestrate our environments and place a profile.d file on build servers / container images: $ more /etc/profile.d/git.sh export GIT_CURL_VERBOSE=1 export GIT_TRACE=1 umask 077 These may/may not work with 2.x git, it appears some of the trace/verbose env vars have changed. 2. You have to hit an error conditions for them to show up. https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1752 as an error (timeout, bad status code, ect..) will throw a git exception with the debug information from stderr / stdout of the git cli command.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38515) Get the output from git client for debugging

2016-09-26 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-38515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Get the output from git client for debugging
 

  
 
 
 
 

 
 If you're running command line git and running on a specific slave and cloning with ssh, you may be able to get the same result by editing your ~/.ssh/config file to place the ssh configuration debug settings there.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38515) Get the output from git client for debugging

2016-09-26 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38515  
 
 
  Get the output from git client for debugging
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


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

2016-09-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Tom FENNELLY I enjoy your amusing squashed git commit comments   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38312) TFS plugin fails with TF400898: An Internal Error Occurred

2016-09-26 Thread olivier.dagen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Dagenais assigned an issue to Jared Jensen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jared Jensen: can you check the Windows Event Log on the TFS server? I've seen something like this before, where the server threw an exception due to the path being too long and it wasn't properly reported back at the other end. Also, what version of the TFS plugin are you using? Please re-assign to me with your answers. Thanks! - Oli  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38312  
 
 
  TFS plugin fails with TF400898: An Internal Error Occurred   
 

  
 
 
 
 

 
Change By: 
 Olivier Dagenais  
 
 
Assignee: 
 redsolo Jared Jensen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38521) javax.servlet.ServletException: java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win

2016-09-26 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please use the Jenkins users mailing list for configuration questions, rather than submitting a bug report. Very few people read the bug reports, while many more read the mailing list and can offer assistance without relying on the plugin maintainer for answers to all questions.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38521  
 
 
  javax.servlet.ServletException: java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  

[JIRA] (JENKINS-38056) Duration of running Pipeline is not live

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler commented on  JENKINS-38056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duration of running Pipeline is not live   
 

  
 
 
 
 

 
 Yeah something along that lines, but IMO the https://codepen.io/seoh/pen/PPZYQy would do just fine. https://www.youtube.com/watch?v=9aA-1rqtQWs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37793) Developer can see meaningful page titles

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler updated  JENKINS-37793  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37793  
 
 
  Developer can see meaningful page titles   
 

  
 
 
 
 

 
Change By: 
 Thorsten Scherler  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37565) Update supported Java version to Java7

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37565  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update supported Java version to Java7   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/remoting/f0f10b0d9319ec201c085a9f4b35c2014befec9f Log: JENKINS-37565 - Really allow compiling with Java 7 (#108) Just a leftover fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37834) Spacing and alignment of "action" icons is inconsistent

2016-09-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37834  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Spacing and alignment of "action" icons is inconsistent   
 

  
 
 
 
 

 
 Cliff Meyers I know Brody Maclean might have some opinions on this (he had a few tweaks in mind for the actions on the cards)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38375) Build parameters not getting propagated in Pipeline (jenkinsfile).

2016-09-26 Thread cchdr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay H commented on  JENKINS-38375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build parameters not getting propagated in Pipeline (jenkinsfile).   
 

  
 
 
 
 

 
 I saw the same behavior. What you can try is to use  node  { echo "$mode" }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38056) Duration of running Pipeline is not live

2016-09-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-38056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duration of running Pipeline is not live   
 

  
 
 
 
 

 
 Ah, good call. Sounds like if duration < 6 millis that we should display the exact number of seconds, in addition to updating every second.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38521) javax.servlet.ServletException: java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win

2016-09-26 Thread nsaitharunre...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sai Tharun Nelaballi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38521  
 
 
  javax.servlet.ServletException: java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2016/Sep/26 9:59 PM  
 
 
Environment: 
 Windows  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sai Tharun Nelaballi  
 

  
 
 
 
 

 
 Trying to create a job with GIT & Jenkins  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 

[JIRA] (JENKINS-35269) Job configuration UI Layout is broken

2016-09-26 Thread grei...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gus reiber assigned an issue to Manuel Adan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35269  
 
 
  Job configuration UI Layout is broken   
 

  
 
 
 
 

 
Change By: 
 gus reiber  
 
 
Assignee: 
 gus reiber Manuel Adan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35269) Job configuration UI Layout is broken

2016-09-26 Thread grei...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gus reiber assigned an issue to Manuel Recena Soto  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35269  
 
 
  Job configuration UI Layout is broken   
 

  
 
 
 
 

 
Change By: 
 gus reiber  
 
 
Assignee: 
 Manuel  Adan  Recena Soto  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35269) Job configuration UI Layout is broken

2016-09-26 Thread grei...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gus reiber commented on  JENKINS-35269  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job configuration UI Layout is broken   
 

  
 
 
 
 

 
 Manuel Recena Soto Can you help me take a look at this. As Daniel Beck describes, the easiest repro is to add a really long text string into the a description input box (or a script field): 
 
I have been using this as my quick test: http://sa-cje-test-1-642-4-1-11.jenkins.beedemo.net/job/pipeline-examples/job/beedemo/job/apple-swift-on-linux/job/master/configure 
Add this string to the description: 

 
asdf asdf asdfasdfasdf asdfasf alsfk 'adklsf';lasfk alsfk fka'fkl afkla'fkla'fkl 'asdfkl as'fkla'sfkla'sfkla'sfkla'fk'afk
 

 
see the form content spill out of the display box 
 I am not able to find any CSS to apply to the parent table cell or any of the parent elements wrapping that textarea (which isn't really a textarea at all, but some 'codemirror' component). Anyway, if you can take a look, I would appreciate it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message 

[JIRA] (JENKINS-35269) Job configuration UI Layout is broken

2016-09-26 Thread grei...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gus reiber assigned an issue to gus reiber  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35269  
 
 
  Job configuration UI Layout is broken   
 

  
 
 
 
 

 
Change By: 
 gus reiber  
 
 
Assignee: 
 gus reiber  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials

2016-09-26 Thread a...@evaluagent.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Richards commented on  JENKINS-34958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Getting "Your Authorization Token has expired" when using ECR credentials   
 

  
 
 
 
 

 
 Hi david ficociello, Drew Halloran, We managed to resolve this problem, after almost 3 weeks of conversation with AWS Support, by using the ecr-credential-helper. You can find the helper and documentation here: https://github.com/awslabs/amazon-ecr-credential-helper Good Luck!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35269) Job configuration UI Layout is broken

2016-09-26 Thread grei...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gus reiber assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35269  
 
 
  Job configuration UI Layout is broken   
 

  
 
 
 
 

 
Change By: 
 gus reiber  
 
 
Assignee: 
 gus reiber  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-24024) Opt-out of pulling changelist info for Build Changes

2016-09-26 Thread matthew.k.sm...@viasat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Smith commented on  JENKINS-24024  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Opt-out of pulling changelist info for Build Changes   
 

  
 
 
 
 

 
 Our project would also like to see this become a feature. Is this going to be resolved soon?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37260) Add PATCH Mode

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add PATCH Mode   
 

  
 
 
 
 

 
 Code changed in jenkins User: Janario Oliveira Path: README.md src/main/java/jenkins/plugins/http_request/HttpMode.java src/main/java/jenkins/plugins/http_request/util/HttpClientUtil.java src/test/java/jenkins/plugins/http_request/HttpRequestStepTest.java src/test/java/jenkins/plugins/http_request/HttpRequestTest.java http://jenkins-ci.org/commit/http-request-plugin/f3d78a89f8320fcd5d919048cb543935d739b757 Log: Merge pull request #19 from kmadel/add-patch-mode JENKINS-37260 Add PATCH Mode Compare: https://github.com/jenkinsci/http-request-plugin/compare/82285c2b86e1...f3d78a89f832  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37260) Add PATCH Mode

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add PATCH Mode   
 

  
 
 
 
 

 
 Code changed in jenkins User: Kurt Madel Path: README.md src/main/java/jenkins/plugins/http_request/HttpMode.java src/main/java/jenkins/plugins/http_request/util/HttpClientUtil.java src/test/java/jenkins/plugins/http_request/HttpRequestStepTest.java src/test/java/jenkins/plugins/http_request/HttpRequestTest.java http://jenkins-ci.org/commit/http-request-plugin/42450f9cb099e6450581fce0302312ff9581a544 Log: fix for JENKINS-37260 Add PATCH Mode, also updated README and added example to show use of PATCH with a request body  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38519) EMail-Ext Extended Pipeline Support - Failed Tests

2016-09-26 Thread matthewrei...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Reiter commented on  JENKINS-38519  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EMail-Ext Extended Pipeline Support - Failed Tests   
 

  
 
 
 
 

 
 I've created a pull request: https://github.com/jenkinsci/email-ext-plugin/pull/141  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37565) Update supported Java version to Java7

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37565  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update supported Java version to Java7   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/remoting/9828cd66ddf70b5f5fc3ac5a91de7ee8c96b90bc Log: JENKINS-37565 - Really allow compiling with Java 7 Just a leftover fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38520) Every message in slave log appears twice

2016-09-26 Thread matej.kor...@nuance.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matěj Korvas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38520  
 
 
  Every message in slave log appears twice   
 

  
 
 
 
 

 
Change By: 
 Matěj Korvas  
 
 
Environment: 
 * Virtualbox 64-bit Ubuntu* Java 7, Oracle:java version "1.7.0_80"  // Java(TM) SE Runtime Environment (build 1.7.0_80-b15)  // Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)* Jenkins installed and run as described in  [Building Jenkins| https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins ] , except I checked out the LTS version tag 2.7.4 (remoting v2.60)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38520) Every message in slave log appears twice

2016-09-26 Thread matej.kor...@nuance.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matěj Korvas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38520  
 
 
  Every message in slave log appears twice   
 

  
 
 
 
 

 
Change By: 
 Matěj Korvas  
 
 
Environment: 
 * Virtualbox 64-bit Ubuntu* Java 7, Oracle: {noformat} java version "1.7.0_80"  // Java(TM) SE Runtime Environment (build 1.7.0_80-b15)  // Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) {noformat} * Jenkins installed and run as described in [Building Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins], except I checked out the LTS version tag 2.7.4 (remoting v2.60)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38520) Every message in slave log appears twice

2016-09-26 Thread matej.kor...@nuance.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matěj Korvas created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38520  
 
 
  Every message in slave log appears twice   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/26 9:17 PM  
 
 
Environment: 
 * Virtualbox 64-bit Ubuntu  * Java 7, Oracle:  {noformat}  java version "1.7.0_80"  Java(TM) SE Runtime Environment (build 1.7.0_80-b15)  Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)  {noformat}  * Jenkins installed and run as described in [Building Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins], except I checked out the LTS version tag 2.7.4 (remoting v2.60)  
 
 
Labels: 
 slaves  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Matěj Korvas  
 

  
 
 
 
 

 
 Running a local slave, launched using a command, with the -slaveLog option causes a log file to be written (as expected) with every message printed twice there, like this: 

 
channel startedchannel started

channel stoppedchannel stopped

 

 (which is not expected). The launch script looks as follows (/home/matej/wc/jenkins is path to the Jenkins clone): 

 
#!/bin/bash --norc
export TMP=$(mktemp -d --tmpdir jenkins-X)

[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials

2016-09-26 Thread da...@cybric.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 david ficociello commented on  JENKINS-34958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Getting "Your Authorization Token has expired" when using ECR credentials   
 

  
 
 
 
 

 
 This is also preventing us from moving forward with this plugin. We are in us-west-2. Is there any timeline at all for this? It would greatly help to know so we can either wait or move on to other solutions. Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38056) Duration of running Pipeline is not live

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler commented on  JENKINS-38056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duration of running Pipeline is not live   
 

  
 
 
 
 

 
 that is not the problem, the problem is that the TimeDuration is using  

 

const duration = moment.duration(millis).humanize();
 

 a fixed format ATM which results in that you see no seconds (because of humanize). In running, however, you would be more interested in a format like we use in the hint 

 

moment.duration(millis).format("M [mos], d [days], h[h], m[m], s[s]");
 

 I can add the updatePeriod but as long we use .humanize() the min update is a minute, you will not see seconds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code

2016-09-26 Thread elaine_richa...@symantec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Elaine Richards commented on  JENKINS-38276  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Increase size of text area for pipeline script code   
 

  
 
 
 
 

 
 Count me in as a plaintive requester for a resizeable text box. I know we can use a script that we edit a file outside of Jenkins, but I'm poking at it in an iterative fashion and having a window large enough to do something more than "Hello World" would be peachy. I use Safari 9.1.1 and Chrome version 53.0.2785.116 (64-bit). Will not try on Firefox because of my personal history of "Why is this taking up so much memory?"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-4816) Allow for grepping console output

2016-09-26 Thread lid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lidiam commented on  JENKINS-4816  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow for grepping console output   
 

  
 
 
 
 

 
 Some of our console log files are quite large and the idea was to avoid loading them whole in the browser for searching. Also, wanted to be able to search for anything, e.g. a certain command that was executed, to see its output, etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35367) EMail-Ext Extended Pipeline Support - Templates

2016-09-26 Thread matthewrei...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Reiter commented on  JENKINS-35367  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EMail-Ext Extended Pipeline Support - Templates   
 

  
 
 
 
 

 
 I've opened JENKINS-38519 for the issue with FAILED_TESTS because it's not directly related to templates.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38519) EMail-Ext Extended Pipeline Support - Failed Tests

2016-09-26 Thread matthewrei...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Reiter created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38519  
 
 
  EMail-Ext Extended Pipeline Support - Failed Tests   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2016/Sep/26 8:57 PM  
 
 
Environment: 
 email-ext-plugin version 2.50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Matthew Reiter  
 

  
 
 
 
 

 
 JENKINS-35367 got part way towards supporting email-ext within pipeline builds, but the following tokens still fail to expand when placed in the subject or body of an email: FAILED_TESTS, TEST_COUNTS, and TRIGGER_NAME. The email instead contains the following text: FAILED_TESTS is not supported in this context  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
   

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

2016-09-26 Thread aziz.alfoud...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abdulaziz Alfoudari edited a comment on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Until there is a fix, a quick  around  workaround  is to  append  prepend  `cd foo &&` to each `sh` inside `dir('foo')`:{code}dir('foo') {sh 'cd foo && make'}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38056) Duration of running Pipeline is not live

2016-09-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-38056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duration of running Pipeline is not live   
 

  
 
 
 
 

 
 I think the component here is actually TimeDuration but in principle it's very similar to ReadableDate. I would suggest that you add another prop called updatePeriod which you can set to any number in millis. Default to 3. Then just use that value instead of "3" when calculating timePeriodMillis. Also probably need to shift that logic to _handleProps since the value of props.updatePeriod can change. And if you just want to kick this bug over to me that is fine too   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


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

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Code changed in jenkins User: Tom Fennelly Path: .printip.js Dockerfile Jenkinsfile nightwatch.conf.js package.json run.sh src/main/java/io/jenkins/blueocean/BOJUnitTest.java src/main/java/io/jenkins/blueocean/BlueOceanWinstoneController.java src/main/java/io/jenkins/blueocean/NightwatchRunner.java src/main/js/custom_commands/moveClassicBottomStickyButtons.js src/main/js/custom_commands/moveConfigpageButtons.js src/main/js/custom_commands/removeBreadcrumbBar.js src/main/js/custom_commands/removePageHead.js src/main/js/globals.js src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/classic_jenkins/folderCreate.js src/main/js/page_objects/classic_jenkins/freestyleConfig.js src/main/js/page_objects/classic_jenkins/freestyleCreate.js src/main/js/page_objects/classic_jenkins/multibranchCreate.js src/main/js/page_objects/classic_jenkins/pipelineCreate.js src/main/nightwatch.json src/test/java/utils/DevRunner.java start-selenium.sh stop-selenium.sh http://jenkins-ci.org/commit/blueocean-acceptance-test/6aac5c09b5614833cb2bcd78bc346a7e4dd0c2da Log: More ATH shenanigans + a Jenkinsfile (#44) 
 
Added a simple Jenkinsfile 
 
 
Use docker-selenium images 
 
 
Use official images in the local start selenium scripts 
 
 
More tweaking of the Jenkinsfile 
 
 
And more tweaking of the Jenkinsfile again 
 
 
what's the pwd 
 
 
what's the pwd 
 
 
what's the pwd 
 
 
Map in a volume for ~/.m2 
 
 
Map in a volume for ~/.m2 
 
 
No clue what I'm doing 
 
 
revert BS tests 

[JIRA] (JENKINS-37446) StringIndexOutOfBoundsException when editing Custom Configuration field

2016-09-26 Thread michael.piff...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Piffret commented on  JENKINS-37446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StringIndexOutOfBoundsException when editing Custom Configuration field   
 

  
 
 
 
 

 
 This would be great. We could suggest a few modifications to the ini4j library, hopefully they'll take pull request (or patches or whatever) though releases seem to be few and far between.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Change By: 
 Brian Ray  
 
 
Attachment: 
 firefox_2016-09-26_13-10-08.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Change By: 
 Brian Ray  
 
 
Attachment: 
 firefox_2016-09-23_13-52-40.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38518) Add ability to specify Mattermost user login credentials

2016-09-26 Thread roger.my...@draeger.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Myung created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38518  
 
 
  Add ability to specify Mattermost user login credentials   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jo Vandeginste  
 
 
Components: 
 mattermost-plugin  
 
 
Created: 
 2016/Sep/26 8:05 PM  
 
 
Environment: 
 The plugin seems to take the login information from the Jenkins user. This is major limitation on Windows since Jenkins uses the Active Directory login, but Mattermost can only use Active Directory if you use Mattermost Enterprise. That means this plugin can only be used on Windows with Mattermost Enterprise.   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Roger Myung  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 firefox_2016-09-23_13-52-40.png, firefox_2016-09-23_13-54-51.png, firefox_2016-09-23_13-57-54.png  
 
 
Components: 
 subversion-plugin, workflow-cps-global-lib-plugin  
 
 
Created: 
 2016/Sep/26 8:04 PM  
 
 
Environment: 
 LTS 2.7.4   scm-api 1.3  subversion 2.6  worfklow-cps-global-lib 2.3   Zulu OpenJDK 8.17.0.3-win64 (1.8.0_102-b14)  Win 7 Pro master--error does not involve agents  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Brian Ray  
 

  
 
 
 
 

 
 ... multiple external SVN Legacy SCM libs are loaded by the Jenkinsfile and the Local module directory indicates preservation/overriding of the parent directory. (Ie, when the dot default is not used and a working copy root directory for each lib is created under the @libs directory. Configuration of global and folder specific libraries as shown in the attachments. The Jenkinsfile script begins 

@Library('pipeline_global_helpers') _ 
@Library('pipeline_branch_build') import com.foo.bar.Application
 Running the pipeline makes it as far as checking out or updating the local working copies in the @libs/pipeline_global_helpers and @libs/pipeline_branch_build in the pipeline workspace on the master, but execution 

[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin

2016-09-26 Thread and...@k-tz.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Barychev edited a comment on  JENKINS-29075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: List of changes escapes HTML output of jira-plugin   
 

  
 
 
 
 

 
 {color:#d04437}*Please disregard the below comment. I  was totally wrong. After switching the Jenkins projects to the other JIRA, the 5.4 issues also appear in escaped HTML. My bad.*{color}I 'm having this problem for a couple of months. My case may be helpful for the plugin developers though.I have *two* JIRA servers. The first is running JIRA 5.4, with both SOAP and REST APIs enabled. The other is running JIRA 6.2, with REST API only.I never had a problem with Jenkins displaying issues' details for projects hosted by JIRA 5.4. However, Jenkins displays the escaped HTML for the issues in projects hosted by JIRA 6.2.Please note, that the {color:red}escaped HTML is displayed{color} only on *Build Status* and *Build Changes* pages. The {color:#14892c}same issues are displayed correctly{color} on the *Project Changes* page. !JIRA-5.4-vs-JIRA-6.2.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37965) REGRESSION react developer tools stopped working

2016-09-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers edited a comment on  JENKINS-37965  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION react developer tools stopped working   
 

  
 
 
 
 

 
 Yeah, same error in today's master. Looks like something in the main dashboard  UI  content  is throwing this error because that part of the React component tree doesn't display in the inspector , but the header, footer and toast drawer show up ok . In its place is a strange message, "node was deleteNode was deleted"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37965) REGRESSION react developer tools stopped working

2016-09-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-37965  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REGRESSION react developer tools stopped working   
 

  
 
 
 
 

 
 Yeah, same error in today's master. Looks like something in the main dashboard UI is throwing this error because that part of the React component tree doesn't display in the inspector. In its place is a strange message, "node was deleteNode was deleted"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin

2016-09-26 Thread and...@k-tz.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Barychev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29075  
 
 
  List of changes escapes HTML output of jira-plugin   
 

  
 
 
 
 

 
Change By: 
 Andrei Barychev  
 
 
Attachment: 
 JIRA-5.4-vs-JIRA-6.2.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37425) Rework the behavior of Toasts for Run, Stop and Replay

2016-09-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated  JENKINS-37425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37425  
 
 
  Rework the behavior of Toasts for Run, Stop and Replay   
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin

2016-09-26 Thread and...@k-tz.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Barychev edited a comment on  JENKINS-29075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: List of changes escapes HTML output of jira-plugin   
 

  
 
 
 
 

 
 I'm having this problem for a couple of months. My case may be helpful for the plugin developers though.I have *two* JIRA servers. The first is running JIRA 5.4, with both SOAP and REST APIs enabled. The other is running JIRA 6.2, with REST API only.I never had a problem with Jenkins displaying issues' details for projects hosted  in  by  JIRA 5.4  projects . However, Jenkins displays the escaped HTML for the issues in projects hosted by JIRA 6.2.Please note, that the {color:red}escaped HTML is displayed{color} only on *Build Status* and *Build Changes* pages. The {color:#14892c}same issues are displayed correctly{color} on the *Project Changes* page. !JIRA-5.4-vs-JIRA-6.2.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin

2016-09-26 Thread and...@k-tz.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Barychev commented on  JENKINS-29075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: List of changes escapes HTML output of jira-plugin   
 

  
 
 
 
 

 
 I'm having this problem for a couple of months. My case may be helpful for the plugin developers though. I have two JIRA servers. The first is running JIRA 5.4, with both SOAP and REST APIs enabled. The other is running JIRA 6.2, with REST API only. I never had a problem with Jenkins displaying issues' details for projects hosted in JIRA 5.4 projects. However, Jenkins displays the escaped HTML for the issues in projects hosted by JIRA 6.2. Please note, that the escaped HTML is displayed only on Build Status and Build Changes pages. The same issues are displayed correctly on the Project Changes page. 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37425) Rework the behavior of Toasts for Run, Stop and Replay

2016-09-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-37425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rework the behavior of Toasts for Run, Stop and Replay   
 

  
 
 
 
 

 
 PR: https://github.com/jenkinsci/blueocean-plugin/pull/515  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38507) pull request builder plugin triggers builds on new commit (without keyword)

2016-09-26 Thread sleonov...@micron.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergey Leonovich commented on  JENKINS-38507  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pull request builder plugin triggers builds on new commit (without keyword)   
 

  
 
 
 
 

 
 Also, it appears that Jenkins setup for the plugin does not support regular expressions for "CI Build Phrases" We only want to trigger the build on ^runbuild$ - complete word.  Not being able to do that can also trigger false build execution if developer just mentions "runbuild" in the comment section without intention to actually run the build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31846) MultiJob plugin should differ when the same job is used multiple times

2016-09-26 Thread brenden.co...@witricity.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brenden Conte edited a comment on  JENKINS-31846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MultiJob plugin should differ when the same job is used multiple times
 

  
 
 
 
 

 
 same issue, would love to see fixed (or help fix it) And by extension, include the __BUILDNAME alongside NUMBER and RESULT for multi-run projects.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31846) MultiJob plugin should differ when the same job is used multiple times

2016-09-26 Thread brenden.co...@witricity.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brenden Conte commented on  JENKINS-31846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MultiJob plugin should differ when the same job is used multiple times
 

  
 
 
 
 

 
 same issue, would love to see fixed (or help fix it)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38464) milestone step incorrectly detected as running inside parallel

2016-09-26 Thread timothy.mcna...@build.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim McNally edited a comment on  JENKINS-38464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: milestone step incorrectly detected as running inside parallel   
 

  
 
 
 
 

 
 Ran into this as well. It seems to fail if the milestone is inside any block if a parallel block is in the script.The following works.{noformat}parallel (foo: {}, bar: {})milestone 1stage ('test') {echo 'hello'}{noformat}Where as this will fail.{noformat}timestamps {parallel (foo: {}, bar: {})milestone 1stage ('test') {echo 'hello'}}{noformat} Yet this will work.{noformat}timestamps {milestone 1stage ('test') {echo 'hello'}}{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38464) milestone step incorrectly detected as running inside parallel

2016-09-26 Thread timothy.mcna...@build.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim McNally edited a comment on  JENKINS-38464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: milestone step incorrectly detected as running inside parallel   
 

  
 
 
 
 

 
 Ran into this as well. It seems to fail if the milestone is inside any block  if a parallel block is in the script .The following works.{noformat}parallel (foo: {}, bar: {})milestone 1stage ('test') {echo 'hello'}{noformat}Where as this will fail.{noformat}timestamps {parallel (foo: {}, bar: {})milestone 1stage ('test') {echo 'hello'}}{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38464) milestone step incorrectly detected as running inside parallel

2016-09-26 Thread timothy.mcna...@build.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim McNally commented on  JENKINS-38464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: milestone step incorrectly detected as running inside parallel   
 

  
 
 
 
 

 
 Ran into this as well. It seems to fail if the milestone is inside any block. The following works. 

 
parallel (
foo: {}, bar: {}
)
milestone 1
stage ('test') {
echo 'hello'
}
 

 Where as this will fail. 

 
timestamps {
parallel (
foo: {}, bar: {}
)
milestone 1
stage ('test') {
echo 'hello'
}
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27219) Job generator config loses "Custom Workspace" everytime the configuration is edited

2016-09-26 Thread karsten.guent...@kamg.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karsten Günther commented on  JENKINS-27219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job generator config loses "Custom Workspace" everytime the configuration is edited   
 

  
 
 
 
 

 
 A workaround for this "not a show stopper"? Replace the plugin with the Job DSL plugin. Fast, reliable and less annoying ...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28961) GET/POST with schedule-build-plugin

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-28961  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GET/POST with schedule-build-plugin   
 

  
 
 
 
 

 
 Code changed in jenkins User: anderl86 Path: src/main/java/org/jenkinsci/plugins/schedulebuild/ScheduleBuildAction.java src/main/resources/org/jenkinsci/plugins/schedulebuild/ScheduleBuildAction/redirect.jelly http://jenkins-ci.org/commit/schedule-build-plugin/1b3bcaf73824a5d9a32fca12c8c0e94401112e01 Log: Merge pull request #5 from phippu/master Fix for JENKINS-28961 Compare: https://github.com/jenkinsci/schedule-build-plugin/compare/39de94f47042...1b3bcaf73824  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28961) GET/POST with schedule-build-plugin

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-28961  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GET/POST with schedule-build-plugin   
 

  
 
 
 
 

 
 Code changed in jenkins User: Philipp Matter Path: src/main/java/org/jenkinsci/plugins/schedulebuild/ScheduleBuildAction.java src/main/resources/org/jenkinsci/plugins/schedulebuild/ScheduleBuildAction/redirect.jelly http://jenkins-ci.org/commit/schedule-build-plugin/e74d9daff886aa4179fae29eebd50cbbae604d21 Log: Fix for JENKINS-28961 schedule build and redirect to project page  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38474) Error after updating AWS SDK to 1.11.37

2016-09-26 Thread tridib.sama...@live.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tridib Samanta commented on  JENKINS-38474  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error after updating AWS SDK to 1.11.37   
 

  
 
 
 
 

 
 This required upgrading the AWS lib version plugin. Created a pull request https://github.com/awslabs/aws-codedeploy-plugin/pull/67  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-09-26 Thread james.vau...@elasticpath.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Vaudry created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38516  
 
 
  "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 James Nord  
 
 
Components: 
 cucumber-testresult-plugin  
 
 
Created: 
 2016/Sep/26 6:21 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Vaudry  
 

  
 
 
 
 

 
 Steps to reproduce: 1. Create a new freestyle job 
 
Add a string parameter: WORK_FOLDER 
Select "Execute concurrent builds if necessary" 
Under "Advanced Project Options", select "Use custom workspace", and input $ {WORK_FOLDER} 
Build action: Invoke Maven 3 "mvn clean verify..." 
Post-build action: "Publish cucumber test result" 
 2. Execute the job twice (simultaneously) with different parameters: 
 
WORK_FOLDER=foo 
WORK_FOLDER=bar 
 Expected behavior: 
 
The two jobs run in parallel and complete independently, using their separate workspaces 
 Actual behavior: One job will wait for the other job to complete. The jobs are dependent on each other in their post-build step.  One job will hang at the step until the second job finishes: 

 
 

[JIRA] (JENKINS-38056) Duration of running Pipeline is not live

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler commented on  JENKINS-38056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duration of running Pipeline is not live   
 

  
 
 
 
 

 
 James Dumay we decided to use the format of the stop clock in case we are in a running job. If not changed within the next 12 hours I will implement as the linked version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35367) EMail-Ext Extended Pipeline Support - Templates

2016-09-26 Thread matthewrei...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Reiter commented on  JENKINS-35367  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EMail-Ext Extended Pipeline Support - Templates   
 

  
 
 
 
 

 
 Even with version 2.50 the FAILED_TESTS macro does not work in pipeline builds; it gets expanded to "FAILED_TESTS is not supported in this context". I believe the problem is that FailedTestsContent was not updated to override the new signature for evaluate() that takes a Run object as opposed to an AbstractBuild object.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37925) Show full log only shows 10000 lines

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler commented on  JENKINS-37925  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Show full log only shows 1 lines   
 

  
 
 
 
 

 
 ping James Sharpe  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38056) Duration of running Pipeline is not live

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler updated  JENKINS-38056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38056  
 
 
  Duration of running Pipeline is not live   
 

  
 
 
 
 

 
Change By: 
 Thorsten Scherler  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38329) REGRESSION Errors on activity and branches tabs

2016-09-26 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler updated  JENKINS-38329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38329  
 
 
  REGRESSION Errors on activity and branches tabs   
 

  
 
 
 
 

 
Change By: 
 Thorsten Scherler  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38515) Get the output from git client for debugging

2016-09-26 Thread jwstr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Strickland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38515  
 
 
  Get the output from git client for debugging
 

  
 
 
 
 

 
Change By: 
 Jonathan Strickland  
 

  
 
 
 
 

 
 We have been experiencing some infrastructure issues are causing some of our git commands to fail (fetch, pull, ect..) on our Jenkins infrastructure side.  We wanted to turn on some deeper git trace levels to capture further information to help us debug the issues.  On our jenkins slaves/master we turned on the below to enable git trace.  The trace shows up when running via the command line and the env vars show up in the system configuration for each slave/master.[jenkins@15d08c2a101e ~]$ more /etc/profile.d/git.shexport GIT_CURL_VERBOSE=1export GIT_TRACE=1The issue we are having is enabling the correct global/job environment variables to show this output in the console of the jobs.  We attempted to enable the verbose env var at https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/GitClient.java (see attachement) but do not get much more information.  Is there an easy way to get the git command output sent to the job console . ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
   

[JIRA] (JENKINS-38515) Get the output from git client for debugging

2016-09-26 Thread jwstr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Strickland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38515  
 
 
  Get the output from git client for debugging
 

  
 
 
 
 

 
Change By: 
 Jonathan Strickland  
 
 
Summary: 
 Get the output from  git client for debugging
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29977) Git Plugin truncates changelog

2016-09-26 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-29977  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Plugin truncates changelog   
 

  
 
 
 
 

 
 AFAIU the comment includes only the first line like many others tools are doing ? https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitChangeSet.java#L233  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37539) Potential NPE in the remoting Engine#connect() if null host or port gets passed

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37539  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Potential NPE in the remoting Engine#connect() if null host or port gets passed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/Engine.java src/main/java/hudson/remoting/Util.java src/main/java/hudson/remoting/jnlp/Main.java src/main/java/org/jenkinsci/remoting/engine/EngineUtil.java src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java http://jenkins-ci.org/commit/remoting/190653b3a3e7a9b582cf923201c735d6d3043ea2 Log: Merge stable-2.x into master (#107) 
 
[maven-release-plugin] prepare release remoting-2.62 
 
 
[maven-release-plugin] prepare for next development iteration 
 
 
[FIXED JENKINS-37539] - Prevent NPE in Engine#connect() when host or port are null or empty (#101) 
 Bug diagnosis: 
 
https://scan8.coverity.com/reports.htm#v14462/p10499/fileInstanceId=12836372=4427367=152195 
https://scan8.coverity.com/reports.htm#v14462/p10499/fileInstanceId=12836372=4427365=152194 
 
 
[CID-152201] - Fix resource leak in remoting.jnlp.Main (#102) 
 
 
[CID-152200,CID-152202] - Resource leak in Cipher I/O streams on exceptional paths (#104) 
 
 
[CID-152200,CID-152202] - Resource leak in Cipher I/O streams on exceptional paths 
 
 
https://scan8.coverity.com/reports.htm#v14462/p10499/fileInstanceId=12836377=4427377=152202 
https://scan8.coverity.com/reports.htm#v14462/p10499/fileInstanceId=12836377=4427377=152200 
 
 
[CID-152202] - Fix typo noticed by @olivergondza 
 
 
Fix another merge conflict 
 
 
Remove EngineUtil#closeAndLogFailures() 
  
 
 

[JIRA] (JENKINS-29977) Git Plugin truncates changelog

2016-09-26 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29977  
 
 
  Git Plugin truncates changelog   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Assignee: 
 Nicolas De Loof  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38515) Get the output from

2016-09-26 Thread jwstr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Strickland created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38515  
 
 
  Get the output from
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 jenkins_gitclient_verbose_script_console.jpg  
 
 
Components: 
 git-client-plugin  
 
 
Created: 
 2016/Sep/26 5:24 PM  
 
 
Environment: 
 Centos 7.x   [jenkins@15d08c2a101e ~]$ git --version  trace: built-in: git 'version'  git version 1.8.3.1   Git Client Plugin - 2.0.0  Git Plugin - 3.0.0  Jenkins Core - 1.656   
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Strickland  
 

  
 
 
 
 

 
 We have been experiencing some infrastructure issues are causing some of our git commands to fail (fetch, pull, ect..) on our Jenkins infrastructure side. We wanted to turn on some deeper git trace levels to capture further information to help us debug the issues. On our jenkins slaves/master we turned on the below to enable git trace. The trace shows up when running via the command line and the env vars show up in the system configuration for each slave/master. [jenkins@15d08c2a101e ~]$ more /etc/profile.d/git.sh export GIT_CURL_VERBOSE=1 export GIT_TRACE=1 The issue we are having is enabling the correct global/job environment variables to show this output in the console of the jobs. We attempted to enable the verbose env var at https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/GitClient.java (see attachement) but do not get much more information. Is there an easy way to get the git command output sent to the job console.  
 

   

[JIRA] (JENKINS-37446) StringIndexOutOfBoundsException when editing Custom Configuration field

2016-09-26 Thread s...@avr-vr.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Delisle commented on  JENKINS-37446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StringIndexOutOfBoundsException when editing Custom Configuration field   
 

  
 
 
 
 

 
 If the parsing of the ini file is modified for this, it might also be possible to fix JENKINS-38038 at the same time so that the order of the confg lines is also preserved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-33210) EOFException when using Static Analysis Collector

2016-09-26 Thread llay...@fc-md.umd.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucas Layman commented on  JENKINS-33210  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EOFException when using Static Analysis Collector   
 

  
 
 
 
 

 
 I am having the same issue. Maven 3.3.9.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38507) pull request builder plugin triggers builds on new commit (without keyword)

2016-09-26 Thread sleonov...@micron.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergey Leonovich commented on  JENKINS-38507  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pull request builder plugin triggers builds on new commit (without keyword)   
 

  
 
 
 
 

 
 We want Plugin to only check last comment for trigger keywords. Push of the commit by itself should not trigger the build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37005) 'properties' step should warn on property deletion in non-multibranch jobs

2016-09-26 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-37005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Whoops, forgot this was merged. =)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37005  
 
 
  'properties' step should warn on property deletion in non-multibranch jobs   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37005) 'properties' step should warn on property deletion in non-multibranch jobs

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray commented on  JENKINS-37005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 'properties' step should warn on property deletion in non-multibranch jobs   
 

  
 
 
 
 

 
 FWIW I was pleasantly surprised that this step works for non-multibranch projects. We'll probably rely on it to keep more of the job configuration under source control. That said, the warning message is a good idea.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38514) CauseOfBlockage from QueueTaskDispatcher.canTake discarded

2016-09-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38514  
 
 
  CauseOfBlockage from QueueTaskDispatcher.canTake discarded   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/26 4:51 PM  
 
 
Labels: 
 queue  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 If you have a QueueTaskDispatcher which returns a CauseOfBlockage from canRun, that becomes BlockedItem.getCauseOfBlockage, which is displayed in the queue widget. But if it returns a CauseOfBlockage from canTake (AFAICT the same for Node.canTake), JobOffer.canTake sees that it is non-null, throws out the actual object with all of its diagnostics, and you wind up with a BuildableItem with CauseOfBlockage.BecauseNodeIsBusy which tells you nothing and may be totally misleading. By asking an implementation to return a @CheckForNull CauseOfBlockage rather than a simple boolean, the implication is that a non-null return value will be displayed to the user. Currently this is not the case. To add insult to injury, Support Core does not report the result of canTake.  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-38513) Unable to copy existing job, getting NoClassDefFoundError AbstractFolder)

2016-09-26 Thread gauravjs...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gaurav Shah created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38513  
 
 
  Unable to copy existing job, getting NoClassDefFoundError AbstractFolder)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 ownership-plugin  
 
 
Created: 
 2016/Sep/26 4:50 PM  
 
 
Environment: 
 Jenkins ver. 1.651.3  Ownership plugin updated from 0.80 to 0.90  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gaurav Shah  
 

  
 
 
 
 

 
 Started getting the below error while trying to use the copy an existing job option in create item. Working fine before upgrading to ownership plugin version 0.90 and worked again after downgrading (which actually uninstalled the plugin). Sep 26, 2016 5:22:03 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving http://:/view/A/createItem java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at 

[JIRA] (JENKINS-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS

2016-09-26 Thread emmanuel.arun...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arun Mathew commented on  JENKINS-32851  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS   
 

  
 
 
 
 

 
 Sebastian Brandt I dont have any proxy set in the jenkins plugin update page. Can you guide me to the tomcat catalina settings? What you tell what exactly you changed? I have nginx acting as reverse proxy.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38134) Generate checksums for war, Windows and OS X distributables

2016-09-26 Thread afernan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Armando Fernandez commented on  JENKINS-38134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Generate checksums for war, Windows and OS X distributables   
 

  
 
 
 
 

 
 Filed another PR for this. See PR description.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38242) Pipeline Model: Add the ability to specify agent parameters (docker)

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38242  
 
 
  Pipeline Model: Add the ability to specify agent parameters (docker)   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38242) Pipeline Model: Add the ability to specify agent parameters (docker)

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Model: Add the ability to specify agent parameters (docker)   
 

  
 
 
 
 

 
 Code changed in jenkins User: Peter Leibiger Path: src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Agent.groovy src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java src/test/resources/agentDocker.groovy src/test/resources/agentDockerWithEmptyDockerArgs.groovy src/test/resources/agentDockerWithNullDockerArgs.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/3878f2932d7c912b777ddabca5cf7f8dcc097d74 Log: [FIXED JENKINS-38242] Add the ability to specify agent parameters (docker) 
 
rename args to dockerArgs 
add tests for null/empty dockerArgs 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38242) Pipeline Model: Add the ability to specify agent parameters (docker)

2016-09-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Model: Add the ability to specify agent parameters (docker)   
 

  
 
 
 
 

 
 Code changed in jenkins User: Peter Leibiger Path: src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Agent.groovy src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java src/test/resources/agentDocker.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/df6eaddfa1fe293f0727d0417082833774647929 Log: [FIXED JENKINS-38242] Add the ability to specify agent parameters (docker)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37817) checkout scm should be able to override extensions/settings

2016-09-26 Thread e...@borgstrom.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Borgstrom resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37817  
 
 
  checkout scm should be able to override extensions/settings   
 

  
 
 
 
 

 
Change By: 
 Evan Borgstrom  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37817) checkout scm should be able to override extensions/settings

2016-09-26 Thread e...@borgstrom.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Borgstrom commented on  JENKINS-37817  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm should be able to override extensions/settings   
 

  
 
 
 
 

 
 I found https://support.cloudbees.com/hc/en-us/articles/226122247-How-to-Customize-Checkout-for-Pipeline-Multibranch that indicates that JENKINS-37658 is the ticket for tracking the changes to allow extensions for GitHub Multibranch projects.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38481) Error while launching new ec2 slave

2016-09-26 Thread mika.jo.karjalai...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mika Karjalainen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38481  
 
 
  Error while launching new ec2 slave   
 

  
 
 
 
 

 
Change By: 
 Mika Karjalainen  
 
 
Component/s: 
 aws-java-sdk-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37737) Intermittent login failures with Active Directory / Matrix-based security

2016-09-26 Thread derek.saka...@rationaleyes.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Derek Sakauye commented on  JENKINS-37737  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent login failures with Active Directory / Matrix-based security   
 

  
 
 
 
 

 
 Hi JR, Our team is pretty small too. So we're in a similar pickle. We actually are running Jenkins with a domain service account. I'll try your "flushdns" workaround next time we can't login. I'll check with Domain Admins about cleaning up the DNS too.  Thanks, 
 
Derek 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


  1   2   >