[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 Elliott Jones commented on JENKINS-42538 Re: Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave I also had this issue https://issues.jenkins-ci.org/browse/JENKINS-41384 and thus had to apply jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave
Title: Message Title Elliott Jones updated an issue Jenkins / JENKINS-42538 Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave Change By: Elliott Jones Component/s: vsphere-cloud-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave
Title: Message Title Elliott Jones edited a comment on JENKINS-42538 Re: Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave That seems to be the key factor, during my upgrade I upgraded vSphere Plugin from 2.4 to 2.15. Downgrading back to 2.4 and the flow job works with the label parameter correctly. Updating ticket details appropriately. Marking minor as workaround is simple for me, plugin downgrade. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave
Title: Message Title Elliott Jones updated an issue Jenkins / JENKINS-42538 Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave Change By: Elliott Jones Environment: Master:Jenkins ver. 2.32.2Windows Server 2012 R2 64 bitjre 1.8.0_121 64 bitRunning Jenkins directly installed as windows serviceInstalled Pluginsace-editor 1.1 true falseant 1.4 true falseantisamy-markup-formatter 1.5 true falseauthentication-tokens 1.3 true falsebouncycastle-api 2.16.0 true falsebranch-api 2.0.7 true falsebuild-blocker-plugin 1.7.3 true falsebuild-flow-plugin 0.20 true falsebuild-name-setter 1.6.5 true falsebuild-timeout 1.18 true falsebuild-user-vars-plugin 1.5 true falsebuildgraph-view 1.5.1 true falsebuildresult-trigger 0.17 true falsecloudbees-folder 5.18 true falsecompact-columns 1.10 true falseconditional-buildstep 1.3.5 true falseconfig-file-provider 2.15.6 true falsecredentials 2.1.13 true falsecredentials-binding 1.10 true falsecvs 2.13 true falsedisplay-url-api 1.1.1 true falsedocker-commons 1.6 true falsedocker-workflow 1.10 true falsedurable-task 1.13 true falsedynamicparameter 0.2.0 true falseemail-ext 2.57 true falseenvinject 1.93.1 true falseextended-choice-parameter 0.76 true falseextensible-choice-parameter 1.3.4 true falseexternal-monitor-job 1.7 true falsegit 3.1.0 true falsegit-client 2.3.0 true falsegit-server 1.7 true falsegradle 1.26 true falsegroovy 1.30 true falsegroovy-label-assignment 1.2.0 true falsegroovy-postbuild 2.3.1 true falsehandlebars 1.1.1 true falsehttp_request 1.8.13 true falseicon-shim 2.0.3 true falsejavadoc 1.4 true falsejobConfigHistory 2.15 true falsejquery 1.11.2-0 true falsejquery-detached 1.2.1 true falsejunit 1.20 true falseldap 1.14 true falseleastload 1.0.3 true falselog-parser 2.0 true falsemailer 1.19 true falsemapdb-api 1.0.9.0 true falsemask-passwords 2.9 true falsematrix-auth 1.4 true falsematrix-project 1.8 true falsemaven-plugin 2.15.1 true falsemomentjs 1.1.1 true falsemonitoring 1.63.0 true falsenode-iterator-api 1.5.0 true falsenodelabelparameter 1.7.2 true falsepam-auth 1.3 true falseparameterized-trigger 2.33 true falsepipeline-build-step 2.4 true falsepipeline-graph-analysis 1.3 true falsepipeline-input-step 2.5 true falsepipeline-milestone-step 1.3 true falsepipeline-model-api 1.0.2 true falsepipeline-model-declarative-agent 1.0.2 true falsepipeline-model-definition 1.0.2 true falsepipeline-rest-api 2.5 true falsepipeline-stage-step 2.2 true falsepipeline-stage-tags-metadata 1.0.2 true falsepipeline-stage-view 2.5 true falseplain-credentials 1.4 true falsepromoted-builds 2.28.1 true falserebuild 1.25 true falserepository-connector 1.1.3 true falseresource-disposer 0.6 true falserole-strategy 2.3.2 true falserun-condition 1.0 true falsescm-api 2.0.8 true falsescript-security 1.27 true falsescriptler 2.9 true falsesimple-theme-plugin 0.3 true falsesitemonitor 0.5 true falsessh-credentials 1.13 true falsessh-slaves 1.13 true falsestructs 1.6 true falsesubversion 2.7.1 true falsetestng-plugin 1.14 true falsetoken-macro 2.0 true falsetranslation 1.15 true falseuno-choice 1.5.2 true falseupdate-sites-manager 2.0.0 true falsevalidating-string-parameter 2.3 true falseview-job-filters 1.27 true falsevsphere-cloud
[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 Elliott Jones updated an issue Jenkins / JENKINS-42538 Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave Change By: Elliott Jones Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave
Title: Message Title Elliott Jones updated an issue Jenkins / JENKINS-42538 Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave Change By: Elliott Jones Summary: Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor when using label parameter to restrict job to vpshere slave Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor
Title: Message Title Elliott Jones commented on JENKINS-42538 Re: Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor That seems to be the key factor, during my upgrade I upgraded vSphere Plugin from 2.4 to 2.15. Downgrading back to 2.4 and the flow job works with the label parameter correctly. Updating ticket details appropriately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor
Title: Message Title Elliott Jones commented on JENKINS-42538 Re: Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor Tried this with a clean install windows intall of 2.32.2 using just the Build Flow and Node and Label parameter plugins: ant 1.4 true false antisamy-markup-formatter 1.5 true false bouncycastle-api 2.16.0 true false build-flow-plugin 0.20 true false display-url-api 1.1.1 true false external-monitor-job 1.7 true false icon-shim 2.0.3 true false
[JIRA] (JENKINS-42538) Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor
Title: Message Title Elliott Jones commented on JENKINS-42538 Re: Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor I thought it could be related to this issue https://issues.jenkins-ci.org/browse/JENKINS-34969 due to similar plugins but nothing on that ticket helps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor
Title: Message Title Elliott Jones updated an issue Jenkins / JENKINS-42538 Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor Change By: Elliott Jones Attachment: Jenkins Issue.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor
Title: Message Title Elliott Jones updated an issue Jenkins / JENKINS-42538 Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor Change By: Elliott Jones Attachment: Jenkins Issue.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42538) Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor
Title: Message Title Elliott Jones created an issue Jenkins / JENKINS-42538 Build Flow jobs only work with slave label parameter when 'master' used otherwise permanently stuck waiting on next available executor Issue Type: Bug Assignee: Craig Rodrigues Attachments: Jenkins Issue.png Components: build-flow-plugin, core, nodelabelparameter-plugin Created: 2017/Mar/07 12:52 PM Environment: Master: Jenkins ver. 2.32.2 Windows Server 2012 R2 64 bit jre 1.8.0_121 64 bit Running Jenkins directly installed as windows service Installed Plugins ace-editor 1.1 true false ant 1.4 true false antisamy-markup-formatter 1.5 true false authentication-tokens 1.3 true false bouncycastle-api 2.16.0 true false branch-api 2.0.7 true false build-blocker-plugin 1.7.3 true false build-flow-plugin 0.20 true false build-name-setter 1.6.5 true false build-timeout 1.18 true false build-user-vars-plugin 1.5 true false buildgraph-view 1.5.1 true false buildresult-trigger 0.17 true false cloudbees-folder 5.18 true false compact-columns 1.10 true false conditional-buildstep 1.3.5 true false config-file-provider 2.15.6 true false credentials 2.1.13 true false credentials-binding 1.10 true false cvs 2.13 true false display-url-api 1.1.1 true false docker-commons 1.6 true false docker-workflow 1.10 true false durable-task 1.13 true false dynamicparameter 0.2.0 true false email-ext 2.57 true false envinject 1.93.1 true false extended-choice-parameter 0.76 true false extensible-choice-parameter 1.3.4 true false external-monitor-job 1.7 true false git 3.1.0 true false git-client 2.3.0 true false git-server 1.7 true false gradle 1.26 true false groovy 1.30 true false groovy-label-assignment 1.2.0 true false groovy-postbuild 2.3.1 true false handlebars 1.1.1 true false http_request 1.8.13 true false icon-shim 2.0.3 true false javadoc 1.4 true false jobConfigHistory 2.15 true false jquery 1.11.2-0 true false jquery-detached 1.2.1 true false junit 1.20 true false ldap 1.14 true false leastload 1.0.3 true false log-parser 2.0 true false mailer 1.19 true false mapdb-api 1.0.9.0 true false mask-passwords 2.9 true false matrix-auth 1.4 true false matrix-project 1.8 true false maven-plugin 2.15.1 true false momentjs 1.1.1 true false monitoring 1.63.0 true false node-iterator-api 1.5.0 true false nodelabelparameter 1.7.2 true false pam-auth 1.3 true false parameterized-trigger 2.33
[JIRA] (JENKINS-18781) Configurable channel timeout for slaves
Title: Message Title Elliott Jones commented on JENKINS-18781 Re: Configurable channel timeout for slaves We have slave disconnect issues and are running on VMware (both master and slave). From the recent available data, the 'Tasks & Events' history does NOT show a 'Migrate virtual machine' entry at the time of disconnect (for either master or the slave or involved). We'll continue to monitor, though we've not had any disconnects since our upgrade to Jenkins 2.7.2 and we used to get 1 or 2 a week. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-32496) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard
Title: Message Title Elliott Jones edited a comment on JENKINS-32496 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard I work with Colin, for us doing a reboot of the server seemed to be the action that triggered the problem to appear in the first place. We'd been running happily and as part of a server change process, stopped everything and took a powered off snapshot. On completion of our server changes the problem was noticed. Restoring our powered off snapshot (and thus having to boot up) still showed the issue , as did subsequent reboots . It's only this post the other issue (14916) that helped us identify the root cause , so thanks! . For reference we're using Jenkins ver. 1.593 and View Job Filters 1.26 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32496) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard
Title: Message Title Elliott Jones commented on JENKINS-32496 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard I work with Colin, for us doing a reboot of the server seemed to be the action that triggered the problem to appear in the first place. We'd been running happily and as part of a server change process, stopped everything and took a powered off snapshot. On completion of our server changes the problem was noticed. Restoring our powered off snapshot (and thus having to boot up) still showed the issue. It's only this post that helped us identify the root cause, so thanks! For reference we're using Jenkins ver. 1.593 and View Job Filters 1.26 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-24287) EnvInject exposes password hashes
Elliott Jones commented on JENKINS-24287 EnvInject exposes password hashes Any thoughts on this being fixed? We have to use passwords managed by a separate IT team for our CI process thus this issue is of concern to them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-25821) Global Mask Password are visible as a plain text in Environment Variables tab
Elliott Jones commented on JENKINS-25821 Global Mask Password are visible as a plain text in Environment Variables tab Even if this (JENKINS-25821) is fixed, this issue JENKINS-24287 still allows hashed passwords to be shown in plain text. It's more work but ultimately still exposes passwords in plain text. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
