[JIRA] [htmlpublisher-plugin] (JENKINS-34557) HTML report does not show "table & color"

2016-05-05 Thread mcroo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mcrooney commented on  JENKINS-34557 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: HTML report does not show "table & color"  
 
 
 
 
 
 
 
 
 
 
Could be a _javascript_/CSS issue related to CSP, could you check out the HTML Publisher section of https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy#ConfiguringContentSecurityPolicy-HTMLPublisherPlugin and see if that helps? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [amazon-ecs-plugin] (JENKINS-33087) HTTP proxy configuration in jenkins tool is faling

2016-05-05 Thread yuanzhanghui.1...@163.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 YUAN ZHANGHUI commented on  JENKINS-33087 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: HTTP proxy configuration in jenkins tool is faling  
 
 
 
 
 
 
 
 
 
 
Hi cleclerc Cyrille Le Clerc , I also meet this issue after install jekins on ubuntu 14.04 . Here is my steps :  wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add - $ sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list' $ sudo apt-get update $ sudo apt-get install jenkins  
After that i open firefox and input "http://irda-yzh.bj.intel.com:8080/" . It displays normally . But i want to install some plugin on jekins , it is failed . Manage Jenkins->  Manage Plugins->Updates->choose Advanced ->Click "Check now" in bottom button . It pops up error message : Stack trace java.io.IOException: Server returned HTTP response code: 403 for URL: http://updates.jenkins-ci.org/update-center.json?id=default=2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012

2016-05-05 Thread andrew.co...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Coats edited a comment on  JENKINS-33164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline bat stuck on Windows Server 2012  
 
 
 
 
 
 
 
 
 
 I am having the same issue. Using Windows 10 Pro (Version 1511). Jenkins 2.1 with all  plugin  the  plugins at the  latest version (5/5/2016).My workaround is to continue using Freestyle projects - but I was hoping to use the pipeline projects in order get a history of changes in GIT.{quote}Results (nunit2) saved as CalAgPermits.Maps.Web.UnitTests.xmlAborted by Andrew CoatsSending interrupt signal to processClick here to forcibly terminate running steps{quote}The "click here to  forcibly terminate running steps" does not seem to work. Once the pipeline job is stuck - I have to reboot the machine and delete the pipeline job. If I do not delete the pipeline job... the job gets stuck in the build queue again even after the reboot (proving that pipeline jobs are durable!). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012

2016-05-05 Thread andrew.co...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Coats edited a comment on  JENKINS-33164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline bat stuck on Windows Server 2012  
 
 
 
 
 
 
 
 
 
 I am having the same issue. Using Windows 10 Pro (Version 1511). Jenkins 2.1 with all plugin the latest version (5/5/2016).My workaround is to continue using Freestyle projects - but I was hoping to use the pipeline projects in order get a history of changes in GIT.{quote}Results (nunit2) saved as CalAgPermits.Maps.Web.UnitTests.xmlAborted by Andrew CoatsSending interrupt signal to processClick here to forcibly terminate running steps{quote}The "click here to  forcibly terminate running steps" does not seem to work.    Once the pipeline job is stuck - I have to reboot the machine and delete the pipeline job. If I do not delete the pipeline job... the job gets stuck in the build queue again even after the reboot (proving that pipeline jobs are durable!). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012

2016-05-05 Thread andrew.co...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Coats commented on  JENKINS-33164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline bat stuck on Windows Server 2012  
 
 
 
 
 
 
 
 
 
 
I am having the same issue. Using Windows 10 Pro (Version 1511). Jenkins 2.1 with all plugin the latest version (5/5/2016). 
My workaround is to continue using Freestyle projects - but I was hoping to use the pipeline projects in order get a history of changes in GIT. 

Results (nunit2) saved as CalAgPermits.Maps.Web.UnitTests.xml Aborted by Andrew Coats Sending interrupt signal to process Click here to forcibly terminate running steps
 
The "click here to forcibly terminate running steps" does not seem to work.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [extended-choice-parameter-plugin] (JENKINS-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

2016-05-05 Thread vi...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil commented on  JENKINS-34524 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 
 
Try 0.70 of extended choice parameter plugin. It has the fix for this issue  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [hp-application-automation-tools-plugin] (JENKINS-33410) Honor Reporter.Filter setting in QC

2016-05-05 Thread xu-liang.ku...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kuang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33410 
 
 
 
  Honor Reporter.Filter setting in QC  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kuang 
 
 
 
 
 
 
 
 
 
 When UFT runs a test and returns a value for Err.Number that is non-zero, a setting of "Reporter.Filter=rfDisableAll" can be set within ALM to not log this error. However, the non-zero value still causes a failure to be logged in Jenkins.  #  It would be useful to have HPToolsRunner honor this same setting, and only report a failure to Jenkins when this property isn't set.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [hp-application-automation-tools-plugin] (JENKINS-33410) Honor Reporter.Filter setting in QC

2016-05-05 Thread xu-liang.ku...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kuang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33410 
 
 
 
  Honor Reporter.Filter setting in QC  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kuang 
 
 
 
 
 
 
 
 
 
 When UFT runs a test and returns a value for Err.Number that is non-zero, a setting of "Reporter.Filter=rfDisableAll" can be set within ALM to not log this error. However, the non-zero value still causes a failure to be logged in Jenkins.  # It would be useful to have HPToolsRunner honor this same setting, and only report a failure to Jenkins when this property isn't set.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

2016-05-05 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Sonneveld commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
Another workaround that doesn't involved deleting jobs (but isn't a long term solution) is to realise that batch steps create two batch files in the @tmp directory (which is relative to where batch is run, so it might be in the workspace if you've changed the directory, or just outside it): a jenkins-main.bat and a jenkins-wrap.bat. The main bat file contains your commands. The wrap bat file will run the main bat, pipe output to a log file and finally writes a result file. 
The bug concerns the wrap bat file not completing so the result file is never written. You can search for the file and run the final line manually (looks like echo %errorlevel% > ...\jenkins-result.txt), or run the wrap batch file again if you don't mind it performing the same operation again. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

2016-05-05 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Sonneveld edited a comment on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 Another workaround that doesn't  involved  involve  deleting jobs (but  also  isn't a long term solution) is to realise that batch steps create two batch files in the @tmp directory (which is relative to where batch is run, so it might be in the workspace if you've changed the directory, or just outside it): a jenkins-main.bat and a jenkins-wrap.bat. The main bat file contains your commands. The wrap bat file will run the main bat, pipe output to a log file and finally writes a result file.The bug concerns the wrap bat file not completing so the result file is never written.  You can search for the file and run the final line manually (looks like echo %errorlevel% > ...\jenkins-result.txt), or run the wrap batch file again if you don't mind it performing the same operation again. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [git-plugin] (JENKINS-34631) times out with git 2.0

2016-05-05 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The plugin does not have any different handling of command line git 1.9 and command line git 2.0. Since you changed the command line git versions, I can only assume there is a different in command line git between those versions. 
The git plugin is actively tested with automation and with interactive tests for versions ranging from 1.7.1 through 2.8.2. I'm confident this is not a plugin issue. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34631 
 
 
 
  times out with git 2.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1

2016-05-05 Thread pe...@bruin.sg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 uncletall commented on  JENKINS-31712 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use SCM from another project is removed after upgrading to 1.5.1  
 
 
 
 
 
 
 
 
 
 
I just noticed something. 
The SCM template job I have created also injects some environment variables into the job and has a simple script. Hence I have the job twice in the job config. 1. Use SCM from other another project, to setup the SCM 2. Use builders from other project (use all builders from this project), to configure some environment variables and run the script. 
For some projects I did not use the second option, for those projects the Use SCM from another project was not removed. For the jobs where I configured both, the Use SCM from another project was removed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-05-05 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tony Wallace edited a comment on  JENKINS-34637 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: pipeline DSL: timeout() does not work if withEnv() is enclosed  
 
 
 
 
 
 
 
 
 
 This  pipeline DSL  works as expected: ie, the "sleep" is interrupted at 20 seconds, the timeout exception is caught, the build ends  {{Timeout has been exceeded}}  . {noformat}def err = nulltry{timeout(time:20, unit:'SECONDS') {node('chapcs00-ptmp') {sh '''#!/bin/bash -exsleep 60'''}}} catch( caughtError ) {println 'catch'err = caughtError} finally {println 'finally'if(err) {throw err}}console output:Started by user Tony Wallace[Pipeline] timeout[Pipeline] {[Pipeline] nodeRunning on chapcs00-ptmp in /ptmp/jenkins/chapel-ci/chapcs00-ptmp/workspace/Z-timeout[Pipeline] {[Pipeline] sh[Z-timeout] Running shell script+ sleep 60Sending interrupt signal to process/ptmp/jenkins/chapel-ci/chapcs00-ptmp/workspace/Z-timeout@tmp/durable-28979ffb/script.sh: line 2: 90895 Terminated  sleep 60[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // timeout[Pipeline] echocatch[Pipeline] echofinally[Pipeline] End of PipelineTimeout has been exceededFinished: ABORTED{noformat}This  DSL script  does  *  not *  work as expected: the sleep runs all the way to 60 seconds. THEN the build ends the same way,  {{Timeout has been exceeded}},  except timeout did not actually interrupt anything.    {noformat}def err = nulltry{timeout(time:20, unit:'SECONDS') {node('chapcs00-ptmp') {withEnv(['BLAH=foo',]) {sh '''#!/bin/bash -exsleep 60: should not be here'''}}}} catch( caughtError ) {println 'catch'err = caughtError} finally {println 'finally'if(err) {throw err}}console output:Started by user Tony Wallace[Pipeline] timeout[Pipeline] {[Pipeline] nodeRunning on chapcs00-ptmp in /ptmp/jenkins/chapel-ci/chapcs00-ptmp/workspace/Z-timeout[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] sh[Z-timeout] Running shell script+ sleep 60+ : should not be here[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // timeout[Pipeline] echocatch[Pipeline] echofinally[Pipeline] End of PipelineTimeout has been exceededFinished: ABORTED{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  

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

2016-05-05 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tony Wallace updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34637 
 
 
 
  pipeline DSL: timeout() does not work if withEnv() is enclosed  
 
 
 
 
 
 
 
 
 
 
configuration details attached. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Tony Wallace 
 
 
 

Attachment:
 
 jenkins.txt 
 
 
 

Attachment:
 
 linux.txt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-05-05 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tony Wallace updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34637 
 
 
 
  pipeline DSL: timeout() does not work if withEnv() is enclosed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tony Wallace 
 
 
 
 
 
 
 
 
 
 Pipeline/ workflow DSL: timeout() does not work as expected when a withEnv() is introduced inside the (same) timeout + node blocks and over the (same) shell command. Specifically, without the withEnv block, the timeout actually interrupts the shell command. With the withEnv block, the timeout does not interrupt the shell command; yet, the build still ends reporting that it was interrupted/ aborted.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-05-05 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tony Wallace commented on  JENKINS-34637 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: pipeline DSL: timeout() does not work if withEnv() is enclosed  
 
 
 
 
 
 
 
 
 
 
The only difference between scripts with right and wrong behavior is 

 
withEnv(['BLAH=foo',]) {  } 

 
was added around the previous shell script 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-05-05 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tony Wallace commented on  JENKINS-34637 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: pipeline DSL: timeout() does not work if withEnv() is enclosed  
 
 
 
 
 
 
 
 
 
 
This works as expected: ie, the "sleep" is interrupted at 20 seconds, the timeout exception is caught, the build ends .  

 
def err = null
try{
timeout(time:20, unit:'SECONDS') {
node('chapcs00-ptmp') {
sh '''#!/bin/bash -ex
sleep 60
'''
}
}
} catch( caughtError ) {
println 'catch'
err = caughtError
} finally {
println 'finally'
if(err) {
throw err
}
}

console output:

Started by user Tony Wallace
[Pipeline] timeout
[Pipeline] {
[Pipeline] node
Running on chapcs00-ptmp in /ptmp/jenkins/chapel-ci/chapcs00-ptmp/workspace/Z-timeout
[Pipeline] {
[Pipeline] sh
[Z-timeout] Running shell script
+ sleep 60
Sending interrupt signal to process
/ptmp/jenkins/chapel-ci/chapcs00-ptmp/workspace/Z-timeout@tmp/durable-28979ffb/script.sh: line 2: 90895 Terminated  sleep 60
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timeout
[Pipeline] echo
catch
[Pipeline] echo
finally
[Pipeline] End of Pipeline
Timeout has been exceeded
Finished: ABORTED
 

 
This does not work as expected: the sleep runs all the way to 60 seconds. THEN the build ends the same way, except timeout did not actually interrupt anything.  

 
def err = null
try{
timeout(time:20, unit:'SECONDS') {
node('chapcs00-ptmp') {
withEnv(['BLAH=foo',]) {
sh '''#!/bin/bash -ex
sleep 60
: should not be here
'''
}
}
}
} catch( caughtError ) {
println 'catch'
err = caughtError
} finally {
println 'finally'
if(err) {
throw err
}
}

console output:

Started by user Tony Wallace
[Pipeline] timeout
[Pipeline] {
[Pipeline] node
Running on chapcs00-ptmp in /ptmp/jenkins/chapel-ci/chapcs00-ptmp/workspace/Z-timeout
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
[Z-timeout] Running shell script
+ sleep 60
+ : should not be here
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timeout
[Pipeline] echo
catch
[Pipeline] echo
finally
[Pipeline] End of Pipeline
Timeout has been exceeded
Finished: ABORTED
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
   

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

2016-05-05 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tony Wallace created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34637 
 
 
 
  pipeline DSL: timeout() does not work if withEnv() is enclosed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/May/06 12:28 AM 
 
 
 

Environment:
 

 Jenkins 1.651.1, up-to-date pipeline and workflow plugins (list attached), IBM JRE 1.7.0, Linux 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Tony Wallace 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 

[JIRA] [workflow-plugin] (JENKINS-28718) withTool

2016-05-05 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-28718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: withTool  
 
 
 
 
 
 
 
 
 
 
Ooo, nifty stuff - wanna write a blog post about your shared stuff? =) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-28718) withTool

2016-05-05 Thread mike.doughe...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Dougherty commented on  JENKINS-28718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: withTool  
 
 
 
 
 
 
 
 
 
 
I've implemented a `withTool` function that we're using at Docker. It's available to our Jenkins instances via the workflow-cps-global-lib-plugin. You can see the implementation here: https://github.com/docker/jenkins-pipeline-scripts/blob/master/vars/withTool.groovy 
I'm sure it's not perfect, but it works well so far. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-16255) Jenkins doesn't handle system wide environment variables which exist in different cases

2016-05-05 Thread rob...@hetzler.ca (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Hetzler commented on  JENKINS-16255 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins doesn't handle system wide environment variables which exist in different cases  
 
 
 
 
 
 
 
 
 
 
Re-raising. this is a problem in jenkins 2.0 as well 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [support-core-plugin] (JENKINS-34636) Get tomcat logs

2016-05-05 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34636 
 
 
 
  Get tomcat logs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Steven Christou 
 
 
 

Components:
 

 support-core-plugin 
 
 
 

Created:
 

 2016/May/05 10:26 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Steven Christou 
 
 
 
 
 
 
 
 
 
 
It would be nice for the support core plugin to request adding the catalina.log files if it is in a tomcat container. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
  

[JIRA] [warnings-plugin] (JENKINS-34635) Configuration of trend graph does use wrong URL

2016-05-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34635 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configuration of trend graph does use wrong URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/3cacc70e58fef4c16c5f62227aed6715b284bbb5 Log: JENKINS-34635 Skip should_store_trend_selection_in_cookie for warnings plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove dependencies with external static resources

2016-05-05 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34628 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove dependencies with external static resources  
 
 
 
 
 
 
 
 
 
 
Agree, we shouldn't do this. Jenkins must be able to work equally well offline (there could be update sites on the local network, which make internet access for even that unnecessary). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [warnings-plugin] (JENKINS-34635) Configuration of trend graph does use wrong URL

2016-05-05 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34635 
 
 
 
  Configuration of trend graph does use wrong URL  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ulli Hafner 
 
 
 

Components:
 

 warnings-plugin 
 
 
 

Created:
 

 2016/May/05 10:12 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ulli Hafner 
 
 
 
 
 
 
 
 
 
 
The configuration of trend graphs using a cookie does not work for the warnings plug-in: the URL is the parser URL and not the plug-in URL.  
See https://github.com/jenkinsci/acceptance-test-harness/commit/b3691320192217d8a2d5e7e60e65119f3b13ea7f 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 

[JIRA] [powershell-plugin] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin

2016-05-05 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-34581 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Please add support for Pipelines to the Powershell plugin  
 
 
 
 
 
 
 
 
 
 
It'd be really great to get real Pipeline integration, a la sh and bat - i.e., a DurableTaskStep implementation for Powershell. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [powershell-plugin] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin

2016-05-05 Thread pw...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34581 
 
 
 
  Please add support for Pipelines to the Powershell plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Wolf 
 
 
 

Labels:
 
 microsoft pipeline powershell windows  workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-34633) ansible-plugin with pipeline groovy multiple misbehaviours

2016-05-05 Thread m...@devopsent.biz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Max Kovgan commented on  JENKINS-34633 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ansible-plugin with pipeline groovy multiple misbehaviours  
 
 
 
 
 
 
 
 
 
 
This could be the problem with issue 2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-34360) Adding Job DSL support of Parameter Filter for Copy Artifact Plugin

2016-05-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34360 
 
 
 
  Adding Job DSL support of Parameter Filter for Copy Artifact Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-34360) Adding Job DSL support of Parameter Filter for Copy Artifact Plugin

2016-05-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34360 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Adding Job DSL support of Parameter Filter for Copy Artifact Plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/8c49dcd6c7ebf74eea5592c4728dc608bb0b3621 Log: Merge branch 'copyArtifactsParameterFilters' 
[FIXES JENKINS-34360] 
Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/b52d0d07cd5c...8c49dcd6c7eb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [acceptance-test-harness] (JENKINS-34634) ATH CreateTestSlave.newSlave fails

2016-05-05 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34634 
 
 
 
  ATH CreateTestSlave.newSlave fails  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/05 9:36 PM 
 
 
 

Environment:
 

 core 1.651.1 or 2.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
Getting the error message  

 

Unable to locate By.cssSelector: #credentials-add-submit-button in http://127.0.0.1:61819/computer/createItem
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
   

[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

2016-05-05 Thread maal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 maaltan natlaam commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
I found a workaround (better than reinstalling at least). 
1. Shutdown jenkins service 2. go to /jobs// and delete the  folder. 3. Restart jenkins. 
There is probably a flag somewhere in that folder you can set to prevent the job from "restarting" after restart. 
Since ive hit this bug about 80% of the runs I've tried so far. this workaround is unusable in any kind of production environment. At least you can run the job again though. I guess another workaround would be allow multiple instances of the job to run and clean up the zombies once a day or something? 
Also, it seems this happens more when i view the console output via jenkins ui while the job is running.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [notification-plugin] (JENKINS-32270) Use the jenkins proxy configuration for the http protocol

2016-05-05 Thread mcroo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mcrooney commented on  JENKINS-32270 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use the jenkins proxy configuration for the http protocol  
 
 
 
 
 
 
 
 
 
 
Thanks for the PR! I've pinged one of the maintainers in it to see if it can be merged  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [notification-plugin] (JENKINS-32270) Use the jenkins proxy configuration for the http protocol

2016-05-05 Thread mcroo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mcrooney edited a comment on  JENKINS-32270 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use the jenkins proxy configuration for the http protocol  
 
 
 
 
 
 
 
 
 
 Thanks for the PR! I've pinged one of the maintainers in it to see if it can be merged :)  https://github.com/jenkinsci/notification-plugin/pull/24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-31611) Unprivileged user may access plugin uninstall form

2016-05-05 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck started work on  JENKINS-31611 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)

2016-05-05 Thread petrikvanderve...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Petrik van der Velde commented on  JENKINS-26420 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)  
 
 
 
 
 
 
 
 
 
 
Ok so version of TFS2015.1 does indeed pass the branches parameter, however this only partially resolves the issue. I still think there is an issue with the GIT plugin.  
When a tag is pushed to the repository a push notification is send to jenkins as well. Because tags aren't related to a given branch only the SHA is send, thus leading back to the problem I discussed above, being that all builds for that repository are triggered regardless of the fact that the build configuration is relevant for that tag. That then leads to many failing builds. 
I think the correct solution(s) would be to either ignore notifications without a branches parameter IF the user has configured the job to look at a specific branch (or set of branches) OR to give the user a configuration option to ignore notifications without the branches parameter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [branch-api-plugin] (JENKINS-33819) Inability to control orphaned item strategy on multibranch children of an organization folder

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto started work on  JENKINS-33819 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [branch-api-plugin] (JENKINS-33819) Inability to control orphaned item strategy on multibranch children of an organization folder

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33819 
 
 
 
  Inability to control orphaned item strategy on multibranch children of an organization folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 stephenconnolly Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-34633) ansible-plugin with pipeline groovy multiple misbehaviours

2016-05-05 Thread m...@devopsent.biz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Max Kovgan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34633 
 
 
 
  ansible-plugin with pipeline groovy multiple misbehaviours  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jean-Christophe Sirot 
 
 
 

Components:
 

 ansible-plugin 
 
 
 

Created:
 

 2016/May/05 9:21 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Max Kovgan 
 
 
 
 
 
 
 
 
 
 
environment 
 

server side: 
 

Jenkins 2.1, pipeline plugin: 2.1, ansible 2.0
 

Java: oracle jdk8: build 1.8.0_91-b14
 

os: Ubuntu 14.04.4 LTS
 
 
 

client side: 
 

Google chrome Version 50.0.2661.94 (64-bit)
 

   

[JIRA] [swarm-plugin] (JENKINS-20668) Persist Jenkins swarm slaves when they go offline

2016-05-05 Thread jacob.kel...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Keller commented on  JENKINS-20668 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Persist Jenkins swarm slaves when they go offline  
 
 
 
 
 
 
 
 
 
 
Another issue I have is similar. 
Say a slave is for some label "node" and goes offline. If no other slave has the label "node" then that label isn't remembered by the Jenkins system. Thus, when a job is edited and saved, it removes the label from the configuration permanently (as it doesn't exist according to the master). This happens for example with a matrix job. 
This is a problem if someone happens to edit a job during a window when a slave is offline, and results in a hidden loss of running on that slave in the matrix job builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-05 Thread zxi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thanh Ha commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
2.5 throws the expected error message now: 
Connection not validated, plugin might not operate correctly: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 
I think we can resolve this bug. Thanks for the quick response and support! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ec2-plugin] (JENKINS-34632) Associate Public IP address button also tried to connect as Public IP

2016-05-05 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34632 
 
 
 
  Associate Public IP address button also tried to connect as Public IP  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Francis Upton 
 
 
 

Components:
 

 ec2-plugin 
 
 
 

Created:
 

 2016/May/05 8:54 PM 
 
 
 

Environment:
 

 Jenkins 2.1, Windows Server 2012R2, EC2 version 1.31 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 
I have checked off the "Associate with Public IP address" button but left the "Connect using Public IP" unchecked.  
Upon doing so, i noticed that in my node log that it was trying to connect using the public IP address even thought the button for that was unchecked. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 

[JIRA] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel

2016-05-05 Thread krish3...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sivakrishna thumati commented on  JENKINS-6817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel  
 
 
 
 
 
 
 
 
 
 
Any resolution for connection timeout issues ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant

2016-05-05 Thread krachyn...@ice-edge.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ken Rachynski commented on  JENKINS-33712 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty parameterized build properties not quoted when passed to ant  
 
 
 
 
 
 
 
 
 
 
I just encountered this bug this week after upgrading my LTS installation to 1.651.1. Rolling back to LTS 1.642.4 fixed the issue for me, but LTS is supposed to be stable, eh? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [extended-choice-parameter-plugin] (JENKINS-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

2016-05-05 Thread mi...@mikey.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 michael pechner commented on  JENKINS-34524 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 
 
down graded to 1.17 - all good. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [git-plugin] (JENKINS-34631) times out with git 2.0

2016-05-05 Thread miguel_f_am...@homedepot.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Miguel Amaro created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34631 
 
 
 
  times out with git 2.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 2016/May/05 8:20 PM 
 
 
 

Environment:
 

 Jenkins 2.1; git-plugin 2.4.4 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Miguel Amaro 
 
 
 
 
 
 
 
 
 
 
I have multiple environments that'll time out at the step listed below. I uninstalled git 2.0 and installed git 1.9.5. With no changes in the Jenkins job, jenkins worked sucessfully. git.exe -c core.askpass=true fetch --tags --progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
   

[JIRA] [extended-choice-parameter-plugin] (JENKINS-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

2016-05-05 Thread mi...@mikey.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 michael pechner commented on  JENKINS-34524 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 
 
Same for me. Windows version 1.651.1, down graded to the 1.18 version and rebooted and remove the XML. Re-approved. 
Still has the message. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34629) Address some NPM warnings

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto started work on  JENKINS-34629 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [accelerated-build-now-plugin] (JENKINS-34630) cant get around stack trace errors

2016-05-05 Thread dtha...@lccc.edu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Donald thaler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34630 
 
 
 
  cant get around stack trace errors  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Anthony Dahanne 
 
 
 

Components:
 

 accelerated-build-now-plugin 
 
 
 

Created:
 

 2016/May/05 7:59 PM 
 
 
 

Environment:
 

 jenkins 1.645 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Donald thaler 
 
 
 
 
 
 
 
 
 
 
coinfigured global security,selected anyone can do anything in the security realm,select matrix-based security, defined permissions for admin user, selected add, save. now when i click on the url to access the jenkins console i immediately get a stack trace error. 
restarted jenkins. entered url in browser (http://banesm.lccc.edu:8080) and get tje stack trace error  
how do i get around this ??? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

[JIRA] [core] (JENKINS-34629) Address some NPM warnings

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34629 
 
 
 
  Address some NPM warnings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Labels:
 
 npm 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34629) Address some NPM warnings

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34629 
 
 
 
  Address some NPM warnings  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/05 7:43 PM 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 

[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Jenkins war 2.2-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- frontend-maven-plugin:1.0:npm (default-cli) @ jenkins-war ---
[INFO] Running 'npm install' in /Users/recena/Development/projects/jenkins/war
[WARNING] npm WARN package.json jenkins-ui@1.0.0 No repository field.
[WARNING] npm WARN package.json jenkins-ui@1.0.0 No README data
[INFO] sticky-kit@1.1.3 node_modules/sticky-kit
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 3.196 s
[INFO] Finished at: 2016-05-05T21:39:40+02:00
[INFO] Final Memory: 10M/309M
[INFO] 

Process finished with exit code 0
 

 
These NPM warnings should be addressed. 
 
 
 

[JIRA] [git-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option

2016-05-05 Thread daldo...@grnoc.iu.edu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Doyle commented on  JENKINS-31939 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The top value is better to be chosed by default of to have such option  
 
 
 
 
 
 
 
 
 
 
We upgraded a few things and this unknowingly broke behavior in our build infrastructure. We were using a Branch selector in a few projects as an optional field to control later behavior, but now it is always set and there does not appear to be a way to deselect it when doing a manual build through the UI. 
It would be really nice if there was a setting to control this behavior. For now we have downgraded to 0.4.0 to fix our issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [extended-choice-parameter-plugin] (JENKINS-34478) JSON-editor with File-Upload causes "Argument list too long" fatal error

2016-05-05 Thread vi...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
marking this as fixed in version 0.65 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34478 
 
 
 
  JSON-editor with File-Upload causes "Argument list too long" fatal error  
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [extended-choice-parameter-plugin] (JENKINS-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

2016-05-05 Thread vi...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
fixed in version 0.70 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34524 
 
 
 
  Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove external static resources

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34628 
 
 
 
  Remove external static resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Issue Type:
 
 Bug Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove dependencies with external static resources

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34628 
 
 
 
  Remove dependencies with external static resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 Remove  dependencies with  external static resources 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove external static resources

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-34628 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove external static resources  
 
 
 
 
 
 
 
 
 
 
Keith Zantow What do you think? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove external static resources

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34628 
 
 
 
  Remove external static resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 There are dependencies with external resources in runtime. You can find an example like this:{code}    @import url(https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css);  @import url(https://fonts.googleapis.com/css?family=Roboto:400,300,500,900,700);{code}in {{core/src/main/resources/jenkins/install/SetupWizard/setupWizardFirstUser.jelly}}.# Remove CSS inline in Jelly file if it is possible.# Remove duplicated refereces: [here|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/install/SetupWizard/setupWizardFirstUser.jelly#L7] and [here|https://github.com/jenkinsci/jenkins/blob/master/war/src/main/less/pluginSetupWizard.less#L1] This does more difficult a real environment without direct internet connection (offline mode). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove external static resources

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34628 
 
 
 
  Remove external static resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 There are dependencies with external resources in runtime. You can find an example like this:{code}    @import url(https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css);  @import url(https://fonts.googleapis.com/css?family=Roboto:400,300,500,900,700);{code}in {{core/src/main/resources/jenkins/install/SetupWizard/setupWizardFirstUser.jelly}}.# Remove CSS inline in Jelly file if it is possible.# Remove duplicated refereces: [here|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/install/SetupWizard/setupWizardFirstUser.jelly#L7] and [here|https://github.com/jenkinsci/jenkins/blob/master/war/src/main/less/pluginSetupWizard.less#L1] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34628) Remove external static resources

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34628 
 
 
 
  Remove external static resources  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/05 7:06 PM 
 
 
 

Labels:
 

 ui 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  

[JIRA] [cli] (JENKINS-18114) Enabling crumb issuer prevents CLI from working

2016-05-05 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Daniel Beck 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-18114 
 
 
 
  Enabling crumb issuer prevents CLI from working  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Assignee:
 
 Daniel Beck 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-05 Thread ogon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
Nevermind, the 2.5 I have just released should report this as an error in while testing connection. Let me know if it does not. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-34627) It is impossible not to pass an inventory file

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34627 
 
 
 
  It is impossible not to pass an inventory file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jean-Christophe Sirot 
 
 
 

Components:
 

 ansible-plugin 
 
 
 

Created:
 

 2016/May/05 6:37 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jean-Christophe Sirot 
 
 
 
 
 
 
 
 
 
 
Once selected, it is not possible to unselect the inventory file. But this is not a mandatory parameter to pass to ansible-playbook. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message 

[JIRA] [ansible-plugin] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
fixed in version 0.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29284 
 
 
 
  Build variables are not available during the ansible-playbook execution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jean-Christophe Sirot 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32950) Jenkins slave resets connection during or just after artifacts download.

2016-05-05 Thread mlandma...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 boris ivan commented on  JENKINS-32950 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins slave resets connection during or just after artifacts download.  
 
 
 
 
 
 
 
 
 
 
I have seen the same problem for years. I typically see this at the end of a build when doing a maven site site:deploy. My guess is that something about the rapid transfer of small files to build the resultant website is preventing some sort of keepalive from working, or tripping some kind of integrity check.  
Same stack trace on windows slave, etc. Always: 
May 04, 2016 10:17:36 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel channel java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) ... ... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29284 
 
 
 
  Build variables are not available during the ansible-playbook execution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jean-Christophe Sirot 
 
 
 

Summary:
 
 Build variables are not available during the ansible- palybook playbook  execution 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-33787) openstack.py dynamic inventory

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-33787 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: openstack.py dynamic inventory  
 
 
 
 
 
 
 
 
 
 
Govindaraj Venkatesan Is the dynamic inventory file openstack.py executable for the jenkins user? If the file does not have the executable flag, ansible tries to read it as a regular inventory. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-33787) openstack.py dynamic inventory

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-33787 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: openstack.py dynamic inventory  
 
 
 
 
 
 
 
 
 
 
Sorry for the late reply. I'm going to investigate your issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-32911) Console output hangs during a playbook execution in a pipeline job

2016-05-05 Thread jean-christophe.si...@cryptolog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in version 0.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32911 
 
 
 
  Console output hangs during a playbook execution in a pipeline job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jean-Christophe Sirot 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-29863) Unable to use masked passwords when passing in extra-vars

2016-05-05 Thread jean-christophe.si...@cryptolog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in ansible-plugin 0.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29863 
 
 
 
  Unable to use masked passwords when passing in extra-vars  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jean-Christophe Sirot 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

2016-05-05 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart edited a comment on  JENKINS-34610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 
 *Ok long story short, for those following along, yes,  i got this to work.*1. You have to follow  those  GP  GPedit.msc  settings  i set earlier along with using Administrator (Has  mentioned above and in the first two sceenshots.2. You have  to  be  use  the  Administrator  user , nothing else works even if they have  'Administrator' by name. You can't use an  administrative  rights, this works*  user of a different name. Got it working. Yay. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

2016-05-05 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 
 
Ok long story short, for those following along, yes, those GP settings i set earlier along with using Administrator (Has to be the Administrator user, nothing else works even if they have administrative rights, this works 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [p4-plugin] (JENKINS-33734) P4 Plugin does not reload UI configuration using the Pipeline Workflow

2016-05-05 Thread cnick...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 C.Nicklaw assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33734 
 
 
 
  P4 Plugin does not reload UI configuration using the Pipeline Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 C.Nicklaw 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ansible-plugin] (JENKINS-29863) Unable to use masked passwords when passing in extra-vars

2016-05-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29863 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use masked passwords when passing in extra-vars  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jean-Christophe Sirot Path: pom.xml src/main/java/org/jenkinsci/plugins/ansible/AbstractAnsibleInvocation.java src/main/java/org/jenkinsci/plugins/ansible/AnsibleAdHocCommandBuilder.java src/main/java/org/jenkinsci/plugins/ansible/AnsibleAdHocCommandInvocation.java src/main/java/org/jenkinsci/plugins/ansible/AnsiblePlaybookBuilder.java src/main/java/org/jenkinsci/plugins/ansible/AnsiblePlaybookInvocation.java src/main/java/org/jenkinsci/plugins/ansible/ExtraVar.java src/main/java/org/jenkinsci/plugins/ansible/workflow/AnsiblePlaybookStep.java src/main/resources/org/jenkinsci/plugins/ansible/AnsibleAdHocCommandBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/ansible/AnsiblePlaybookBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/ansible/workflow/AnsiblePlaybookStep/config.jelly http://jenkins-ci.org/commit/ansible-plugin/b8fc86d508104d494abf99bff125492a193668e1 Log: JENKINS-29863 Add dedicated support for extra variables in build widget and pipeline 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-pipeline-plugin] (JENKINS-33935) Can't rerun a build

2016-05-05 Thread peter.k...@thomsonreuters.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Kain commented on  JENKINS-33935 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't rerun a build  
 
 
 
 
 
 
 
 
 
 
I've come across this same issue after upgrading Jenkins and the plugin to the described versions (Jenkins 1.655, build-pipeline-plugin 1.5.2). Is there any update here? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [nodejs-plugin] (JENKINS-34626) NodeJS menu not showing on Jenkins 2.0/2.1 config page

2016-05-05 Thread jason.ge...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Gerry commented on  JENKINS-34626 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NodeJS menu not showing on Jenkins 2.0/2.1 config page  
 
 
 
 
 
 
 
 
 
 
My bad - the config is now under Global Tools. Apologies!  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [junit-plugin] (JENKINS-9980) Add the "Publish JUnit test result report" option to maven job configuration page

2016-05-05 Thread zdavid...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach David commented on  JENKINS-9980 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the "Publish JUnit test result report" option to maven job configuration page  
 
 
 
 
 
 
 
 
 
 
Matei Dragu -  
Answers to your questions per my understanding: 
A maven job should publish JUnit test result report automatically. This only needs to be configured if it is a freestyle job Artifact Publisher plugin should solve the publishing issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [nodejs-plugin] (JENKINS-34626) NodeJS menu not showing on Jenkins 2.0/2.1 config page

2016-05-05 Thread jason.ge...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Gerry closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34626 
 
 
 
  NodeJS menu not showing on Jenkins 2.0/2.1 config page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Gerry 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [nodejs-plugin] (JENKINS-34626) NodeJS menu not showing on Jenkins 2.0/2.1 config page

2016-05-05 Thread jason.ge...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Gerry created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34626 
 
 
 
  NodeJS menu not showing on Jenkins 2.0/2.1 config page  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 nodejs-plugin 
 
 
 

Created:
 

 2016/May/05 4:26 PM 
 
 
 

Environment:
 

 Amazon Linux 2016.03  openjdk version "1.8.0_91"  Jenkins 2.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jason Gerry 
 
 
 
 
 
 
 
 
 
 
I'm doing some testing on upgrading from Jenkins 1.642.4 to Jenkins 2.0/2.1. I'm seeing the same issue on both 2.0 and 2.1: the NodeJS menu doesn't appear on the global config page.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[JIRA] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

2016-05-05 Thread chrisen...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Engel edited a comment on  JENKINS-29652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin  
 
 
 
 
 
 
 
 
 
 I made a quick hack to resolve the issue.  This appears to work for me but I haven't verified it will work in all cases.  But with this patch I'm able to retrigger a failed build and on success the expected join job will be run as I would expect.  Added as attachment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

2016-05-05 Thread chrisen...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Engel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29652 
 
 
 
  Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin  
 
 
 
 
 
 
 
 
 
 
I made a quick hack to resolve the issue. This appears to work for me but I haven't verified it will work in all cases. But with this patch I'm able to retrigger a failed build and on success the expected join job will be run as I would expect. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Engel 
 
 
 

Attachment:
 
 0001-Join-plugin-fix-to-allow-retry-on-failure.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [coverity-plugin] (JENKINS-33560) Coverity plugin no longer wraps SCM tool-arg in quotes

2016-05-05 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran commented on  JENKINS-33560 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Coverity plugin no longer wraps SCM tool-arg in quotes  
 
 
 
 
 
 
 
 
 
 
we also are stuck at 1.5 for a long time 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-34455) Provide easy access to current commit ID in Jenkinsfile

2016-05-05 Thread zimb...@zimbatm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zimba tm commented on  JENKINS-34455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provide easy access to current commit ID in Jenkinsfile  
 
 
 
 
 
 
 
 
 
 
I have a less than ideal workaround: 

 

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


sh "git rev-parse --short HEAD > .git/commit-id"
commit_id = readFile('.git/commit-id')
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-34455) Provide easy access to current commit ID in Jenkinsfile

2016-05-05 Thread zimb...@zimbatm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zimba tm edited a comment on  JENKINS-34455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provide easy access to current commit ID in Jenkinsfile  
 
 
 
 
 
 
 
 
 
 I have a less than ideal workaround:{code: groovy none }sh "git rev-parse --short HEAD > .git/commit-id"commit_id = readFile('.git/commit-id'){code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34594) Login page should be stylized

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-34594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Login page should be stylized  
 
 
 
 
 
 
 
 
 
 
Keith Zantow, perfect. I'll do it soon. Your feedback would be great when my PR is ready. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34594) Login page should be stylized

2016-05-05 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34594 
 
 
 
  Login page should be stylized  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ant-plugin] (JENKINS-34325) Ant plugin regression between release 1.642.4 ant 1.651.1

2016-05-05 Thread afernan...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Armando Fernandez commented on  JENKINS-34325 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ant plugin regression between release 1.642.4 ant 1.651.1  
 
 
 
 
 
 
 
 
 
 
I was able to reproduce this on Windows and after some investigation, noticed that there is already a PR for this. Also, this ticket is duplicated by JENKINS-33712 so I guess this can be closed. I will leave that up to the maintainer. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

2016-05-05 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 
 
Never mind. It's somehow come back. There is something at play here that i can't locate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-05 Thread zxi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thanh Ha updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34578 
 
 
 
  Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
I'm not sure I understood what you're looking for but attached is a full stacktrace of running the 3 println commands. Let me know if you wanted me to do something else. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Thanh Ha 
 
 
 

Attachment:
 
 script.log 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudbees-folder-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute

2016-05-05 Thread docw...@gerf.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Höltje commented on  JENKINS-34458 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 
 
I'm pretty sure that trigger is for rebuilding the Folder itself, not the project. The project uses the webhook. The folder is set to update itself (rescan Github organizations) once a day if it hasn't run already in the last 24 hours. That  is for once a day and  is 24 * 60 * 60 * 1000 or 24 hours in milliseconds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34594) Login page should be stylized

2016-05-05 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow commented on  JENKINS-34594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Login page should be stylized  
 
 
 
 
 
 
 
 
 
 
Manuel Jesús Recena Soto Yes, a new style for this page would be great. I'd probably just apply the bootstrap form styles to the inputs, as you said similar to the setup wizard. You just need to include the right css file and add a few classes, mostly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

2016-05-05 Thread ttt43...@126.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wilson Tian edited a comment on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 I encounter this issue too. I'm running a maven job using {code: groovy java }bat "${mavenHome}\\bin\\mvn clean package"{code}. But the job always hangs at last and never exits.Is there any workaround? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

2016-05-05 Thread ttt43...@126.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wilson Tian commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
I encounter this issue too. I'm running a maven job using  

 

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

bat "${mavenHome}\\bin\\mvn clean package" 

 
. But the job always hangs at last and never exits. Is there any workaround? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-05 Thread ogon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
That does no matter the "Test connection" does not work. You can still save it and give it a try. I have the fix prepared but trying to be sure it does what is necessary. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-23862) when viewing console output, way too much screen real estate wasted

2016-05-05 Thread mlandma...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 boris ivan commented on  JENKINS-23862 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: when viewing console output, way too much screen real estate wasted  
 
 
 
 
 
 
 
 
 
 
Any chance this can get prioritized? The wasted space is killing me. It's causing a majority of lines to wrap that would otherwise not wrap, more difficult to read. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-05 Thread zxi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thanh Ha commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
I'm not able to get the first cloud configured because of this problem so running the above script throws a missing property exception. 
groovy.lang.MissingPropertyException: No such property: openstack for class: jenkins.plugins.jclouds.compute.JCloudsCloud 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-34573) Running out of Heap Memory (2048m)

2016-05-05 Thread alexandrby...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandr Bykov commented on  JENKINS-34573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 
 
I have same issue with Jenkins 2.1 after update from 1.656. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

2016-05-05 Thread maal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 maaltan natlaam commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
I have this issue also. my batch invocation is: 
 bat ''' call %BUILD_CONFIG_PATH%setenv.cmd perl  ''' 
This has broken the job completely. I cannot terminate the job, nor can i start another (this is an incremental build with a fixed workspace location so i dont want to run concurrently). If i restart jenkins the job restarts and immediately hangs again. 
Are there any workaround short of full uninstall/reinstall of jenkins to recover this job setup? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [maven-plugin] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful

2016-05-05 Thread jtsw...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Sweet updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21330 
 
 
 
  java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful  
 
 
 
 
 
 
 
 
 

Change By:
 
 James Sweet 
 
 
 

Labels:
 
 robustness 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [selenium-plugin] (JENKINS-34625) Selenium plugin kills connection to slaves on jenkins restart

2016-05-05 Thread d...@djjohnjoseph.co.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Joseph created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34625 
 
 
 
  Selenium plugin kills connection to slaves on jenkins restart  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 selenium-plugin 
 
 
 

Created:
 

 2016/May/05 1:12 PM 
 
 
 

Environment:
 

 Jenkins 2.1  Selenium Plugin 2.53  Slave to Master Access Control DISABLED  Windows Server 2012 Box  Java 8 Update 91 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 John Joseph 
 
 
 
 
 
 
 
 
 
 
I'm getting the following in my log file when jenkins starts up, after updating to 2.1 and the latest selenium plugin: 
A thread (TCP agent connection handler #1 with /IP_OF_SLAVE_MACHINE:52178/67) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:112) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown 

  1   2   >