[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22
Title: Message Title pjdarton updated JENKINS-61131 Fixed in version 2.23, which was released a few minutes ago. Jenkins / JENKINS-61131 vsphere-cloud: Credentials selection is broken in UI since 2.22 Change By: pjdarton Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204653.1582040133000.6836.1584114960693%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title pjdarton commented on JENKINS-61164 Re: Configure Clouds - no credentials visible for vSphere Cloud Thanks for that folks - much appreciated. On the basis of 2 confirmed "it works" reports, I've kicked off a release; it's uploaded and should start showing up within the next few hours. i.e. This is fixed in the 2.23 release which went out just now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204698.1582196162000.6831.1584114900176%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title pjdarton commented on JENKINS-61164 Re: Configure Clouds - no credentials visible for vSphere Cloud No ETA; vSphere plugin maintenance (i.e. building, testing and releasing new versions) is something I do in my "spare" time at work (and there's precious little of that at present). There is, however, something you (or anyone else watching this) can do to speed things up: download the .hpi file from the URL above and install it using the "advanced" tab on the manage plugins page. test it let me know if it fixes the problem for you If you can do that then it'll give me confidence that the fix works and is worth releasing officially, meaning I can get a release out much sooner. If you can't help with that then you'll have to wait until I have the time to do all that myself unaided ... and that might be a while. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204698.1582196162000.6625.1584097860247%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title pjdarton commented on JENKINS-61164 Re: Configure Clouds - no credentials visible for vSphere Cloud FAO anyone watching: this will be fixed in the next release. In the meantime, anyone affected by this issue can grab an as-yet-unreleased build from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204698.1582196162000.3380.1583772660729%40Atlassian.JIRA.
[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22
Title: Message Title pjdarton updated JENKINS-61131 Jenkins / JENKINS-61131 vsphere-cloud: Credentials selection is broken in UI since 2.22 Change By: pjdarton Status: In Progress Fixed but Unreleased Assignee: pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204653.1582040133000.3358.1583772540750%40Atlassian.JIRA.
[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22
Title: Message Title pjdarton commented on JENKINS-61131 Re: vsphere-cloud: Credentials selection is broken in UI since 2.22 PR merged; it'll be fixed in the next release. In the meantime, anyone affected by this issue can grab an as-yet-unreleased build from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204653.1582040133000.3345.1583772420295%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title pjdarton edited a comment on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails It should be fixed in the next release.In the meantime, grab the as-yet-unreleased version from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/artifact/ (and if that _doesn't_ fix it, please do let me know) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4526.1581096360169%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title pjdarton commented on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails It should be fix in the next release. In the meantime, grab the as-yet-unreleased version from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/artifact/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4520.1581096300283%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title pjdarton edited a comment on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails It should be fix fixed in the next release.In the meantime, grab the as-yet-unreleased version from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/artifact/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4522.1581096300503%40Atlassian.JIRA.
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title pjdarton commented on JENKINS-54496 Re: Node monitoring should not log exceptions for disconnected nodes Well, it seems to be working. I'd normally expect to see over a dozen of those exceptions during the course of a morning and the log is quiet (well, it's still very active, but it's no longer getting lots of those exceptions ... which will make it easier for me to concentrate on tracking down the other exceptions I'm seeing now ) PR-4461 submitted (by me - I'm "pjdarton" on here and on github). Changes are as suggested above - just the addition of those 5 lines. Note that github doesn't seem to recognise "jeffret-g" so either it's not letting me see you, or there's a typo ... I did find a "jeffret-b" user with real name matching yours so I'm asssuming a b/g typo ... and if that's not the case, I've just pinged the wrong person... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195266.1541524267000.8915.1580394360475%40Atlassian.JIRA.
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title pjdarton commented on JENKINS-54496 Re: Node monitoring should not log exceptions for disconnected nodes I was able to build a jenkins.war this afternoon; it's going "live" on my main Jenkins server tonight and so, with the workload that gets each day, I should be able to tell if it's resolved within a day or two (assuming no other work gets in the way, that is). If it works, I'll submit a PR. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195266.1541524267000.8475.1580333520217%40Atlassian.JIRA.
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title
pjdarton edited a comment on JENKINS-54496
Re: Node monitoring should not log exceptions for disconnected nodes
I've done a bit of digging...I believe the problem stems from the fact that {{monitorDetailed()}} gets the list of {{Computer}} s instances from Jenkins at the start, but this list can change while the monitoring is taking place such that, by the time {{Future.get}} returns with an answer (or an exception), the {{Computer}} being monitored may have been removed from Jenkinsand if it has been removed from Jenkins and the monitoring threw an exception of the form "can't talk to this slave node anymore" then that's pretty much "expected behavior" rather than something worthy of logging a warning & exception trace.i.e. before this method logs a big complaint to the logfile, it should check to see if the slave node being monitored still exists in Jenkins as, if Jenkins has forgotten about it, we shouldn't go logging about it.I think that the answer may be to modify AbstractAsyncNodeMonitorDescriptor's {{private void error(Computer c, Throwable x)}} method so that instead of [this|https://github.com/jenkinsci/jenkins/blob/jenkins-2.204.1/core/src/main/java/hudson/node_monitors/AbstractAsyncNodeMonitorDescriptor.java#L126-L132]:{code:java}private void error(Computer c, Throwable x) {if (c instanceof SlaveComputer) {Functions.printStackTrace(x, ((SlaveComputer) c).getListener().error("Failed to monitor for " + getDisplayName()));} else {LOGGER.log(WARNING, "Failed to monitor " + c.getDisplayName() + " for " + getDisplayName(), x);}}{code}it does this{code:java}private void error(Computer c, Throwable x) {// JENKINS-54496: don't log if c was removed from Jenkins after we'd started monitoringfinal boolean cIsStillCurrent = Jenkins.get().getComputer(c.getName()) == c;if (!cIsStillCurrent) {return;}if (c instanceof SlaveComputer) {Functions.printStackTrace(x, ((SlaveComputer) c).getListener().error("Failed to monitor for " + getDisplayName()));} else {LOGGER.log(WARNING, "Failed to monitor " + c.getDisplayName() + " for " + getDisplayName(), x);}}{code}If I can persuade my dev environmemt to build me a custom jenkins.war with this code change, I'll be able to try that out and see if that resolves the issue ... but in the meantime, WDYT?
Add Comment
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title
pjdarton edited a comment on JENKINS-54496
Re: Node monitoring should not log exceptions for disconnected nodes
I've done a bit of digging ...I believe the problem stems from the fact that {{monitorDetailed()}} gets the list of {{Computer}}s from Jenkins at the start, but this list can change while the monitoring is taking place such that, by the time {{Future.get}} returns with an answer (or an exception), the {{Computer}} being monitored may have been removed from Jenkins and if it has been removed from Jenkins and the monitoring threw an exception of the form "can't talk to this slave node anymore" then that's pretty much "expected behavior" rather than something worthy of logging a warning & exception trace.i.e. before this method logs a big complaint to the logfile, it should check to see if the slave node being monitored still exists in Jenkins as, if Jenkins has forgotten about it, we shouldn't go logging about it. I think that the answer may be to modify AbstractAsyncNodeMonitorDescriptor's {{private void error(Computer c, Throwable x)}} method so that instead of [this|https://github.com/jenkinsci/jenkins/blob/jenkins-2.204.1/core/src/main/java/hudson/node_monitors/AbstractAsyncNodeMonitorDescriptor.java#L126-L132]:{code:java}private void error(Computer c, Throwable x) {if (c instanceof SlaveComputer) {Functions.printStackTrace(x, ((SlaveComputer) c).getListener().error("Failed to monitor for " + getDisplayName()));} else {LOGGER.log(WARNING, "Failed to monitor " + c.getDisplayName() + " for " + getDisplayName(), x);}}{code}it does this{code:java}private void error(Computer c, Throwable x) {// JENKINS-54496: don't log if c was removed from Jenkins after we'd started monitoringfinal boolean cIsStillCurrent = Jenkins.get().getComputer(c.getName()) == c;if (!cIsStillCurrent) {return;}if (c instanceof SlaveComputer) {Functions.printStackTrace(x, ((SlaveComputer) c).getListener().error("Failed to monitor for " + getDisplayName()));} else {LOGGER.log(WARNING, "Failed to monitor " + c.getDisplayName() + " for " + getDisplayName(), x);}}{code}If I can persuade my dev environmemt to build me a custom jenkins.war with this code change, I'll be able to try that out and see if that resolves the issue ... but in the meantime, WDYT?
Add Comment
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title
pjdarton commented on JENKINS-54496
Re: Node monitoring should not log exceptions for disconnected nodes
I've done a bit of digging and I think that the answer may be to modify AbstractAsyncNodeMonitorDescriptor's private void error(Computer c, Throwable x) method so that instead of this:
private void error(Computer c, Throwable x) {
if (c instanceof SlaveComputer) {
Functions.printStackTrace(x, ((SlaveComputer) c).getListener().error("Failed to monitor for " + getDisplayName()));
} else {
LOGGER.log(WARNING, "Failed to monitor " + c.getDisplayName() + " for " + getDisplayName(), x);
}
}
it does this
private void error(Computer c, Throwable x) {
// JENKINS-54496: don't log if c was removed from Jenkins after we'd started monitoring
final boolean cIsStillCurrent = Jenkins.get().getComputer(c.getName()) == c;
if (!cIsStillCurrent) {
return;
}
if (c instanceof SlaveComputer) {
Functions.printStackTrace(x, ((SlaveComputer) c).getListener().error("Failed to monitor for " + getDisplayName()));
} else {
LOGGER.log(WARNING, "Failed to monitor " + c.getDisplayName() + " for " + getDisplayName(), x);
}
}
If I can persuade my dev environmemt to build me a custom jenkins.war with this code change, I'll be able to try that out and see if that resolves the issue ... but in the meantime, WDYT?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-54496
Node monitoring should not log exceptions for disconnected nodes
Change By:
pjdarton
In an environment in which Jenkins nodes are being created and removed a lot, e.g. when using the docker-plugin to create single-use containers as slave nodes, the node monitoring functionality can fill the logs full of spurious exceptions, e.g.{code:none}Oct 13, 2018 10:18:14 PM io.jenkins.docker.DockerTransientNode$1 printlnINFO: Disconnected computer for node 'docker-hst02-00030qwaqtu3g'.Oct 13, 2018 10:18:14 PM io.jenkins.docker.DockerTransientNode$1 printlnINFO: Removed Node for node 'docker-hst02-00030qwaqtu3g'.Oct 13, 2018 10:18:14 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitorDetailedWARNING: Failed to monitor docker-hst02-00030qwaqtu3g for Clock Differencejava.util.concurrent.ExecutionException: java.io.IOException: Cannot locate RemoteClassLoader.ClassLoaderProxy(2) in the channel exported table at hudson.remoting.Channel$2.adapt(Channel.java:992) at hudson.remoting.Channel$2.adapt(Channel.java:986) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305)Caused by: java.io.IOException: Cannot locate RemoteClassLoader.ClassLoaderProxy(2) in the channel exported table at hudson.remoting.MultiClassLoaderSerializer$Input.readClassLoader(MultiClassLoaderSerializer.java:107) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:128) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1826) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2000) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422) at hudson.remoting.UserRequest.deserialize(UserRequest.java:291) at hudson.remoting.UserRequest$NormalResponse.retrieve(UserRequest.java:326) at hudson.remoting.Channel$2.adapt(Channel.java:990) ... 5 moreCaused by: java.util.concurrent.ExecutionException: Invalid object ID 2 iota=7 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.get(ExportTable.java:397) at hudson.remoting.Channel.getExportedObject(Channel.java:780) at hudson.remoting.MultiClassLoaderSerializer$Input.readClassLoader(MultiClassLoaderSerializer.java:105) ... 14 moreOct 13, 2018 10:18:14 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitorDetailedWARNING: Failed to monitor docker-hst02-00030qwaqtu3g for Free Temp Spacejava.util.concurrent.ExecutionException: java.io.IOException: Cannot locate RemoteClassLoader.ClassLoade
[JIRA] (JENKINS-42811) Vsphere Cloud plugin stops working after a number of builds
Title: Message Title pjdarton commented on JENKINS-42811 Re: Vsphere Cloud plugin stops working after a number of builds Well, for the scenario you've given logs for, the behavoir is working-as-designed - it was told not to provision more than 10 of that template so that's what it did. It only broke that limit after you killed off the old cloud and replaced it with one with no memory of the old instances If you can reproduce the scenario where it's "not creating more instances" when there is "no cap" (and provide logs & other information) then that'd make the problem more solvable. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179810.1489595244000.7069.1578912780341%40Atlassian.JIRA.
[JIRA] (JENKINS-42811) Vsphere Cloud plugin stops working after a number of builds
Title: Message Title pjdarton commented on JENKINS-42811 Re: Vsphere Cloud plugin stops working after a number of builds According to that log message, you've set a max=10 for instances from that template. So, unless you've got other templates defined on that cloud, you're never going to reach 50 as that template is capped at 10 - that's why it's saying it's 100% full when it's got 10 instances provisioned with max=10. You either need to allow that template to spawn an unlimited number of instances (capped only by the cloud instance cap), or to spawn a larger number of instances, or to define other templates such that the sum of all templates' max fields comes to at least the cloud's instance cap. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179810.1489595244000.6594.1578678060182%40Atlassian.JIRA.
[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart
Title: Message Title pjdarton commented on JENKINS-39636 Re: Could not initialize class org.jfree.chart.JFreeChart > I can confirm on Ubuntu using the openjdk-8-jdk solves this problem. ...so can I, although in my case (I had the headless jre installed initially), I had to reboot my server. Just stopping and restarting the Jenkins service didn't change anything. I remain "somewhat disgruntled" about installing the non-headless JRE on a headless server; IMO a headless server should not have any X11 code on it anywhere and installing the non-headless JRE pulled in numerous X11-related packages which offends my sense of neatness ... but my devs don't care as they're just happy they've got their pretty graphs back again, and it didn't take long either Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176200.1478758105000.15008.1577099340351%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton commented on JENKINS-53208 Re: Split main configuration page, takes too long to load FYI most of the folks currently writing/maintaining Jenkins & its plugins ended up in that position simply because, at some point in the past, they wanted a change that nobody else wanted as much as they did. The great strength of FOSS like Jenkins is that, unlike privately owned software, you always have the option to join in. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193234.1535030695000.5116.1576060560325%40Atlassian.JIRA.
[JIRA] (JENKINS-59764) Connection timeout is not honored
Title: Message Title pjdarton updated JENKINS-59764 Code changes went into the release of docker-plugin version 1.1.9 Jenkins / JENKINS-59764 Connection timeout is not honored Change By: pjdarton Status: Fixed but Unreleased Closed Assignee: Ivan Fernandez Calvo Released As: docker-plugin version 1.1.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received
[JIRA] (JENKINS-59764) Connection timeout is not honored
Title: Message Title pjdarton updated JENKINS-59764 PR has been merged. Will be FITNR. Jenkins / JENKINS-59764 Connection timeout is not honored Change By: pjdarton Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title pjdarton commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Note: $@ not $* FYI "$*" will glob all CLI arguments into one argument, which is pretty-much guaranteed to break things (it'll break things if more than one argument was provided), whereas $* would only break things if folks provided arguments containing whitespace. "$@" is the best option when you want to "pass through all arguments as they were provided". TL;DR: Whitespace in arguments is very easy to get wrong Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and st
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
pjdarton commented on JENKINS-59790
Re: Container cannot connect to node because it doesn't exist
Personally, I approve of adding retry logic to pretty-much anything network related. The SSH connection mechanism from Master -> Slave-Node has lots of (configurable) retry logic so there is "prior art" to having this. There's a lot of chicken/egg issues when it comes to starting Jenkins slaves and so it makes a lot of sense to ensure that no aspect of this delicate negotiation process requires things to happen in a specific order. e.g. in the docker-plugin's case, it wants to know the container-ID of the container (which is only available once the "run container" command has returned) to write into the slave node instance before returning it to Jenkins, so it has to start the container before Jenkins gets it ... but if the slave container starts up very quickly then Jenkins might well receive and reject its connection request before Jenkins adds the node to its list of permitted slaves. A retry mechanism would allow an easy workaround for this ... as well as helping with situations where the network between the master and slave is less than perfect. FYI the script I use for starting Windows VMs with the vSphere-plugin (linked to from the vSphere plugin's wiki page) that connect via JNLP contains a lot of retry logic and that's proved its worth many times over. What I would recommend, however, is that the number of retries and the delay between retries be made configurable. ...and I'd also recommend that
$ACTUAL_ENTRYPOINT $*
should be changed to
${ACTUAL_ENTRYPOINT} "$@"
so whitespace in arguments gets preserved (something that'd be less of an issue if this retry logic was incorporated in the core /usr/local/bin/jenkins-slave script).
Add Comment
[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title pjdarton commented on JENKINS-53810 Re: Launch Agents fails with ERROR: null java.util.concurrent.CancellationException I'd be a bit wary of updating the docker-plugin so it requires a fully up-to-date version of Jenkins. I believe that users should be able to use the latest docker-plugin with a core Jenkins that's at least 6 months out of date. If we had a critical security defect that required the latest Jenkins core then, sure, I guess we'd have to do that but for anything else, it'd be best not to force everyone to update. FYI what the docker-plugin is trying to do is to poll the docker container (that it just created) to wait until the container is ready to accept SSH connections before allowing the main SSHLauncher code to start trying to connect. If the docker-plugin declared its provisioning "complete" and the slave stayed offline for any period then Jenkins would ask it to make more slave nodes than are required, causing resource wastage. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194324.1538032375000.6947.1571050860510%40Atlassian.JIRA.
[JIRA] (JENKINS-59764) Connection timeout is not honored
Title: Message Title pjdarton commented on JENKINS-59764 Re: Connection timeout is not honored Without any information regarding what timeout(s) were set and were expected, the message "after 0 seconds" could be working-as-designed. All it's doing is saying how many seconds (rounded down) things took to fail, so if there's a 100ms timeout then that's all you'd ever see. i.e. it's not the best error message ever for fast systems :-/ In general, it's best to configure the SSH connector to try multiple times and wait between attempts, and I'd guess that's not what's being done here (otherwise things wouldn't be able to fail so fast). I've checked the PR and, yes, it looks like the code being changed may well be the source of this problem ... and that'll be discussed in the PR itself. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202487.1570988284000.6904.1571046480145%40Atlassian.JIRA.
[JIRA] (JENKINS-26407) expandableTextbox has inconsistent form validation
Title: Message Title pjdarton commented on JENKINS-26407 Re: expandableTextbox has inconsistent form validation I just lost a couple of hours to this bug I've updated the description as best I can - it looks like the problem is (today) exactly as Kanstantsin described in the comments (from a few years ago) - but jelly code is not something I understand; I hope my clarification might help others who know jelly better than I do figure out a way forward... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160071.142113908.9848.1570031400205%40Atlassian.JIRA.
[JIRA] (JENKINS-26407) expandableTextbox has inconsistent form validation
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-26407
expandableTextbox has inconsistent form validation
Change By:
pjdarton
Consider a Java bean with a potentially _multi-line_ String field {{myField}} and associated {{config.jelly}} file{code:xml} {code}If {{myField}} has a multi-line value (as decided by calling {{hudson.Functions.isMultiline(String)}}) when the web form is first loaded then everything works as expected - the {{Descriptor}}'s {{doCheck}} methods get called as expected (i.e. as documented). However, if the field value is either empty or is just a single-line value (i.e. when {{expandableTextbox.jelly}}'s {{test="${h.isMultiline(value)}"}} is not true) then {{}} will never call the {{doCheck}} methods. That's a bug - it's not working as documented (or as expected). If a {{doCheck}} method is present, it should get called, regardless whether a field value is being rendered as a {{textarea}}, {{textbox}} or {{expandableTextbox}}. Impact: This means that users entering data for the first time will not have their data validated. It also means that plugin developers can loose a few hours trying to figure out why one or more of their carefully-coded {{doCheck}} methods are being silently ignored most of the time... :( Workaround: Developers could use {{}} ... but that leads to a cluttered UI as it always uses a minimum height of 5 rows (as set by {{$\{h.determineRows(value)}}} which calls {{hudson.Functions.determineRows(String)}} which returns a minimum of 5 even for an empty string). *TL;DR:* {{expandableTextbox}} should not be an exception to the general rule regarding form validation.
Add Comment
[JIRA] (JENKINS-26407) expandableTextbox has inconsistent form validation
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-26407 expandableTextbox has inconsistent form validation Change By: pjdarton Summary: Support expandableTextbox has inconsistent form validation Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160071.142113908.9770.1570029540620%40Atlassian.JIRA.
[JIRA] (JENKINS-26407) Support expandableTextbox form validation
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-26407 Support expandableTextbox form validation Change By: pjdarton Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160071.142113908.9765.1570029540568%40Atlassian.JIRA.
[JIRA] (JENKINS-54155) Jobs using docker agents disrupt each other if triggered simultaneously
Title: Message Title pjdarton commented on JENKINS-54155 Re: Jobs using docker agents disrupt each other if triggered simultaneously Re: What else? A nice short & simple way of reproducing the issue would be ideal See https://github.com/jenkinsci/docker-plugin/blob/master/CONTRIBUTING.md#reporting-a-new-issue In this case, I'd want to look at the clouds/templates defined in config.xml and the pipeline code you're running but, if there's nothing obvious there, a full repro case using just the official default slave images would be needed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194784.1539930502000.9587.1570011840161%40Atlassian.JIRA.
[JIRA] (JENKINS-54499) Loosing connection to Docker container
Title: Message Title pjdarton closed an issue as Fixed This was fixed in PR-693 and that was released in version 1.1.6 Jenkins / JENKINS-54499 Loosing connection to Docker container Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.go
[JIRA] (JENKINS-58712) Docker tool configuration over Jenkins slaves
Title: Message Title pjdarton closed an issue as Not A Defect It doesn't work that way... Builds run on slave nodes. If your slave nodes don't have the docker client on them and don't have access to a docker daemon then your slave nodes have no docker capabilities, which is why your attempts to use those missing capabilities are failing. A machine without the docker daemon on it (and running) can't contain docker containers. A machine without a docker client on it can't talk to a docker daemon about docker containers. The docker-commons-plugin provides a Java docker client that's used by the docker-plugin to talk to docker daemons, but that capability is there for the Jenkins master and isn't really exposed to the slave nodes. If you want to run docker commands as part of a build process on a build slave node then you need to have build slave nodes that have the docker client on them and they either a link to another docker daemon (whether that's via the DOCKER_HOST env var or by cross-mounting /var/lib/docker.sock from the docker host into a docker container) or (to keep things nice and simple and isolated) their own running docker daemon (less efficient, but much simpler as every build gets its own docker daemon, so you don't get nasty collisions). TL;DR: If you want docker on your slave nodes, you need to install docker on your slave nodes. Jenkins / JENKINS-58712 Docker tool configuration over Jenkins slaves Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-58561 Seeing issue when i tried to push an image to ECR using docker pipeline plugin Change By: pjdarton Component/s: docker-workflow-plugin Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200711.1563472694000.4350.1569340140347%40Atlassian.JIRA.
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title pjdarton commented on JENKINS-58561 Re: Seeing issue when i tried to push an image to ECR using docker pipeline plugin Wrong component, sorry. You're using the docker-workflow-plugin, not the docker-plugin. I'll edit the "component affected" field... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200711.1563472694000.4347.1569340140298%40Atlassian.JIRA.
[JIRA] (JENKINS-58582) pending—'Jenkins' doesn't have label 'agent'
Title: Message Title pjdarton commented on JENKINS-58582 Re: pending—'Jenkins' doesn't have label 'agent' My guess is that your docker container doesn't have a /home/jenkins/ folder which is why, when you try to start a container using a template that's saying remoteFs='/home/jenkins', it's blowing up with a "not found" error. You need to ensure that the template configuration is correct for the docker image you're using. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200736.1563683406000.4344.1569340020384%40Atlassian.JIRA.
[JIRA] (JENKINS-58390) Docker cloud provisioning 1 slave behind
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58390 Docker cloud provisioning 1 slave behind Change By: pjdarton Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200514.1562609303000.4322.1569339780203%40Atlassian.JIRA.
[JIRA] (JENKINS-58712) Docker tool configuration over Jenkins slaves
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58712 Docker tool configuration over Jenkins slaves Change By: pjdarton Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201004.1564419517000.4325.1569339840408%40Atlassian.JIRA.
[JIRA] (JENKINS-58582) pending—'Jenkins' doesn't have label 'agent'
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58582 pending—'Jenkins' doesn't have label 'agent' Change By: pjdarton Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200736.1563683406000.4335.1569339840533%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) SPAM-Not an issue
Title: Message Title pjdarton closed an issue as Not A Defect Jenkins / JENKINS-58983 SPAM-Not an issue Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201332.1566190633000.4319.1569339600434%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) SPAM-Not an issue
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58983 SPAM-Not an issue Change By: pjdarton Summary: Jual Obat Erogan Asli Di Riau 0812 SPAM - 8282-3454 Gratis Ongkir Not an issue URL: https://agenobatbentrap.siterubix.com/ Priority: Minor Trivial Labels: plugin Released As: Jual Obat Erogan Asli Di Riau, Jual Obat Erogan Di Riau, Jual Erogan Di Riau, Erogan Asli Di Riau, Harga Jual Obat Erogan Di Riau, Erogan Di Riau, Agen Jual Erogan Di Riau. Environment: Jual Obat Erogan Asli Di Riau 081-2828-23454 Sprint: Post-launch Assignee: Joseph Petersen Add Comment
[JIRA] (JENKINS-59190) SPAM-Not an issue
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-59190 SPAM-Not an issue Change By: pjdarton Summary: Pusat Jual Obat Viagra Asli Dari Dokter Obat Kuat Herbal Di Apotik Bali SPAM-Not an issue URL: https://jualtitangelbali.com/jual-viagra-asli-bali/ Priority: Minor Trivial Labels: obatkuat viagra Assignee: Piyex Tokwae Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59190) SPAM-Not an issue
Title: Message Title pjdarton closed an issue as Not A Defect Jenkins / JENKINS-59190 SPAM-Not an issue Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201631.1567441109000.4314.1569339480389%40Atlassian.JIRA.
[JIRA] (JENKINS-59226) Add support for declarative pipeline
Title: Message Title pjdarton commented on JENKINS-59226 Re: Add support for declarative pipeline I have no idea how to do that ... but if you can find another plugin whose functionality can be called from a pipeline like that (and provide an example of its use), then I might take a look at how to do the same thing with this plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201683.1567606546000.4308.1569339120272%40Atlassian.JIRA.
[JIRA] (JENKINS-59226) Add support for declarative pipeline
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-59226 Add support for declarative pipeline Change By: pjdarton Assignee: tspengler Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201683.1567606546000.4304.1569339060189%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton resolved as Fixed Fixed in plugin version 2.21, which was released a few minutes ago. Jenkins / JENKINS-46375 vSphere template definition doesn't allow environment variables to be defined Change By: pjdarton Status: In Progress Resolved Assignee: pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received t
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title pjdarton resolved as Fixed Fixed in plugin version 2.21, which was released a few minutes ago. Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: pjdarton Status: In Progress Resolved Assignee: pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message becaus
[JIRA] (JENKINS-58136) vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration
Title: Message Title pjdarton updated JENKINS-58136 Fixed in plugin version 2.21, which was released a few minutes ago. Jenkins / JENKINS-58136 vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration Change By: pjdarton Status: Fixed but Unreleased Resolved Assignee: Rudolf-Walter Kiss-Szakacs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenk
[JIRA] (JENKINS-58033) error when remove docker slave
Title: Message Title pjdarton closed an issue as Not A Defect It's not a bug. The docker-plugin uses the dockerjava library and the dockerjava library (needlessly) logs a lot of exceptions as "SEVERE" that are part of its official API, that are perfectly normal and are passed up to the calling code (the docker-plugin) to decide what to do about it. The dockerjava library is a bit of a drama queen - you can ignore 99.999% of these exceptions. Most of what it logs is just saying something line "OMG! Red alert! Panic! Something normal happened!" e.g. if you ask it (dockerjava) to stop a container that's already stopped, it'll tell you that the container has already stopped, so you know that you can then go ahead and then ask it to remove it ... but it'll also log an error along the lines of "It's a total disaster! We didn't actually need to do anything after all". Similarly, when we're making sure a container is gone, we'll ask it to remove the container and, if there's nothing to be done because the container no longer exists, it'll log severe exceptions as it panics about the fact that what it'd been asked to do had already been done and no further action was necessary. Sadly, there's no way of telling it not to log the exceptions that it's also passing back to whatever called it (the docker-plugin code in this case, which knows that no panic is necessary in this situation). All you can do is filter those out of the log. The problem is that sometimes dockerjava really does have something worth mentioning and, in such cases, an exception will get passed up by the dockerjava code to whatever was calling it, and "whatever was calling it" will have an exception it doesn't know how to handle ... at which point "whatever was calling it" will log an error, so you'll see the dockerjava exception is immediately followed by the "whatever was calling it" error. In such circumstances, the exception that dockerjava logged may provide useful additional information as to what actually went wrong. TL;DR: Ignore everything logged by dockerjava unless it's also accompanied by an error raised by other (less shouty) code. Jenkins / JENKINS-58033 error when remove docker slave Change By: pjdarton Status: Open Closed Assignee: Nicolas De Loof Resolution: Not A Defect
[JIRA] (JENKINS-56624) docker.build
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-56624 docker.build Change By: pjdarton Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198251.1553020753000.4216.1569330240184%40Atlassian.JIRA.
[JIRA] (JENKINS-54155) Jobs using docker agents disrupt each other if triggered simultaneously
Title: Message Title pjdarton commented on JENKINS-54155 Re: Jobs using docker agents disrupt each other if triggered simultaneously This is probably because docker containers are specifically designed to do one and only one job and then be destroyed. If you're having more than one bit of work run on a container then that's not going to go well - you need to ensure that your pipeline code takes over one node exclusively and uses it exclusively until it's done with it - no sharing. If you've got multiple pipelines all after the same template then Jenkins should spin up multiple containers for that workload - we shouldn't have any jobs sharing containers... I'm sorry I don't have a specific answer for this one - if it's still an problem with the latest release then please do see what else you can find out; of not, please close the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194784.1539930502000.4213.1569330180159%40Atlassian.JIRA.
[JIRA] (JENKINS-53668) hudson.remoting.ChannelClosedException
Title: Message Title pjdarton closed an issue as Incomplete Without further information, it won't be possible to debug this. If you're still experiencing this issue, and getting it with a recent version of the plugin, please add log information (see https://github.com/jenkinsci/docker-plugin/blob/master/CONTRIBUTING.md for hints about this) and re-open the issue. Jenkins / JENKINS-53668 hudson.remoting.ChannelClosedException Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title pjdarton commented on JENKINS-53259 Re: Jenkins Pipeline build fails when trying to jenkins docker plugin FYI pipeline code like withDockerServer means you're using the docker-workflow-plugin not the docker-plugin. I've updated the "components" field accordingly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193334.1535391573000.4199.1569329580261%40Atlassian.JIRA.
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-53259 Jenkins Pipeline build fails when trying to jenkins docker plugin Change By: pjdarton Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193334.1535391573000.4191.1569329520323%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-53208 Split main configuration page, takes too long to load Change By: pjdarton Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193234.1535030695000.4189.1569329340401%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-53208 Split main configuration page, takes too long to load Change By: pjdarton Over time, we encountered that the main Jenkins configuration page took longer and longer to load. We suspect that this stems from an ever increasing number of Docker agent templates defined in clouds , which also multiplies by the number of configured Docker clouds.It would therefor be nice if some parts were seprated separated from the main configuration, namely said Docker clouds incl. agent templates and maybe the global environment variables (we also have quite a few of them). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msg
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton commented on JENKINS-53208 Re: Split main configuration page, takes too long to load I think that this issue isn't really about the docker-plugin, but it's more about the core - when there are a lot of "cloud" instances configured, the main config page takes ages to load. We've got the same symptoms, but that's mostly from vSphere and OpenStack clouds - there's a lot of field verification going on all at once, and this takes time. FYI one of the changes I made to the docker plugin was to hide a lot of information within "optional" sections so that the web-page wasn't horribly long by default, allowing the Jenkins admin to only "expand" the sections they were interested in, but this doesn't make much difference to loading speed, only to the visual appearance and navigability of the page. I think the solution here is for the core to automatically split out the "Clouds" bit into multiple pages when it starts to get large. That isn't an enhancement that belongs to the docker-plugin, that's a wider issue. What I would suggest is that the Jenkins main jelly code has some sort of "if clouds.size>=1 then punt Clouds into its own page" logic, e.g. have a separate "Clouds" section that magically appears when clouds.size>=1 and have the "Clouds" section in the main config magically turn from the current menu/list (that can become huge and slow) into a link to that new page whenever clouds.size >= 1. ...or, alternatively, make it unconditional, much like what was done when the Jenkins "thread dump" functionality was moved to its own page. Either way, it's not something that the docker-plugin can do on its own - that's a core issue. I'll amend the "components" field accordingly... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-45227) Need support for docker labels ( --label )
Title: Message Title pjdarton closed an issue as Fixed Jenkins / JENKINS-45227 Need support for docker labels ( --label ) Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183357.1498777378000.4159.1569328260725%40Atlassian.JIRA.
[JIRA] (JENKINS-45227) Need support for docker labels ( --label )
Title: Message Title pjdarton commented on JENKINS-45227 Re: Need support for docker labels ( --label ) Support for setting user-specified labels was added by PR-747. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183357.1498777378000.4157.1569328260702%40Atlassian.JIRA.
[JIRA] (JENKINS-33627) Docker Plug-in: Changelog is not generated
Title: Message Title pjdarton closed an issue as Incomplete Jenkins / JENKINS-33627 Docker Plug-in: Changelog is not generated Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169074.1458231512000.4152.1569328020276%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title pjdarton commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters FYI withDockerRegistry etc come from the docker-workflow-plugin, not the docker-plugin. I've updated the components field accordingly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.4150.1569327840380%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-58837 withDockerRegistry on multiple clusters Change By: pjdarton Component/s: docker-workflow-plugin Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.4145.1569327720237%40Atlassian.JIRA.
[JIRA] (JENKINS-55789) Document expected bug 23212 - idle timeout overrides boot
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-55789 Document expected bug 23212 - idle timeout overrides boot Change By: pjdarton [ This 2014 comment |https://issues.jenkins-ci.org/browse/JENKINS-23212?focusedCommentId=204868&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-204868] is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect." However, I cannot find this documented anywhere and it should be on the plugin page – or fixed. Idle timeout should not start counting down until after the connect is complete. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To un
[JIRA] (JENKINS-55789) Document expected bug 23212 - idle timeout overrides boot
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-55789 Document expected bug 23212 - idle timeout overrides boot Change By: pjdarton [This comment from JENKINS-23212 |https://issues.jenkins-ci.org/browse/JENKINS-23212?focusedCommentId=204868&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-204868] is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect."However, I cannot find this documented anywhere and it should be on the plugin page – or fixed. Idle timeout should not start counting down until after the connect is complete. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" grou
[JIRA] (JENKINS-54666) vsphere plugin job succesful but VMs in vcenter not created
Title: Message Title pjdarton closed an issue as Incomplete If you want to raise an enhancement request, you'll need to add a lot more information describing exactly what it is you want done ... and then you'll probably end up having to implement it yourself. With the description as-is, this is user-error being hidden by JENKINS-38472 - the logs show what the issue is but the build isn't reporting the error. If there's a specific enhancement that you think would help (aside from JENKINS-38472) feel free to re-open and provide a full description. Jenkins / JENKINS-54666 vsphere plugin job succesful but VMs in vcenter not created Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53093) Don't wait for VM IP on vsphere expose info step
Title: Message Title pjdarton commented on JENKINS-53093 Re: Don't wait for VM IP on vsphere expose info step Looks like the code was enhanced in version 2.16 to implement a "waitForIp4" parameter that'd for the IP address to become available. I've looked at the code and, as far as I can make out, IF that flag is set to true THEN the action will wait indefinitely for the IP address to appear. There's no indication of any looping in your logs so I suspect that the waitForIp4 field is not set to "true". ...it also looks like there's no public Boolean getWaitForIp4() method so it might be very easy for this flag to get set to false when the action is saved. It could be that this flag only works correctly when invoked from a Jenkins pipeline build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193088.1534510405000.4136.1569327000160%40Atlassian.JIRA.
[JIRA] (JENKINS-53086) vSphere plugin fails to start a VM for pipeline jobs that request a node with no specific label
Title: Message Title
pjdarton commented on JENKINS-53086
Re: vSphere plugin fails to start a VM for pipeline jobs that request a node with no specific label
Yes, I have to agree with you there - that's a bug. It's not a bug I have time to fix myself, but I can at least point the way forwards so, if anyone feels like having a go and submitting a PR that fixes the issue, please do. So the issue is that the provision(label,number) method isn't using the same (null-proof) logic as the getTemplates(label) method to determine if a node matches the given label or not. What's needed is to extract that null-proof logic into a method that we can call from both places, and then use it from both methods. So, I'd guess that what we need is a common method
private static boolean meetsLabelRequirements(final Label requirements, final Mode actualMode,
final Set actualLabel) {
if (actualMode == Node.Mode.NORMAL) {
if (requirements == null || requirements.matches(actualLabel)) {
return true;
}
} else if (actualMode == Node.Mode.EXCLUSIVE) {
if (requirements != null && requirements.matches(actualLabel)) {
return true;
}
}
return false;
}
...and then to refactor the getTemplates(final Label label) method so that it says
private List getTemplates(final Label requirements) {
if (this.templates == null)
return Collections.emptyList();
List matchingTemplates = new ArrayList();
for (vSphereCloudSlaveTemplate t : this.templates) {
final Set actualLabel = t.getLabelSet();
final Mode actualMode = t.getMode();
if (meetsLabelRequirements(requirements, actualMode, actualLabel)) {
matchingTemplates.add(t);
}
}
return matchingTemplates;
}
to change the buggy line in the provision method to be
if (n.getComputer().isOffline() && meetsLabelRequirements(label, n.getMode(), n.getAssignedLabels())) {
...and (and this is the bit I don't have time for) test it to make damned sure that it's not broken anything and that it fixes the problem. If it's all ok, wrap it up in a pull-request referencing this issue (see https://github.com/jenkinsci/vsphere-cloud-plugin/blob/master/CONTRIBUTING.md for more details). If you, or someone else, does that, I'd be happy to review and merge it so it'll be in the next release.
[JIRA] (JENKINS-50690) Cannot log in to vSphere with plugin 2.17
Title: Message Title pjdarton closed an issue as Not A Defect Version 2.17 enabled HTTPS certificate validation by default. Prior to that, the vSphere plugin always disabled SSL certificate validation, which was a security flaw as it opened up Jenkins to a man-in-the-middle attack. FYI the security fix there was to change a "disable security check" boolean that was hard-coded to "true" into a user-configurable field that defaulted to "false" for anyone upgrading. So, while 2.17 fixed that security flaw by enabling SSL validation, you can turn it off again through the configuration UI which, while that leaves you an in insecure state (just like 2.16 and earlier), it means that the way the plugin connects is exactly the same as it was in 2.16 and earlier. So, short term, you can tick the "Disable SSL Check" box (Manage Jenkins -> Configure System, scroll down to the vSphere Cloud section). Long term, I think you're going to have to fix your certificate errors so that you don't have to disable security features to make things work... Jenkins / JENKINS-50690 Cannot log in to vSphere with plugin 2.17 Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-48024) vSphere plugin waits forever attempting to power-off a VM that is already powered-off
Title: Message Title pjdarton commented on JENKINS-48024 Re: vSphere plugin waits forever attempting to power-off a VM that is already powered-off According to the code, it's checking and only telling vSphere to turn the VM off if vSphere says the VM is powered on (or suspended, if the "even if suspended" flag is set). Even then, it only waits until vSphere says it's powered-off. i.e. "that shouldn't happen". Can you verify that this is (still) an issue with the current version of the plugin? If so, can you provide a repro case (e.g. a pipeline script) that demonstrates the issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186564.1510747848000.4100.1569323100307%40Atlassian.JIRA.
[JIRA] (JENKINS-42811) Vsphere Cloud plugin stops working after a number of builds
Title: Message Title pjdarton commented on JENKINS-42811 Re: Vsphere Cloud plugin stops working after a number of builds First, is this still a problem with the current version (2.20) of the plugin? If not, please close the issue. If it is... when you say "the following error appears in the main Jenkins.log file", what error do you mean? The log shows no errors, only "INFO" and "WARNING". As for your ingenious workaround... creating a new vSphereCloud instance and passing in an instanceCap of 0 will result in an instanceCap of Integer.MAX_VALUE (2147483647); that's expected. It's ugly, sure, but it is expected. There's a lot of code in this plugin that's evolved over time and is "just about good enough" - if folks were to rewrite it today, coding against Jenkins as it is right now, it could look a lot neater, but this is old code, so it's got a few wrinkles. By repeatedly re-creating the templates, you're defeating the plugin's ability to track what VMs exist, which may well result in duplicate slave/VM names, and maybe causing yourself a memory leak; that shouldn't be necessary and, as far as I am aware (as "it works for me"), is not necessary. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jen
[JIRA] (JENKINS-42538) Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave
Title: Message Title pjdarton commented on JENKINS-42538 Re: Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave Elliott Jones Can you see if the issue is fixed in version 2.7 but broken in version 2.8? FYI a change was made that disallowed "flyweight tasks" from running on vSphere nodes. This was done because vSphere nodes can be turned off, restarted etc when they've finished their main work and, if a "flyweight task" happens to be running on them when that happens, it'll break the "flyweight task" process. I'm unfamiliar with flow jobs but I do wonder if these make use of "flyweight tasks" to run and that'd be why they're unable to run on vSphere nodes on newer versions of the plugin. If that's the case, it'd be relatively straightforward to make the "don't allow flyweight tasks to run here" behavior a configurable tick-box option... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179467.1488891146000.4079.1569321300159%40Atlassian.JIRA.
[JIRA] (JENKINS-39279) Add ability to add/remove/verify USB device connections
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-39279 Add ability to add/remove/verify USB device connections Change By: pjdarton Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175710.1477509819000.4057.1569320100745%40Atlassian.JIRA.
[JIRA] (JENKINS-39279) Add ability to add/remove/verify USB device connections
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-39279 Add ability to add/remove/verify USB device connections Change By: pjdarton Assignee: pjdarton Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175710.1477509819000.4046.1569320040182%40Atlassian.JIRA.
[JIRA] (JENKINS-38959) vSphere plugin doesn't change behavior option once node goes offline and remember only first time selected option
Title: Message Title pjdarton closed an issue as Incomplete Closing due to incomplete problem description. If this is still an issue, feel free to re-open, but include a lot more information, i.e. a full description of how to reproduce the problem, what happens at present, and what you think should happen instead. Jenkins / JENKINS-38959 vSphere plugin doesn't change behavior option once node goes offline and remember only first time selected option Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You recei
[JIRA] (JENKINS-38959) vSphere plugin doesn't change behavior option once node goes offline and remember only first time selected option
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-38959 vSphere plugin doesn't change behavior option once node goes offline and remember only first time selected option Change By: pjdarton Summary: vSphre vSphere plugin doesn't change behavior option once node goes offline and remember only first time selected option Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175376.1476357955000.4033.1569319860144%40Atlassian.JIRA.
[JIRA] (JENKINS-30858) Slave Agent does not Disconnect During Windows Shutdown Sequence
Title: Message Title pjdarton closed an issue as Done Looks like this was solved in JENKINS-21810 Jenkins / JENKINS-30858 Slave Agent does not Disconnect During Windows Shutdown Sequence Change By: pjdarton Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://group
[JIRA] (JENKINS-33129) Unable to change virtual machine port group
Title: Message Title pjdarton closed an issue as Not A Defect While the exception handling could be improved (y'all free to submit a PR for that...) this was user-error. Jenkins / JENKINS-33129 Unable to change virtual machine port group Change By: pjdarton Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegro
[JIRA] (JENKINS-31735) Remoting : NioChannelHub is not currently running
Title: Message Title pjdarton closed an issue as Cannot Reproduce "it works for me" I know it's not much comfort if it doesn't work for you, but it does work. FYI there's (now) lots of information on the plugin's wiki page regarding how to get Windows VMs to work. Windows makes things non-trivial, but it's not a Jenkins bug or a vSphere plugin bug. Jenkins / JENKINS-31735 Remoting : NioChannelHub is not currently running Change By: pjdarton Status: Open Closed Assignee: Kohsuke Kawaguchi Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-28930) Make VSphereBuildStepContainer implement SimpleBuildStep
Title: Message Title pjdarton closed an issue as Fixed Was done ages ago (in 2016); this issue wasn't marked as closed at the time. Jenkins / JENKINS-28930 Make VSphereBuildStepContainer implement SimpleBuildStep Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on
[JIRA] (JENKINS-25292) Allow a "fallback to unclean" timeout in the power off vm
Title: Message Title pjdarton closed an issue as Done The "power off VM" operation (already) does a force-shutdown after a timeout if the clean shutdown didn't work. That came out in version 1.1.11 (July 8th 2014). There's also a power-on operation; just call that after the power-off. Jenkins / JENKINS-25292 Allow a "fallback to unclean" timeout in the power off vm Change By: pjdarton Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-22810) Add support for running tasks on VM using Invoke-VMScript
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-22810 Add support for running tasks on VM using Invoke-VMScript Change By: pjdarton Issue Type: Improvement New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154624.1398801191000.3969.1569317340480%40Atlassian.JIRA.
[JIRA] (JENKINS-35371) Please add option to deploy ova file using vSphere Cloud Plugin
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-35371 Please add option to deploy ova file using vSphere Cloud Plugin Change By: pjdarton Issue Type: Task New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171162.1465210496000.3959.1569317280477%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton commented on JENKINS-46375 Re: vSphere template definition doesn't allow environment variables to be defined You'll be pleased to know that You are correct - this does affect the ws cleanup plugin node property, along with pretty much any other node property. I've fixed this issue in the as-yet-unreleased code, which I'm intending to release "soon" ... which will be "sooner" if you help ... ... you can get a pre-release build from here. Please try it out and let me know if it works for you - that'll help me and help speed up the official release. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184639.1503478575000.1927.1568280001648%40Atlassian.JIRA.
[JIRA] (JENKINS-7116) Doesn't take custom workspace into account
Title: Message Title pjdarton closed an issue as Won't Fix Jenkins runs on the assumption that, when it runs a build, that build has sole ownership of the workspace folder it's running in. If you've got two jobs that both hit the same folder on the same slaves then you've got a problem that you're going to have to resolve yourself (a) by not enabling this plugin for those builds and (b) by ensuring that those builds don't run at the same time. So, given that, in such circumstances, resource collisions are inevitable unless the user takes responsibility for ensuring that nothing goes awry, I think it's reasonable for the user to take steps to avoid this situation. I don't think it's reasonable to expect this plugin to go scanning all jobs loaded by Jenkins looking for workspaces that might collide - that could take a long time. ...although, if someone wants to write code that'll do that and make it an optional thing (so not every build has to do that) then I guess that'd be an option. Jenkins / JENKINS-7116 Doesn't take custom workspace into account Change By: pjdarton Status: Open Closed Resolution: Won't Fix Add Comment
[JIRA] (JENKINS-53636) not first time build project，but tip"ERROR: Invalid project setup: Connection reset ERROR: Processing failed due to a bug in the code"
Title: Message Title pjdarton closed an issue as Incomplete Closing: Insufficient information to find the correct component, and no response from original author. Jenkins / JENKINS-53636 not first time build project，but tip"ERROR: Invalid project setup: Connection reset ERROR: Processing failed due to a bug in the code" Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194121.1537256474000.2646.1567080960541%40Atlassian.JIRA.
[JIRA] (JENKINS-56342) javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems
Title: Message Title pjdarton closed an issue as Cannot Reproduce OK, firstly, Jenkins version 1.533 is ancient - chances are your problem will be resolved by using a recent version; hell, chances are that the problem was caused by you trying to use an ancient version of Jenkins with plugins that require a later version. Try with the latest LTS Jenkins - if you can reproduce this issue with that then re-open the issue (and provide an updated stacktrace) and give a full description of how to reproduce the issue. Secondly, it doesn't look like this stacktrace has anything to do with the hudson-wsclean-plugin - there's no mention of its code in that stacktrace and it has nothing to do with SCM triggers - any failure to save things due to missing classes of that type are unlikely to be related to that plugin. So, if you do re-open the issue, please change the "component/s" field to where the problem actually is (which is likely "core" given the stacktrace above) ... but first you need to reproduce the issue using a modern version of Jenkins. Jenkins / JENKINS-56342 javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment
[JIRA] (JENKINS-56342) javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-56342 javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems Change By: pjdarton Assignee: tspengler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197928.1551449451000.2642.1567080360276%40Atlassian.JIRA.
[JIRA] (JENKINS-14519) Misses some slaves when changing label expression of job
Title: Message Title pjdarton resolved as Fixed This was fixed in version 1.0.6, which was released yesterday. The plugin can now be configured to look at where the build actually ran instead of looking at where future builds could run. Jenkins / JENKINS-14519 Misses some slaves when changing label _expression_ of job Change By: pjdarton Status: Open Resolved Assignee: tspengler pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://g
[JIRA] (JENKINS-58493) Add NodeProperty to skip-clean-on-this-node
Title: Message Title pjdarton resolved as Fixed Fixed in version 1.0.6, which was released today. Jenkins / JENKINS-58493 Add NodeProperty to skip-clean-on-this-node Change By: pjdarton Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200632.1563189253000.2032.1566997440135%40Atlassian.JIRA.
[JIRA] (JENKINS-58492) Improve robustness w.r.t. bad slave nodes
Title: Message Title pjdarton resolved as Fixed Fixed in version 1.0.6, which was released today. Jenkins / JENKINS-58492 Improve robustness w.r.t. bad slave nodes Change By: pjdarton Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200631.1563187768000.2033.1566997500854%40Atlassian.JIRA.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title pjdarton resolved as Fixed Fixed in version 1.0.6, which was released today. Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: pjdarton Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180392.1490961803000.2028.1566997380611%40Atlassian.JIRA.
[JIRA] (JENKINS-41567) Vsphere plugin and dynamic slaves
Title: Message Title pjdarton commented on JENKINS-41567 Re: Vsphere plugin and dynamic slaves I have no idea if your usecase is possible - I'd guess it is as most things are possible (especially using a pipeline), but I don't know how, and this isn't the place for general support questions. I'd suggest you ask in the Jenkins forums about how to alternate between master & slave contexts - your usecase is unlikely to be specific to the vSphere plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178383.1485795093000.505.1566897002656%40Atlassian.JIRA.
[JIRA] (JENKINS-58136) vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration
Title: Message Title pjdarton commented on JENKINS-58136 Re: vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration Che Duro FYI you can download a preview of the next release here: vsphere-cloud.hpi. Please can you can test this and verify that this fixes the issue you raised. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200181.1561105641000.7742.1566470700157%40Atlassian.JIRA.
[JIRA] (JENKINS-58136) vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration
Title: Message Title pjdarton updated JENKINS-58136 PR#106 has been merged in and will be included in the next release. i.e. This is fixed in the next release. Jenkins / JENKINS-58136 vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration Change By: pjdarton Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200181.1561105641000.7725.1566467940544%40Atlassian.JIRA.
[JIRA] (JENKINS-7116) Doesn't take custom workspace into account
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-7116 Doesn't take custom workspace into account Change By: pjdarton Assignee: tspengler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137213.1280728436000.6830.1566385980201%40Atlassian.JIRA.
[JIRA] (JENKINS-7116) Doesn't take custom workspace into account
Title: Message Title pjdarton commented on JENKINS-7116 Re: Doesn't take custom workspace into account My optimism was misplaced - when the code runs, it has a fairly myopic view of the world and only sees the project/job that it's running within. To fix this issue properly, it would be necessary for the code, once it has an idea of what workspaces (on what slaves) it might want to remove, to then iterate across the entire Jenkins configuration, asking each project in turn where their "current" workspace is, and then removing this from the list of workspaces to be cleaned. That's unlikely to be quick. ...and I guess it should also iterate across all currently-running builds and ensure that their workspaces aren't cleaned either (as, in the case of concurrent builds, it's possible to have the same build folder being used on multiple slave nodes). So, while my recent changes will have made this issue easier to fix, they've not fixed it; right now, the only workaround is for users to refrain from enabling the workspace cleanup on jobs that share both workspaces and slaves. One could argue that, in such a case, there's little point in enabling the plugin for those builds as they're re-using the same workspaces anyway, so the end-user impact of not be able to enable the plugin safely in such situations is of limited significance and hence of "minor" significance rather than "major". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137213.1280728436000.6820.1566385920891%40Atlassian.JIRA.
[JIRA] (JENKINS-7116) Doesn't take custom workspace into account
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-7116 Doesn't take custom workspace into account Change By: pjdarton Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137213.1280728436000.6827.1566385921179%40Atlassian.JIRA.
[JIRA] (JENKINS-58493) Add NodeProperty to skip-clean-on-this-node
Title: Message Title pjdarton commented on JENKINS-58493 Re: Add NodeProperty to skip-clean-on-this-node Update for anyone watching this: I implemented a NodeProperty ... but then found that not all of the cloud plugins I used supported NodeProperties, so I've also added the ability to filter by nodeName as well. There's now a Pull Request that contains a fix for this issue (plus other enhancements). Anyone can download the .hpi file of the bugfixed plugin from there and then upload that (Manage Jenkins -> Manage Plugins ->Advanced -> Upload plugin) to their own Jenkins server(s) to try it out. Once I'm confident that everything is OK then I'll merge those changes in and release the new plugin officially. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200632.1563189253000.6803.1566385140055%40Atlassian.JIRA.
[JIRA] (JENKINS-58492) Improve robustness w.r.t. bad slave nodes
Title: Message Title pjdarton commented on JENKINS-58492 Re: Improve robustness w.r.t. bad slave nodes Update for anyone watching this: There's now a Pull Request that contains a fix for this issue (plus other enhancements). Anyone can download the .hpi file of the bugfixed plugin from there and then upload that (Manage Jenkins -> Manage Plugins ->Advanced -> Upload plugin) to their own Jenkins server(s) to try it out. Once I'm confident that everything is OK then I'll merge those changes in and release the new plugin officially. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200631.1563187768000.6801.1566385020272%40Atlassian.JIRA.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title pjdarton commented on JENKINS-43269 Re: workspace cleanup removes workspaces for running job Update for anyone watching this: There's now a Pull Request that contains a fix for this issue (plus other enhancements). Anyone can download the .hpi file of the bugfixed plugin from there and then upload that (Manage Jenkins -> Manage Plugins ->Advanced -> Upload plugin) to their own Jenkins server(s) to try it out. It would be very helpful if everyone watching this could download and test that these changes fix the issue (and don't introduce any other big problems). You're all welcome to take a look at the code changes and comment on there too, if you're so inclined. Once I'm confident that everything is OK then I'll merge those changes in and release the new plugin officially. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180392.1490961803000.6797.1566384960186%40Atlassian.JIRA.
[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton closed an issue as Won't Do Looks like it wasn't as "in progress" as shown. If I'm wrong, feel free to re-open this and submit a PR that does this. Jenkins / JENKINS-28870 allow specifying target host when cloning a VM Change By: pjdarton Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163328.1434024869000.3636.1565891280351%40Atlassian.JIRA.
