[JIRA] (JENKINS-39258) nullreferenceException
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-39258 nullreferenceException Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 2016/Oct/26 5:55 AM Environment: Windows Server 2008 R2 Datacenter Priority: Minor Reporter: Ronny Borchert I use Jenkins 2.27 with latest plugin of EnvInject. at hudson.model.Run.getRootDir(Run.java:1014) at org.jenkinsci.lib.envinject.EnvInjectAction.writeReplace(EnvInjectAction.java:98) at sun.reflect.GeneratedMethodAccessor369.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:141) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at
[JIRA] (JENKINS-39201) Unstable build shows up as UNKNOWN (purple vomit)
Title: Message Title Josh McDonald updated JENKINS-39201 Fixed in 47f591995b2360aeb2e828490944a6f892ecfae6 Jenkins / JENKINS-39201 Unstable build shows up as UNKNOWN (purple vomit) Change By: Josh McDonald Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-35821) API to return per node averages, and ETA based on history of execution
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35821 API to return per node averages, and ETA based on history of execution Change By: James Dumay In scope* Data to support JENKINS-35849* We would like to be able to know the:** ETA expected time to completion of a node** how long a node ran for** how long a step executed ** expected completion time of a step** expected 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] (JENKINS-35821) API to return per node averages, and ETA based on history of execution
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35821 API to return per node averages, and ETA based on history of execution Change By: James Dumay In scope* Data to support JENKINS-35849 * We would like to be able to know the:** ETA 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] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Title: Message Title Daniel Beck commented on JENKINS-27722 Re: upgrade to the release plugin has left the plugin broken Weird, 2.6 and up contain the fix for JENKINS-28132 which should result in all administrators getting release permssion. Did you forget to restart Jenkins? 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] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Daniel Beck commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard FTR, this change is part of Jenkins 2.0 and not mentioned anywhere since the feature was added during the 2.0 preview/beta releases and this issue discovered and fixed before 2.0. 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] (JENKINS-35821) API to return per node averages, and ETA based on history of execution
Title: Message Title James Dumay commented on JENKINS-35821 Re: API to return per node averages, and ETA based on history of execution As discussed: There is a low level API in bismuth to retrieve this data. We will use the low level API in Blue Ocean to drive out the requirements of a future higher level API Think of it as a PoC that lives within Blue Ocean that we could either throw away or reuse. Vivek Pandey to meet with Sam Van Oort to co-ordinate how it should be done. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Ioannis Moutsatsos commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Bruno P. Kinoshita Matthias Zangl I can' reproduce the issue o Windows 10, with Jenkins 2.11 and ActiveChoices v1.4. Sorry... 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] (JENKINS-38260) Kubernetes plugin does not respect Container Cap
Title: Message Title Jonathan Rogers commented on JENKINS-38260 Re: Kubernetes plugin does not respect Container Cap BTW, I have switched to Kubernetes CI Plugin. That plugin requires a bit more knowledge about Kubernetes but is more flexible and behaves more correctly in my experience. Specifically, it better respects configured concurrent container count. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Matthias Zangl I could not reproduce the issue. Dean Thackery thank you for trying it out and confirming you were running on Linux too. Here's my set up: Jenkins 1.580.1 and Jenkins 2.19.1 Plug-in version: 1.5-SNAPSHOT, latest in Git Linux Ubuntu 16.04.1 So the best I can guess is that the latest code has some fix, that is not available in 1.14. If that's the case, anyone trying the attached snapshot HPI should be able to test and confirm the issue is gone Cheers Bruno 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Bruno P. Kinoshita Attachment: GIFrecord_2016-10-26_134846.gif 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita edited a comment on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Followed the same steps described earlier. Copied the OPTION_A and OPTION_C scripts that were added in one of the comments above. Here's the screen cast of the result. !GIFrecord_2016-10-26_134846.gif! 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Followed the same steps described earlier. Copied the OPTION_A and OPTION_C scripts that were added in one of the comments above. Here's the screen cast of the result. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Bruno P. Kinoshita Attachment: Screenshot from 2016-10-26 13-46-44.png Attachment: Screenshot from 2016-10-26 13-46-58.png 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Installed latest plug-in, in a brand new Jenkins 2.19.1. Attaching screen shots. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Attached uno-choice-0.15-20161026.hpi, which contains the same code that I used to try to reproduce the issue. Giving it a last try, by trying to run this hpi with a brand new Jenkins LTS war. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Bruno P. Kinoshita Attachment: uno-choice-0.15-20161026.hpi 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] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-39229 Regression: Initial stage run does not show graph Change By: James Dumay Assignee: Vivek Pandey Thorsten Scherler 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita edited a comment on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Attaching a screencast of the job in action. !GIFrecord_2016-10-26_132739.gif! It works without any problem for me. Will produce a snapshot binary and attach it here. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Bruno P. Kinoshita Attachment: GIFrecord_2016-10-26_132739.gif 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Attaching a screencast of the job in action. It works without any problem for me. Will produce a snapshot binary and attach it here. 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] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title Vivek Pandey commented on JENKINS-39229 Re: Regression: Initial stage run does not show graph James Dumay backend API is returning DAG. it might have something to do with UI reacting to SSE and there is some bug in SSE where it deals with blocked scope stages. I tried the same script modified as legacy (non blocked scope) and it appears fine. Brief look at JS code tells me, DAG is drawn using SSE events and not by fetching DAG from node API. Thorsten Scherler please confirm if my evaluation is correct. 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] (JENKINS-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Running with Jenkins 1.580.1, in Eclipse/Maven, in debug mode. Using the latest from the git repository. Created a job, with two parameters, as in the images provided by Matthias. OPTION_A is a simple active choices, with the following script. return [ 'Alpha:selected', 'Beta', 'Gamma'] Then, there is OPTION_C, which is an active reactive reference parameter. It references OPTION_A, and has the following script. return "$OPTION_A" 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] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title Xian Yi Teng updated an issue Jenkins / JENKINS-39189 JOB_NAME includes parameters Change By: Xian Yi Teng Attachment: config.xml 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] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Title: Message Title dma_k commented on JENKINS-27722 Re: upgrade to the release plugin has left the plugin broken I have the same issue with Release Plugin v2.6.1. I use "Logged-in users can do anything" authorization mode and "Matrix-based security" is not an option for me. Richard Otter: What is the workaround? Enable matrix and tick all checkboxes, save, and then switch back to "Logged-in users can do anything"? 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] (JENKINS-39257) p4 plugin escapes/converts plaintext to HTML
Title: Message Title Matthew Hall commented on JENKINS-39257 Re: p4 plugin escapes/converts plaintext to HTML The changelog.xml on disk looks like : [root@ 67]# pwd /home/jenkins/jobs/b-monitoring/builds/67 [root@ 67]# more changelog.xml 953319 redacted-monitoring SUMMARY: Dont reuse variables. DETAILS: The code was trying to create a new properties dict for each topic, but was instead reusing the same one over and over. Make it use a new copy each time. This doesnt cause a functional change, but makes the code cleaner. OTS: redacted (visual OTS) TESTING: None redacted 2016-10-25 14:20:04 false 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] (JENKINS-39257) p4 plugin escapes/converts plaintext to HTML
Title: Message Title Matthew Hall commented on JENKINS-39257 Re: p4 plugin escapes/converts plaintext to HTML To be clear which URL/endpoint I'm referring to : http://jenkins:8080/job/b-monitoring/changes (displays changes correctly) http://jenkins:8080/job/b-monitoring/67/changes (renders the above wrong output) 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] (JENKINS-39257) p4 plugin escapes/converts plaintext to HTML
Title: Message Title
Matthew Hall edited a comment on JENKINS-39257
Re: p4 plugin escapes/converts plaintext to HTML
This is what the change actually looks like when asking the p4 server : {noformat}$ p4 change -o 953319# A Perforce Change Specification.# # Change: The change number . 'new' on a new changelist . # Date:The date this specification was last modified . # Client: The client on which the changelist was created. Read-only.# User:The user who created the changelist.# Status: Either 'pending' or 'submitted'. Read-only.# Type:Either 'public' or 'restricted'. Default is 'public'.# Description: Comments about the changelist. Required.# ImportedBy: The user who fetched or pushed this change to this server.# Identity:Identifier for this change.# Jobs:What opened jobs are to be closed by this changelist.# You may delete jobs from this list. (New changelists only.)# Files: What opened files from the default changelist are to be added# to this changelist. You may delete files from this list.# (New changelists only.) Change: 953319Date: 2016/10/25 14:20:04Client: redacted-monitoringUser: redactedStatus: submittedDescription:SUMMARY: Don't reuse variables. DETAILS: The code was trying to create a new properties dictfor each topic, but was instead reusing the same one over andover. Make it use a new copy each time. This doesn't cause afunctional change, but makes the code cleaner. OTS: redacted (visual OTS) TESTING: None{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39257) p4 plugin escapes/converts plaintext to HTML
Title: Message Title Matthew Hall commented on JENKINS-39257 Re: p4 plugin escapes/converts plaintext to HTML This is what the change actually looks like when asking the p4 server : $ p4 change -o 953319 # A Perforce Change Specification. # # Change: The change number. 'new' on a new changelist. # Date:The date this specification was last modified. # Client: The client on which the changelist was created. Read-only. # User:The user who created the changelist. # Status: Either 'pending' or 'submitted'. Read-only. # Type:Either 'public' or 'restricted'. Default is 'public'. # Description: Comments about the changelist. Required. # ImportedBy: The user who fetched or pushed this change to this server. # Identity:Identifier for this change. # Jobs:What opened jobs are to be closed by this changelist. # You may delete jobs from this list. (New changelists only.) # Files: What opened files from the default changelist are to be added # to this changelist. You may delete files from this list. # (New changelists only.) Change: 953319 Date: 2016/10/25 14:20:04 Client: redacted-monitoring User: redacted Status: submitted Description: SUMMARY: Don't reuse variables. DETAILS: The code was trying to create a new properties dict for each topic, but was instead reusing the same one over and over. Make it use a new copy each time. This doesn't cause a functional change, but makes the code cleaner. OTS: redacted (visual OTS) TESTING: None Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39257) p4 plugin escapes/converts plaintext to HTML
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-39257 p4 plugin escapes/converts plaintext to HTML Change By: Matthew Hall Summary: p4 plugin escapes /converts plaintext to HTML in changelist 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] (JENKINS-39257) p4 plugin escapes HTML in changelist
Title: Message Title Matthew Hall created an issue Jenkins / JENKINS-39257 p4 plugin escapes HTML in changelist Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Oct/25 11:04 PM Environment: jenkins 2.19.1 p4 plugin 1.4.8 Priority: Minor Reporter: Matthew Hall p4 plugin, when inspecting the 'Changes' link, shows all output as escaped and barely readable plaintext with html mixed in. 953319 by userredacted@userredacted-monitoring on Oct 25, 2016 2:20:04 PM SUMMARY: Dont reuse variables. DETAILS: The code was trying to create a new properties dict for each topic, but was instead reusing the same one over and over. Make it use a new copy each time. This doesnt cause a functional change, but makes the code cleaner. OTS: userredacted (visual OTS) TESTING: None Submitted Files: //somepath/somefile.py #3
[JIRA] (JENKINS-26107) Allow stage to operate as a labelled block
Title: Message Title Owen Mehegan commented on JENKINS-26107 Re: Allow stage to operate as a labelled block Kyle Flavin concurrency as a parameter to the stage step is deprecated, in favor of the milestone step. See https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+Step+Plugin and https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin 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] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title
Xian Yi Teng updated an issue
Jenkins / JENKINS-39189
JOB_NAME includes parameters
Change By:
Xian Yi Teng
Comment:
Job config attached. [^config.xml] {code}Jenkins ver. 1.642.4{code}{code}Started by upstream project "XIAN_TENG_TEST_JOB" build number 1originally caused by: Started by user xian.teng[EnvInject] - Loading node environment variables.Building remotely on ubuntu-1204-03-64 (qa_runner admin_linux build_docs 12.04 amd64-Ubuntu Ubuntu amd64-Ubuntu-12.04 Ubuntu-12.04 amd64) in workspace /jenkins_data/jenkins/workspace/XIAN_TENG_TEST_JOB/parameter1_axis/value1/parameter2_axis/value2[value2] $ /bin/sh -xe /tmp/hudson5641186992722460038.sh+ echo build stepbuild step+ echo value1value1+ echo value2value2+ echo XIAN_TENG_TEST_JOB/parameter1_axis=value1,parameter2_axis=value2XIAN_TENG_TEST_JOB/parameter1_axis=value1,parameter2_axis=value2Finished: SUCCESS{code}
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
[JIRA] (JENKINS-39256) Allow stages to appear within nodes
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-39256 Allow stages to appear within nodes Issue Type: Improvement Assignee: Unassigned Components: pipeline-view-plugin Created: 2016/Oct/25 10:20 PM Priority: Major Reporter: Justin Rainwater I think this issue may have already been raised or at least a similar version of it, but I couldnt find an example of exactly what I'm looking for. In a way this is the inverse of this other issue I logged: https://issues.jenkins-ci.org/browse/JENKINS-39119. In pre-pipeline Jenkins we'd have a single job that does git checkout, build, unit test, archive, etc. For pipeline we liked having these nice pretty stages for each of these steps. The problem is that the stash/unstash workflow really slows things down with the only benefit being the pretty stage display. If we put all of these steps into a single stage then it all works great, but then we just have this single green or red box which doesn't feel very 'pipeline-y'. We thought we solved everything when realizing we could save the node information between stages and force downstream stages to run on the same node. That way we could run in the same workspace and avoid the need for all the unstashing. The big catch with this approach is that between stages the node is briefly available so if another job is queued up then it will immediately grab it and the test stage will be stuck waiting for the now busy node. Our team has spent way too long trying to solve this core problem by trying our own methods of reserving a node by adding and removing node labels at the beginning and end of the pipeline. That however has created its own headaches in that modifying the labels doesnt seem reliable. We've also taken a look at the External Workspace Manager plugin but compiling a build over a network share is slower than doing stash/unstash. What would really solve things is if the stage view would let us parallelize for platform x config (so we're running say
[JIRA] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title Xian Yi Teng commented on JENKINS-39189 Re: JOB_NAME includes parameters Job config attached. config.xml Jenkins ver. 1.642.4 Started by upstream project "XIAN_TENG_TEST_JOB" build number 1 originally caused by: Started by user xian.teng [EnvInject] - Loading node environment variables. Building remotely on ubuntu-1204-03-64 (qa_runner admin_linux build_docs 12.04 amd64-Ubuntu Ubuntu amd64-Ubuntu-12.04 Ubuntu-12.04 amd64) in workspace /jenkins_data/jenkins/workspace/XIAN_TENG_TEST_JOB/parameter1_axis/value1/parameter2_axis/value2 [value2] $ /bin/sh -xe /tmp/hudson5641186992722460038.sh + echo build step build step + echo value1 value1 + echo value2 value2 + echo XIAN_TENG_TEST_JOB/parameter1_axis=value1,parameter2_axis=value2 XIAN_TENG_TEST_JOB/parameter1_axis=value1,parameter2_axis=value2 Finished: SUCCESS 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
[JIRA] (JENKINS-36948) return all selected values, when gets the default value
Title: Message Title Bruno P. Kinoshita commented on JENKINS-36948 Re: return all selected values, when gets the default value Hi Boguslaw Klimas, I think the pull request looks good, but maybe we are fixing the wrong issue. When you open the browser, and you have an HTML DOM, the plug-in inspects it, evals the code, and does not use the getDefaultParameterValue. Instead, it will evaluate the right value, given your Groovy script. What your pull request is doing, is basically changing the default parameter value, to return the script return value. The default behavior is simply return the first element, unless you specify otherwise. At the moment the plug-in *needs* a HTML DOM, and is not fully tested being used with curl, Pipeline Plug-in, or with different plug-ins. There are other issues that are aiming at making the plug-in compatible with headless environments, running in a pipeline, etc. Fixing those issues, would also fix your issue I think. 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] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title Xian Yi Teng commented on JENKINS-39189 Re: JOB_NAME includes parameters Job config attached. config.xml Jenkins ver. 1.642.4 Started by upstream project "XIAN_TENG_TEST_JOB" build number 1 originally caused by: Started by user xian.teng [EnvInject] - Loading node environment variables. Building remotely on ubuntu-1204-03-64 (qa_runner admin_linux build_docs 12.04 amd64-Ubuntu Ubuntu amd64-Ubuntu-12.04 Ubuntu-12.04 amd64) in workspace /jenkins_data/jenkins/workspace/XIAN_TENG_TEST_JOB/parameter1_axis/value1/parameter2_axis/value2 [value2] $ /bin/sh -xe /tmp/hudson5641186992722460038.sh + echo build step build step + echo value1 value1 + echo value2 value2 + echo XIAN_TENG_TEST_JOB/parameter1_axis=value1,parameter2_axis=value2 XIAN_TENG_TEST_JOB/parameter1_axis=value1,parameter2_axis=value2 Finished: SUCCESS 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
[JIRA] (JENKINS-39255) Timeout 'clean before checkout' configurable
Title: Message Title Casper Roubos updated an issue Jenkins / JENKINS-39255 Timeout 'clean before checkout' configurable Change By: Casper Roubos _as_ a Jenkins Git user on a system,_I want_ to have a configurable timeout length for 'Clean before checkout' ,_so_ I can set the timeout for every job separately.On a machine with multiple services some jobs require more time to 'clean before checkout' than the standard 10 minutes. Especially the job with a large amount of smaller files.I would like to be able to set timeout of the jobs with a lot small files larger than 10 minutes.!errorGit.PNG|width=600! 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] (JENKINS-39255) Timeout 'clean before checkout' configurable
Title: Message Title Casper Roubos created an issue Jenkins / JENKINS-39255 Timeout 'clean before checkout' configurable Issue Type: Bug Assignee: Mark Waite Attachments: errorGit.PNG Components: git-client-plugin, git-plugin Created: 2016/Oct/25 9:55 PM Priority: Minor Reporter: Casper Roubos as a Jenkins Git user on a system, I want to have a configurable timeout length, so I can set the timeout for every job separately. On a machine with multiple services some jobs require more time to 'clean before checkout' than the standard 10 minutes. Especially the job with a large amount of smaller files. I would like to be able to set timeout of the jobs with a lot small files larger than 10 minutes. Unable to render embedded object: File (errorGIt.PNG) not found. Add Comment
[JIRA] (JENKINS-39255) Timeout 'clean before checkout' configurable
Title: Message Title Casper Roubos updated an issue Jenkins / JENKINS-39255 Timeout 'clean before checkout' configurable Change By: Casper Roubos _as_ a Jenkins Git user on a system,_I want_ to have a configurable timeout length,_so_ I can set the timeout for every job separately.On a machine with multiple services some jobs require more time to 'clean before checkout' than the standard 10 minutes. Especially the job with a large amount of smaller files.I would like to be able to set timeout of the jobs with a lot small files larger than 10 minutes.! errorGIt errorGit .PNG|width=600! 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] (JENKINS-36524) Set a default localPath when there's not value
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-36524 Set a default localPath when there's not value Change By: Raphael CHAUMIER Actually, When the plugin transfers a library to the remote server, it uses the localPath defined in the configuration.xml.If no value is set, the plugins try to download to null/The improvement is to use a default localPath when no value is set and add a warning in the log file The temp directory will be used by default. 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] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title Rachel Moreno commented on JENKINS-39189 Re: JOB_NAME includes parameters Please, give us more details: Jenkins version, execution example, console output, ... According to logins, accounts.jenkins.io is only to manage your account. You don't need to login twice to use JIRA. Only in https://issues.jenkins-ci.org. 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] (JENKINS-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik commented on JENKINS-39253 Re: Clarification on Git submodules case If the job's SCM (git) URL "loosely matches" that of the git repository listed inside the BitBucket-provided payload, AND Probably this is not true if: job's SCM (git) URL is MAIN repository URL and git repository listed inside the BitBucket-provided is a _some git sub module URL _ ... Correct me if I am wrong ... 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] (JENKINS-38763) NPE while loading build with workflow job
Title: Message Title olamy commented on JENKINS-38763 Re: NPE while loading build with workflow job This is a plugin I'm hacking and I got the issue with. By the way the issue happen with non pipeline project as well. I have created a sample plugin to reproduce. https://github.com/olamy/JENKINS-38763 use mvn hpi:run Use this plugin as a build step. Run one build. Now restart hpi:run then go to the project page see the logs. Run the project once again no more NPE. Caused by: java.lang.NullPointerException at hudson.model.AbstractProject._getRuns (AbstractProject.java:954) at hudson.model.AbstractProject._getRuns (AbstractProject.java:145) at hudson.model.Job.getBuilds (Job.java:683) at org.olamy.jenkins.foo.FooProjectAction.getData (FooProjectAction.java:37) at org.olamy.jenkins.foo.FooProjectAction.doTrend (FooProjectAction.java:32) I hope it help to reproduce. 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
[JIRA] (JENKINS-36524) Set a default localPath when there's not value
Title: Message Title Raphael CHAUMIER started work on JENKINS-36524 Change By: Raphael CHAUMIER Status: Open In Progress 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] (JENKINS-38218) Additionnals classpath validation should support many dependencies
Title: Message Title Raphael CHAUMIER resolved as Fixed Jenkins / JENKINS-38218 Additionnals classpath validation should support many dependencies Change By: Raphael CHAUMIER Status: In Progress Resolved Resolution: Fixed 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] (JENKINS-39029) NPE when deploying if no deployment policies are set
Title: Message Title Raphael CHAUMIER stopped work on JENKINS-39029 Change By: Raphael CHAUMIER Status: In Progress Open 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] (JENKINS-39029) NPE when deploying if no deployment policies are set
Title: Message Title Raphael CHAUMIER resolved as Fixed weblogic-deployer-plugin-3.6 Jenkins / JENKINS-39029 NPE when deploying if no deployment policies are set Change By: Raphael CHAUMIER Status: Open Resolved Resolution: Fixed 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] (JENKINS-39254) Add possibility to change commit URL
Title: Message Title Michal Bocek created an issue Jenkins / JENKINS-39254 Add possibility to change commit URL Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Oct/25 9:10 PM Environment: Jenkins 1.651.3 GitHub API Plugin 1.76 GitHub plugin 1.20.0 Labels: plugin security jenkins Priority: Major Reporter: Michal Bocek Please add a possibility to change commit status URL (backreference), that on GitHub points to the Jenkins job build result. The Jenkins instance we use is on an internal server and its URL is not supposed to be revealed/visible on GitHub. Instead, we'd like to provide custom URL, for example to a public server where the job result would be stored. Storing the result somewhere else is of course not part of this ticket - that may be handled by a post-build action. It is currently possible to change 'Commit context' and 'Status result' within the 'Set status for GitHub commit [universal]' post-build action. This ticket asks for another field like 'Commit status URL'.
[JIRA] (JENKINS-38679) Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Title: Message Title
Anton Lundin commented on JENKINS-38679
Re: Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Shared libraries do not participate in polling.
, yes, they do and they cause every scm poll call to trigger a build, due to the scm poll function not finding the library in the jobs workspace, so it things its something new and thus a new build is required. Thats the bug I've reported all a long. With pipeline-chasspath i referrer to pipeline-classpath-step-plugin, its mentioned under different names in different places. Why are you saying that its a possible security hole?
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] (JENKINS-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39253 Clarification on Git submodules case Change By: Alexey Melezhik Hi ! Not sure if this an issue. But after reading bitbucket plugin docs I am not clear if plugin works properly for jobs configured as Git SCM ( Git plugin ) with sub modules.The history of this question is we have about ~ 300 bitbucket git repositories get together as git sub modules into a single git repository, lets call it MAIN repository. So obviously we *** don not want *** to have a 300 jenkins jobs ( each for every repo ) as every repo is just a logical unit of whole project/system, we want to trigger some actions when whatever repository listed as git submodule at MAIN repository is updated. So I have a following job setup:* Git SCM for MAIN repository with sub modules update enabled* Some builds steps to be taken when MAIN repos is updated ( read when one of git sub modules is updated )I am till not sure if bitbucket plugin trigger my job build using so called URLs smart "loosely matching " , as obviously those URLS - are git sub modules URLs , not MAIN repo one... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39253 Clarification on Git submodules case Change By: Alexey Melezhik Hi ! Not sure if it is the this an issue. But after reading bitbucket plugin docs I am not clear if plugins plugin works properly for jobs configured with as Git SCM ( git Git plugin ) with sub modules.The history of this question is we have about ~ 300 bitbucket git repositories get together as git sub modules into a single git rep mdo repository , lets call it MAIN repository. So I obviously we *** don 't not want obviously *** to have a 300 jenkins jobs ( each for every repo , ) as every repo is just a logical unit of whole project /system , I we want to trigger some action actions when whatever repository listed as git submodule at MAIN repository is updated. So I have a following job setup:* Git SCM for MAIN repository with sub modules update enabled * Some builds steps to be taken when MAIN repos is updated ( read when one of git sub modules is updated ) I am till not sure if bitbucket plugin trigger my job build using so called URLs smart matching, as obviously those URLS - are git sub modules URLs , not MAIN repo one... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39253 Clarification on Git submodules case Change By: Alexey Melezhik Summary: clerafiaction Clarification on Git submodules case 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] (JENKINS-39253) clerafiaction on Git submodules case
Title: Message Title Alexey Melezhik created an issue Jenkins / JENKINS-39253 clerafiaction on Git submodules case Issue Type: Task Assignee: Unassigned Components: bitbucket-plugin Created: 2016/Oct/25 8:45 PM Priority: Minor Reporter: Alexey Melezhik Hi ! Not sure if it is the issue. But after reading bitbucket plugin docs I am not clear if plugins works properly for jobs configured with Git SCM ( git plugin ) with sub modules. The history of this question is we have about ~ 300 bitbucket git repositories get together as git sub modules into a single git rep mdo, lets call it MAIN repository. So I don't want obviously have a 300 jenkins jobs each for every repo, as every repo is just a logical unit of whole project, I want to trigger some action when whatever repository listed as git submodule at MAIN repository updated. So I have job setup: Git SCM for MAIN repository with sub modules update enabled I am till not sure if bitbucket plugin trigger my job build using so called URLs smart matching, as obviously those URLS - are git sub modules URLs , not MAIN repo one...
[JIRA] (JENKINS-39251) Multibranch-Multiconfiguration project workspace path not following folder structure layout
Title: Message Title Stephen Connolly assigned an issue to Jesse Glick Jenkins / JENKINS-39251 Multibranch-Multiconfiguration project workspace path not following folder structure layout Change By: Stephen Connolly Assignee: Stephen Connolly Jesse Glick 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] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) I also need this, without the knowledge of what number was synced i cannot migrate to pipelines. 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] (JENKINS-32532) User build variables are not injected on "Before Build" step
Title: Message Title Oleg Nenashev commented on JENKINS-32532 Re: User build variables are not injected on "Before Build" step There is also a different fix proposal in https://github.com/jenkinsci/build-user-vars-plugin/pull/10 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] (JENKINS-38218) Additionnals classpath validation should support many dependencies
Title: Message Title Raphael CHAUMIER started work on JENKINS-38218 Change By: Raphael CHAUMIER Status: Open In Progress 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] (JENKINS-39252) AWS linux master - windows 2012R2 slaves won't start via JNLP
Title: Message Title marlene cote created an issue Jenkins / JENKINS-39252 AWS linux master - windows 2012R2 slaves won't start via JNLP Issue Type: Bug Assignee: Giuseppe Landolfi Components: slave-setup-plugin Created: 2016/Oct/25 8:29 PM Environment: centos7 linux master, windows 2012R2 64 bit slave - both machines are ec2 instances in AWS java 1.8 no reverse proxy or tomcat container IE version 11 Priority: Critical Reporter: marlene cote This setup works fine with Jenkins war org.jenkins-ci.main:jenkins-war:1.649, but the latest jenkins on a new server/slave doesn't work. The only way I was able to get the slave to start is on the command line and then I created a bat file which is kicked off by the task scheduler. I have tried this on 2 different setups. I tried all the methods here: https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines, and https://support.cloudbees.com/hc/en-us/articles/217423827-How-to-Install-Several-Windows-Slaves-as-a-Service, and https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM. The error message is: java.net.MalformedURLException: no protocol: jnlpJars/slave.jar
[JIRA] (JENKINS-37943) ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory
Title: Message Title Raphael CHAUMIER closed an issue as Not A Defect Jenkins / JENKINS-37943 ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory Change By: Raphael CHAUMIER Status: Open Closed Resolution: Not A Defect 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] (JENKINS-37077) Check classpath exists before launching weblogic.Deployer java command
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-37077 Check classpath exists before launching weblogic.Deployer java command Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3.6 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] (JENKINS-37943) ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory
Title: Message Title Raphael CHAUMIER commented on JENKINS-37943 Re: ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory Hi kiran kiran I have no news about this issue. I close the ticket. Regards 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Jenkins ThreadDump from one of our hung executors: Executor #0 for GJ-WTX64-S05V13 : executing jenkins_admin_component_1 #25147 / waiting for hudson.remoting.Channel@45b513d2:GJ-WTX64-S05V13 "Executor #0 for GJ-WTX64-S05V13 : executing jenkins_admin_component_1 #25147 / waiting for hudson.remoting.Channel@45b513d2:GJ-WTX64-S05V13" Id=204 Group=main TIMED_WAITING on hudson.remoting.UserRequest@33f1c9bd at java.lang.Object.wait(Native Method) waiting on hudson.remoting.UserRequest@33f1c9bd at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:796) at hudson.FilePath.act(FilePath.java:1007) at hudson.FilePath.act(FilePath.java:996) at hudson.FilePath.deleteRecursive(FilePath.java:1198) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:934) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) ThreadDump from that server: Channel reader thread: channel "Channel reader thread: channel" Id=2301 Group=main RUNNABLE (in native) at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) locked java.io.BufferedInputStream@40bda018 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:86) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) main "main" Id=1 Group=main WAITING on hudson.remoting.Engine@a3d1956 at java.lang.Object.wait(Native Method) waiting on
[JIRA] (JENKINS-39029) NPE when deploying if no deployment policies are set
Title: Message Title Raphael CHAUMIER started work on JENKINS-39029 Change By: Raphael CHAUMIER Status: Open In Progress 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] (JENKINS-39251) Multibranch-Multiconfiguration project workspace path not following folder structure layout
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-39251 Multibranch-Multiconfiguration project workspace path not following folder structure layout Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2016/Oct/25 8:09 PM Environment: Branch API Plugin 1.11 Priority: Major Reporter: Rick Liu Starting from Branch API Plugin ver. 1.11, the workspace paths are all moved to top level under the node's workspace directory. This breaks the layout of jobs under CloudBees Folders Plugin. Another downside is I have about 2000+ multibranch branch jobs spread across different multibranch jobs and folders. This means I'll get 2000+ folders right under the single node's workspace directory. eg. /jenkins_slave/workspace/Test/Test-Multi/trunk/ /jenkins_slave/workspace/Test_Test-Multi_trunk-IUMOWUQRUH5TKVIRME7LH55RHUW53YREWPROXXNXXAL3DYASUA5A Add Comment
[JIRA] (JENKINS-32532) User build variables are not injected on "Before Build" step
Title: Message Title Oleg Nenashev commented on JENKINS-32532 Re: User build variables are not injected on "Before Build" step John Tal Well, you can always propose a pull request. Since there is a fix example, the change is trivial 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] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title Xian Yi Teng commented on JENKINS-39189 Re: JOB_NAME includes parameters In an execute shell build step and also an execute shell post-build action. Also, this is unrelated, but I think there are two separate logins for the Jenkins Jira? accounts.jenkins.io and the link on the top right. I had to log in to both of them... Took me a while to figure that out. 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] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Daniel Serodio commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard It seems that this was included in the 2.27 release even thou it's not mentioned in the Changelog 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] (JENKINS-39250) Add option to disable automatic user creation in Git plugin
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-39250 Add option to disable automatic user creation in Git plugin Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2016/Oct/25 6:57 PM Priority: Major Reporter: Kevin Phillips Currently the Git plugin has this 'weird' behavior where by, when someone navigates to changeset details on the Jenkins dashboard the changeset information is parsed to pull out user information for each commit and if one or more of those users don't have user profiles in Jenkins new ones are created for them on the fly automatically. This automatic behavior has the unfortunate side effect of causing redundant, superfluous user profiles to be created on Jenkins which is confusing at best and fragile at worst. For example, suppose a user logs in to the Jenkins dashboard authenticating via LDAP or AD - they will get a user profile created. Then suppose they commit some changes to Git and their Git client / profile has a slightly different configuration from their LDAP profile (ie: maybe their user name is slightly different). Then when someone browses for those changesets on the Jenkins dashboard a second user profile gets magically created with a very similar name to the first - sometimes with overlapping / duplicated metadata in each. Heaven forbid that the same user then has several different repositories or systems they do work on, each potentially with slightly different user names on them, each of which will produce even more redundant copies of Jenkins users magically behind the scenes. To make matters worse, any other Jenkins plugins that make use of these superfluous user profiles ends up producing different results depending on which user profile they decide to choose for any particular operation. Plugins such as the Claim broken build plugin offer very obvious examples of how this causes no end of confusion. Since this plugin allows the user to select a Jenkins user name from a drop down
[JIRA] (JENKINS-32532) User build variables are not injected on "Before Build" step
Title: Message Title John Tal commented on JENKINS-32532 Re: User build variables are not injected on "Before Build" step +1 for the 1 hour fix 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] (JENKINS-38679) Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Title: Message Title
Jesse Glick commented on JENKINS-38679
Re: Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Legacy SCM is supported. The “legacy place in Subversion” sounds dubious. Yes I know what SCM polling is, but not what it has to do with this issue. Shared libraries do not participate in polling. Do not what pipeline-classpath is but it is not supported and sounds like a possible security hole.
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] (JENKINS-38116) Add duration time to flow graph table in pipeline steps
Title: Message Title JT Chu closed an issue as Fixed It is implemented in Jenkins ver. 2.7.20.2 (CloudBees Jenkins Enterprise 2.7.20.2-rolling) Jenkins / JENKINS-38116 Add duration time to flow graph table in pipeline steps Change By: JT Chu Status: Open Closed Resolution: Fixed 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,
[JIRA] (JENKINS-38737) SemaphoreStep does not attach a TimingAction to its flownode
Title: Message Title Jesse Glick commented on JENKINS-38737 Re: SemaphoreStep does not attach a TimingAction to its flownode Test in workflow-support PR 16. 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] (JENKINS-38679) Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Title: Message Title
Anton Lundin commented on JENKINS-38679
Re: Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Sorry for the simpe typo. What i ment was “every SCM poll call”. Or don't you know what scm polling is? Anyhow, if you're not planning to support the "Legacy SCM api" I'd suggest you completly remove the support for it, so others don't need to waste their time trying to get workflow-cps-global-lib-plugin working with it. Anyhow, i've solved my problems with the pipeline-classpath plugin instead. Not as pretty, but it works, way better.
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] (JENKINS-38268) Parallel step and closure scope
Title: Message Title Jesse Glick commented on JENKINS-38268 Re: Parallel step and closure scope No idea offhand, will have to reproduce in a functional test and study in a debugger. 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] (JENKINS-38679) Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Title: Message Title
Anton Lundin updated an issue
Jenkins / JENKINS-38679
Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Change By:
Anton Lundin
I see a wierd bug when using global libraries on pipeline.We have a groovy class with static defines, which lives in a legacy place in subversion and can't be moved.I've worked around that by configuring a global library:{code:java} mylib https://svn/project/data${library.ladok3.version}/legacy/path/mylib xxx src/mylib infinity true/.*false false/trunk false true{code}Every poll scm poll call finishes like:Workspace doesn't contain https://svn/project/data${library.mylib.version}/legacy/path/mylib. Need a new build.Everything loads just file when i use:@Library("mylib@/trunk")import mylibbut the polling bug makes it re-build every poll call.I started out using the Legacy SCM api to declare the lib, because the modern scm dropdown is empty, and due to the nice workaround checking out the library to src/library i can't easily switch to the modern SCM api.The library is checked out just fine in workspace/pipeline@libs/src/mylib , but it looks like the polling is confused due to this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38763) NPE while loading build with workflow job
Title: Message Title Jesse Glick commented on JENKINS-38763 Re: NPE while loading build with workflow job I know nothing about the thing you are pointing to. Are there specific instructions to reproduce the problem from scratch? 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] (JENKINS-39213) Add ability for computed folders to control the views in the folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39213 Re: Add ability for computed folders to control the views in the folder Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolder.java src/main/resources/com/cloudbees/hudson/plugins/folder/AbstractFolder/configure.jelly src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/f3068bbc9ce417f7ae6e6351face1f74ebddda8b Log: JENKINS-39213 Fix bug and commit test Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/3df543235f78...f3068bbc9ce4 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] (JENKINS-38268) Parallel step and closure scope
Title: Message Title Alexander Olofsson commented on JENKINS-38268 Re: Parallel step and closure scope To be honest, currying was just a good way to showcase the issue. Anything that embeds a value into the closure seems to be lost in parallelisation, so even wrapping the closure into another one that feeds it the value as a static parameter doesn't work. (file30 and file31 in the example) Ran into this when trying to create a list of parallel steps out of files from a folder, to spread out a series of fixed-time workloads onto many executors so that the build step wouldn't take as much time. Tried everything I could think of to work around the problem, not even rolling my own closure class to store the value worked. 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] (JENKINS-39213) Add ability for computed folders to control the views in the folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39213 Re: Add ability for computed folders to control the views in the folder Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/views/AbstractFolderViewHolder.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/96bfd09a343138a9a2d62eeb060f9ec4f6389c94 Log: JENKINS-39213 Jesse wants us not to use ExtensionPoint unless it is an @Extension 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] (JENKINS-30414) RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject getProperty java.lang.String (org.jenkinsci.plugins.workflow.cps.CpsClosure2.docker)
Title: Message Title Jesse Glick commented on JENKINS-30414 Re: RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject getProperty java.lang.String (org.jenkinsci.plugins.workflow.cps.CpsClosure2.docker) Well the issue here was installing some plugins without restart which require an update of other plugins, which can only happen after restart. The Jenkins plugin manager is too dumb to handle this case properly. It does warn you in the UI to restart, but does not block the new plugins from being dynamically loaded. Maybe 2.19.x behaves better, have not checked yet. 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] (JENKINS-37718) Block Pipeline job while upstream or downstream projects are building
Title: Message Title Jesse Glick commented on JENKINS-37718 Re: Block Pipeline job while upstream or downstream projects are building Did not understand the last comment at all. 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] (JENKINS-38268) Parallel step and closure scope
Title: Message Title Jesse Glick commented on JENKINS-38268 Re: Parallel step and closure scope Well that is more likely an issue with curry; not sure if that was ever implemented. 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] (JENKINS-37559) cannot abort shell scripts on 64-bit Solaris
Title: Message Title Oleg Nenashev commented on JENKINS-37559 Re: cannot abort shell scripts on 64-bit Solaris Christopher Siden The fix is released, so changed the status back 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] (JENKINS-37559) cannot abort shell scripts on 64-bit Solaris
Title: Message Title Oleg Nenashev updated JENKINS-37559 Jenkins / JENKINS-37559 cannot abort shell scripts on 64-bit Solaris Change By: Oleg Nenashev Status: In Review Resolved 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] (JENKINS-37771) "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.
Title: Message Title Norman Klehr commented on JENKINS-37771 Re: "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server. I was facing the same issue but with the RBENV plugin. I configured it for a job in the 'Build Environment' section to use Ruby version 2.2.4. Every time Jenkins service gets restarted or server rebooted it was dropping this configuration on the job level. Strange thing was also when I checked the config.xml file for this job it still looked the same and timestamp of that file didnt even change. Is there a cache Jenkins keeping that information before fetching from config.xml again? Anyway downgrading the Ruby-Runtime-Plugin from 0.13 to 0.12 helped in my case as well. I would like to know what the difference is between these versions but doesnt seem to be under github?! 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] (JENKINS-37559) cannot abort shell scripts on 64-bit Solaris
Title: Message Title rabin khadka updated JENKINS-37559 Jenkins / JENKINS-37559 cannot abort shell scripts on 64-bit Solaris Change By: rabin khadka Status: Resolved In Review 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] (JENKINS-34982) Add configure block in DSL for promotions
Title: Message Title Frédéric Chuong updated an issue Jenkins / JENKINS-34982 Add configure block in DSL for promotions Change By: Frédéric Chuong Component/s: job-dsl-plugin 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] (JENKINS-34982) Add configure block in DSL for promotions
Title: Message Title
Frédéric Chuong commented on JENKINS-34982
Re: Add configure block in DSL for promotions
FYI an experimental branch tried to rethink the design of the Job-DSL integration (and more generally address the scalability of the promoted-builds-plugin DSL) https://github.com/jenkinsci/promoted-builds-plugin/pull/96#issuecomment-255899713 :
The driver for those changes is the scalability of the DSL extension when using the existing implementation:
promoted-builds-plugin developers may not know how/when they also have to provide DSL integration to allow `job-dsl-plugin`. Eg: GroovyCondition is not covered by the DSL extension even though it is provided by the very same plugin.
Third-party plugin developers wanting to extend promoted-builds-plugin (ie. wanting to provide custom PromotionCondition (which extends ExtensionPoint) for their own plugin) have to add binary dependency on promoted-builds-plugin to their own plugin because of the domain object to XML serialization approach (this creates a chicken-egg problem defeating the purpose of providing {{ExtensionPoint}}s).
job-dsl-plugin users cannot manipulate the PromotionProcess XML to workaround lack of integration https://github.com/jenkinsci/job-dsl-plugin/wiki/The-Configure-Block
Those issues all have a common impact: they prevent job-dsl-plugin users from being able to generate fine-tuned promotions as soon as the components they need is not implemented into the DSL extension. The proposed changes tries to adopt the https://github.com/jenkinsci/job-dsl-plugin/wiki/Automatically-Generated-DSL approach applied to this DSL extension to fix those issues.
As for the implementation, it indeed needs to be improved/fixed at least for the reported issues
The branch itself brings its share of issues (as reminded by plugin maintainer): binary compatibility and migration path. It could also use some advice from job-dsl-plugin maintainers for approval/endorsement purpose.
Add Comment
[JIRA] (JENKINS-39249) DNS Cache
Title: Message Title Michael Gardner updated an issue Jenkins / JENKINS-39249 DNS Cache Change By: Michael Gardner Component/s: gerrit-trigger-plugin 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] (JENKINS-39249) DNS Cache Not Updating
Title: Message Title Michael Gardner updated an issue Jenkins / JENKINS-39249 DNS Cache Not Updating Change By: Michael Gardner Summary: DNS Cache Not Updating 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] (JENKINS-39249) DNS Cache
Title: Message Title Michael Gardner created an issue Jenkins / JENKINS-39249 DNS Cache Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/25 4:47 PM Environment: Ubuntu 14.04 java version "1.7.0_111" OpenJDK Runtime Environment (IcedTea 2.6.7) (7u111-2.6.7-0ubuntu0.14.04.3) OpenJDK 64-Bit Server VM (build 24.111-b01, mixed mode) Priority: Major Reporter: Michael Gardner We're using the Gerrit Trigger plugin. The Gerrit server had to undergo a reboot and our internal DNS changed its IP. The A record in the DNS server was updated. After flushing the DNS on the Jenkins host I can ping the Gerrit server and the IP resolves correctly. However, within Jenkins the Gerrit Trigger plugin now complains that it cannot find a route to the host with the gerrit.host.internal name. If I remove the hostname and replace it with the actual IP the plugin works fine. I believe this has to be some issue with DNS caching inside Jenkins. I've read a few posts about disabling JAVA's caching for DNS but I'm not finding any success.
[JIRA] (JENKINS-39248) Synchronize Jenkins user database with LDAP
Title: Message Title Daniel Beck assigned an issue to Unassigned Why was this assigned to me? Jenkins / JENKINS-39248 Synchronize Jenkins user database with LDAP Change By: Daniel Beck Assignee: Daniel Beck 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] (JENKINS-39248) Synchronize Jenkins user database with LDAP
Title: Message Title Kevin Phillips commented on JENKINS-39248 Re: Synchronize Jenkins user database with LDAP I've linked this improvement to several other issues in the tracker, and admittedly there is some overlap between this and the others however I think there are some unique requirements I'd like to see resolved here that aren't explicitly covered elsewhere. For example, the feature for 'disabling' users (JENKINS-11205) would be great however if the process of disabling users is still a manual process once that task is complete then I would like to see it extended such that users for which there is no active LDAP account would be automatically disabled without manual intervention. Also, in the case of JENKINS-24894 the scope of work is limited to just the display names of the users. I would suggest that LDAP synchronization should also include changes to email addresses and any other metadata that may be pulled from LDAP and cached by Jenkins and that this process should be automatic as well (ie: on user login). Further, if it makes the logic easier to implement I would suggest that you simply provide a check-box on the Manage Jenkins page for LDAP to force the synchronization of LDAP data to Jenkins, causing any user customizations to be tossed. This would ensure consistency with the LDAP database, which 'should' be the definitive source for user information, and make it easier to keep the Jenkins database in sync (ie: no need to cache previous data from LDAP and compare with local user changes and such). IMO this would be the preferred behavior or any large scale implementation but making it optional - and even disabled by default if so desired - would be acceptable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39248) Synchronize Jenkins user database with LDAP
Title: Message Title Kevin Phillips assigned an issue to Daniel Beck Jenkins / JENKINS-39248 Synchronize Jenkins user database with LDAP Change By: Kevin Phillips Assignee: Kohsuke Kawaguchi Daniel Beck 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] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title Johnny Baloney commented on JENKINS-35113 Re: Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin The plugin did not appear to work for me on fresh installations of Jenkins versions 1.651.2 or 1.651.3 (courtesy of Docker). It worked fine with 1.651.1. Printing environment variables with env did not show the preset variables from the upstream job and the parameters link on the job page showed an empty Parameters window. However, the Jenkins logs showed: Oct 25, 2016 3:39:00 PM hudson.model.ParametersAction filter WARNING: Skipped parameter `foo` as it is undefined on `DOWNSTREAM_JOB`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach Running Jenkins with: java -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war solved the problem. I think the plugin page needs updating to mention this change in plugin behaviour or to make it more visible if it does already. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39248) Synchronize Jenkins user database with LDAP
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-39248 Synchronize Jenkins user database with LDAP Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 2016/Oct/25 4:17 PM Priority: Major Reporter: Kevin Phillips I would like to see an option to synchronize Jenkins users with an LDAP database, either manually or automatically in some way. There are several reasons for my request, including the following: when information about a user changes it doesn't appear to get reflected in the Jenkins user database (ie: name changes, email address changes, and the like) causing the Jenkins DB to be out of date alternate sources appear to directly manipulate the Jenkins user database, such as the Git plugin (see the "Create new accounts base on author/committer's email" option) which results in superfluous and / or duplicate user profiles getting created on the master when users are removed from LDAP (ie: no longer work for the company) their user profiles remain in the Jenkins database, which exposes their profiles and settings on the Jenkins dashboard for other plugins like the email publisher, claim plugin, etc. to use which is confusing at best and causes build failures at worst Having some way to either delete or at least disable Jenkins profiles that are not found in LDAP, and making sure the user information contained in the valid profiles is kept up to date, would be extremely helpful. On large scale rollouts with hundreds or thousands of users and with frequent LDAP changes makes for an extremely tedious and time consuming job to keep these two systems in synch. Ideally the solution would be automatic in some way, perhaps
[JIRA] (JENKINS-3404) mix LDAP and local Hudson users
Title: Message Title Kevin Phillips commented on JENKINS-3404 Re: mix LDAP and local Hudson users I too would like to have the ability to define a couple of static local users on a Jenkins server, for pretty much the same reasons stated above - automated processes accessing Jenkins, accessing the dashboard when LDAP/AD are down, etc. This would be very helpful. 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] (JENKINS-39247) Add support for concurrent builds in Jenkins
Title: Message Title David Pärsson commented on JENKINS-39247 Re: Add support for concurrent builds in Jenkins May be related to JENKINS-32715. 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] (JENKINS-39109) Agent docker should be configurable by admin to run on specific agent label
Title: Message Title Andrew Bayer updated JENKINS-39109 Jenkins / JENKINS-39109 Agent docker should be configurable by admin to run on specific agent label Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed 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.
