[JIRA] [ansicolor-plugin] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp

2016-04-04 Thread alast...@d-silva.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alastair D'Silva created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34019 
 
 
 
  ANSIColor plugin leaks format onto next line's timestamp  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Steven G Brown 
 
 
 

Attachments:
 

 consolelog.png 
 
 
 

Components:
 

 ansicolor-plugin, timestamper-plugin 
 
 
 

Created:
 

 2016/Apr/05 5:54 AM 
 
 
 

Environment:
 

 Jenkins 1.650 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alastair D'Silva 
 
 
 
 
 
 
 
 
 
 
When used with timestamped console output, the formatting from one line sometimes (but not always) leaks over and colors the timestamp on the next line. 
 
 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU commented on  JENKINS-34012 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fail to automatically install JDK 1.8.0_77  
 
 
 
 
 
 
 
 
 
 
Not sure : exit code is not the same (Exit code=-80) and i don't have any slave node configured. I only use the master 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] [subversion-plugin] (JENKINS-34018) Detect SVN Branches/Tags in non-standard locations

2016-04-04 Thread naught...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 naught 101 created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34018 
 
 
 
  Detect SVN Branches/Tags in non-standard locations  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 subversion-plugin 
 
 
 

Created:
 

 2016/Apr/05 5:18 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 naught 101 
 
 
 
 
 
 
 
 
 
 
As noted here: http://stackoverflow.com/questions/35833635/jenkins-with-svn-branches-in-non-standard-locations, it is sometimes the case that branches are not located in a standard subversion repository layout. For example, our organisation uses `branches/Users//`. 
Is it at all possible to modify this subversion plugin so that it can detect branches at non-standard locations? If not, any other suggestions that would allow users to select their branches would be greatly appreciated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
  

[JIRA] [pipeline-stage-view-plugin] (JENKINS-33430) Stage view UI loses history when stages are changed

2016-04-04 Thread svano...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort commented on  JENKINS-33430 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stage view UI loses history when stages are changed  
 
 
 
 
 
 
 
 
 
 
Agreed this is useful - in the near future I will take a look and see what we can do; there are related pieces of code that need to be touched at the same time (around the UI rendering process), so it would be a logical pair to include. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [copyartifact-plugin] (JENKINS-34017) copyartifact dies with hudson.util.IOException2

2016-04-04 Thread j...@hoblitt.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Hoblitt commented on  JENKINS-34017 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: copyartifact dies with hudson.util.IOException2  
 
 
 
 
 
 
 
 
 
 
The same exception occurs under jenkins 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] [core] (JENKINS-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread grei...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gus reiber commented on  JENKINS-33955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 
 
Yeah, so my conclusion is that they have to be top aligned as they are now. Before when they were vertical middle, with tall controls, it was almost impossible to tell what the hell the icon even related to. With single line controls, align middle is better, but only slightly so. I thought I had tried to offset the top such that for single lines, even when the item was aligned top, it actually seemed centered. I will take another look, but the thing is that i don't have any metadata that tells me if this label or that icon is associated with a short or tall control. 
...thus I need some rules that work mostly well in the most cases. 
There are still some cases where the text vertical alignment is totally messed up. 
...anyway. I will take a look, but I am happy to say the alignment is much, much better now than it was. I don't think perfect is possible given the table hackery being used to render these guys. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [copyartifact-plugin] (JENKINS-34017) copyartifact dies with hudson.util.IOException2

2016-04-04 Thread j...@hoblitt.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Hoblitt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34017 
 
 
 
  copyartifact dies with hudson.util.IOException2  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 copyartifact-plugin 
 
 
 

Created:
 

 2016/Apr/05 3:38 AM 
 
 
 

Environment:
 

 jenkins 1.651  copyartifact 1.37 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Joshua Hoblitt 
 
 
 
 
 
 
 
 
 
 
Configurinig any job with the copyartifact-plugin causes a fatal exception when running a build. 

 

Started by user Joshua Hoblitt
[EnvInject] - Loading node environment variables.
Building remotely on jenkins-el6-1-febf2de4 (jenkins-el6-1 centos-6 swarm) in workspace /home/jenkins-slave/workspace/copy-test
FATAL: Failed to copy /var/lib/jenkins/jobs/run-rebuild/builds/5/archive/results/manifest.txt to /home/jenkins-slave/workspace/copy-test/results/manifest.txt
hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/run-rebuild/builds/5/archive/results/manifest.txt to /home/jenkins-slave/workspace/copy-test/results/manifest.txt
	at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:117)
	at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyAll(FingerprintingCopyMethod.java:67)
	at 

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

2016-04-04 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
While investigating, I didn't see any error show up consistently before missing the log statement. I didn't see this occur as often on 2.0 before clicking the "Install New Features". Luckily it doesn't seem to be disruptive to my Jenkins, so that's a plus. Trying to see if there's a problem after "Installing new features" or running it under heavy stress. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

2016-04-04 Thread dmwj...@isomedia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Douglas Wooster commented on  JENKINS-28492 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 
I'm not aware of any special ping setting on Master startup. How would I check? 
There's no special operands on the slave startup. Just -jnlpUrl pointing the Master. 
Looking at ChannelPinger.java, I think it executes on BOTH the slave and the master. See lines 88-104. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33937) setup wizard plugin selection - no links to wiki...

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33937 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: setup wizard plugin selection - no links to wiki...  
 
 
 
 
 
 
 
 
 
 
James Nord I'm not going to Jira-wrestle you over the type field. IMO, this is a brand new feature with no previous equivalent, so can't be a regression...and the initial implementation of the feature to display the plugin name works, but is lacking the very-useful nicety of providing a clickable link to the wiki...making it a very worthy improvement. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33955 
 
 
 
  help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 
 
Perhaps I misread. I read this issue as: you'd like the icon moved down to be centered on the horizontal center-line of the textbox...moving up and down is vertical alignment/offset. If you meant that you want more/less space between the right-edge of textbox and the left-edge of the help icon, that would be horizontal alignment/offset. 
For comparison, I have attached the old alignments with my own notes about what was ugly nice about them. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Attachment:
 
 Screen Shot 2016-04-04 at 9.19.33 PM.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn edited a comment on  JENKINS-33955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 
 Perhaps I misread.  I read this issue as: you'd like the icon moved down to be centered on the horizontal center-line of the textbox...moving up and down is vertical alignment/offset.  If you meant that you want more/less space between the right-edge of textbox and the left-edge of the help icon, that would be horizontal alignment/offset.For comparison, I have attached the old alignments with my own notes about what was ugly nice about them. !Screen Shot 2016-04-04 at 9.19.33 PM.png|thumbnail! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vmware-vrealize-automation-plugin] (JENKINS-34016) SSL exception logging

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34016 
 
 
 
  SSL exception logging  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 2016/Apr/05 1:16 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kris Thieler 
 
 
 
 
 
 
 
 
 
 
If a CA does not exist in Java's key store an exception will be logged to the Jenkins.log. Additional exceptions may also be logged in the console due to the SSL handshake error. However, the downstream exceptions may cause confusion. Additional exception handling is required to log an exception to the console and clearly show the problem lies with the SSL handshake. 
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provide r.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) 
 
 
 
 
 
 
 
 
 

[JIRA] [vmware-vrealize-automation-plugin] (JENKINS-34015) Deployment configuration parameters not working.

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34015 
 
 
 
  Deployment configuration parameters not working.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 2016/Apr/05 1:12 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kris Thieler 
 
 
 
 
 
 
 
 
 
 
When no configuration parameters are specified an NPE occurs. The configuration parameters must also be checked for non-existent parameter object that may occur if user deletes the default empty parameter on the configuration screen. 
Building on master in workspace /var/lib/jenkins/workspace/vRA7 FATAL: null java.lang.NullPointerException at com.inkysea.vmware.vra.jenkins.plugin.model.Request.fetchBluePrint(Request.java:215) at com.inkysea.vmware.vra.jenkins.plugin.model.Deployment.Create(Deployment.java:99) at com.inkysea.vmware.vra.jenkins.plugin.vRABuildWrapper.setUp(vRABuildWrapper.java:91) at hudson.model.Build$BuildExecution.doRun(https://t.co/RPeM5ywjPB) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(https://t.co/ZzeOzAjCCc) at hudson.model.FreeStyleBuild.run(https://t.co/bRToUcfKSW) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(https://t.co/dtpq9PQyxY) Finished: FAILURE 
 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [vmware-vrealize-automation-plugin] (JENKINS-32261) Exclude bcprov dependencies

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added to release 1.1 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32261 
 
 
 
  Exclude bcprov dependencies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

Status:
 
 In Progress 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] [vmware-vrealize-automation-plugin] (JENKINS-32810) Return environment environment name

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added to release 1.1 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32810 
 
 
 
  Return environment environment name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

Status:
 
 In Progress 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] [vmware-vrealize-automation-plugin] (JENKINS-32811) Expire environment

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added to release 1.1 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32811 
 
 
 
  Expire environment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

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] [vmware-vrealize-automation-plugin] (JENKINS-32816) Blueprint as code

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added to release 1.2 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32816 
 
 
 
  Blueprint as code  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

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] [vmware-vrealize-automation-plugin] (JENKINS-32812) Blueprint paramemters

2016-04-04 Thread kris.thie...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added to release 1.1 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32812 
 
 
 
  Blueprint paramemters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

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] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

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

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 
Oleg Nenashev Maybe worth it to take a look at this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-14191) Load Statistics: Exponential Moving Average artifacts make interpretation difficult

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

 
 
 
 
 
 
 
  Re: Load Statistics: Exponential Moving Average artifacts make interpretation difficult  
 
 
 
 
 
 
 
 
 
 
Ok fair enough. Maybe in that case there needs to be a separate data stream for that then because exponential moving average is useless for a human to see what is actually going on. On my current Jenkins instance it takes a period of 8 minutes (short term view) for a build to go from 1 to 0. In reality it didn't take that long, it was either building or it was not. Obviously 8 minutes isn't much but the moving average does so much smoothing that the load statistics view is essentially useless. If there are many short running jobs the machine never looks busy on the load statistics but in reality it will be busy nearly all the 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] [envinject-plugin] (JENKINS-18297) Can not set PATH environment variable on master node

2016-04-04 Thread c...@factset.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cheng-Yu Pai commented on  JENKINS-18297 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can not set PATH environment variable on master node  
 
 
 
 
 
 
 
 
 
 
Still present in EnvInject 1.91.3 and Jenkins 1.617. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-14191) Load Statistics: Exponential Moving Average artifacts make interpretation difficult

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

 
 
 
 
 
 
 
  Re: Load Statistics: Exponential Moving Average artifacts make interpretation difficult  
 
 
 
 
 
 
 
 
 
 
Load statistics are the basis for the decision to boot up new cloud agents from e.g. EC2 or Docker. So rapid jumps in values would completely break that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-14191) Load Statistics: Exponential Moving Average artifacts make interpretation difficult

2016-04-04 Thread petrikvanderve...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Petrik van der Velde updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-14191 
 
 
 
  Load Statistics: Exponential Moving Average artifacts make interpretation difficult  
 
 
 
 
 
 
 
 
 
 
Is there a reason why an exponential moving average is used here? Realistically the number of executors and the number of running builds are integer numbers, there is no such thing as an 1/2 executor or 1/3 build. Wouldn't it be better to use a discrete graph, e.g. like the attached image (excuse the crappy editing work) 
 
Using the discrete graph would more accurately indicate what is actually happening. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Petrik van der Velde 
 
 
 

Attachment:
 
 jenkinsload_discrete.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34014) p4unshelve task uses the wrong Perforce workspace

2016-04-04 Thread mr...@sjm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34014 
 
 
 
  p4unshelve task uses the wrong Perforce workspace  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 2016/Apr/04 11:47 PM 
 
 
 

Environment:
 

 1.3.8-SNAPSHOT (private-3c567c28-jenkins) 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Rose 
 
 
 
 
 
 
 
 
 
 
I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace. 
My pipeline script looks something like this: 
node(linux)  { p4sync stream: '//buildtools/jenkins_review_workflow' pipeline = load 'workflows/linux-p4-review-build.groovy' pipeline.run_workflow() } 
Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called. 
 
 
   

[JIRA] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is any "Metadata" field

2016-04-04 Thread r...@sensics.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Pavlik updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33088 
 
 
 
  Can't upload to S3 direct from slaves if there is any "Metadata" field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Pavlik 
 
 
 

Summary:
 
 Can't upload to S3 direct from slaves if there is  an empty  any  "Metadata" field 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field

2016-04-04 Thread r...@sensics.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Pavlik commented on  JENKINS-33088 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't upload to S3 direct from slaves if there is an empty "Metadata" field  
 
 
 
 
 
 
 
 
 
 
Ah, interesting. No, sorry - no idea besides just not running upload from slave. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33773) Warnings logged after upgrading from 1.x and detaching plugins

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

 
 
 
 
 
 
 
  Re: Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 
 
The list is so short because apparently I updated plugins in 1.532.3 before updating Jenkins, so that doesn't help. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33773) Warnings logged after upgrading from 1.x and detaching plugins

2016-04-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33773 
 
 
 
  Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33773) Warnings logged after upgrading from 1.x and detaching plugins

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

 
 
 
 
 
 
 
  Re: Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 
 
Interestingly, I tried reproducing the behavior I saw with alpha 4 (which predates my snapshot), beta 1 (which is newer and should be roughly the same), and beta 2, and was unavailable to do this with any of them. 
Notably, the list of plugins in all these cases are much longer and include e.g. maven plugin. Not sure whether this means anything to you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34013) Errors after upgrading Jenkins from "1.0" to 2.0-beta-2

2016-04-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34013 
 
 
 
  Errors after upgrading Jenkins from "1.0" to 2.0-beta-2  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tom FENNELLY 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/04 11:12 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Daniel Beck 
 
 
 
 
 
 
 
 
 
 
Steps to reproduce 
 

Define pristine Jenkins home directory
 

Run Jenkins 1.532.3
 

Save the Global Security configuration page once to get a config.xml declaring 1.0
 

Kill Jenkins
 

Run Jenkins 2.0-beta-2 on the same Jenkins home
 
 
Expected result 
Upgrading works. 
Actual result 
Jenkins spews warnings 

 
$ java -jar 

[JIRA] [core] (JENKINS-33773) Warnings logged after upgrading from 1.x and detaching plugins

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

 
 
 
 
 
 
 
  Re: Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 
 
Tom FENNELLY Beta 1 was released the same day, I believe that was my final testing on what was essentially the same content. I will retest with beta 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] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77

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

 
 
 
 
 
 
 
  Re: Fail to automatically install JDK 1.8.0_77  
 
 
 
 
 
 
 
 
 
 
Could this be JENKINS-23366? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33966) JAVA_HOME is not set when Maven is automatically installed

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

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 
Not sure that's how it's supposed to work. Jesse Glick? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pipeline-stage-view-plugin] (JENKINS-33606) Parallel build steps show as successfully completed when still in proc

2016-04-04 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp commented on  JENKINS-33606 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parallel build steps show as successfully completed when still in proc  
 
 
 
 
 
 
 
 
 
 
Antonio, can you please expand on your reasoning for this and a work around for the need to visually see "stages" that are run in parallel? 
There are a ton of valid usecases for needing this functionality. Without going into any specific use case, if a parallel step is wrapped up into a single stage, then when one of those parallel items fails, the only way to know what actually failed is by digging into the console/logs. Being able to use the visualization as a dashboard, and accurately see what is going on is HUGE. Right now I use stages insides of parallel steps so that I can see exactly what my pipeline is doing and where it fails. As mentioned by the reporter, the current visualization doesn't display that information as well as it could/should. 
If you don't want to enhance it because of technical concerns of having stages within parallel steps, 
 

Is there documentation letting pipeline users not to put stages inside of parallel steps?
 

Could the visualization be enhanced to show parallel steps as "stages" in the view?
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34012) Fail to automatically install JDK 1.8.0_77

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34012 
 
 
 
  Fail to automatically install JDK 1.8.0_77  
 
 
 
 
 
 
 
 
 

Change By:
 
 Laurent TOURREAU 
 
 
 
 
 
 
 
 
 
 On Windows 10, after configuring under Global Tool Configuration a new JDK installation called "JDK-1.8" and selecting _Install automatically_ (I selected _Java SE Development Kit 8u77_ in the combo box) and running the following pipeline code{code}node {  git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'  def mvnHome = tool 'M3'  tool 'JDK-1.8'  bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{code} I get this error: {code}[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitFetching changes from the remote Git repositoryChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)[Pipeline] tool[Pipeline] toolInstalling JDK jdk-8u77-oth-JPRDownloading JDK from http://download.oracle.com/otn-pub/java/jdk/8u77-b03/jdk-8u77-windows-i586.exeDownloading 190848568 bytesInstalling C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\JDK-1.8\jdk.exe[JDK-1.8] $ "C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\JDK-1.8\jdk.exe" /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress "INSTALLDIR=C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\JDK-1.8" /L "C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\install6891913520880051828log"Failed to install JDK. Exit code=1 619[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: nullFinished: FAILURE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34012 
 
 
 
  Fail to automatically install JDK 1.8.0_77  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/04 10:01 PM 
 
 
 

Environment:
 

 Windows 10. Jenkins 2.0-beta-1 
 
 
 

Labels:
 

 2.0 2.0-beta jdk installation java8 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Laurent TOURREAU 
 
 
 
 
 
 
 
 
 
 
On Windows 10, after configuring under Global Tool Configuration a new JDK installation called "JDK-1.8" and selecting Install automatically (I selected Java SE Development Kit 8u77 in the combo box) and running the following pipeline code 

 

node {
  git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'
  def mvnHome = tool 'M3'
  tool 'JDK-1.8'
  bat "\"${mvnHome}\"\\bin\\mvn -B verify"
}
 

 
 

[JIRA] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU commented on  JENKINS-33966 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 
I did this as it : 

 

node {
  git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'
  def mvnHome = tool 'M3'
  def javaHome = tool 'JDK-1.8'
  bat "\"${mvnHome}\"\\bin\\mvn -B verify"
}
 

 
I still get the error: 

 

[Pipeline] Allocate node : Start
Running on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline
[Pipeline] node {
[Pipeline] git
Fetching changes from the remote Git repository
Checking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)
[Pipeline] tool
[Pipeline] tool
[Pipeline] bat
[myPipeline] Running batch script

C:\Program Files (x86)\Jenkins\workspace\myPipeline>"C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3"\bin\mvn -B verify 

Error: JAVA_HOME not found in your environment. 
Please set the JAVA_HOME variable in your environment to match the 
location of your Java installation. 

[Pipeline] } //node
[Pipeline] Allocate node : End
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE
 

 
If i explicitely set JAVA_HOME, it works 

 

node {
  git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'
  def mvnHome = tool 'M3'
  env.JAVA_HOME = tool 'JDK-1.8'
  bat "\"${mvnHome}\"\\bin\\mvn -B verify"
}
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU edited a comment on  JENKINS-33966 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 I did this as it :{code}node {  git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'  def mvnHome = tool 'M3'   def javaHome =  tool 'JDK-1.8'  bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{code}I still get the error:{code}[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitFetching changes from the remote Git repositoryChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)[Pipeline] tool[Pipeline] tool[Pipeline] bat[myPipeline] Running batch scriptC:\Program Files (x86)\Jenkins\workspace\myPipeline>"C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3"\bin\mvn -B verify Error: JAVA_HOME not found in your environment. Please set the JAVA_HOME variable in your environment to match the location of your Java installation. [Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}If i explicitely set JAVA_HOME, it works{code}node {  git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'  def mvnHome = tool 'M3'  env.JAVA_HOME = tool 'JDK-1.8'  bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{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] [pipeline-stage-view-plugin] (JENKINS-33430) Stage view UI loses history when stages are changed

2016-04-04 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp commented on  JENKINS-33430 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stage view UI loses history when stages are changed  
 
 
 
 
 
 
 
 
 
 
+1 for this enhancement. 
I have a pipeline that builds a number of other pipeline jobs. However, this orchestration pipeline determines what it needs to build based on a set of parameters. It can build anywhere from 1 - 6 different jobs, and each of these jobs is built within a stage. Unfortunately, with the current implementation, I can't get an accurate visualization of what stages actually ran for previous 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] [repo-plugin] (JENKINS-33958) RepoScm changelog hang when used with pipeline

2016-04-04 Thread andre...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez commented on  JENKINS-33958 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RepoScm changelog hang when used with pipeline  
 
 
 
 
 
 
 
 
 
 
Thread dump: 
Thread #2 at DSL.checkout(Native Method) at WorkflowScript.repoSync(WorkflowScript:34) at WorkflowScript.run(WorkflowScript:43) at DSL.node(Native Method) at WorkflowScript.run(WorkflowScript:41) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [sauce-ondemand-plugin] (JENKINS-34011) Sauce On Demand plugin 1.150 Fails to Install. Version 1.149 is OK

2016-04-04 Thread michelene.c...@am.sony.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 M Chon created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34011 
 
 
 
  Sauce On Demand plugin 1.150 Fails to Install. Version 1.149 is OK  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jack Moxon 
 
 
 

Components:
 

 sauce-ondemand-plugin 
 
 
 

Created:
 

 2016/Apr/04 9:25 PM 
 
 
 

Environment:
 

 Ubuntu 14.04 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 M Chon 
 
 
 
 
 
 
 
 
 
 
When I upgrade to version 1.150 of the sauce-on-demand plugin, I got this error and it failed to install. Re-installing version 1.149 of the plugin worked. 
{{Apr 03, 2016 1:33:16 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin sauce-ondemand java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager$2$1$1.run(PluginManager.java:384) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:924) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Unable to read /var/lib/jenkins/sauce-ondemand.xml at 

[JIRA] [core] (JENKINS-33773) Warnings logged after upgrading from 1.x and detaching plugins

2016-04-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY edited a comment on  JENKINS-33773 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 
 [~danielbeck] The log  in  the description says "_Upgraded Jenkins from version 1.532.3 to version 2.0-alpha-5-SNAPSHOT_" i.e. not beta2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33773) Warnings logged after upgrading from 1.x and detaching plugins

2016-04-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY commented on  JENKINS-33773 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 
 
Daniel Beck The log the description says "Upgraded Jenkins from version 1.532.3 to version 2.0-alpha-5-SNAPSHOT" i.e. not beta2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clover-plugin] (JENKINS-34010) Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS

2016-04-04 Thread robertx.mie...@intel.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Miesen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34010 
 
 
 
  Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 stephenconnolly 
 
 
 

Components:
 

 clover-plugin 
 
 
 

Created:
 

 2016/Apr/04 9:15 PM 
 
 
 

Environment:
 

 Jenkins: version 1.642.2 LTS  Clover plugin: version 4.4.0Operating system: Debian 7.8 "Wheezy"  Linux Kernel: 3.2.73+deb7u3 x86_64  Java: 1.7.0_95 (OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1))   Browsers used:   * IE 11   * Chrome, version 49.0.2623.110 m 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Robert Miesen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-33773) Warnings logged after upgrading from 1.x and detaching plugins

2016-04-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY commented on  JENKINS-33773 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings logged after upgrading from 1.x and detaching plugins  
 
 
 
 
 
 
 
 
 
 
Daniel Beck 
Hmmm ... I went through the above steps but did not get those warnings. Though I did get {{WARNING: There was an OPT answer. Not currently handled. ... }} warnings. 

 

$ java -jar $TWOGIG jenkins-2.0-beta2.war
Picked up JAVA_TOOL_OPTIONS: -Djava.awt.headless=true
Running from: /Users/tfennelly/je-releases/jenkins-2.0-beta2.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
Apr 04, 2016 10:06:15 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Logging initialized @295ms
Apr 04, 2016 10:06:15 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Apr 04, 2016 10:06:16 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Empty contextPath
Apr 04, 2016 10:06:16 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-9.2.z-SNAPSHOT
Apr 04, 2016 10:06:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Jenkins home directory: /Users/tfennelly/je-releases/work found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
Apr 04, 2016 10:06:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started w.@2f03ac05{/,file:/Users/tfennelly/je-releases/work/war/,AVAILABLE}{/Users/tfennelly/je-releases/work/war}
Apr 04, 2016 10:06:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started ServerConnector@7a79e5e7{HTTP/1.1}{0.0.0.0:8080}
Apr 04, 2016 10:06:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started @2824ms
Apr 04, 2016 10:06:17 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Apr 04, 2016 10:06:17 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Apr 04, 2016 10:06:17 PM hudson.PluginManager loadDetachedPlugins
INFO: Upgrading Jenkins. The last running version was 1.532.3. This Jenkins is version 2.0-beta-2.
Apr 04, 2016 10:06:18 PM hudson.PluginManager loadDetachedPlugins
INFO: Upgraded Jenkins from version 1.532.3 to version 2.0-beta-2. Loaded detached plugins (and dependencies): [maven-plugin.hpi, matrix-auth.hpi, windows-slaves.hpi, matrix-project.hpi, mailer.hpi, script-security.hpi, external-monitor-job.hpi, antisamy-markup-formatter.hpi, pam-auth.hpi, subversion.hpi, ldap.hpi, junit.hpi, javadoc.hpi, cvs.hpi]
Apr 04, 2016 10:06:26 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Apr 04, 2016 10:06:28 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Apr 04, 2016 10:06:28 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Apr 04, 2016 10:06:28 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Apr 04, 2016 10:06:29 PM jenkins.model.RunIdMigrator migrate
INFO: Migrating build records in /Users/tfennelly/je-releases/work/jobs/freebie/builds
Apr 04, 2016 10:06:29 PM jenkins.model.RunIdMigrator doMigrate
WARNING: found unexpected dir lastStableBuild
Apr 04, 2016 10:06:29 PM jenkins.model.RunIdMigrator doMigrate
WARNING: found unexpected dir lastSuccessfulBuild
Apr 04, 2016 10:06:29 PM jenkins.model.RunIdMigrator migrate
WARNING: Build record migration (https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration) is one-way. If you need to downgrade Jenkins, run: java -classpath "/Users/tfennelly/je-releases/work/war/WEB-INF/lib/jenkins-core-2.0-beta-2.jar:/Users/tfennelly/je-releases/work/war/WEB-INF/lib/commons-io-2.4.jar:/Users/tfennelly/je-releases/work/war/WEB-INF/lib/stapler-1.239.jar:/Users/tfennelly/je-releases/work/war/WEB-INF/lib/ant-1.8.4.jar:/Users/tfennelly/je-releases/work/war/WEB-INF/lib/commons-lang-2.6.jar" 

[JIRA] [core] (JENKINS-33619) Script definition area rendered over header section

2016-04-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY commented on  JENKINS-33619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Script definition area rendered over header section  
 
 
 
 
 
 
 
 
 
 
Antonio Muñiz afraid this is a new one to me ... haven't seen it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30363) Logo for Workflow feature

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

 
 
 
 
 
 
 
  Re: Logo for Workflow feature  
 
 
 
 
 
 
 
 
 
 
gus reiber It seems the PR #375 was 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed

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

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 
What happens when you call tool 'JDK-1.8' in your 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU edited a comment on  JENKINS-33966 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 On Global Tool Configuration, I add a new JDK installation called "JDK-1.8".I set the JAVA_HOME  field under installation name  to C:\Program Files\Java\jdk1.8.0_77 and run the job again -> same result JAVA_HOME is not found. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33966) JAVA_HOME is not set when Maven is automatically installed

2016-04-04 Thread laur...@tourreau.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Laurent TOURREAU commented on  JENKINS-33966 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 
On Global Tool Configuration, I add a new JDK installation called "JDK-1.8". I set the JAVA_HOME to C:\Program Files\Java\jdk1.8.0_77 and run the job again -> same result JAVA_HOME is not found. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [parameterized-trigger-plugin] (JENKINS-34009) plugin doesn't perform conversion for subtypes of StringParameterDefinition

2016-04-04 Thread jim.carroth...@sap.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jim Carrothers created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34009 
 
 
 
  plugin doesn't perform conversion for subtypes of StringParameterDefinition  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 huybrechts 
 
 
 

Components:
 

 parameterized-trigger-plugin 
 
 
 

Created:
 

 2016/Apr/04 7:56 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jim Carrothers 
 
 
 
 
 
 
 
 
 
 
Pull request: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/94 
ParameterDefinition types which extend StringParameterDefinition still need to be converted, when possible, in order to ensure correct handling of any additional logic implemented by the sub-type. 
The code change is simply to use a more exacting check then the instanceof keyword because any parameter types which sub-class StringParameterDefinition in order to avoid re-implemeting its behaviour are not currently converted when they could be. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

[JIRA] [workflow-plugin] (JENKINS-34008) Allow other contributions to global library post receive hook

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34008 
 
 
 
  Allow other contributions to global library post receive hook  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/04 7:50 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
Right now, only UserDefinedGlobalVariableSet gets rebuilt on a change to the global library repository. It'd be very handy to be able to contribute other calls to make (even if they're just a standard "rebuild" method on extensions of something) so that other plugins can take advantage of the global library repository for things other than UserDefinedGlobalVariables. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
  

[JIRA] [core] (JENKINS-33826) Build history text badge display cut off and overlaps other content

2016-04-04 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier commented on  JENKINS-33826 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build history text badge display cut off and overlaps other content  
 
 
 
 
 
 
 
 
 
 
To mark it only as resolved. Otherwise with the current workflow we cannot edit closed issues and thus add a tags 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33826) Build history text badge display cut off and overlaps other content

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

 
 
 
 
 
 
 
  Re: Build history text badge display cut off and overlaps other content  
 
 
 
 
 
 
 
 
 
 
Whoops, what's the right thing to do? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()

2016-04-04 Thread manosn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos edited a comment on  JENKINS-32694 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NullPointerException at CreateTextFile.CreateFileTask.call()  
 
 
 
 
 
 
 
 
 
 Trying to use Plugin version 1.3.1, I'm getting on this file: \  $ \ {WORKSPACE } \ } /Custom_Data.properties  Failed to create/update file.nullThe file content is: \ $ \ {My_Custom_Data \ }I tried with or without WORKSPACE option, with slash and backslash.System is Windows 2008, Jenkins 1.647 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()

2016-04-04 Thread manosn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos edited a comment on  JENKINS-32694 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NullPointerException at CreateTextFile.CreateFileTask.call()  
 
 
 
 
 
 
 
 
 
 Trying to use Plugin version 1.3.1, I'm getting on this file: \ ${WORKSPACE} \ /Custom_Data.properties * Failed to create/update file.null * The file content is: \ ${My_Custom_Data}I tried with or without WORKSPACE option, with slash and backslash.System is Windows 2008, Jenkins 1.647 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33826) Build history text badge display cut off and overlaps other content

2016-04-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33826 
 
 
 
  Build history text badge display cut off and overlaps other content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Reopened 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-33826) Build history text badge display cut off and overlaps other content

2016-04-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing issues is evil. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33826 
 
 
 
  Build history text badge display cut off and overlaps other content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26481) Mishandling of binary methods accepting Closure

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

 
 
 
 
 
 
 
  Re: Mishandling of binary methods accepting Closure  
 
 
 
 
 
 
 
 
 
 
I assume additional changes will be needed for, say, collect and collectEntries? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26481) Mishandling of binary methods accepting Closure

2016-04-04 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer edited a comment on  JENKINS-26481 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Mishandling of binary methods accepting Closure  
 
 
 
 
 
 
 
 
 
 I assume additional changes will be needed for, say, collect  and ,  collectEntries , any, every, find, findAll ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26481) Mishandling of binary methods accepting Closure

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

 
 
 
 
 
 
 
  Re: Mishandling of binary methods accepting Closure  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: cps/pom.xml cps/src/main/java/org/jenkinsci/plugins/workflow/cps/persistence/IteratorHack.java cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-plugin/5b102a5b06745b1eeeb7c1305096bf80e37c1a90 Log: Merge pull request #372 from jenkinsci/eachClosure-JENKINS-26481 
JENKINS-26481 JENKINS-27421 Fix ArrayList$Itr, and integration test for Object.each(Closure) 
Compare: https://github.com/jenkinsci/workflow-plugin/compare/e3906483924d...5b102a5b0674 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27421) java.util.ArrayList$Itr is not Serializable

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

 
 
 
 
 
 
 
  Re: java.util.ArrayList$Itr is not Serializable  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: cps/pom.xml cps/src/main/java/org/jenkinsci/plugins/workflow/cps/persistence/IteratorHack.java cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-plugin/5b102a5b06745b1eeeb7c1305096bf80e37c1a90 Log: Merge pull request #372 from jenkinsci/eachClosure-JENKINS-26481 
JENKINS-26481 JENKINS-27421 Fix ArrayList$Itr, and integration test for Object.each(Closure) 
Compare: https://github.com/jenkinsci/workflow-plugin/compare/e3906483924d...5b102a5b0674 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread jn...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord commented on  JENKINS-33955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 
 
I think I meant horizontally aligned - but you get what I mean  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33619) Script definition area rendered over header section

2016-04-04 Thread amu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-33619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Script definition area rendered over header section  
 
 
 
 
 
 
 
 
 
 
Spike Washburn Right, it seems to be fixed for the editor line numbers element, but it's still happening for the samples button as Daniel Beck said. But I'm not sure what commit fixed it, perhaps Tom FENNELLY knows? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [robot-plugin] (JENKINS-31409) Manage jenkins configure system screen crashes after plugins installed

2016-04-04 Thread jyri.il...@eficode.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jyri Ilama commented on  JENKINS-31409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manage jenkins configure system screen crashes after plugins installed  
 
 
 
 
 
 
 
 
 
 
I faced this problem suddenly today, without changing anything. Tried to update robot plugin (to 1.6.4), no help. Updating build-pipeline plugin to the latest version (1.5.2) fixed it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33938) setup wizard always installs plugins - so just strip "plugin".

2016-04-04 Thread jn...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord commented on  JENKINS-33938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: setup wizard always installs plugins - so just strip "plugin".  
 
 
 
 
 
 
 
 
 
 
fix plugin manager later? 
basically this is a new UI so has the oppertunity to "do things better" tm 
The layout of the new install wizard also makes this worse than the plugin manager (pick a plugin with a lot of dependencies and look at the amount of extra wrapping and space that is required). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33954) ExtensionFinder log at incorrect level

2016-04-04 Thread jn...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord edited a comment on  JENKINS-33954 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ExtensionFinder log at incorrect level  
 
 
 
 
 
 
 
 
 
 . bq .  Could be changed to not log anythingI was meaning this could/should be at INFO level rather than hidden.If something is expected behavior why is it a warning?It's not a regression - but the OOB experience is likely to make this much more evident as Subversion is not likely to be installed but pipeline will be. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33954) ExtensionFinder log at incorrect level

2016-04-04 Thread jn...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord commented on  JENKINS-33954 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ExtensionFinder log at incorrect level  
 
 
 
 
 
 
 
 
 
 
.bq Could be changed to not log anything 
I was meaning this could/should be at INFO level rather than hidden. If something is expected behavior why is it a warning? 
It's not a regression - but the OOB experience is likely to make this much more evident as Subversion is not likely to be installed but pipeline will be. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33951) ok button location in newJob UI

2016-04-04 Thread jn...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord commented on  JENKINS-33951 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ok button location in newJob UI  
 
 
 
 
 
 
 
 
 
 
Spike Washburn agreed, but it was more indented previously. also noticed that the "Add" button to add the commment in JIRA is at the bottom left (maybe its a web thang?) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22853) SEVERE: Trying to unexport an object that's already unexported

2016-04-04 Thread adreyf...@palantir.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andy Dreyfuss commented on  JENKINS-22853 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Trying to unexport an object that's already unexported  
 
 
 
 
 
 
 
 
 
 
Is matching java versions between master/slave a prerequisite or expectation for full 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] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

2016-04-04 Thread mmit...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Mitchell commented on  JENKINS-28492 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 
So I think what's going on is that certain kind of network outages (or maybe a reboot) are causing issues with the master realizing that the connection is closed. 
I think I see one place where there is a bug: 
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/slaves/ChannelPinger.java#L111 
I've seen the call into the PingFailureAnalyzer return NPE, causing us to miss the call to terminate the channel. However, unless I'm misunderstanding the code, I think that's executing on the client, which wouldn't cause the server to keep the channel open. 
Do you have any special ping setting set on Jenkins startup? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34007) Jenkins 2.0 - wizard 'X' button

2016-04-04 Thread michal.c.slusarc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Slusarczyk created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34007 
 
 
 
  Jenkins 2.0 - wizard 'X' button   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Screen Shot 2016-04-04 at 11.12.44 AM.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/04 6:18 PM 
 
 
 

Environment:
 

 docker image jenkinsci/jenkins:2.0-beta-1 
 
 
 

Labels:
 

 2.0-beta ux 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michal Slusarczyk 
 
 
 
 
 
 
 
 
 
 
Setup wizard close button (see screenshot) should be guarded by 'Are you sure?' question. I misclicked it and there is no way of going back to the wizard. 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-33951) ok button location in newJob UI

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33951 
 
 
 
  ok button location in newJob UI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 
 
 
 
 
 
 
 the OK button is in the bottom left on the  newJOb plugin  newJob page .On every other UI in the world with L2R T2B language it is in the bottom right.It just looks strange. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33926) Jenkins no longer appears to shutdown correctly

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn assigned an issue to Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33926 
 
 
 
  Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33951) ok button location in newJob UI

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33951 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ok button location in newJob UI  
 
 
 
 
 
 
 
 
 
 
FWIW: OK button was always in the bottom left, this wasn't regressed by the new UI. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33573) Getting Started and Job configuration views should not use two different loading animations

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33573 
 
 
 
  Getting Started and Job configuration views should not use two different loading animations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Labels:
 
 2.0  community-bee 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22853) SEVERE: Trying to unexport an object that's already unexported

2016-04-04 Thread s...@cisco.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christenson commented on  JENKINS-22853 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Trying to unexport an object that's already unexported  
 
 
 
 
 
 
 
 
 
 
 Our Jenkins Master and Slave versions were running different versions of the JDK/JRE. (Specifically some slaves were 1.6!). After updating all slaves to 1.7 we are not seeing the Unexport problem any more we have even moved the master to OpenJDK 1.8 and it seems to be getting along just fine with Oracle JDK/JRE 1.7 on most slaves. 
We are now getting hammered by a different mega stack trace: MalformedURLException: no protocol: 
But the unexport exceptions are gone. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33769) Closing the upgrade banner redirects to the index page for no reason

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Unnecessary if we're going to have the real fix via JENKINS-33663 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33769 
 
 
 
  Closing the upgrade banner redirects to the index page for no reason  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33769) Closing the upgrade banner redirects to the index page for no reason

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn edited a comment on  JENKINS-33769 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Closing the upgrade banner redirects to the index page for no reason  
 
 
 
 
 
 
 
 
 
 If we solve JENKINS- 33568 33663 , then this issue will go away.   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33926) Jenkins no longer appears to shutdown correctly

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

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
Same issue for me on OS X so does not seem limited to Windows. 
If this means that e.g. service restarts don't do a clean restart, and e.g. lose the queue contents, that would be bad. 
If it's just a case of Jetty 9 no longer logging this, we'll survive  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33769) Closing the upgrade banner redirects to the index page for no reason

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33769 
 
 
 
  Closing the upgrade banner redirects to the index page for no reason  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Labels:
 
 2.0 2.0-beta  community-bee 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33769) Closing the upgrade banner redirects to the index page for no reason

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33769 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Closing the upgrade banner redirects to the index page for no reason  
 
 
 
 
 
 
 
 
 
 
If we solve 

JENKINS-33568
, then this issue will go away. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33948) 2.0 setup wizard - Notifications and Publishing never highlighted.

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33948 
 
 
 
  2.0 setup wizard - Notifications and Publishing never highlighted.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Labels:
 
 2.0 2.0-beta  community-bee  ui 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33948) 2.0 setup wizard - Notifications and Publishing never highlighted.

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33948 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 2.0 setup wizard - Notifications and Publishing never highlighted.  
 
 
 
 
 
 
 
 
 
 
For the case where you click the section on the left side, we should be able to show it selected properly. There was a similar problem on the configuration page tabs and a fix was made to highlight the clicked section. 
Not sure what we can do about this in the scroll case. If you don't click, it's ambiguous which section is "active". As currently coded, the top-most section title on the screen is highlighted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33956) Jenkins 2.0 - 'X' on required conf elements

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn assigned an issue to Daniel Beck 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33956 
 
 
 
  Jenkins 2.0 - 'X' on required conf elements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

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] [core] (JENKINS-33956) Jenkins 2.0 - 'X' on required conf elements

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33956 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0 - 'X' on required conf elements  
 
 
 
 
 
 
 
 
 
 
Daniel will investigate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33936) setup wizard plugin selection - "WTF is plugin X"?

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33936 
 
 
 
  setup wizard plugin selection - "WTF is plugin X"?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33936) setup wizard plugin selection - "WTF is plugin X"?

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33936 
 
 
 
  setup wizard plugin selection - "WTF is plugin X"?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Labels:
 
 2.0 2.0-beta UI  community-bee 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33936) setup wizard plugin selection - "WTF is plugin X"?

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33936 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: setup wizard plugin selection - "WTF is plugin X"?  
 
 
 
 
 
 
 
 
 
 
Suggested behavior: Clicking on the dependent plugin name should take you to the wiki page for the 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-33936) setup wizard plugin selection - "WTF is plugin X"?

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33936 
 
 
 
  setup wizard plugin selection - "WTF is plugin X"?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 
 
 
 
 
 
 
 2.0-beta-1 initial setup wizardGo to choose which plugins to install.Expand the dependencies on "Dashboard view"Notice a "OWASP Markup Formatter Plugin"h3. expected results1) Click on "OWASP Markup Formatter Plugin" to get more info2) Click on "OWASP Markup Formatter Plugin" to get more info3)  Search the list of plugins to find out what "OWASP Markup Formatter Plugin" is.h3. actual results1) this toggles the plugin selection2) this does nothing3) the plugin is not listed.WTF?(yes **I** know why it is not listed but I should be able to get more info about it to see if this is a plugin that I wish to install). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26481) Mishandling of binary methods accepting Closure

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

 
 
 
 
 
 
 
  Re: Mishandling of binary methods accepting Closure  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: cps/pom.xml cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-plugin/b356799f09d18b0d9f96c1084354df072b7d656f Log: JENKINS-26481 With new script-security and groovy-cps releases, eachClosure finally passes. 
Compare: https://github.com/jenkinsci/workflow-plugin/compare/a990468a828e...b356799f09d1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 
 
gus reiber perhaps you could make a ruling on how "broken" and "ugly" this is. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 
 
Top-align looks better for large controls, but not as good for single-line controls. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn assigned an issue to gus reiber 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33955 
 
 
 
  help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Assignee:
 
 gus reiber 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33955 
 
 
 
  help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Labels:
 
 2.0 2.0-beta  community-bee  ui 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33955 
 
 
 
  help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 
 
 
 
 
 
 
 The blue "Help" icons are no longer correctly aligned on the 2.0 newJob page.In previous releases for textboxes & dropdowns  they where  vertically  aligned in the center which looked visually appealing.  Now they are aligned at the top which looks ugly.The icon should be aligned with the first line of text - just as it is for checkboxes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33955) help icons vertically mis-aligned on 2.0 newJob page

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33955 
 
 
 
  help icons vertically mis-aligned on 2.0 newJob page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Summary:
 
 help icons  vertically  mis -  aligned on 2.0 newJob page 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33562) Intermediate tabs are highlighted when scrolling in job configuration

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Beta2 no longer has this behavior. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33562 
 
 
 
  Intermediate tabs are highlighted when scrolling in job configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Spike Washburn 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33938) setup wizard always installs plugins - so just strip "plugin".

2016-04-04 Thread swashb...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Spike Washburn commented on  JENKINS-33938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: setup wizard always installs plugins - so just strip "plugin".  
 
 
 
 
 
 
 
 
 
 
The Plugin Manager also shows the "plugin". Is there a reason this should behave differently from the Plugin Manager? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.


  1   2   3   >