[JIRA] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz commented on JENKINS-51267 Re: Warnings polluted with unrelated Qt MSBuild warnings Thanks for looking into that issue. It seems you have to be logged in Phabricator to read the post I've linked. I'm attaching a screenshot of that post. I don't understand the meaning of: "Why are you feeding the parsers with the whole log?" Do you ask about: 1) Why am I passing following line? CMAKE_CXX_FLAGS=/Wall or 2) Why our Jenkins administrator feeds parser with the whole log? I have been told, it's nothing that we can fix on our side. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz updated an issue Jenkins / JENKINS-51267 Warnings polluted with unrelated Qt MSBuild warnings Change By: Łukasz Wojniłowicz Attachment: jenkins.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz updated an issue Jenkins / JENKINS-51267 Warnings polluted with unrelated Qt MSBuild warnings Change By: Łukasz Wojniłowicz Attachment: jenkins.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz updated an issue Jenkins / JENKINS-51267 Warnings polluted with unrelated Qt MSBuild warnings Change By: Łukasz Wojniłowicz Attachment: jenkins.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51134) GitSCMTelescope should support DiscoverOtherRefsTrait
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-51134 GitSCMTelescope should support DiscoverOtherRefsTrait Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51217) Option to squash commits on merge
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-51217 Option to squash commits on merge Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51061) No commits are discovered by Jenkins after force push
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-51061 No commits are discovered by Jenkins after force push Change By: Mark Waite Summary: No commits are discovered by Jenkins after force push Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51061) No commits are discovered by Jenkins after git force push
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-51061 No commits are discovered by Jenkins after git force push Change By: Mark Waite Summary: No commits are discovered by Jenkins after git force push Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51061) No commits are discovered by Jenkins
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-51061 No commits are discovered by Jenkins Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-50401 Checkout resolution misbehaves with local branch and forward slashes Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51434) Spurious builds using SCM polling and path whitelisting with git plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-51434 Spurious builds using SCM polling and path whitelisting with git plugin Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" xercesImpl-2.11.0 seem to be clashing with the XML parser shipped with the JVM. I don't catch why the analysis-core plugin is pulling an XML Parser, there have been one in the JVM for years. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" xercesImpl-2.11.0 seem to be clashing with the XML parser shipped with the JVM. I don't catch why the analysis-core plugin is pulling an XML Parser, there have been one in the JVM for years. I'm investigating further. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51434) Spurious builds using SCM polling and path whitelisting with git plugin
Title: Message Title Elias Levy created an issue Jenkins / JENKINS-51434 Spurious builds using SCM polling and path whitelisting with git plugin Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-05-19 00:50 Priority: Major Reporter: Elias Levy Builds using SCM polling of a Git repo using Additional Behaviours / Included Regions results in spurious builds. The build Changes shows that none of the changes apply to the paths configured in the Included Regions, but reviewing the Polling Log and then executing the git log command the Git plugin uses to determine changes seems to show the cause. The plugin uses git log --full-history --no-abbrev --format=raw -M -m --raw to determine what changed. This not only includes merge commits, but in addition the -m flag causes a full diff for the parents to be shown, causing previously processed commits to show up, some which may match the whitelist and result in a spurious build. Add Comment
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title David van Laatum commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients you need to add a to parameter, recipientProviders is a list of classes that generate recipients emailext body: '', subject: '', to: 'a...@example.com' Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51096) Support external H2 database
Title: Message Title Cyrille Le Clerc updated JENKINS-51096 Jenkins / JENKINS-51096 Support external H2 database Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51096) Support external H2 database
Title: Message Title Cyrille Le Clerc started work on JENKINS-51096 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick updated JENKINS-51390 Jenkins / JENKINS-51390 java.io.NotSerializableException: org.jclouds.http.HttpCommand Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50520) Remove jClouds shading
Title: Message Title Jesse Glick commented on JENKINS-50520 Re: Remove jClouds shading Wanted to test how changes to jclouds affect the plugin, but found it impossible to get a usable version of Guava in the test classpath. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50520) Remove jClouds shading
Title: Message Title Jesse Glick commented on JENKINS-50520 Re: Remove jClouds shading At least in tests, it does not work to just use Guava 18, since for example NullOutputStream was apparently deleted sometime after 11, and there is code in Jenkins which uses it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50520) Remove jClouds shading
Title: Message Title Jesse Glick commented on JENKINS-50520 Re: Remove jClouds shading We are not actually depending on the wrapper plugin currently—we are depending on the shaded JAR, meaning we are bundling our own copy of jclouds. It is a mess. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi resolved as Fixed releases as 1.2.4, should be available shortly Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi updated JENKINS-50293 Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Status: Resolved In Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi updated JENKINS-50293 Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Status: In Review Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi assigned an issue to Jae Gangemi Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Assignee: Jae Gangemi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50963) UpdatePolicy reset to default on edit
Title: Message Title Jae Gangemi closed an issue as Fixed Jenkins / JENKINS-50963 UpdatePolicy reset to default on edit Change By: Jae Gangemi Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50963) UpdatePolicy reset to default on edit
Title: Message Title Jae Gangemi resolved as Fixed releases as 1.2.4, should be available shortly Jenkins / JENKINS-50963 UpdatePolicy reset to default on edit Change By: Jae Gangemi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick commented on JENKINS-51390 Re: java.io.NotSerializableException: org.jclouds.http.HttpCommand Note that even if you fix program.dat serialization to not blow up, ErrorAction serialization will still issue a JEP-200 warning about the inappropriate fields. There is no further impact because JENKINS-49025 handles that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51433) Exactly same project one always pass but another one always failed with BlueOcean
Title: Message Title
Baivoom Chen created an issue
Jenkins / JENKINS-51433
Exactly same project one always pass but another one always failed with BlueOcean
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
1.txt, 2.txt
Components:
blueocean-plugin
Created:
2018-05-18 21:59
Environment:
jenkinsci/blueocean docker image host: windows 10 blueocean-plugin: 1.5
Labels:
Shellscript npm
Priority:
Major
Reporter:
Baivoom Chen
Frist, I created a new project, TestA, using BlueOcean Plugin and its editor to create a task: ``` pipeline { agent { docker { image 'node:alpine' args '-p 3000:3000' } } stages { stage('build') { parallel { stage('build') { steps { sh 'npm install' } } stage('test') { steps { sh 'npm test' } } stage('deliver') { steps { sh 'npm start' } } } } } } ``` then, the construction always failed with an error `+ sh 'npm test' sh: 0: Can't open npm`. I tried many times but could not pass any stage of the construction. I googled but no clue, so I tried to create another project NoBlueOcean, with jenkins only, without BlueOcean, with the exactly same source code and config. This time, the construction past in the new project and to my surprise, the previous TestA project past two stages `build` and `test` but failed at the stage `deliver`, the construction logs: ``` + npm start > testa@1.0.0 start
[JIRA] (JENKINS-50963) UpdatePolicy reset to default on edit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50963 Re: UpdatePolicy reset to default on edit Code changed in jenkins User: tJouve Path: src/main/java/org/jvnet/hudson/plugins/repositoryconnector/ArtifactResolver.java http://jenkins-ci.org/commit/repository-connector-plugin/abe4c4fa280ca27c6e8cb34d3e161e234774a09f Log: JENKINS-50963 - UpdatePolicies and ChecksumPolicy rest to default on edit. On doFill action for those field the default value is no longer forced. (#34) *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Ulli Hafner commented on JENKINS-51267 Re: Warnings polluted with unrelated Qt MSBuild warnings I haven't checked in detail but sometimes it is almost impossible to write a parser in a way that it does not report issues from other tools. Why are you feeding the parsers with the whole log? Cat the corresponding log sections to files and use these as input for the different parsers. BTW: the read more link is not visible. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Mark Waite resolved as Fixed I created a test job that confirms the exception message is not empty with latest plugin versions as of 18 May 2018. Bug appears to be fixed. Jenkins / JENKINS-34042 Git exception message is null when using workflow checkout step Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller closed an issue as Fixed The root cause of this failure is due to launching the SSH server in the Jenkins test harness, which generates an SSH key. This key generation requires entropy, and Linux blocks when there isn't enough entropy available. In Virtual Machines, especially when running high test volumes, it is very easy to consume all of the available entropy, causing the tests to block when attempting to start the JenkinsRule. If entropy took too long to generate, it resulted in random test failures. This was fixed/worked around by upgrading to a newer version of Jenkins which has the SSH server disabled by default, thus avoiding the root cause of key generation. Jenkins / JENKINS-50642 intermittent JenkinsRule test timeout failure Change By: Jacob Keller Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Jacob Keller commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure Yea, upgrading to depending on the 2.60.3 Jenkins server avoids the issue due to no longer starting up SSH. Will close. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51390 java.io.NotSerializableException: org.jclouds.http.HttpCommand Change By: Jesse Glick Component/s: workflow-support-plugin Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Amir Barkal edited a comment on JENKINS-34042 Re: Git exception message is null when using workflow checkout step (+)1 on this issue.Trying to create a mechanism to alert users when their branch cannot be merged into master, or any other problem with the checkout - but the try-catch block of checkout scm isn't working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Amir Barkal commented on JENKINS-34042 Re: Git exception message is null when using workflow checkout step (+)1 on this issue. Trying to create a mechanism to alert users when their branch cannot be merged into master, or any other problem with the checkout - but the try-catch block of checkout scm isn't working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Mark Waite commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure Jacob Keller it appears that the JDK 8 changes which have been included in the git plugin master branch 14 May 2018 have resolved this issue, at least in the cases that I've checked. Can this bug be closed? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51432) Add multibranch support for task streams
Title: Message Title Dylan H created an issue Jenkins / JENKINS-51432 Add multibranch support for task streams Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-05-18 20:36 Labels: p4-plugin multibranch Priority: Minor Reporter: Dylan H Currently when using the 'Helix Streams' option in a multibranch build the p4-plugin will run the following command to check for the existence of a Jenkinsfile: p4 files -e However, when this command is run against a task stream where the Jenkinsfile has not been changed the command states 'no such file(s)'. The p4-plugin will then skip creating a build for the task branch. The expected behavior is that if the Jenkinsfile has not been changed in the task stream, but the Jenkinsfile has been mapped from the parent stream that the task stream would not be skipped.
[JIRA] (JENKINS-51431) Unable to connect to REST service
Title: Message Title Juan Gomez updated an issue Jenkins / JENKINS-51431 Unable to connect to REST service Change By: Juan Gomez Attachment: JenkinsError.PNG Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51431) Unable to connect to REST service
Title: Message Title Juan Gomez created an issue Jenkins / JENKINS-51431 Unable to connect to REST service Issue Type: Bug Assignee: Unassigned Components: jira-issue-updater-plugin Created: 2018-05-18 20:27 Priority: Minor Reporter: Juan Gomez Hello team, We are trying to integrate JIRA and Jenkins, but, we see the following error: Quote D:\Jenkins\workspace\Jenkins DevOps>exit 0 --- JIRA Update Build Step --- Unable to connect to REST service java.io.FileNotFoundException: https://stagingacc01-test.accenture.com/jira/rest/api/latest/issue/JD-1/search?jqlFinished: SUCCESS Unquote Although, if we just access the URL: https://stagingacc01-test.accenture.com/jira/rest/api/latest/issue/JD-1 we are able to see the code. Is there any configuration we are missing? Best regards Add Comment
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title
Timothy Williams edited a comment on JENKINS-41102
Re: Job "Changes" do not match "Filter for Poll SCM"
I have not tested this yet, but is this issue resolved by the following bolded bold [release note text|https://wiki.jenkins.io/display/JENKINS/AccuRev+Plugin]? Thanks.{quote}{color:red}Version 0.7.16 (05/15/2018) - Micro Focus Contributed{color}* It is now possible to enable / disable the AccuRev plugin from interacting with the AccuRev server. This is useful when the AccuRev stream hierarchy is being reworked and you don’t want Jenkins building while this activity is underway.* Fixed problem with Jenkins reporting "No port number specified for connecting to server" error, when using AccuRev 7.1 or higher.* *Jenkins now correctly works with the "Filter for Poll SCM" option.** Jenkins user can now validate the connection of configured AccuRev server , using "Test Connection" option.{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" I have not tested this yet, but is this issue resolved by the following bolded release note text? Thanks. Version 0.7.16 (05/15/2018) - Micro Focus Contributed It is now possible to enable / disable the AccuRev plugin from interacting with the AccuRev server. This is useful when the AccuRev stream hierarchy is being reworked and you don’t want Jenkins building while this activity is underway. Fixed problem with Jenkins reporting "No port number specified for connecting to server" error, when using AccuRev 7.1 or higher. Jenkins now correctly works with the "Filter for Poll SCM" option. Jenkins user can now validate the connection of configured AccuRev server , using "Test Connection" option. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50293 Re: Repository Connector Plugin does not use Jenkins configured proxy correctly Code changed in jenkins User: Milan Koníř Path: src/main/java/org/jvnet/hudson/plugins/repositoryconnector/aether/Aether.java src/test/java/org/jvnet/hudson/plugins/repositoryconnector/aether/AetherTest.java http://jenkins-ci.org/commit/repository-connector-plugin/8851b74464cb5cc6041576c70f0c28b45a2650dd Log: JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly (#33) *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Martin Spielmann commented on JENKINS-51429 Re: schedule-build-plugin - build with parameters Hi Jared Kauppila, no problems, these are the bugs I like the most Thanks for your quick feedback and also for using the plugin Regards Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Martin Spielmann edited a comment on JENKINS-51429 Re: schedule-build-plugin - build with parameters Hi [~jakauppila],no problems problem , these are the bugs I like the most :)Thanks for your quick feedback and also for using the plugin :)Regards Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Jared Kauppila closed an issue as Not A Defect Jenkins / JENKINS-51429 schedule-build-plugin - build with parameters Change By: Jared Kauppila Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Jared Kauppila commented on JENKINS-51429 Re: schedule-build-plugin - build with parameters Hey Martin Spielmann, Yup, just user error I must have been clicking around on a few jobs and saw that on a non-parameterized job when I thought it was. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51430 Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51430 Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS Change By: Oleg Nenashev Component/s: other Component/s: core Component/s: packaging Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Oleg Nenashev assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-51430 Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51430 Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS Change By: Oleg Nenashev Component/s: packaging Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick commented on JENKINS-51390 Re: java.io.NotSerializableException: org.jclouds.http.HttpCommand Found a way to fake it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51390 Re: java.io.NotSerializableException: org.jclouds.http.HttpCommand Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/io/jenkins/plugins/artifact_manager_s3/S3BlobStore.java src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsArtifactManagerTest.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/db58f723750155ca003e0d9d81ae0339badc8e4d Log: JENKINS-51390 Reproduced error in test by deliberately breaking a session token, unarchiving, and then manipulating the exception. Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/7bed48130b86^...db58f7237501 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Martin Spielmann assigned an issue to Jared Kauppila Hi Jared Kauppila, scheduling parameterized pipelines is already possible. Just click "Schedule build" and select the parameters afterwards: I'm not sure if I understand the problem correctly. Jenkins / JENKINS-51429 schedule-build-plugin - build with parameters Change By: Martin Spielmann Assignee: Martin Spielmann Jared Kauppila Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Martin Spielmann started work on JENKINS-51429 Change By: Martin Spielmann Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Martin Spielmann updated an issue Jenkins / JENKINS-51429 schedule-build-plugin - build with parameters Change By: Martin Spielmann Attachment: schedule_build_params 2018-05-18 20-41.gif Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51409) SauceConnect PID Not Being Removed
Title: Message Title Sam Schiavo updated an issue Jenkins / JENKINS-51409 SauceConnect PID Not Being Removed Change By: Sam Schiavo Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51409) SauceConnect PID Not Being Removed
Title: Message Title Sam Schiavo resolved as Not A Defect This issue has been resolved. The jobs that were failing had the "Enable SauceConnect" button checked, so it was trying to establish a tunnel when one was already in place. When I unchecked this box, the jobs completed with no issues. Jenkins / JENKINS-51409 SauceConnect PID Not Being Removed Change By: Sam Schiavo Status: Open Resolved Assignee: Yeh Fang Sam Schiavo Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51409) SauceConnect PID Not Being Removed
Title: Message Title Sam Schiavo commented on JENKINS-51409 Re: SauceConnect PID Not Being Removed This issue has been resolved. I found that all the jobs had the "Enable SauceConnect" box checked, which would try to open a tunnel when one was already opened. When I uncheck this box, the jobs run with no issues through the tunnel that is already set up and configured. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Devin Nusbaum commented on JENKINS-51430 Re: Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS On IRC we discussed that the /usr/lib/jenkins/jenkins-run file appears to be coming from voxpupuli/puppet-jenkins, which is not part of the jenkinsci organization. You'll want to open an issue or file a PR on that repo directly. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Devin Nusbaum edited a comment on JENKINS-51430 Re: Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS On IRC we discussed that the /usr/lib/jenkins/jenkins-run file appears to be coming from [voxpupuli/puppet-jenkins|https://github.com/voxpupuli/puppet-jenkins/blob/master/templates/jenkins-run.erb], which is not part of the jenkinsci organization. You'll want to open an issue or file a PR on that repo directly.(EDIT: Did not see previous comment when this was made) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Samuel Beaulieu commented on JENKINS-51430 Re: Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS This is a puppet-jenkins issue. I'll open the PR there. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-51390 java.io.NotSerializableException: org.jclouds.http.HttpCommand Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick started work on JENKINS-51390 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44142) Step jobDsl can be used at most once in pipeline with DELETE
Title: Message Title Christian V commented on JENKINS-44142 Re: Step jobDsl can be used at most once in pipeline with DELETE Hmm, Generated*BuildActions also contain the lookup strategy. One would have to have up to two actions per type, one per possible strategy. Then, JENKINS-29784 should also be solved, hopefully. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44142) Step jobDsl can be used at most once in pipeline with DELETE
Title: Message Title Christian V edited a comment on JENKINS-44142 Re: Step jobDsl can be used at most once in pipeline with DELETE Hmm, Generated*BuildActions also contain contains the lookup strategy. One would have to have up to two actions per type, one per possible strategy. Then, JENKINS-29784 should also be solved, hopefully. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title R. Tyler Croy commented on JENKINS-49866 Re: Automatically configure Docker Cloud if the docker.sock is available Baptiste Mathus, that doesn't surprise me We have a lot of problems we should address in the backlog about wiring some configuration up like this automatically depending on environment, so a broader solution is very likely required. Try to keep in mind where we are in the product development trajectory though Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/315ad4e689897dedb20c900b8f32f1ce607fb32c Log: Merge pull request #313 from presPetkov/JENKINS-48258-busy-ssh-text-file Jenkins 48258 busy ssh text file fix Compare: https://github.com/jenkinsci/git-client-plugin/compare/98eea34dc4e2...315ad4e68989 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51426) support core makes systems with performance problems worse
Title: Message Title Oleg Nenashev commented on JENKINS-51426 Re: support core makes systems with performance problems worse > Add a configuration option to turn off the automatic building of support bundles. This thing would be good, but I've thought it's already there. CC Emilio Escobar > Have support core be smart enough to not try building bundles when the system is under pressure (and put up a banner on $JENKINS_URL/manage to showing bundles were skipped) If we had logic to evaluate pressure reliably, the first thing would be to have a manager which reduces that. E.g. throttling tasks or whatever Regarding the issue itself In this case it impacts the performance of course... by design since it needs to collect logs (IMHO). The thing you could do is to limit log rotation by size, for example. But it will also make the plugin useless. So a real solution would be to either fix JENKINS-49745 or to apply java.util.logging patch to disable this logger for now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Code changed in jenkins User: presPetkov Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/1199beea0743e60e09c987b1306cc0a8fdfb6879 Log: Jenkins 48258 ssh text file busy (#2) JENKINS-48258 Use a copy of ssh file Corrected exception handling as per bug report Fixed error Fixed error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Samuel Beaulieu created an issue Jenkins / JENKINS-51430 Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-18 17:14 Environment: Jenkins 2.73.3 CentOs 7 Openjdk version 1.8 Labels: systemd service Priority: Major Reporter: Samuel Beaulieu How to reproduce: Run in a systemd OS like CentOS 7 with /etc/sysconfig/jenkins JENKINS_JAVA_OPTIONS=-Dhudson.model.DirectoryBrowserSupport.CSP="default-src 'self';" As per https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy Error message in journalctl Error: Could not find or load main class 'self';" Investigation This is because the last line of the systemd script /usr/lib/jenkins/jenkins-run is
[JIRA] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Jared Kauppila created an issue Jenkins / JENKINS-51429 schedule-build-plugin - build with parameters Issue Type: Improvement Assignee: Martin Spielmann Components: schedule-build-plugin Created: 2018-05-18 17:06 Environment: schedule-build-plugin 0.5.1 Priority: Major Reporter: Jared Kauppila We have been pushing a lot of our automation into Jenkins Pipeline but that means that our builds are parameterized. Being able to schedule a build with parameters would be incredibly useful. Add Comment
[JIRA] (JENKINS-51428) Scripts not permitted error when using createReviewRequests()
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-51428
Scripts not permitted error when using createReviewRequests()
Change By:
Christian Höltje
When using {{createReviewRequests}} I get:{noformat}Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.github.PullRequestGroovyObject createReviewRequests java.lang.String java.lang.String).{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51428) Scripts not permitted error when using createReviewRequests()
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-51428 Scripts not permitted error when using createReviewRequests() Issue Type: Bug Assignee: Aaron Whiteside Components: pipeline-github-plugin Created: 2018-05-18 17:00 Environment: Jenkins 2.107.3 pipeline-github-2.0 pipeline-github-lib-1.0 Priority: Minor Reporter: Christian Höltje When using createReviewRequests I get: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.github.PullRequestGroovyObject createReviewRequests java.lang.String java.lang.String). Add Comment
[JIRA] (JENKINS-51390) java.io.NotSerializableException: org.jclouds.http.HttpCommand
Title: Message Title Jesse Glick commented on JENKINS-51390 Re: java.io.NotSerializableException: org.jclouds.http.HttpCommand Do you know if there is a simple way to reproduce this error? I can try to invent one if not. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51374) Create a plugin skeleton
Title: Message Title Abhishek Gautam started work on JENKINS-51374 Change By: Abhishek Gautam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51427) Publish over Dropbox sending Access Token as Access Code
Title: Message Title
Kerim Djiho created an issue
Jenkins / JENKINS-51427
Publish over Dropbox sending Access Token as Access Code
Issue Type:
Bug
Assignee:
René de Groot
Components:
publish-over-dropbox-plugin
Created:
2018-05-18 16:40
Environment:
Publish Over Dropbox 1.2.2
Priority:
Blocker
Reporter:
Kerim Djiho
Hi! I'm trying to use the plugin and it worked fine, until today when I wanted to add new credentials. It returns HTTP 400 {"error_description": "code doesn't exist or has expired", "error": "invalid_grant"}, and after some investigation I figured out that the cause of this is that it is sending the token as an Access Code used to retrieve the Access Token, instead of sending it as Access Token. Also, on another Jenkins instance, when I try to add credentials it returns: java.net.ConnectException: Connection refused (Connection refused), and I still haven't figured out what is causing this. Thank you in advance.
Add Comment
[JIRA] (JENKINS-35342) Allow to download a bundle
Title: Message Title Arnaud Héritier commented on JENKINS-35342 Re: Allow to download a bundle Only JENKINS-35341 and JENKINS-35343 were implemented in https://github.com/jenkinsci/support-core-plugin/pull/105 by Jean-Pascal THIERY We cannot download bundles already generated on the disk AFAIK Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50379) Jenkins kills long running sh script with no output
Title: Message Title Jacob Keller commented on JENKINS-50379 Re: Jenkins kills long running sh script with no output I see this issue on scripts which do generate some output, but it happens that parts of the script take some time to run: in my case I'm compiling a kernel module and even when the make output is sent to the console, sometimes individual steps take longer than the timeout... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51419) Jenkins polling doesn't detect commits in Github
Title: Message Title
Mark Waite edited a comment on JENKINS-51419
Re: Jenkins polling doesn't detect commits in Github
I don't understand the meaning of The {{poll: true}} in the {{git}} Pipeline step seems to be described in the [workflow-scm-step README|https://github . Since com/jenkinsci/workflow-scm-step-plugin/blob/master/README.md#polling]. I assume you did not list must be using a Pipeline job (rather than a multi-branch Pipeline job) and are defining the polling frequency , I don't understand how in the job definition rather than defining it in inside the Pipeline would interpret {{poll:true}} itself .Others have observed that the {{git}} Pipeline step is a shorthand form of the {{checkout}} step. Rather than use the shorthand {{git}} form, please use you might try the {{checkout}} step.Examples which use polling with multi-branch Pipeline scripts are available in the following samples that I have gathered:* [JENKINS-43468 check job|https://github.com/MarkEWaite/jenkins-bugs/blob/e4a43e2e54b3915a8eafa0f11c418a928eb33bb4/Jenkinsfile#L9]* [JENKINS-43687 check job|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-43687/Jenkinsfile#L8]* [JENKINS-43754 check job|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-43754/Jenkinsfile#L8]* [JENKINS-50556 check job|https://github.com/MarkEWaite/jenkins-bugs/blob/2d1a5fd87c068ffbce7f1d8874c36d75f26eef1d/Jenkinsfile#L9]* [JENKINS-50886 check job|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-50886/Jenkinsfile#L9] Polling Periodic polling inside a Pipeline step job is almost always a bad practice. It creates unnecessary load on the git server by asking questions of the git server. The user will have a much better experience if the git server informs the Jenkins server when a change happens rather than having the Jenkins server regularly ask if there are changes. Refer to the "[polling must die|http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]" blog post from Kohsuke Kawaguchi for more details.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51419) Jenkins polling doesn't detect commits in Github
Title: Message Title Mark Waite commented on JENKINS-51419 Re: Jenkins polling doesn't detect commits in Github I don't understand the meaning of poll: true in the git Pipeline step. Since you did not list a polling frequency, I don't understand how Pipeline would interpret poll:true. Others have observed that the git Pipeline step is a shorthand form of the checkout step. Rather than use the shorthand git form, please use the checkout step. Examples which use polling with Pipeline scripts are available in the following samples that I have gathered: JENKINS-43468 check job JENKINS-43687 check job JENKINS-43754 check job JENKINS-50556 check job JENKINS-50886 check job Polling inside a Pipeline step is almost always a bad practice. It creates unnecessary load on the git server by asking questions of the git server. The user will have a much better experience if the git server informs the Jenkins server when a change happens rather than having the Jenkins server regularly ask if there are changes. Refer to the "polling must die" blog post from Kohsuke Kawaguchi for more details. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-45990) Git plugin support for non standard branches during auto discover
Title: Message Title Florian Bäuerle commented on JENKINS-45990 Re: Git plugin support for non standard branches during auto discover I closed the Issue overzealously. The Multibranch pipeline actually detects the branch, but building them does not succeed. I get this message: ERROR: Could not determine exact tip revision of pull/2212/merge; falling back to nondeterministic checkout In the end, the correct commit is checked out but as soon as the actual pipeline script is executed on a node, the job fails with java.nio.file.NoSuchFileException. The Dockerfile cannot be found, which makes sense, because there is absolutetly nothing created on the slave (not even a workdir is being created). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45990) Git plugin support for non standard branches during auto discover
Title: Message Title Florian Bäuerle reopened an issue Jenkins / JENKINS-45990 Git plugin support for non standard branches during auto discover Change By: Florian Bäuerle Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51419) Jenkins polling doesn't detect commits in Github
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-51419
Jenkins polling doesn't detect commits in Github
Change By:
Mark Waite
I am currently using the "Poll SCM" option in Jenkins with the poll frequency set to 1 minute for now. My goal is to trigger the build job when the polling detects a commit in Github. However, despite committing to "Feature" branch multiple times, the polling doesn't detect the commit. It continually displays message similar to this:{noformat}Started on May 18, 2018 4:51:00 PM Using strategy: Default [poll] Last Built Revision: Revision ecf20b8hhh2f3d63b5809mle268024500364f2fb (refs/remotes/origin/feature/template-api)> /usr/bin/git --version # timeout=10 using GIT_ASKPASS to set credentialsSetting http proxy: surf.proxy.company:80> /usr/bin/git ls-remote -h https://github.developer.company.com/my- project.git # timeout=10Found 3 remote heads on https://github.developer.company.com/my-project.gitDone.Took 3.7 secNo changes{noformat}My pipeline script is as below:{noformat}node {stage('Preparation') {git ( poll: true, branch: 'feature/template-api', credentialsId: '8u56qwcf-e74e-44z3-9437-c81b19cd3a29', url: 'https://github.developer.company.com/my-project.git' )}}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-46487) Git Plugin only scans refs/heads on multibranch scan
Title: Message Title Florian Bäuerle commented on JENKINS-46487 Re: Git Plugin only scans refs/heads on multibranch scan Stephen Catt Thanks. Correct - looks like I was a bit too overzealously closing the other Issue. I get this message: ERROR: Could not determine exact tip revision of pull/2212/merge; falling back to nondeterministic checkout In the end, the correct commit is checked out but as soon as the actual pipeline script is executed on a node, the job fails with java.nio.file.NoSuchFileException. The Dockerfile cannot be found, which makes sense, because there is absolutetly nothing created on the slave (not even a workdir is being created). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51419) Jenkins polling doesn't detect commits in Github
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-51419
Jenkins polling doesn't detect commits in Github
Change By:
Mark Waite
I am currently using the "Poll SCM" option in Jenkins with the poll frequency set to 1 minute for now. My goal is to trigger the build job when the polling detects a commit in Github. However, despite committing to "Feature" branch multiple times, the polling doesn't detect the commit. It continually displays message similar to this:{ { noformat} Started on May 18, 2018 4:51:00 PM Using strategy: Default [poll] Last Built Revision: Revision ecf20b8hhh2f3d63b5809mle268024500364f2fb (refs/remotes/origin/feature/template-api) > /usr/bin/git --version # timeout=10 using GIT_ASKPASS to set credentials Setting http proxy: surf.proxy.company:80 > /usr/bin/git ls-remote -h https://github.developer.company.com/my- project.git # timeout=10 Found 3 remote heads on https://github.developer.company.com/my-project.git Done. Took 3.7 sec No changes {noformat } } My pipeline script is as below:{ {node \{ noformat } } node { { stage('Preparation') \ { }} {{ git ( poll: true, branch: 'feature/template-api', credentialsId: '8u56qwcf-e74e-44z3-9437-c81b19cd3a29', url: 'https://github.developer.company.com/my-project.git' ) } } {{ } }} { { noformat } }}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51419) Jenkins polling doesn't detect commits in Github
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-51419 Jenkins polling doesn't detect commits in Github Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45896) Malformed GitHub Plugin configuration (no protocol: )
Title: Message Title Michael Yardley commented on JENKINS-45896 Re: Malformed GitHub Plugin configuration (no protocol: ) I am observing this issue as well. My error log looks the same as the one posted above. I was not attempting to make a Github update. My Github configuration was setup long ago and is still working today. I was attempting to set up the E-mail Notification option. I was able to send a test email (Test configuration by sending a test e-mail) so the configuration I added appeared to be correct. When I selected the Save button the exception was displayed. When I re-entered the configuration page I noticed my E-mail Notification settings were not saved. I then tried setting up the Global Slack Notifier Settings and then selected the save button and the exception was displayed again. I received a message in my Slack channel (added an integration to this channel: jenkins) so I believe I configured it correctly. If I go into the Configure System menu and then press the save button the exception will be displayed, even with NO changes being made. I would appreciate any advice on this issue. Thank you for all your help! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44132) Random JNLP Agent disconnect
Title: Message Title Ben Dean commented on JENKINS-44132 Re: Random JNLP Agent disconnect I ran into this with a Windows build agent connecting via jnlp where the connection was going through an AWS ELB that was in front of our Kubernetes cluster where the Jenkins Master is running. (Note that we're using the ELB not so much for load balancing, there is only one master after all, but just as a way to provide access to the private remoting port from outside the kube cluster.) The idle connection timeout on the ELB was set to 60 seconds and we had repo cloning that was taking longer than a minute and not producing any output during that time. Seems to be fixed by changing the ELB idle connection timeout to something higher (300 seconds or more seems okay, maybe if you have a very silent, very long build step you might need more). Also marlene cote, I don't know if you realize this or not, but you put your connection secret in the post, you should maybe change that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44142) Step jobDsl can be used at most once in pipeline with DELETE
Title: Message Title
Christian V commented on JENKINS-44142
Re: Step jobDsl can be used at most once in pipeline with DELETE
I've taken another look at this. When multiple job-dsl scripts are run, job-dsl will attach multiple "actions" to the build. The current code seems to assume that there is only a single one. To find the last generated objects, it's probably a simple change, maybe something like this:
Set findLastGeneratedObjects() {
for (Run run = job.lastBuild; run != null; run = run.previousBuild) {
// We need to fetch all actions because job-dsl could habe been run multiple times in a single build.
// Previously, it would use the first build, whose first buildAction's modifiedObjects was set
// Now, it chooses the first build, where at least one buildAction's modifiedObjects is set
List actions = run.getActions(buildActionClass)
Set result = []
boolean useThisResult = false
for (B action : actions) {
if (action.modifiedObjects != null) {
useThisResult = true
result += action.modifiedObjects
}
}
if (useThisResult) {
return result
}
}
[]
}
Further, job-dsl needs to be made aware of previous invocations during the same build run. Currently, it compares the "new items" against the items items from the first suitable previous run. Here's a simple idea:
GeneratedItems generatedItems = dslScriptLoader.runScripts(scriptRequests);
mergeWithCurrentRun(generatedItems, run); // <-- this would be the only change
Set freshJobs = generatedItems.getJobs();
Set freshViews = generatedItems.getViews();
Set freshConfigFiles = generatedItems.getConfigFiles();
Set freshUserContents = generatedItems.getUserContents();
One could simply pretend that a subsequent invocation also "generated" the items that were generated previously in the same run. The last invocation's log output would then summarize everything that job-dsl did. Finally, one could check whether a build action is already appened to the current run and replace it it instead, instead of unconditionally doing run.addAction:
// Save onto Builder, which belongs to a Project.
run.addAction(new GeneratedJobsBuildAction(freshJobs, getLookupStrategy()));
run.addAction(new GeneratedViewsBuildAction(freshViews, getLookupStrategy()));
run.addAction(new GeneratedConfigFilesBuildAction(freshConfigFiles));
run.addAction(new GeneratedUserContentsBuildAction(freshUserContents));
This might affect JENKINS-29784 Daniel Spilker Thoughts?
[JIRA] (JENKINS-48913) sshagent block serialization error when script with git clone fails
Title: Message Title Jesse Glick commented on JENKINS-48913 Re: sshagent block serialization error when script with git clone fails Note that BasicSSHUserPrivateKey.FileOnMasterPrivateKeySource is not Serializable, nor is UsersPrivateKeySource, only DirectEntryPrivateKeySource, since CredentialsSnapshotTakerImpl converts the former two into the latter. For purposes of XStream serialization, Serializable is irrelevant. For purposes of Remoting, plugin code is expected to call CredentialsProvider.snapshot before transmitting credentials to an agent. But a Credentials object is never expected to be serialized inside a Pipeline program. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48913) sshagent block serialization error when script with git clone fails
Title: Message Title Jesse Glick commented on JENKINS-48913 Re: sshagent block serialization error when script with git clone fails I was unable to reproduce any error like this. Apparently an BasicSSHUserPrivateKey object is somehow getting saved into the Pipeline program state, which should not happen—SSHAgentStepExecution merely loads private keys in a Java local variable, uses them to add identities to an agent, binds an SSH_AUTH_SOCK, and then runs its body. I see no plausible code path by which this type from the ssh-credentials could be “leaking” into an attempted save to program.dat. Is there any known way to reproduce from scratch, including particular versions of Jenkins core, this ssh-agent plugin, and Pipeline-related plugins such as workflow-job and workflow-cps? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48913) sshagent block serialization error when script with git clone fails
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48913 sshagent block serialization error when script with git clone fails Change By: Jesse Glick Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Eliseo Ocampos commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs For everyone who may still facing this problem, please refer to the workaround mentioned here. I can confirm it solves the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Eliseo Ocampos commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries This bug is still present on version 2.116. I found that the workaround mentioned here is the way to go for the moment. Thanks Allan BURDAJEWICZ! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21281) Validation button for private key passphrase field
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-21281 Validation button for private key passphrase field Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46487) Git Plugin only scans refs/heads on multibranch scan
Title: Message Title Stephen Catt commented on JENKINS-46487 Re: Git Plugin only scans refs/heads on multibranch scan Florian Bäuerle, I installed the update over the weekend. Though the "discover other refs" plugin will now successfully scan for the branches, it won't build them. It kept throwing an error that it could not find a revision to build. I was looking through the git plugin repo and it looks like they have not implemented telescoping support yet, which may be the issue. From what I could tell, this i tracked in JENKINS-51134 So, hopefully, the next version will fix it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49646) FileOnMasterPrivateKeySource not serializable
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-49646 FileOnMasterPrivateKeySource not serializable Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46253) Support subPath for volumes in the slave PodTemplates
Title: Message Title Carlos Sanchez commented on JENKINS-46253 Re: Support subPath for volumes in the slave PodTemplates this is possible with the yaml syntax Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
