[JIRA] (JENKINS-39214) "Goals and Opptions" and "Root POM" not written to config.xml
Title: Message Title Francois Aichelbaum commented on JENKINS-39214 Re: "Goals and Opptions" and "Root POM" not written to config.xml Hi Adam I'm fully up to date but still no luck on my side. Did you change anything else ? 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-39718) Fix PCT against 2.x baseline and migrate to 2.17 parent POM
Title: Message Title Evaristo Gutierrez updated JENKINS-39718 Jenkins / JENKINS-39718 Fix PCT against 2.x baseline and migrate to 2.17 parent POM Change By: Evaristo Gutierrez 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.
[JIRA] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository
Title: Message Title Christoph Obexer commented on JENKINS-22752 Re: Initial poll (just after project creation) spawns builds for all the existing branches in repository Maybe this should be merged with https://issues.jenkins-ci.org/browse/JENKINS-38552? Also this is not specific to git is it? 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-39587) Blue Ocean dashboard is showing no Pipelines
Title: Message Title Michael Neale commented on JENKINS-39587 Re: Blue Ocean dashboard is showing no Pipelines This has now been released in b12 - which is now in the update center. 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-38291) Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name
Title: Message Title Oleg Nenashev resolved as Duplicate Right. Didn't notice it somehow Jenkins / JENKINS-38291 Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate 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-39214) "Goals and Opptions" and "Root POM" not written to config.xml
Title: Message Title Adam commented on JENKINS-39214 Re: "Goals and Opptions" and "Root POM" not written to config.xml Francois Aichelbaum hmm.. I just tried again, both in docker as well as my regular install and all seems working now. be curious if yours is fixed now too. wondering if maybe there was a plugin update that I did which fixed it. 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-35808) Autogenerate a swagger spec for rest api
Title: Message Title James Dumay commented on JENKINS-35808 Re: Autogenerate a swagger spec for rest api The CloudBees members decided that we wouldn't be doing it any time soon so we closed it out. However if you want to contribute it then please reopen 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-35808) Autogenerate a swagger spec for rest api
Title: Message Title cliffano commented on JENKINS-35808 Re: Autogenerate a swagger spec for rest api James Dumay Could you please advise why this issue was resolved as won't fix? I'm interested in a Swagger / OpenAPI spec for Jenkins (core would be nice, plugins would be a great bonus). 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-39735) Builds hang and never finish
Title: Message Title Phil Porada updated an issue Jenkins / JENKINS-39735 Builds hang and never finish Change By: Phil Porada When I trigger a build using this plugin, my container is correctly started and environment variables are passed in with a workaround from JENKINS-32393. What happens to me is that at the end of the shell executor build step, the build process hangs indefinitely. I have verified that the last step of my shell executor has completed successfully. Why does the build not finish? If I run the build with strictly the shell executor and run manual commands to mount the workdir/tmp into a docker container, everything works fine. When I use this plugin, something is very 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
[JIRA] (JENKINS-25421) Swarm plugin requires "Prevent Cross Site Request Forgery exploits" be enabled.
Title: Message Title Anita Dongare commented on JENKINS-25421 Re: Swarm plugin requires "Prevent Cross Site Request Forgery exploits" be enabled. Hi team , We are seeing the same issue on our Jenkins master, can someone help explain and resolve this error with swarm plugin ? Thanks Anita 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-39735) Builds hang and never finish
Title: Message Title Phil Porada updated an issue Jenkins / JENKINS-39735 Builds hang and never finish Change By: Phil Porada When I trigger a build using this plugin, my container is correctly started and environment variables are passed in with a workaround from JENKINS- 39457 32393 . What happens to me is that at the end of the shell executor build step, the build process hangs indefinitely. I have verified that the last step of my shell executor has completed successfully. Why does the build not finish? 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-39735) Builds hang and never finish
Title: Message Title Phil Porada created an issue Jenkins / JENKINS-39735 Builds hang and never finish Issue Type: Bug Assignee: Nicolas De Loof Attachments: dockerbuild.png, dockerbuild02.png, dockerbuild03.png Components: docker-custom-build-environment-plugin Created: 2016/Nov/15 4:14 AM Environment: Jenkins ver. 2.19.2 Customer Build Environment Plugin 1.6.5 Priority: Major Reporter: Phil Porada When I trigger a build using this plugin, my container is correctly started and environment variables are passed in with a workaround from JENKINS-39457. What happens to me is that at the end of the shell executor build step, the build process hangs indefinitely. I have verified that the last step of my shell executor has completed successfully. Why does the build not finish? Add Comment
[JIRA] (JENKINS-5055) server rejected connection: already connected to master
Title: Message Title Matthew Mitchell commented on JENKINS-5055 Re: server rejected connection: already connected to master I have some other data (Jenkins 6.42.1 running on Ubuntu 16.04 Java 8). This only happens on nodes that were connected via jnlp by running a command on the node (java -jar ...) and is not limited to Windows. Seen on OSX too. The failure is always preceded by: INFO: Ping failed. Terminating the channel The ping fails for many machines within a few seconds. Only those machines connected via manual jnlp remoting call fail ping In the server we have running, the nodes running that don't fail are connected via ssh and are Linux, FreeBSD, etc. The nodes that fail and don't fail exist in the same locations (VMs in Azure) So the interesting data point here I think is the fact that the ping doesn't fail on the machines connected via SSH channel. Is it that they aren't using the JNLP remoting protocol? 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
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title James Dumay commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint Thanks both for taking a look 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-38529) API Steps, stages and parallels should reflect the "aborted"
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38529 API Steps, stages and parallels should reflect the "aborted" Change By: Michael Neale Sprint: atlantic, indian , arctic 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-38529) API Steps, stages and parallels should reflect the "aborted"
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38529 API Steps, stages and parallels should reflect the "aborted" Change By: Michael Neale Sprint: atlantic, indian , tasman 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-31514) Jenkins Swarm slave goes remains offline after master restarts
Title: Message Title Alex Gray commented on JENKINS-31514 Re: Jenkins Swarm slave goes remains offline after master restarts You can use a service like "supervisor" that will automatically start the swarm jar on the slave if it ever goes down. That is what we use. We have the process retry X times with a sleep of Y seconds in between each attempt. That way, we can restart our master for maintenance, and when it is back online the agents will magically re-connect. 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-38291) Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name
Title: Message Title Ben Hines commented on JENKINS-38291 Re: Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name Duplicate of JENKINS-33633 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-33633) Change Key values to "_" vs "." as this breaks ES 2.0 and later
Title: Message Title Ben Hines commented on JENKINS-33633 Re: Change Key values to "_" vs "." as this breaks ES 2.0 and later Is this still a problem? I wanted to try out this plugin with the latest ELK. 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-39202) Pull request table should have pull request ID and branch name column
Title: Message Title Ivan Meredith updated JENKINS-39202 Jenkins / JENKINS-39202 Pull request table should have pull request ID and branch name column Change By: Ivan Meredith 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.
[JIRA] (JENKINS-39336) Cannot right click to open results from activity, branches, PR tab
Title: Message Title Ivan Meredith updated JENKINS-39336 Jenkins / JENKINS-39336 Cannot right click to open results from activity, branches, PR tab Change By: Ivan Meredith 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.
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Created a PR, which seems to be a plausible workaround. https://github.com/jenkinsci/jenkins/pull/2635 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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title Matt Hoffman commented on JENKINS-39734 Re: P4 Trigger (/p4/change) Doesn't Detect p4port Rob Petti I definitely did, I apologize! Thank you for the re-assignment! 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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title Rob Petti assigned an issue to Paul Allen Jenkins / JENKINS-39734 P4 Trigger (/p4/change) Doesn't Detect p4port Change By: Rob Petti Assignee: Paul Allen 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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title Rob Petti updated an issue Jenkins / JENKINS-39734 P4 Trigger (/p4/change) Doesn't Detect p4port Change By: Rob Petti Component/s: p4-plugin Component/s: perforce-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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-39734 P4 Trigger (/p4/change) Doesn't Detect p4port Change By: Rob Petti Assignee: Rob Petti 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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title Rob Petti commented on JENKINS-39734 Re: P4 Trigger (/p4/change) Doesn't Detect p4port perforce-plugin has no such functionality, and the latest version of it is 1.3.36, which is far less than what you've listed as having. I'm going to assume this was filed for the wrong 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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman updated an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Change By:
Matt Hoffman
Hi all,We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) *this will cause the build to correctly trigger and fire*.We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use:curl --header "Content-Type: application/json" --request POST --data "payload={change:200,p4port:\"perf.mysite.com:1666\"}" http://jenkins.mysite.com:8192/p4/changeAnd Postman:POST /p4/change HTTP/1.1Host: jenkins.mysite.com:8192Content-Type: application/jsonCache-Control: no-cachePostman-Token: 8425cf56-212f-f0fa-7007-b70a4591565epayload={"change":"500", "p4port" :"perf.mysite.com:1666"}*Job Setup:*It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve it) and the Perforce Credentials were chosen. A workspace name was assigned, and a View Mapping was applied. Under "Build Triggers", *only "Perforce triggered build." is checked*. *Logs:*When Postman is used to POST the JSON payload as a simple test-case the following is printed into the logs (note that this was POST'd multiple times with different change values): {quote} Nov 14, 2016 3:44:32 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeReceived trigger event: {"change":"202","p4port":"perf.mysite.com:1666"}Nov 14, 2016 3:44:48 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeReceived trigger event: {"change":500,"p4port":"perf.mysite.com:1666"} {quote} However, nothing in the logs happens after that. I know that the [probeJobs](https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java#L92) function works, as the Manual Trigger also invokes it and that is successfully printed. If I run the "Manual Configuration for Trigger" via the webpage, the following is printed into the logs: {quote} Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeSubmitManual trigger event: Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobsP4: probing: MY_PROJECTNov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger pokeP4: poking: MY_PROJECTNov 14, 2016 3:50:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChangegetBuildChange:return:726 {quote} The only thing I can think of at this point is that it is not correctly retrieving the string for "p4port" variable, thus it never runs probeJobs when called from doChange. I cannot get it
[JIRA] (JENKINS-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman updated an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Change By:
Matt Hoffman
Hi all,We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) *this will cause the build to correctly trigger and fire*.We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use:curl --header "Content-Type: application/json" --request POST --data "payload={change:200,p4port:\"perf.mysite.com:1666\"}" http://jenkins.mysite.com:8192/p4/changeAnd Postman:POST /p4/change HTTP/1.1Host: jenkins.mysite.com:8192Content-Type: application/jsonCache-Control: no-cachePostman-Token: 8425cf56-212f-f0fa-7007-b70a4591565epayload={"change":"500", "p4port" :"perf.mysite.com:1666"}*Job Setup:*It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve it) and the Perforce Credentials were chosen. A workspace name was assigned, and a View Mapping was applied. Under "Build Triggers", *only "Perforce triggered build." is checked*. *Logs:*When Postman is used to POST the JSON payload as a simple test-case the following is printed into the logs (note that this was POST'd multiple times with different change values):{quote}Nov 14, 2016 3:44:32 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeReceived trigger event: {"change":"202","p4port":"perf.mysite.com:1666"}Nov 14, 2016 3:44:48 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeReceived trigger event: {"change":500,"p4port":"perf.mysite.com:1666"}{quote}However, nothing in the logs happens after that. I know that the [probeJobs](https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java#L92) function works, as the Manual Trigger also invokes it and that is successfully printed. If I run the "Manual Configuration for Trigger" via the webpage, the following is printed into the logs: bq. {quote} Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeSubmit bq. Manual trigger event: bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobs bq. P4: probing: MY_PROJECT bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger poke bq. P4: poking: MY_PROJECT bq. Nov 14, 2016 3:50:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChange bq. getBuildChange:return:726 {quote} bq. The only thing I can think of at this point is that it is not correctly retrieving the string for "p4port" variable, thus it never runs
[JIRA] (JENKINS-39631) Declarative plugin adds extra step for failed step but doesn't mark it as error
Title: Message Title Andrew Bayer updated JENKINS-39631 Jenkins / JENKINS-39631 Declarative plugin adds extra step for failed step but doesn't mark it as error 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.
[JIRA] (JENKINS-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman updated an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Change By:
Matt Hoffman
Hi all,We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) *this will cause the build to correctly trigger and fire*.We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use:curl --header "Content-Type: application/json" --request POST --data "payload={change:200,p4port:\"perf.mysite.com:1666\"}" http://jenkins.mysite.com:8192/p4/changeAnd Postman:POST /p4/change HTTP/1.1Host: jenkins.mysite.com:8192Content-Type: application/jsonCache-Control: no-cachePostman-Token: 8425cf56-212f-f0fa-7007-b70a4591565epayload={"change":"500", "p4port" :"perf.mysite.com:1666"}*Job Setup:*It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve it) and the Perforce Credentials were chosen. A workspace name was assigned, and a View Mapping was applied. Under "Build Triggers", *only "Perforce triggered build." is checked*. *Logs:*When Postman is used to POST the JSON payload as a simple test-case the following is printed into the logs (note that this was POST'd multiple times with different change values): bq. {quote} Nov 14, 2016 3:44:32 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChange bq. Received trigger event: {"change":"202","p4port":"perf.mysite.com:1666"} bq. Nov 14, 2016 3:44:48 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChange bq. Received trigger event: {"change":500,"p4port":"perf.mysite.com:1666"} {quote} However, nothing in the logs happens after that. I know that the [probeJobs](https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java#L92) function works, as the Manual Trigger also invokes it and that is successfully printed. If I run the "Manual Configuration for Trigger" via the webpage, the following is printed into the logs:bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeSubmitbq. Manual trigger event: bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobsbq. P4: probing: MY_PROJECTbq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger pokebq. P4: poking: MY_PROJECTbq. Nov 14, 2016 3:50:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChangebq. getBuildChange:return:726bq. The only thing I can think of at this point is that it is not correctly retrieving the string for "p4port" variable, thus it never runs probeJobs
[JIRA] (JENKINS-39631) Declarative plugin adds extra step for failed step but doesn't mark it as error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39631 Re: Declarative plugin adds extra step for failed step but doesn't mark it as error Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/pom.xml pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/Utils.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/1d397c25acff419a0a82611e0f5ae13679b9639f Log: [FIXED JENKINS-39631] Last step in failed stage has an error. 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-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman updated an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Change By:
Matt Hoffman
Hi all,We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) *this will cause the build to correctly trigger and fire*.We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use: {quote} curl --header "Content-Type: application/json" --request POST --data "payload={change:200,p4port:\"perf.mysite.com:1666\"}" http://jenkins.mysite.com:8192/p4/change {quote} And Postman:POST /p4/change HTTP/1.1Host: jenkins.mysite.com:8192Content-Type: application/jsonCache-Control: no-cachePostman-Token: 8425cf56-212f-f0fa-7007-b70a4591565epayload={"change":"500", "p4port" :"perf.mysite.com:1666"}*Job Setup:*It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve it) and the Perforce Credentials were chosen. A workspace name was assigned, and a View Mapping was applied. Under "Build Triggers", *only "Perforce triggered build." is checked*. *Logs:*When Postman is used to POST the JSON payload as a simple test-case the following is printed into the logs (note that this was POST'd multiple times with different change values):bq. Nov 14, 2016 3:44:32 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangebq. Received trigger event: {"change":"202","p4port":"perf.mysite.com:1666"}bq. Nov 14, 2016 3:44:48 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangebq. Received trigger event: {"change":500,"p4port":"perf.mysite.com:1666"}However, nothing in the logs happens after that. I know that the [probeJobs](https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java#L92) function works, as the Manual Trigger also invokes it and that is successfully printed. If I run the "Manual Configuration for Trigger" via the webpage, the following is printed into the logs:bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeSubmitbq. Manual trigger event: bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobsbq. P4: probing: MY_PROJECTbq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger pokebq. P4: poking: MY_PROJECTbq. Nov 14, 2016 3:50:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChangebq. getBuildChange:return:726bq. The only thing I can think of at this point is that it is not correctly retrieving the string for "p4port" variable, thus it never runs probeJobs when
[JIRA] (JENKINS-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman updated an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Change By:
Matt Hoffman
Hi all,We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) *this will cause the build to correctly trigger and fire*.We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use:{ { quote} curl --header "Content-Type: application/json" --request POST --data "payload={change:200,p4port:\"perf.mysite.com:1666\"}" http://jenkins.mysite.com:8192/p4/change {quote } } And Postman: {{ POST /p4/change HTTP/1.1Host: jenkins.mysite.com:8192Content-Type: application/jsonCache-Control: no-cachePostman-Token: 8425cf56-212f-f0fa-7007-b70a4591565epayload={"change":"500", "p4port" :"perf.mysite.com:1666"} }} *Job Setup:*It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve it) and the Perforce Credentials were chosen. A workspace name was assigned, and a View Mapping was applied. Under "Build Triggers", *only "Perforce triggered build." is checked*. *Logs:*When Postman is used to POST the JSON payload as a simple test-case the following is printed into the logs (note that this was POST'd multiple times with different change values):bq. Nov 14, 2016 3:44:32 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangebq. Received trigger event: {"change":"202","p4port":"perf.mysite.com:1666"}bq. Nov 14, 2016 3:44:48 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangebq. Received trigger event: {"change":500,"p4port":"perf.mysite.com:1666"}However, nothing in the logs happens after that. I know that the [probeJobs](https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java#L92) function works, as the Manual Trigger also invokes it and that is successfully printed. If I run the "Manual Configuration for Trigger" via the webpage, the following is printed into the logs:bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeSubmitbq. Manual trigger event: bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobsbq. P4: probing: MY_PROJECTbq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger pokebq. P4: poking: MY_PROJECTbq. Nov 14, 2016 3:50:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChangebq. getBuildChange:return:726bq. The only thing I can think of at this point is that it is not correctly retrieving the string for "p4port" variable, thus it never runs
[JIRA] (JENKINS-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman updated an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Change By:
Matt Hoffman
Hi all,We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) *this will cause the build to correctly trigger and fire*.We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use: {{ curl --header "Content-Type: application/json" --request POST --data "payload={change:200,p4port:\"perf.mysite.com:1666\"}" http://jenkins.mysite.com:8192/p4/change }} And Postman: {{ POST /p4/change HTTP/1.1Host: jenkins.mysite.com:8192Content-Type: application/jsonCache-Control: no-cachePostman-Token: 8425cf56-212f-f0fa-7007-b70a4591565epayload={"change":"500", "p4port" :"perf.mysite.com:1666"} }} *Job Setup:*It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve it) and the Perforce Credentials were chosen. A workspace name was assigned, and a View Mapping was applied. Under "Build Triggers", *only "Perforce triggered build." is checked*. *Logs:*When Postman is used to POST the JSON payload as a simple test-case the following is printed into the logs (note that this was POST'd multiple times with different change values): bq. Nov 14, 2016 3:44:32 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChange bq. Received trigger event: {"change":"202","p4port":"perf.mysite.com:1666"} bq. Nov 14, 2016 3:44:48 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChange bq. Received trigger event: {"change":500,"p4port":"perf.mysite.com:1666"}However, nothing in the logs happens after that. I know that the [probeJobs](https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java#L92) function works, as the Manual Trigger also invokes it and that is successfully printed. If I run the "Manual Configuration for Trigger" via the webpage, the following is printed into the logs: bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChangeSubmit bq. Manual trigger event: bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobs bq. P4: probing: MY_PROJECT bq. Nov 14, 2016 3:49:57 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger poke bq. P4: poking: MY_PROJECT bq. Nov 14, 2016 3:50:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChange bq. getBuildChange:return:726 bq. The only thing I can think of at this point is that it is not correctly retrieving the string for "p4port" variable, thus it never runs
[JIRA] (JENKINS-39734) P4 Trigger (/p4/change) Doesn't Detect p4port
Title: Message Title
Matt Hoffman created an issue
Jenkins / JENKINS-39734
P4 Trigger (/p4/change) Doesn't Detect p4port
Issue Type:
Bug
Assignee:
Rob Petti
Components:
perforce-plugin
Created:
2016/Nov/15 12:18 AM
Environment:
Jenkins ver. 2.19.2 Peforce Plugin ver. 1.4.8 Windows Server 2012
Labels:
trigger, perforce
Priority:
Minor
Reporter:
Matt Hoffman
Hi all, We are unable to get P4 Triggered builds to work on our local Jenkin/Perforce setup. When the JSON payload is POST'd to /p4/change it does not trigger our builds which are set to "Perforce triggered build.", but using the "Manual Configuration for Trigger" does work. If I use the /p4/ url and the "Manual Configuration for Trigger" and specify the port as: "perf.mysite.com:1666", and the change as "200" (not entirely clear what this field is used for, any number seems to work) this will cause the build to correctly trigger and fire. We have tried both using cURL (as per the example) and Postman and neither of them can successfully trigger builds. This is the exact cUrl command we use: curl --header "Content-Type: application/json" --request POST --data "payload= {change:200,p4port:\"perf.mysite.com:1666\"} " http://jenkins.mysite.com:8192/p4/change And Postman: POST /p4/change HTTP/1.1 Host: jenkins.mysite.com:8192 Content-Type: application/json Cache-Control: no-cache Postman-Token: 8425cf56-212f-f0fa-7007-b70a4591565e payload= {"change":"500", "p4port" :"perf.mysite.com:1666"} Job Setup: It was set up as a freestyle job (inside of a folder, though moving the job to the root level does not resolve
[JIRA] (JENKINS-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Michael Neale commented on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) Try installing this plugin directly: https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Pipeline+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-18005) Git Publisher plugin does not use token macro expressions for tag name
Title: Message Title Michael Fowler commented on JENKINS-18005 Re: Git Publisher plugin does not use token macro expressions for tag name Fixed in Pull Request: https://github.com/jenkinsci/git-plugin/pull/448 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title James Dumay commented on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) Jakub Czaplicki sorry you ran into this problem. Ill get someone to take a look ASAP. 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39723 BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) Change By: James Dumay Component/s: pipeline-model-definition-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-38316) Putting Jenkins in shutdown mode breaks running pipeline runs
Title: Message Title Dan Alvizu updated an issue Jenkins / JENKINS-38316 Putting Jenkins in shutdown mode breaks running pipeline runs Change By: Dan Alvizu Component/s: pipeline Component/s: build-pipeline-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-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay commented on JENKINS-39647 Re: Failed to write defaultParameterValue Ivan Meredith from Vivek Pandey "first we need to see why is it giving Illegal choice error and then submit a PR to that 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: James Dumay Sprint: arctic 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: James Dumay Sprint: tasman 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-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Damon Osgood commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails I am just now setting up Jenkins with Kubernetes slaves, and I do see this problem. I had thought it might have to do with failed builds, but extremely quick builds could also be the key. 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: James Dumay The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781) and we .In Scope* Skipped stages are shown as not built* Declarative Pipeline will need some way to show these on not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.* If the first stage is skipped then the pipeline graph should start from a "Start" node . * If the last stage is skipped then the pipeline should end with a "End" node.* Ensure that the editors start/end nodes match the style in this mockup 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
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title James Dumay stopped work on JENKINS-39628 Change By: James Dumay 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: James Dumay Assignee: Brody Maclean 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-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-39620 Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters Change By: Bruno P. Kinoshita Attachment: uno-choice-1.5.2-SNAPSHOT-20161115122800.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-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Title: Message Title
Bruno P. Kinoshita commented on JENKINS-39620
Re: Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Hi Paul, >We just upgraded our plugin to 1.5.1 (from 1.3) on our TEST server and have experienced this exact issue It's great to have another test server to experiment with changes. Could you run some tests with alpha/beta versions? >Is the hpi available on the download server definitely the correct one? Just downloaded the 1.5.1 hpi, and decompiled with jad. The fields are definitely not transient. However, while looking at the decompiled code, I noticed the serialVersionUID was not updated. So I've update the serialversionUID locally. Could you give it a go in your local test environment, please? I'm attaching the hpi with this change:
~/Development/java/workspace/active-choices-plugin$ git diff
diff --git a/src/main/java/org/biouno/unochoice/model/GroovyScript.java b/src/main/java/org/biouno/unochoice/model/GroovyScript.java
index d74d9ab..2b828b3 100644
--- a/src/main/java/org/biouno/unochoice/model/GroovyScript.java
+++ b/src/main/java/org/biouno/unochoice/model/GroovyScript.java
@@ -53,7 +53,7 @@ public class GroovyScript extends AbstractScript {
/*
* Serial UID.
*/
-private static final long serialVersionUID = -4886250205110550815L;
+private static final long serialVersionUID = -3741105849416473898L;
private static final Logger LOGGER = Logger.getLogger(GroovyScript.class.getName())
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39478) Select box / Dropdown component
Title: Message Title Brody Maclean commented on JENKINS-39478 Re: Select box / Dropdown component Updated Dropdown / Select Box at bottom Zeplin https://zpl.io/20uAgw 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-39478) Select box / Dropdown component
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-39478 Select box / Dropdown component Change By: Brody Maclean Attachment: Buttons.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-36975) User should only see the administration link in the header if they are logged in
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36975 User should only see the administration link in the header if they are logged in Change By: James Dumay Sprint: 1.0-beta-1, 1.0-b05/b-06 , arctic 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-36975) User should only see the administration link in the header if they are logged in
Title: Message Title James Dumay reopened an issue Ivan Meredith lets get this one fixed too. Jenkins / JENKINS-36975 User should only see the administration link in the header if they are logged in Change By: James Dumay Resolution: Fixed Status: Resolved Reopened 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-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-39647 Failed to write defaultParameterValue Change By: James Dumay Assignee: Ivan Meredith 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-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39647 Failed to write defaultParameterValue Change By: James Dumay Sprint: tasman arctic 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-28403) OpenStack-Clouds-Plugin (single-use slave has already been used and is pending removal for 10 Mins.)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28403 Re: OpenStack-Clouds-Plugin (single-use slave has already been used and is pending removal for 10 Mins.) Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/pom.xml jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/InstancesToRun.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsCloud.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsOneOffSlave.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsStartupHandler.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/internal/TerminateNodes.java jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/InstancesToRun/config.jelly jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper/help-instancesToRun.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper/help.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsOneOffSlave/help.html jclouds-plugin/src/test/java/jenkins/plugins/jclouds/compute/internal/TerminateNodesTest.java http://jenkins-ci.org/commit/jclouds-plugin/3bc1200cba16f54c9bcad01cec6402bf29b2e6c6 Log: Fixing JENKINS-28403 and JENKINS-27471 (WIP) 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
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Brody Maclean edited a comment on JENKINS-39628 Re: Handle skipped stages and parallels in the Pipeline Graph Zeplin https://zpl.io/Z2m0Q0lStart / End nodes are added when First / Last stages are skipped. (see bottom of mockup)Example of skipping 2 stages also at the bottom of the mockup !Skipped Step.png|thumbnail! 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-27471) jClouds deletes nodes that are running flyweight builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27471 Re: jClouds deletes nodes that are running flyweight builds Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/pom.xml jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/InstancesToRun.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsCloud.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsOneOffSlave.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsStartupHandler.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/internal/TerminateNodes.java jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/InstancesToRun/config.jelly jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper/help-instancesToRun.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper/help.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsOneOffSlave/help.html jclouds-plugin/src/test/java/jenkins/plugins/jclouds/compute/internal/TerminateNodesTest.java http://jenkins-ci.org/commit/jclouds-plugin/3bc1200cba16f54c9bcad01cec6402bf29b2e6c6 Log: Fixing JENKINS-28403 and JENKINS-27471 (WIP) 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: Brody Maclean Attachment: Skipped Step.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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Brody Maclean edited a comment on JENKINS-39628 Re: Handle skipped stages and parallels in the Pipeline Graph Zeplin https://zpl.io/ 1wgQ9k Z2m0Q0l Start / End nodes are added when First / Last stages are skipped. (see bottom of mockup)Example of skipping 2 stages also at the bottom of the mockup !Skipped Step.png|thumbnail! 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: Brody Maclean Attachment: Skipped Step.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-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay commented on JENKINS-39647 Re: Failed to write defaultParameterValue Thanks ill get someone to take a look. 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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title Vivek Pandey commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint Tom FENNELLY Great thanks. I will look at generalizing it. BTW, whats the best way to create 5000+ jobs? groovy script console? 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-39133) Aborting a build can result in an UNKNOWN stage state
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39133 Aborting a build can result in an UNKNOWN stage state Change By: Michael Neale Sprint: tasman 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-39658) Include failed step's error to it's log
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39658 Include failed step's error to it's log Change By: Michael Neale Sprint: tasman 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-39133) Aborting a build can result in an UNKNOWN stage state
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39133 Aborting a build can result in an UNKNOWN stage state Change By: Michael Neale Sprint: arctic 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-39681) Creating a pipeline with a duplicate name returns a 500 error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39681 Creating a pipeline with a duplicate name returns a 500 error Change By: Michael Neale Sprint: arctic 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-39681) Creating a pipeline with a duplicate name returns a 500 error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39681 Creating a pipeline with a duplicate name returns a 500 error Change By: Michael Neale Sprint: tasman 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-39658) Include failed step's error to it's log
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39658 Include failed step's error to it's log Change By: Michael Neale Sprint: arctic 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-39733) pipeline stage view confusingly applies final build status to all stages
Title: Message Title mcrooney created an issue Jenkins / JENKINS-39733 pipeline stage view confusingly applies final build status to all stages Issue Type: Bug Assignee: Sam Van Oort Attachments: current.png, proposed.png Components: pipeline-stage-view-plugin Created: 2016/Nov/14 10:57 PM Priority: Major Reporter: mcrooney The Pipeline stage view has individual cells for each stage, but colors all stages the color of the build result at the end of the build. This makes it very confusing to figure out at which stage the build became unstable/failed, and is rather deceptive as it appears to always have done so at the first step. Please see "current" and "proposed" attachments for a suggestion about how this could be improved to make debugging much easier and be less deceptive. This would really be awesome! Add Comment
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz edited a comment on JENKINS-33632
Re: docker.inside broken
Hello [~jglick],I think I found a self-contained example showing that the issue is still around. Using the following versions of Docker* Docker 1.12.2, build bb80604 (on linux).* Docker 1.12.3, build 6b644ec, experimental (on windows).And using [this gist|https://gist.github.com/PierreBtz/9bf58de96fdf5f0b0f272cba850f1161], I ended up with the following error on my two machines:{noformat}$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/jobs/demo/workspace -v /var/jenkins_home/jobs/demo/workspace:/var/jenkins_home/jobs/demo/workspace:rw -v /var/jenkins_home/jobs/demo/workspace@tmp:/var/jenkins_home/jobs/demo/workspace@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat ubuntu[Pipeline] {[Pipeline] sh[workspace] Running shell scriptsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/pid: Directory nonexistentsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-log.txt: Directory nonexistentsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-result.txt: Directory nonexistent{noformat}Version of the Docker pipeline is 1.9.1 at the time of this writing , but as you can see in the console dump, the -v flag is used instead of the --volume-from, as if the plugin did not detect it was running inside a container . *Steps to reproduce** Copy [this gist|https://gist.github.com/PierreBtz/9bf58de96fdf5f0b0f272cba850f1161]* Set the executable permissions on the scripts.* Run the build script and then the run script.* The Jenkins instance will be available on port 8080. There is one job in it running the following:{noformat}node ('master') {sh 'pwd'img = docker.image('ubuntu')img.inside {sh 'pwd'}}{noformat}Do you think there is enough to reopen this issue?Thanks
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz commented on JENKINS-33632
Re: docker.inside broken
Hello Jesse Glick, I think I found a self-contained example showing that the issue is still around. Using the following versions of Docker
Docker 1.12.2, build bb80604 (on linux).
Docker 1.12.3, build 6b644ec, experimental (on windows).
And using this gist, I ended up with the following error on my two machines:
$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/jobs/demo/workspace -v /var/jenkins_home/jobs/demo/workspace:/var/jenkins_home/jobs/demo/workspace:rw -v /var/jenkins_home/jobs/demo/workspace@tmp:/var/jenkins_home/jobs/demo/workspace@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat ubuntu
[Pipeline] {
[Pipeline] sh
[workspace] Running shell script
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/pid: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-log.txt: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-result.txt: Directory nonexistent
Version of the Docker pipeline is 1.9.1 at the time of this writing. Steps to reproduce
Copy this gist
Set the executable permissions on the scripts.
Run the build script and then the run script.
The Jenkins instance will be available on port 8080. There is one job in it running the following:
node ('master') {
sh 'pwd'
img = docker.image('ubuntu')
img.inside {
sh 'pwd'
}
}
Do you think there is enough to reopen this issue? Thanks
Add Comment
[JIRA] (JENKINS-39732) Specific Jenkinsfile hangs indefinitely on archiveArtifacts step
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-39732 Specific Jenkinsfile hangs indefinitely on archiveArtifacts step Issue Type: Bug Assignee: CloudBees Inc. Components: pipeline Created: 2016/Nov/14 10:30 PM Environment: Jenkins 2.19.1 Priority: Minor Reporter: R. Tyler Croy This Jenkinsfile hangs indefinitely on the archiveArtifacts step. Unfortunately, despite my best efforts I have not been able to reduce this into a smaller test case Creating a single Pipeline with "Pipeline from SCM" using the GIt repo: git://github.com/jenkins-infra/plugin-site-api.git and the "Branch" set to the SHA1: e84390edc3e801369e1de3f52c35ff44223f4f0f should be enough to reproduce this. Add Comment
[JIRA] (JENKINS-39684) Use docker images from private registry
Title: Message Title
Michael Neale commented on JENKINS-39684
Re: Use docker images from private registry
Patrick Wolf Andrew Bayer I think the agent syntax was made flexible enough to cater for this. agent docker:"foo" registry: {... config for registry} would something like that work? or the docker item take a block in that case with all the config needed? (Andrew would be able to comment on what is best)
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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title Tom FENNELLY commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint Michael Neale If you just get one record (https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0=1) you'll see that it's 23,000+ lines of JSON and it looks like most of that is artifacts. 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-39570) Maven job type's "module" shown on dashboard
Title: Message Title James Dumay commented on JENKINS-39570 Re: Maven job type's "module" shown on dashboard would be good to get a test for this 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-32393) PATH and HOME are being overwritten when executing command
Title: Message Title Phil Porada commented on JENKINS-32393 Re: PATH and HOME are being overwritten when executing command I am experiencing this as well. Here is my current workaround on all jobs that use this 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-32393) PATH and HOME are being overwritten when executing command
Title: Message Title Phil Porada updated an issue Jenkins / JENKINS-32393 PATH and HOME are being overwritten when executing command Change By: Phil Porada Attachment: workaround.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-39729) build issue when file name as spaces
Title: Message Title desh hari assigned an issue to desh hari Jenkins / JENKINS-39729 build issue when file name as spaces Change By: desh hari Assignee: Kohsuke Kawaguchi desh hari 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-34538) Pipeline Stage View duplicates rows if displayName is changed
Title: Message Title James Dumay commented on JENKINS-34538 Re: Pipeline Stage View duplicates rows if displayName is changed Tom FENNELLY would you mind giving this a review for Julien Pivotto please? 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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title Michael Neale commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint Tom FENNELLY interesting - on your last comment, would that response be helped by using correct pagination? (that response size seems odd - what is bloating it?) 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-39731) Integrations
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39731 Integrations Issue Type: Epic Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/14 9:14 PM Priority: Minor Reporter: James Dumay 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
[JIRA] (JENKINS-39730) Developer wants to see a list of JIRA tickets on changes tab
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39730 Developer wants to see a list of JIRA tickets on changes tab Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/14 9:13 PM Priority: Minor Reporter: James Dumay Developer wants to see a list of JIRA tickets on the changes tab. A table listing all the JIRA tickets with the status, summary, assignee and resolution should appear above the commits. In Scope Reuse the JIRA Plugin to detect links to JIRA from commit messages Add Comment
[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Title: Message Title Paul Martin reopened an issue Hi Bruno, We just upgraded our plugin to 1.5.1 (from 1.3) on our TEST server and have experienced this exact issue. We tried downgrading/upgrading and manually installing the hpi... neither worked. Is the hpi available on the download server definitely the correct one? Thanks! Paul Jenkins / JENKINS-39620 Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters Change By: Paul Martin Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-26315) Git plugin can't handle property references in repository URLs when polling
Title: Message Title Michael Fowler resolved as Duplicate Jenkins / JENKINS-26315 Git plugin can't handle property references in repository URLs when polling Change By: Michael Fowler Status: Open Resolved Resolution: Duplicate 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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Sai tharun nelaballi commented on JENKINS-39728 Re: Jenkins not able to clone private bitbucket repo I am using an older version of plugins in my another laptop, there I am not getting any issues at all. I am using Windows 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-37533) Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL
Title: Message Title Michael Fowler resolved as Duplicate Jenkins / JENKINS-37533 Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL Change By: Michael Fowler Status: Open Resolved Resolution: Duplicate 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-39729) build issue when file name as spaces
Title: Message Title desh hari created an issue Jenkins / JENKINS-39729 build issue when file name as spaces Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: _unsorted, sonar Created: 2016/Nov/14 8:39 PM Environment: sonarqube plugin Labels: jenkins Priority: Blocker Reporter: desh hari I created a job where sonar pulls the required jobs from jenkins workspace, but couple of files has spaces in it and its considering as "MSBUILD : error MSB1008: Only one project can be specified." I realized that i need to write a script or update jenkins to take files from workspace irrespective of spaces or special characters, that files should undergo sonar. Kindly suggest how this can be done. INFO: Start | Analysis | C:/Users/tcepoc/.jenkins/jobs/ClearcaseSonar/workspace/eng_kpi.udf_ProjectX_P4_Report_Rev_12 12 11.UserDefinedFunction.sql INFO: Location | Output Report | C:\Users\tcepoc\.jenkins\jobs\ClearcaseSonar\workspace\.sonar\sqlcodeguard_report.xml INFO: Start | Execution | C:\sonarqube-5.6\extensions\plugins\TechCognia-Tsql-Plugin-1.5.1\TechCognia-Tsql-Plugin-1.5.1\Attachments\TechCognia\SqlCodeGuard.msbuild INFO: Executing command: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "C:\sonarqube-5.6\extensions\plugins\TechCognia-Tsql-Plugin-1.5.1\TechCognia-Tsql-Plugin-1.5.1\Attachments\TechCognia\SqlCodeGuard.msbuild" /p:SourcePath="C:/Users/tcepoc/.jenkins/jobs/ClearcaseSonar/workspace/eng_kpi.udf_ProjectX_P4_Report_Rev_12 12
[JIRA] (JENKINS-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Sai tharun nelaballi created an issue Jenkins / JENKINS-39728 Jenkins not able to clone private bitbucket repo Issue Type: Task Assignee: Stephen Connolly Components: credentials-plugin, git-plugin Created: 2016/Nov/14 8:30 PM Priority: Critical Reporter: Sai tharun nelaballi Building in workspace C:\Program Files (x86)\Jenkins\workspace\test Cloning the remote Git repository Cloning repository https://saitharu...@bitbucket.org/mmanche_bitbucket/winzonepoc.git > git.exe init C:\Program Files (x86)\Jenkins\workspace\test # timeout=10 Fetching upstream changes from https://saitharu...@bitbucket.org/mmanche_bitbucket/winzonepoc.git > git.exe --version # timeout=10 using GIT_ASKPASS to set credentials > git.exe fetch --tags --progress https://saitharu...@bitbucket.org/mmanche_bitbucket/winzonepoc.git +refs/heads/:refs/remotes/origin/ ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git.exe fetch --tags --progress https://saitharu...@bitbucket.org/mmanche_bitbucket/winzonepoc.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: fatal: unable to access 'https://saitharu...@bitbucket.org/mmanche_bitbucket/winzonepoc.git/': Failed to connect to bitbucket.org port 443: Connection refused at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1042) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at
[JIRA] (JENKINS-39727) Any way to control builds from PR comments?
Title: Message Title Sergiy Kukunin created an issue Jenkins / JENKINS-39727 Any way to control builds from PR comments? Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Nov/14 8:08 PM Priority: Minor Reporter: Sergiy Kukunin Github Pull Request Builder plugin, which isn't compatible with Pipeline had a great ability to control builds from comments on Github for given PR. It is possible to re-run build using 'retest this please', and also it asked before running build automatically. Can we implement something like this on top of github organization folder plugin? Add Comment
[JIRA] (JENKINS-36391) promoted build sort order
Title: Message Title Jon Bettinger commented on JENKINS-36391 Re: promoted build sort order Ah, looks like this has been fixed, but not released yet. https://github.com/jenkinsci/promoted-builds-plugin/pull/92 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-39726) Don't rebuild all PRs on base branch update
Title: Message Title Sergiy Kukunin created an issue Jenkins / JENKINS-39726 Don't rebuild all PRs on base branch update Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Nov/14 7:53 PM Priority: Minor Reporter: Sergiy Kukunin I migrated to Pipeline with Github Organization Folder plugin very soon, it's so great and I'm so happy with it. However, it has a behaviour, that when on PR gets merged, and base branch gets updated, all PRs get rebuilt. While it makes sense, it causes huge load on build server. Can you do it configurable? At least, it makes sense to not rebuild PRs with failed previous build (on unfinished PR) Add Comment
[JIRA] (JENKINS-39563) Basic form components
Title: Message Title Cliff Meyers commented on JENKINS-39563 Re: Basic form components Initial PR for developer feedback: https://github.com/jenkinsci/jenkins-design-language/pull/114 This is not far along enough yet to be considered "In Review" IMO. 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-39725) Not able to clone Bitbucket private repo
Title: Message Title Mark Waite closed an issue as Not A Defect Please don't use bug reports to ask for help with authentication issues with your git repository. The Jenkins user mailing list has many more users on the list who can assist with authentication related questions. You may also want to review other bug reports related to bitbucket authentication issues, particularly those which refer to embedding the user name and password in the bitbucket URL. Jenkins / JENKINS-39725 Not able to clone Bitbucket private repo Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39725) Not able to clone Bitbucket private repo
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39725 Not able to clone Bitbucket private repo Change By: Mark Waite Assignee: Mark Waite 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-39718) Fix PCT against 2.x baseline and migrate to 2.17 parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39718 Re: Fix PCT against 2.x baseline and migrate to 2.17 parent POM Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/plugins/asynchttpclient/AHC.java http://jenkins-ci.org/commit/async-http-client-plugin/f688e1590b2ea42b2e5e1378f6cc304d7318a9aa Log: Merge pull request #6 from varyvol/JENKINS-39718 JENKINS-39718 Fix PCT against 2.x baseline and migrate to 2.17 parent POM Compare: https://github.com/jenkinsci/async-http-client-plugin/compare/3a4acefb9c04...f688e1590b2e 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-39718) Fix PCT against 2.x baseline and migrate to 2.17 parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39718 Re: Fix PCT against 2.x baseline and migrate to 2.17 parent POM Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml src/main/java/jenkins/plugins/asynchttpclient/AHC.java http://jenkins-ci.org/commit/async-http-client-plugin/5310b13b4a96bd94912364672ec90bf3c1395491 Log: JENKINS-39718 Fix Windbag error on PCT. Migrate to 2.17 parent POM. 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-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title Christoph Obexer commented on JENKINS-38552 Re: Multibranch pipeline (re)creation intelligence "Skip initial build on first branch indexing" would be awesome. 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-39724) Show LoadRunner scneario result embeded in Jenkins
Title: Message Title Yafim Kazak commented on JENKINS-39724 Re: Show LoadRunner scneario result embeded in Jenkins Available today with two speciallized action buttons per build. Each build has action button that link to transaction report and action button that links to summary report. Currently, if you use Jenkins version above 1.625 than you should follow the following guidelines in case you have issues with seeing the reports linked to the actions - https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-ContentSecurityPolicyHeader 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.
