[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-38447 Bitbucket hooks don't work for Pipeline jobs Change By: Hendrik Brinkmann Priority: Major Critical 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-36907) OrganizationImpl needs to not use Jenkins.getDisplayName
Title: Message Title James Dumay reopened an issue Jenkins / JENKINS-36907 OrganizationImpl needs to not use Jenkins.getDisplayName Change By: James Dumay Resolution: Won't Fix Status: Resolved Reopened Assignee: 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 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-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title Rob Birdwell commented on JENKINS-39960 Re: EC2 Plugin: Invalid groupID parameter when provisioning I had to enter the security group ID (sg-X) for the "Security group names" and additionally enter the Subnet ID for VPC (subnet-) in order for this to disappear. 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-40054) Connect to 127.0.0.1:2375 [/127.0.0.1] failed: Connection refused
Title: Message Title Mark Lehky commented on JENKINS-40054 Re: Connect to 127.0.0.1:2375 [/127.0.0.1] failed: Connection refused So I guess I need to configure Docker, something like https://docs.docker.com/engine/admin/ But when I use the plugin Docker installer, where I do I find the docker.conf? And why can I not do this from the plugin page in Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title James Dumay commented on JENKINS-38536 Re: Execution time of parallel blocks of in-flight jobs wrong Sam Van Oort if its not too much trouble are you able to verify that this fixes JENKINS-39158 ? 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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Sam Van Oort commented on JENKINS-38536 Re: Execution time of parallel blocks of in-flight jobs wrong Another fix yielded the full solution (combined with this one). Ready for release now. 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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Sam Van Oort updated JENKINS-38536 Pending release as v2.8 Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Change By: Sam Van Oort 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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Change By: Sam Van Oort Component/s: pipeline-stage-view-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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38536 Re: Execution time of parallel blocks of in-flight jobs wrong Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScanner.java src/test/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScannerTest.java http://jenkins-ci.org/commit/workflow-api-plugin/eca21af30bcf90e4a7ae29c14747ebdfedd8d84b Log: Merge pull request #20 from jenkinsci/final-parallel-branch-ordering Ensure that for SimpleBlockVisitor we find the REAL last branch for a parallel JENKINS-38536 Compare: https://github.com/jenkinsci/workflow-api-plugin/compare/92ab59a0cff1...eca21af30bcf 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-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-39854 REGRESSION: activity/branch run status is not updated after closing karaoke mode Change By: James Dumay Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title James Dumay commented on JENKINS-39854 Re: REGRESSION: activity/branch run status is not updated after closing karaoke mode I can confirm this has been fixed. Nice one! 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-39953) Under some conditions clicking on activity forces a reload
Title: Message Title James Dumay resolved as Fixed Looks like this is fixed Jenkins / JENKINS-39953 Under some conditions clicking on activity forces a reload Change By: James Dumay Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40114) The details of changes can't be shown in page after upgrade to 1.10.4
Title: Message Title Makson Lee started work on JENKINS-40114 Change By: Makson Lee Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33981) P4 Plugin - Using auto cleanup & sync with REPLACE missing/modified files fails
Title: Message Title yury nedelin updated an issue Jenkins / JENKINS-33981 P4 Plugin - Using auto cleanup & sync with REPLACE missing/modified files fails Change By: yury nedelin Priority: Minor Major 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-33981) P4 Plugin - Using auto cleanup & sync with REPLACE missing/modified files fails
Title: Message Title yury nedelin commented on JENKINS-33981 Re: P4 Plugin - Using auto cleanup & sync with REPLACE missing/modified files fails I am having exactly the same problem. Is there a solution for this or a work around? thank you Yury 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-40114) The details of changes can't be shown in page after upgrade to 1.10.4
Title: Message Title Makson Lee assigned an issue to Makson Lee Jenkins / JENKINS-40114 The details of changes can't be shown in page after upgrade to 1.10.4 Change By: Makson Lee Assignee: Makson Lee 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-40115) Ability to specify feed to use for poling
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-40115 Ability to specify feed to use for poling Issue Type: Improvement Assignee: Unassigned Components: nuget-plugin Created: 2016/Nov/30 4:31 AM Priority: Major Reporter: Michael Fowler 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
[JIRA] (JENKINS-40114) The details of changes can't be shown in page after upgrade to 1.10.4
Title: Message Title Makson Lee commented on JENKINS-40114 Re: The details of changes can't be shown in page after upgrade to 1.10.4 seems that [1] changed the visibility of class ChangeLogEntry from public to default so the details of changes can't be accessed from src/main/resources/hudson/plugins/repo/RepoChangeLogSet/index.jelly. [1] https://github.com/maksonlee/repo-plugin/commit/ae08c754dd451a16f735a9173178b84932769c1d 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-40114) The details of changes can't be shown in page after upgrade to 1.10.4
Title: Message Title Makson Lee created an issue Jenkins / JENKINS-40114 The details of changes can't be shown in page after upgrade to 1.10.4 Issue Type: Bug Assignee: Unassigned Components: repo-plugin Created: 2016/Nov/30 4:17 AM Priority: Minor Reporter: Makson Lee 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
[JIRA] (JENKINS-39998) Token expansion of a config file not happening
Title: Message Title
Sathyakumar Seshachalam commented on JENKINS-39998
Re: Token expansion of a config file not happening
Thanks for the reply. I am still unable to get this working. I do have Token macro plugin installed. I understood the unit test case, I gave the exact string $ {ENV, var="JOB_NAME"} inside my config file, and yet they came back un-replaced. And I got ${ENV, var="JOB_NAME"} $ {ENV, var="INSTANCE"} Any pointers on how to debug this which log to verify etc., ? From your reply, it seems like there is a configuration issue at my end, because $ {INSTANCE} never really threw any error whatsoever and am unable to figure out what configuration I am missing.
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-39713) java.io.IOException: Failed to dynamically deploy this plugin for job-dsl plugin
Title: Message Title Gowtham Prudhvi updated an issue Jenkins / JENKINS-39713 java.io.IOException: Failed to dynamically deploy this plugin for job-dsl plugin Change By: Gowtham Prudhvi Issue Type: Bug Patch 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-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Mac Feliciano updated an issue Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff Change By: Mac Feliciano The semantic-versioning-plugin plugin causes the dashboard to display: "Oops! ...A problem occurred while processing the request, " along with a stack trace. See attached screenshot. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.34.jar!/hudson/model/View/index.jelly:42:43: JSONObject["displayStrategy"] not found. at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)As stated on the [semantic-versioning-plugin info page|https://wiki.jenkins-ci.org/display/JENKINS/semantic-versioning-plugin], "The second part of the plugin adds a column to the Dashboard that displays the Semantic Versioning string from the most recent successful build." Something is broken with that second part. Whenever the plugin is enabled, the dashboard biffs. When it's disabled, the dashboard displays fine.A fix would be greatly appreciated! A workaround is NOT to simply disable the plugin, as we need semantic versioning, and so we need this plug-in. Perhaps simply remove the additional column being added to the Dashboard by the plug-in for now.Related tickets ticket : https://issues.jenkins-ci.org/browse/JENKINS-37993 Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Mac Feliciano created an issue Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-11-29 at 8.11.24 PM.png Components: semantic-versioning-plugin Created: 2016/Nov/30 3:32 AM Environment: semantic-versioning-plugin 1.10 Jenkins v2.34 Amazon Linux 4.4.30-32.54.amzn1.x86_64 Priority: Major Reporter: Mac Feliciano The semantic-versioning-plugin plugin causes the dashboard to display: "Oops! ...A problem occurred while processing the request, " along with a stack trace. See attached screenshot. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.34.jar!/hudson/model/View/index.jelly:42:43: JSONObject["displayStrategy"] not found. at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) As stated on the semantic-versioning-plugin info page, "The second part of the plugin adds a column to the Dashboard that displays the Semantic Versioning string from the most recent successful build." Something is broken with that second part. Whenever the plugin is enabled, the dashboard biffs. When it's disabled, the dashboard displays fine. A fix would be greatly appreciated! A workaround is NOT to simply disable the plugin, as we need semantic versioning, and so we need this plug-in. Perhaps simply remove the additional column being added to the Dashboard by the plug-in
[JIRA] (JENKINS-39790) API to validate that the Github access token is valid
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39790
API to validate that the Github access token is valid
Change By:
James Dumay
* Send access token in request body* Response can be** 200, returning credential in response body** 403 if token is invalid or has insufficient access * The access token credential is created on 200 and is User scoped Sample request:{code}{"accessToken": "abcd1234..."}{code}Sample 200 response:{code}{"credentialId": "1234-..."}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39788) API to get all the repositories in an organization
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-39788 API to get all the repositories in an organization Change By: James Dumay Assignee: Vivek Pandey 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-39789) API to get all the organizations the user has access to
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-39789 API to get all the organizations the user has access to Change By: James Dumay Assignee: Vivek Pandey 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-39790) API to validate that the Github access token is valid
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-39790 API to validate that the Github access token is valid Change By: James Dumay Assignee: Vivek Pandey 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-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Assignee: Vivek Pandey 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-39788) API to get all the repositories in an organization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39788 API to get all the repositories in an organization 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-39789) API to get all the organizations the user has access to
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39789 API to get all the organizations the user has access to 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-36610) [Blue Ocean] Remove hard coded link to new job from blue ocean header
Title: Message Title James Dumay resolved as Duplicate There's a whole epic planned (JENKINS-36588) to remove this and replace it with something nicer! Jenkins / JENKINS-36610 [Blue Ocean] Remove hard coded link to new job from blue ocean header Change By: James Dumay 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
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed 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-39790) API to validate that the Github access token is valid
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39790 API to validate that the Github access token is valid 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-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Dennis Cheung commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline Is there a commanded way to check if concurrent running jobs on same node cause some problems/regression? In the old freestyle job, there are records on the history page. It is easy to identify overlapping and blame it for performance regression. However, same information lost and quite hidden from the Pipeline. You cannot even tell which nodes were used without look into the full log. 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-36455) Enable merge commits to be built from origin PRs by default
Title: Message Title James Dumay resolved as Won't Fix Jenkins / JENKINS-36455 Enable merge commits to be built from origin PRs by default Change By: James Dumay Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39795) API to check that Org folder indexing has completed
Title: Message Title James Dumay resolved as Duplicate The work for this has been subsumed into JENKINS-38847 Jenkins / JENKINS-39795 API to check that Org folder indexing has completed Change By: James Dumay 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-39791) API to determine for a Github repository and branch name if it contains a Jenkinsfile
Title: Message Title James Dumay resolved as Won't Fix Jenkins / JENKINS-39791 API to determine for a Github repository and branch name if it contains a Jenkinsfile Change By: James Dumay Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39791) API to determine for a Github repository and branch name if it contains a Jenkinsfile
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-39791 API to determine for a Github repository and branch name if it contains a Jenkinsfile Change By: Cliff Meyers *Use case** When the user clicks on a repository in the list** Jenkinsfile is present they will go to the executing Pipeline** Jenkinsfile is not present they will segue to the Editor*Notes*On click we can use https://developer.github.com/v3/repos/contents/ to determine if there is a Jenkinsfile there or not.Bitbucket have this too https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/downloads/%7Bfilename%7D Request 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-38438) image.inside { ... } does not create full configured user account
Title: Message Title
Mike Kobit commented on JENKINS-38438
Re: image.inside { ... } does not create full configured user account
Some of the restrictions here could possibly be worked around by power users if a custom entrypoint was allowed to be overridden (at https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L175). I haven't thought too much about the side effects, but this would allow for some more customizability, such as creating the user and group creation/mapping at startup. Another thing is that our developers already have tooling and automation built around docker, so they are not inclined to use docker.build with the Jenkinsfile. They would prefer to use the existing build plugins and tools inside of the Jenkinsfile, so being able to provide some way to mount the host Docker socket in (possible today) while also creating a user/group to allow the current -u user/group mapping would be useful.
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-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title Sam Van Oort commented on JENKINS-38491 Re: Add new "waitingForInput" status to API for runs, dag and steps @vivek I'm shocked to see you really do need all the statuses in pipeline-graph-analysis (PAUSED_PENDING_INPUT) Two easy ways to get the FlowNode: it'll be a current head (FlowExecution.getCurrentHeads()) and have a PauseAction on it, or mark it when the StatusAndTiming API gives you the node status (it'll be PAUSED_PENDING_INPUT). 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Matt Traynham edited a comment on JENKINS-36195 Re: Pipeline polling ignores special polling rules [~markewaite], this has been a fairly bothersome bug for my team. Most of our pipelines are set up to do maven releases, which can be a bit chatty with Git commit/push; one for the release version commit, a second for the dependency version bump. The two extra concurrent builds can create heavy load on the machine, sometimes causing the release build to fail which can leave our SCM and Nexus repos in a weird limbo state.There are two potential workarounds we've identified to getting this down to a single extra build. Either we restrict the maven push til the very end or attempt to filter out webhook calls from our repo service. Both are a bit of a hack, and we were trying to gauge this bug, ultimately filtering out certain commits with particular messages/users.Could you make a recommendation on any other potential solutions, or point me in the right direction of which projects/code would likely need to change to get this fixed? We are using multi-branch for this, so that may even complicate our position a bit further as mentioned above , it doesn't really use workspace polling. 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Matt Traynham edited a comment on JENKINS-36195 Re: Pipeline polling ignores special polling rules [~markewaite], this has been a fairly bothersome bug for my team. Most of our pipelines are set up to do maven releases, which can be a bit chatty with Git commit/push; one for the release version commit, a second for the dependency version bump. The two extra concurrent builds can create heavy load on the machine, sometimes causing the release build to fail which can leave our SCM and Nexus repos in a weird limbo state.There are two potential workarounds we've identified to getting this down to a single extra build. Either we restrict the maven push til the very end or attempt to filter out webhook calls from our repo service. Both are a bit of a hack, and we were trying to gauge this bug, ultimately filtering out certain commits with particular messages/users.Could you make a recommendation on any other potential solutions, or point me in the right direction of which projects/code would likely need to change to get this fixed? We are using multi-branch for this, so that may even complicate our position a bit further as mentioned above it doesn't really use workspace polling. 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Matt Traynham commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Mark Waite, this has been a fairly bothersome bug for my team. Most of our pipelines are set up to do maven releases, which can be a bit chatty with Git commit/push; one for the release version commit, a second for the dependency version bump. The two extra concurrent builds can create heavy load on the machine, sometimes causing the release build to fail which can leave our SCM and Nexus repos in a weird limbo state. There are two potential workarounds we've identified to getting this down to a single extra build. Either we restrict the maven push til the very end or attempt to filter out webhook calls from our repo service. Both are a bit of a hack, and we were trying to gauge this bug, ultimately filtering out certain commits with particular messages/users. Could you make a recommendation on any other potential solutions, or point me in the right direction of which projects/code would likely need to change to get this 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-14531) CAS1 and 'Trigger builds remotely' incompatibility
Title: Message Title J. David Beutel commented on JENKINS-14531 Re: CAS1 and 'Trigger builds remotely' incompatibility Sorry, I just found this old issue and pull request. I guess it has been overtaken by events, and should not be merged, because cas1-plugin is obsolete and superseded by cas-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-17371) CAS Plugin causes infinite redirects after Jenkins 1.508 upgrade
Title: Message Title J. David Beutel resolved as Won't Fix Sorry, I just found this old issue. I don't think that anyone will work on it, because cas1-plugin is obsolete and superseded by cas-plugin, so I'm resolving this issue as "Won't Fix". I suggest trying cas-plugin instead. Jenkins / JENKINS-17371 CAS Plugin causes infinite redirects after Jenkins 1.508 upgrade Change By: J. David Beutel Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-35698) Initial run of parameterized pipeline build should return properties default value
Title: Message Title
Geoff Kirk updated an issue
Jenkins / JENKINS-35698
Initial run of parameterized pipeline build should return properties default value
Change By:
Geoff Kirk
{color:red}colored text{color} On the first build the config parameter doesn't exist but it'd be great if on this initial build Config parameter could be setup with the default value.For example,{code}properties ([[$class: 'ParametersDefinitionProperty', parameterDefinitions: [[$class: 'StringParameterDefinition', defaultValue: 'Release', description: '', name: 'configParam') {code}So{{binding.hasVariable('configParameter')}} should return true, and should has the value {{Release}}
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-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title
Jacek Sniecikowski created an issue
Jenkins / JENKINS-40112
Having '=' in injected variable value, erases build history after running JobDSL
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
envinject-plugin, job-dsl-plugin
Created:
2016/Nov/30 1:26 AM
Environment:
Jenkins ver. 1.609.3;Environment Injector Plugin 1.93.1;JobDSL 1.45
Priority:
Minor
Reporter:
Jacek Sniecikowski
Looks like EnvInject and/or JobDSL have a bug. Steps to reproduce: 1. Set up a job that runs this JobDSL: `job('run_deploy_mock') { steps { environmentVariables { env('deployedArtifacts', 'component1=1.0.0.2') } } }` 2. Run it and it will create a job called 'deploy_mock' 3. Run the 'deploy_mock' job. After build #1 is done, go to build details and check 'Environmental Variables' section for an entry called 'component1' 4. Run the JobDSL job again 5. Check 'Environmental Variables' section for 'deploy_mock' build #1. The 'component1' variable is now missing. If I substitute the '=' for something else, it works as expected.
[JIRA] (JENKINS-39790) API to validate that the Github access token is valid
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-39790
API to validate that the Github access token is valid
Change By:
Cliff Meyers
* Send access token in request body* Response can be** 200, returning credential in response body** 400 403 if token is invalid or has insufficient accessSample request:{code}{"accessToken": "abcd1234..."}{code}Sample 200 response:{code}{"credentialId": "1234-..."}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39790) API to validate that the Github access token is valid
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-39790
API to validate that the Github access token is valid
Change By:
Cliff Meyers
* Send access token in request body* Response can be** 200, returning credential in response body** 400 if token is invalid or has insufficient accessSample request:{code}{"accessToken": "abcd1234..."}{code}Sample 200 response:{code}{ "credentialId": "1234-..." }{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39790) API to validate that the Github access token is valid
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-39790
API to validate that the Github access token is valid
Change By:
Cliff Meyers
* Send access token in request body* Response can be** 200, returning {{{ credentialId: '1234-...' }}} credential in response body** 400 if token is invalid or has insufficient access Sample 200 response:{code}{ "credentialId": "1234-..." }{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39790) API to validate that the Github access token is valid
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-39790
API to validate that the Github access token is valid
Change By:
Cliff Meyers
* Send access token in request body* Response can be** 200, returning {{{ credentialId: '1234-...' }}} in response body** 400 if token is invalid or has insufficient access
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-39953) Under some conditions clicking on activity forces a reload
Title: Message Title Cliff Meyers commented on JENKINS-39953 Re: Under some conditions clicking on activity forces a reload James Dumay I am fairly confident this was fixed in https://github.com/jenkinsci/blueocean-plugin/pull/614 . Looking at the giphy, the URL does not update after closing the modal. This means the content on the screen is actually the cloned "background DOM" that is used to prevent the "flash" when the modal opens and closes - which is disconnected from React / React Router and won't handle link clicks correctly. Perhaps you'd be willing to test this one more time and close if not repro? 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-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title Cliff Meyers commented on JENKINS-39854 Re: REGRESSION: activity/branch run status is not updated after closing karaoke mode Michael Neale I am fairly confident this was fixed in https://github.com/jenkinsci/blueocean-plugin/pull/614 . Looking at both giphy, the URL does not update after closing the modal. This means the content on the screen is actually the cloned "background DOM" that is used to prevent the "flash" when the modal opens and closes - which is disconnected from React and won't be updated. Perhaps you'd be willing to test this one more time and close if not repro? 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-39894) REGRESSION: SSE broken on MS Edge and IE11
Title: Message Title Tom FENNELLY commented on JENKINS-39894 Re: REGRESSION: SSE broken on MS Edge and IE11 I tried Edge on Windows 10 and it seemed to work fine: https://youtu.be/hR5tFnP5Iww Will try IE 11 now. Jim Klimov Is there anything else you can think of that would help us to reproduce 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-38598) User can create pipeline from Github repository
Title: Message Title Cliff Meyers started work on JENKINS-38598 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title Cliff Meyers stopped work on JENKINS-39854 Change By: Cliff Meyers 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-38323) Developer can drag and drop to reorder steps within a stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38323 Developer can drag and drop to reorder steps within a stage Change By: Michael Neale Priority: Minor Major 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-40111) Make more space for editor components
Title: Message Title Michael Neale closed an issue as Won't Fix needs more thought... premature ticket opening Jenkins / JENKINS-40111 Make more space for editor components Change By: Michael Neale Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40110) Tasks sometimes get broken clients on connection
Title: Message Title Nils Carlson assigned an issue to Paul Allen Jenkins / JENKINS-40110 Tasks sometimes get broken clients on connection Change By: Nils Carlson 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-40111) Make more space for editor components
Title: Message Title Michael Neale commented on JENKINS-40111 Re: Make more space for editor components Seeing which one James prefers 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-40111) Make more space for editor components
Title: Message Title Michael Neale assigned an issue to James Dumay Jenkins / JENKINS-40111 Make more space for editor components Change By: Michael Neale Assignee: 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 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-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title Vivek Pandey commented on JENKINS-38491 Re: Add new "waitingForInput" status to API for runs, dag and steps Sam Van Oort We need to associate a FlowNode (StepAtomNode) with an InputStep. Only possible way I can do it now is, WorkflowRun.getExecutions() and then InputStepExecution.getInput() gives me input but there is no public method to get underlying FlowNode from InputStepExecution. Is there way we can do such association? 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-40111) Make more space for editor components
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40111 Make more space for editor components Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/30 12:06 AM Priority: Major Reporter: Michael Neale The space for the step editor is currently very small, less than 1/5th of the screen. Brody Maclean has a proposed design which looks like it should solve this: http://d.pr/i/P3UI Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40110) Tasks sometimes get broken clients on connection
Title: Message Title Nils Carlson commented on JENKINS-40110 Re: Tasks sometimes get broken clients on connection Paul Allen An ugly workaround is available here: https://github.com/pyssling/p4-plugin/commit/a7af0bcddf2b81b07c86262fe787579cd87dd36e (This breaks unit tests, so really not for merging.) As far as I can tell this goes all the way down to the java API, but a lot of the ConnectionHelper.java stuff is a bit convoluted. I also don't quite understand why setWorkspace in AbstractTask sets the workspace on a connection and then closes it, maybe it would be best to set the workspace only when executing the task? But my understanding of this stuff is pretty sketchy. 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-40110) Tasks sometimes get broken clients on connection
Title: Message Title Nils Carlson updated an issue Jenkins / JENKINS-40110 Tasks sometimes get broken clients on connection Change By: Nils Carlson Environment: Jenkins 2.31p4-plugin 1.4.10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40110) Tasks sometimes get broken clients on connection
Title: Message Title Nils Carlson created an issue Jenkins / JENKINS-40110 Tasks sometimes get broken clients on connection Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Nov/29 11:54 PM Priority: Major Reporter: Nils Carlson Tasks sometimes get a corrupted client when executing. In this case the name of the client and the intended client name do not match. A hackish solution is to throw an exeception in AbstractTask.java if ClientHelper.getClient().getName() and AbstractTask.getClient() do not match. But this is not a real solution in any way. Add Comment
[JIRA] (JENKINS-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Nils Carlson updated JENKINS-40048 Jenkins / JENKINS-40048 Multiple checkout with pipeline script with nested depot paths causes continous builds Change By: Nils Carlson Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Nils Carlson started work on JENKINS-40048 Change By: Nils Carlson Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Cyrille Le Clerc commented on JENKINS-39407 Re: Use system default Maven, Maven Settings if not specified So, if the maven settings file (resp maven global settings file) is not define in "withMaven(...)", then we would default to the default strategy defined on Jenkins global config screen (jenkins.mvn.GlobalMavenConfig): jenkins.mvn.GlobalMavenConfig#getSettingsProvider() jenkins.mvn.GlobalMavenConfig#getGlobalSettingsProvider() 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-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-39407 Use system default Maven, Maven Settings if not specified Change By: Cyrille Le Clerc Attachment: maven-global-settings.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-34908) mask-password does not mask url encoded passwords
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34908 Re: mask-password does not mask url encoded passwords Code changed in jenkins User: msperisen Path: src/main/java/com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream.java src/test/java/com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsURLEncodingTest.java http://jenkins-ci.org/commit/mask-passwords-plugin/25947b074119ee6a4cfc30917375ef7c10c06319 Log: JENKINS-34908, mask url encoded passwords if necessary 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-34908) mask-password does not mask url encoded passwords
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34908 Re: mask-password does not mask url encoded passwords Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream.java src/test/java/com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsURLEncodingTest.java http://jenkins-ci.org/commit/mask-passwords-plugin/38bea3abecd78b31e20a281bcaa1564324f1ac8f Log: Merge branch 'merge/JENKINS-34908' Conflicts: src/main/java/com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream.java Compare: https://github.com/jenkinsci/mask-passwords-plugin/compare/f8fb42b62323...38bea3abecd7 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-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-39407 Use system default Maven, Maven Settings if not specified Change By: Cyrille Le Clerc Attachment: maven-global-settings.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-40107) Blue Ocean support for ANSI Color output
Title: Message Title James Dumay commented on JENKINS-40107 Re: Blue Ocean support for ANSI Color output thanks for filing E V. I'd be curious if Daniel Doubrovkine (maintainer of the ANSI color plugin) would like to help us build console annotation support for Blue Ocean. 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-40109) returnStdout returns java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title
Sasha Shkolnik created an issue
Jenkins / JENKINS-40109
returnStdout returns java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-durable-task-step-plugin
Created:
2016/Nov/29 10:52 PM
Environment:
Ubuntu
Priority:
Major
Reporter:
Sasha Shkolnik
I am trying to run the latest new feature to get output from sh command. Here is my code: _ emails = sh ( script: "git --no-pager show -s --format='%ae' $ {commit_hash} " returnStdout: true ) echo "emails: $ {emails} "_ I am getting back an error: java.io.NotSerializableException: org.codehaus.groovy.control.ErrorCollector at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at
[JIRA] (JENKINS-40107) Blue Ocean support for ANSI Color output
Title: Message Title James Dumay commented on JENKINS-40107 Re: Blue Ocean support for ANSI Color output I suspect this will need some changes to Blue Ocean and Pipeline for this to work. io.jenkins.blueocean.service.embedded.rest.LogResource is a good start. 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-39134) com.google.inject.CreationException after resuming build in script {} or withMaven {}
Title: Message Title
Jesse Glick commented on JENKINS-39134
Re: com.google.inject.CreationException after resuming build in script {} or withMaven {}
Could not find a way to make AbstractStepExecutionImpl work in such cases. Considering deprecating 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-39134) com.google.inject.CreationException after resuming build in script {} or withMaven {}
Title: Message Title
Jesse Glick updated JENKINS-39134
Jenkins / JENKINS-39134
com.google.inject.CreationException after resuming build in script {} or withMaven {}
Change By:
Jesse Glick
Status:
In Progress Review
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40108) Plugin Compatibility
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40108 Plugin Compatibility Issue Type: Epic Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/29 10:37 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
[JIRA] (JENKINS-40083) Blueocean fails to show pipelines due to analysis-core failure
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40083 Blueocean fails to show pipelines due to analysis-core failure Change By: James Dumay Component/s: analysis-core-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-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title James Dumay commented on JENKINS-38491 Re: Add new "waitingForInput" status to API for runs, dag and steps Vivek Pandey Paused is fine by me. 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-34922) NullPointerException Creating and Resolving Issues
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34922 Re: NullPointerException Creating and Resolving Issues Code changed in jenkins User: Alexander Leibzon Path: src/main/java/org/jenkinsci/plugins/pagerduty/PagerDutyTrigger.java http://jenkins-ci.org/commit/pagerduty-plugin/62077523494fcc523e101ad2c6950d46d559abbb Log: Merge pull request #2 from brenarth/JENKINS-34922 Check for null result when resolving incidents Compare: https://github.com/jenkinsci/pagerduty-plugin/compare/c795510e1658...62077523494f 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-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title Vivek Pandey commented on JENKINS-38491 Re: Add new "waitingForInput" status to API for runs, dag and steps James Dumay Michael Neale We should really be calling it PAUSED state. waiting for input really means run and node is in paused state, however specific step inside it could be in waitingForInput state though. This will let us use PAUSED state used for different type of pulse causes. What do you think? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40056) Error when installing plugins via the cli
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40056 Error when installing plugins via the cli Change By: James Dumay Priority: Minor Critical 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-40056) Error when installing plugins via the cli
Title: Message Title James Dumay edited a comment on JENKINS-40056 Re: Error when installing plugins via the cli I deleted my jenkins home, setup Jenkins with no plugins, enabled JNLP random setting then ran the cli and I did not see this issue. It seems to be happening with Jenkins JNLP setting disabled (as it is when you setup a fresh Jenkins) . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40056) Error when installing plugins via the cli
Title: Message Title James Dumay commented on JENKINS-40056 Re: Error when installing plugins via the cli I deleted my jenkins home, setup Jenkins with no plugins, enabled JNLP random setting then ran the cli and I did not see this issue. It seems to be happening with Jenkins JNLP setting disabled. 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-40056) Error when installing plugins via the cli
Title: Message Title Daniel Beck commented on JENKINS-40056 Re: Error when installing plugins via the cli According to James Dumay on IRC, enabling JNLP port makes this work, so this is an issue with the HTTP fallback mode for the CLI. Next step – someone to bisect 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 https://github.com/jenkinsci/jenkins/pull/2653 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-40056) Error when installing plugins via the cli
Title: Message Title Daniel Beck commented on JENKINS-40056 Re: Error when installing plugins via the cli Is JNLP port and the CLI protocols enabled in security preferences, or does this use the HTTP fallback? Would be interesting to know when this broke. 2.24 could be a culprit, we fixed a few CLI related issues then. 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-40056) Blue Ocean plugin error when installing via CLI
Title: Message Title
James Dumay edited a comment on JENKINS-40056
Re: Blue Ocean plugin error when installing via CLI
I've verified that all plugin installation via the CLI fails on Jenkins 2.34 for all plugins .Log from CLI {{/usr/local/Cellar/jenkins/2.34/bin/jenkins-cli -s http://localhost:8080/ install-plugin junit -restart --username admin --password admin}}{noformat}[WARN] Failed to authenticate with your SSH keys. Proceeding as anonymousInstalling junit from update centerNov 30, 2016 8:46:58 AM hudson.remoting.SynchronousCommandTransport$ReaderThread runSEVERE: I/O error in channel Chunked connection to http://localhost:8080/clijava.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:888) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:92) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:821) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) at com.sun.proxy.$Proxy3.main(Unknown Source) at hudson.cli.CLI.execute(CLI.java:332) at hudson.cli.CLI._main(CLI.java:503) at hudson.cli.CLI.main(CLI.java:384)Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59){noformat}The server log:{noformat}Nov 30, 2016 8:46:52 AM hudson.model.UpdateSite$Plugin deployINFO: Adding dependent install of structs for plugin junitNov 30, 2016 8:46:52 AM hudson.model.UpdateSite$Plugin deployINFO: Adding dependent install of bouncycastle-api for plugin structsNov 30, 2016 8:46:53 AM hudson.model.UpdateSite$Plugin deployINFO: Dependent install of bouncycastle-api for plugin junit already added, skippingNov 30, 2016 8:46:53 AM hudson.model.UpdateCenter$DownloadJob runINFO: Starting the installation of bouncycastle API Plugin on behalf of adminNov 30, 2016 8:46:54 AM hudson.model.UpdateCenter$UpdateCenterConfiguration
[JIRA] (JENKINS-40056) Blue Ocean plugin error when installing via CLI
Title: Message Title James Dumay commented on JENKINS-40056 Re: Blue Ocean plugin error when installing via CLI I've verified that all plugin installation via the CLI fails on Jenkins 2.34. Log from CLI /usr/local/Cellar/jenkins/2.34/bin/jenkins-cli -s http://localhost:8080/ install-plugin junit -restart --username admin --password admin [WARN] Failed to authenticate with your SSH keys. Proceeding as anonymous Installing junit from update center Nov 30, 2016 8:46:58 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://localhost:8080/cli java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:888) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:92) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:821) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) at com.sun.proxy.$Proxy3.main(Unknown Source) at hudson.cli.CLI.execute(CLI.java:332) at hudson.cli.CLI._main(CLI.java:503) at hudson.cli.CLI.main(CLI.java:384) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) The server log: Nov 30, 2016 8:46:52 AM hudson.model.UpdateSite$Plugin deploy INFO: Adding dependent install of structs for plugin junit Nov 30, 2016 8:46:52 AM
[JIRA] (JENKINS-40107) Blue Ocean support for ANSI Color output
Title: Message Title E V updated an issue Jenkins / JENKINS-40107 Blue Ocean support for ANSI Color output Change By: E V Summary: Blue Ocean support for ANSI Color Support output Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40056) Error when installing plugins via the cli
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40056 Error when installing plugins via the cli Change By: James Dumay Summary: Blue Ocean plugin error Error when installing plugins via CLI the cli 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-40107) ANSI Color Support
Title: Message Title E V created an issue Jenkins / JENKINS-40107 ANSI Color Support Issue Type: Improvement Assignee: Unassigned Attachments: without_color.png, with_color.png Components: ansicolor-plugin, blueocean-plugin Created: 2016/Nov/29 9:49 PM Environment: Jenkins 2.19 Blue Ocean Beta 1.0.0-b12 AnsiColor 0.4.3 Labels: pipeline user-experience ansicolor blueocean Priority: Minor Reporter: E V It appears that the ANSI Color plugin currently does not work with the Blue Ocean UX. We're expecting to see shell output which is colored but it's not. I am not sure if it would be up to the Blue Ocean plugin team or the ANSI color plugin team to resolve this so I mapped both components to it. Please feel free to edit this ticket as needed. By the way, we're using the pipeline syntax for generating the output. I've read the guidelines for ticket creation and searched for similar issues and was unable to find any. Having said this, please let me know if there is something wrong with this ticket or if this is a known issue. Also, I was not sure which sprint to add this to so I left it blank. Thanks!
[JIRA] (JENKINS-40106) Adding PMD plugin gives javax.servlet.ServletException: java.lang.NoSuchFieldError: VALIDATE_ANT_FILE_MASK_BOUND
Title: Message Title
S Sharma updated an issue
Jenkins / JENKINS-40106
Adding PMD plugin gives javax.servlet.ServletException: java.lang.NoSuchFieldError: VALIDATE_ANT_FILE_MASK_BOUND
Change By:
S Sharma
Hi,I am trying to publish PMD analysis report published by my ANT script in freestyle project(jenkins job). The ANT Script runs successfully and i can see the warnings generated in the pmd.xml file in my jenkins workspace folder .The pmd report is saved as pmd.xml in the root of workspace. Also, when I configure the settings of the job, i see an ERROR right away after i add publish PMD report in Post build actions. The stack trace has been attached along with the console output for pmd. What I tried: Downgrading to Static Analysis Utilities 1.60. with no success in resolving the issue. Update: I tried build again, without any changes but it gives me different stack trace on console from first output (attached):{color:red}(second build console output ){color}Total time: 2 seconds[PMD] Collecting PMD analysis files...ERROR: Publisher hudson.plugins.pmd.PmdPublisher aborted due to exceptionjava.lang.NoClassDefFoundError: jenkins/MasterToSlaveFileCallable at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:756) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:86) at hudson.ClassicPluginStrategy$DependencyClassLoader.findClass(ClassicPluginStrategy.java:634) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at jenkins.util.AntClassLoader.findBaseClass(AntClassLoader.java:1397) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1074) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at hudson.plugins.pmd.PmdPublisher.perform(PmdPublisher.java:80) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:280) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at
[JIRA] (JENKINS-40056) Blue Ocean plugin error when installing via CLI
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40056 Blue Ocean plugin error when installing via CLI Change By: James Dumay Component/s: cli Component/s: core Component/s: blueocean-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-39291) Form elements
Title: Message Title James Dumay updated JENKINS-39291 Jenkins / JENKINS-39291 Form elements Change By: James Dumay 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-40106) Adding PMD plugin gives javax.servlet.ServletException: java.lang.NoSuchFieldError: VALIDATE_ANT_FILE_MASK_BOUND
Title: Message Title S Sharma updated an issue Jenkins / JENKINS-40106 Adding PMD plugin gives javax.servlet.ServletException: java.lang.NoSuchFieldError: VALIDATE_ANT_FILE_MASK_BOUND Change By: S Sharma Environment: Windows 7 E, 64 bit | Jenkins v1.581 | analysis-core-1.79 |analysis-collector-1.41| pmd- 3.45 | apache-ant-1.9.4| jdk-1.7.0-60 | Static analysis utilities-1.79 | Web Browser- Chrome | pmd 5.5.2 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-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title Vivek Pandey started work on JENKINS-38491 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40093) Blue Ocean: Failed to write lastFinishedBuild
Title: Message Title James Dumay resolved as Duplicate This is a duplicate of JENKINS-40083 that effects the analysis plugins and there is a fix waiting to be reviewed by its maintainers. Jenkins / JENKINS-40093 Blue Ocean: Failed to write lastFinishedBuild Change By: James Dumay 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
