[JIRA] (JENKINS-42763) Env var HOME for containers has regressed
Title: Message Title Parag Doke commented on JENKINS-42763 Re: Env var HOME for containers has regressed I think inheriting from a template is a workaround. Why make it mandatory for everyone to: 1) Have an invalid HOME 2) Else inherit from a template If their kube cluster is not on OpenShift. I think we need to fix this the right way ... which should be to add an optional param (ensure HOME is valid ... or something to that effect). I wish I were better at development ... would make an attempt and raise a PR myself. 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-42763) Env var HOME for containers has regressed
Title: Message Title Parag Doke commented on JENKINS-42763 Re: Env var HOME for containers has regressed CC Nicolas De Loof, @drcapulet, Ioannis Canellos 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-42763) Env var HOME for containers has regressed
Title: Message Title
Parag Doke created an issue
Jenkins / JENKINS-42763
Env var HOME for containers has regressed
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Mar/14 5:34 PM
Environment:
Jenkins ver. 2.7.21.0.1 (CloudBees Jenkins Enterprise 2.7.21.0.1-fixed) Kubernetes plugin version 0.9
Priority:
Major
Reporter:
Parag Doke
Since version 0.7 of kubernetes-plugin, due to PR https://github.com/jenkinsci/kubernetes-plugin/pull/57, a change was made that I think is specific to some kubernetes cloud environments (openshift), but not all. For instance, I have a Jenkins instances connected to a kubernetes cluster, and don't want HOME to be set to working directory. I also saw https://github.com/jenkinsci/kubernetes-plugin/pull/128 that attempted to address some points, but (correct me if I am wrong), we'd still need to set HOME on each pod template. I think a better way of fixing the problem would be to introduce a checkbox on the cloud config level ... that says something to the effect of "Ensure functional HOME folder" (to begin with). Such a param would remove the need for each pod template to be configured ... and yet allow Jenkins admin(s) to get the desired effect in case of openshift. Needless to say, this would be conditional:
env.put("HOME", containerTemplate.getWorkingDir());
[JIRA] [build-flow-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke commented on JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Works on Jenkins 1.597. Broken on 1.598 (other things being constant). 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] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke commented on JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node I tried this combination today and it was able to identify a vsphere slave node correctly: vsphere-cloud version 2.3 build-flow plugin version 0.16 Jenkins version 1.583 Out of curiosity, I updated both plugins ... and let Jenkins stay at 1.583. That worked too. So this combination also works: vsphere-slave plugin 2.4 build-flow plugin 0.17 Jenkins version 1.583 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] [build-flow-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Added "build-flow-plugin" as a component. Change By: Parag Doke (30/Mar/15 11:27 AM) Component/s: build-flow-plugin 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] [build-flow-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Added "core" as a component. Change By: Parag Doke (30/Mar/15 11:26 AM) Component/s: core 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke closed JENKINS-26776 as Fixed Jenkins vSphere cloud plugin does not terminate sessions Closing. Change By: Parag Doke (06/Mar/15 6:51 AM) Status: Resolved Closed 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke resolved JENKINS-26776 as Fixed Jenkins vSphere cloud plugin does not terminate sessions Fix appears in version 2.4. Change By: Parag Doke (06/Mar/15 6:51 AM) Status: Open Resolved Resolution: Fixed 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions Didn't figure how to tag. Assigned to Jason instead. I need to learn how to associate a pull request with an existing issue. 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions Testing tagging ... @jswager 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions @jswager1 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke assigned JENKINS-26776 to Jason Swager Jenkins vSphere cloud plugin does not terminate sessions Change By: Parag Doke (03/Mar/15 5:04 AM) Assignee: JasonSwager 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] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke created JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 03/Mar/15 4:56 AM Description: Steps 1) Deploy a Jenkins instance from the appropriate war, and get those 2 plugins installed. 2) Configure a test vcenter, a vsphere cloud slave instance (in my case the configuration was: boot on demand, connect via ssh launcher, shut down when idle after 10 min of idle time). 3) Tie a job to the slave and kick it off. I observe that the build simply sits in queue and never kicks off. Environment: vsphere-cloud plugin version 2.3 build-flow plugin version 0.17 Jenkins build 1.599 [Java / OS does not matter] Project: Jenkins Priority: Blocker Reporter: Parag Doke 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] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Change By: Parag Doke (03/Mar/15 4:57 AM) Environment: vsphere-cloudpluginversion2.3build-flowpluginversion0.17Jenkinsbuild1.599[Java version /OSdoesnotmatter] 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions Jason Swager merged pull request https://github.com/jenkinsci/vsphere-cloud-plugin/pull/26. Don't know the next step. Probably to wait until the next version is out and close this issue after noting the version number? 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] [workflow-plugin] (JENKINS-27076) Need ability to name workspaces
Parag Doke created JENKINS-27076 Need ability to name workspaces Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 23/Feb/15 10:47 AM Description: On configuring a long running job using the workflow plugin and running it in say 2 threads, the standard output from both threads is intermingled. 2nd workspace on the same slave node has "@2" appended, but from loads of build related logging, those 2 characters make it difficult to spot what comes from where. This issue is to implement (or document if already implemented) a feature to optionally name the workspaces with a friendly name that the human can identify with. Environment: Jenkins 1.599 + Workflow aggregator plugin 1.2 running on Windows 7 x64 with Java 1.7 and multiple executors on the master node. Project: Jenkins Priority: Major Reporter: Parag Doke 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] [workflow-plugin] (JENKINS-27078) Need ability to isolate console output from threaded execution
Parag Doke created JENKINS-27078 Need ability to isolate console output from threaded execution Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 23/Feb/15 11:06 AM Description: This is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-27076. Summary: Console logs from threaded executions get intermingled and it is hard to identify what came from where. If there can be a way to isolate console output from multiple workspaces, it will make things far easier to read. Environment: Jenkins 1.599 + Workflow aggregator plugin 1.2 running on Windows 7 x64 with Java 1.7 and multiple executors on the master node. Project: Jenkins Priority: Minor Reporter: Parag Doke 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] [workflow-plugin] (JENKINS-27076) Need ability to name workspaces
Parag Doke commented on JENKINS-27076 Need ability to name workspaces The "name" in this request is synonymous to "tag" / "label" ... purely cosmetic in nature. 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke created JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 04/Feb/15 9:56 AM Description: We use multiple Jenkins versions (as noted in the environment) to boot VMs on a single vCenter for running builds. The vCenter admins noted that the VMware vCenter would receive loads and loads of connections from Jenkins instances ... and the sessions never terminated / closed. I have attempted a fix to this which can be viewed here: https://github.com/ParagDoke/vsphere-cloud-plugin/compare/disconnect-vsphere?expand=1 Disclaimer: I'm a Java noob and have no insight into Jenkins model / functioning (let alone code). Please review with highest caution . For now, we have asked our vCenter admins to upload a locally built hpi. Yet to hear about the results. Environment: VMware vCenter Server 5.1.0, 1123961 Jenkins versions: 1.554.1 1.571 1.588 1.576 1.583 1.598 vSphere Cloud plugin versions: 1.1.10 2.2 Project: Jenkins Priority: Blocker Reporter: Parag Doke 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions This issue is being marked a blocker because it prohibits us from picking up the vsphere-cloud plugin version available on the Jenkins update center (regular as well as stable). However, given that we've deployed a locally built hpi, if downgrading the priority is the right way to go, please feel free to lower it. I also set up a tiny environment (2 ESX systems on junkyard class machines and 1 vCenter running on a VM within) to test my changes. I did notice VMs being powered on and off correctly when using vSphere slave nodes. I am yet to test the build step feature (only planning to test power on and power off). Will share my observations on this issue. 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] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions No problems observed when testing build steps with modified plugin code. 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.
