[JIRA] (JENKINS-49528) Peformance graphs for individual tests are not created when a single test has failed
Title: Message Title Tobias Lingemann commented on JENKINS-49528 Re: Peformance graphs for individual tests are not created when a single test has failed As I suspected. The custom metric graph was created successfully. 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-49038) Jenkins does not start due to a deadlock
Title: Message Title Arnaud TAMAILLON resolved as Fixed Jenkins / JENKINS-49038 Jenkins does not start due to a deadlock Change By: Arnaud TAMAILLON Status: Open Resolved Assignee: Christian Bremer Arnaud TAMAILLON 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-49038) Jenkins does not start due to a deadlock
Title: Message Title Arnaud TAMAILLON commented on JENKINS-49038 Re: Jenkins does not start due to a deadlock Thanks for your help! Fixed in 2.14.1 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-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title dan tran edited a comment on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' i dont I don't think this is fixed. instead every supposed empty 'Deployed artfifact Artfifacts ' is filled with the same set. Also, it also missing my important final package the list only shows .jar files ( a i have . rpm and . ova , etc ) 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-49038) Jenkins does not start due to a deadlock
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49038 Re: Jenkins does not start due to a deadlock Code changed in jenkins User: Arnaud Path: src/main/java/hudson/plugins/claim/http/PreventRefreshFilter.java http://jenkins-ci.org/commit/claim-plugin/16e22544affcff18b8e4b4ae01036ad3482de698 Log: JENKINS-49038 Jenkins does not start due to a deadlock the idea is to get the ClaimConfig retrieval out of guice logic. 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-44398) Add few more steps around Issues
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-44398 Add few more steps around Issues Change By: Naresh Rayapati Need to add new steps: Based on most use cases it looks like these are common steps it would help avoid some boilerplate: * iraAddIssueLabel jiraTagIssueLabel * jiraAddIssueFixVersion jiraTagIssueFixVersion * jiraAddIssueComponent jiraTagIssueComponent * Issuetype (get, post and query whichever applies) 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-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title dan tran commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' i dont think this is fixed. instead every supposed empty 'Deployed artfifact' is filled with the same set. Also, it also missing my important final package ( a .ova ) 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Owen Mehegan assigned an issue to Chen Cohen Jenkins / JENKINS-27371 Parent builds sometimes hang on successful child builds of same type Change By: Owen Mehegan Assignee: Chen Cohen 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-48816) Add an option to choose behaviour
Title: Message Title Rafael Ramos updated JENKINS-48816 Released in version 1.3.0 Jenkins / JENKINS-48816 Add an option to choose behaviour Change By: Rafael Ramos Status: In Review 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-48816) Add an option to choose behaviour
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48816 Re: Add an option to choose behaviour Code changed in jenkins User: Rafael Ramos Path: pom.xml src/main/java/org/quality/gates/jenkins/plugin/JobConfigData.java src/main/java/org/quality/gates/jenkins/plugin/JobConfigurationService.java src/main/java/org/quality/gates/jenkins/plugin/QGBuilder.java src/main/java/org/quality/gates/jenkins/plugin/QGBuilderDescriptor.java src/main/java/org/quality/gates/jenkins/plugin/QGPublisher.java src/main/java/org/quality/gates/jenkins/plugin/QGPublisherDescriptor.java src/main/java/org/quality/gates/jenkins/plugin/enumeration/BuildStatusEnum.java src/main/resources/org/quality/gates/jenkins/plugin/QGBuilder/config.jelly src/main/resources/org/quality/gates/jenkins/plugin/QGBuilder/help-buildStatus.html src/main/resources/org/quality/gates/jenkins/plugin/QGPublisher/config.jelly src/main/resources/org/quality/gates/jenkins/plugin/QGPublisher/help-buildStatus.html src/test/java/org/quality/gates/jenkins/plugin/JobConfigurationServiceTest.java src/test/java/org/quality/gates/jenkins/plugin/QGBuilderTest.java src/test/java/org/quality/gates/jenkins/plugin/QGPublisherTest.java http://jenkins-ci.org/commit/sonar-quality-gates-plugin/9ca1caa6ac5798f56be798c292b2cadaf32048d0 Log: Merge pull request #12 from arkanjoms/master JENKINS-48816 Inserted combo to choose job status when analyse fail. Compare: https://github.com/jenkinsci/sonar-quality-gates-plugin/compare/a3e3eb2016f5...9ca1caa6ac57 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-48816) Add an option to choose behaviour
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48816 Re: Add an option to choose behaviour Code changed in jenkins User: Rafael Ramos Path: pom.xml src/main/java/org/quality/gates/jenkins/plugin/JobConfigData.java src/main/java/org/quality/gates/jenkins/plugin/JobConfigurationService.java src/main/java/org/quality/gates/jenkins/plugin/QGBuilder.java src/main/java/org/quality/gates/jenkins/plugin/QGBuilderDescriptor.java src/main/java/org/quality/gates/jenkins/plugin/QGPublisher.java src/main/java/org/quality/gates/jenkins/plugin/QGPublisherDescriptor.java src/main/java/org/quality/gates/jenkins/plugin/enumeration/BuildStatusEnum.java src/main/resources/org/quality/gates/jenkins/plugin/QGBuilder/config.jelly src/main/resources/org/quality/gates/jenkins/plugin/QGBuilder/help-buildStatus.html src/main/resources/org/quality/gates/jenkins/plugin/QGPublisher/config.jelly src/main/resources/org/quality/gates/jenkins/plugin/QGPublisher/help-buildStatus.html src/test/java/org/quality/gates/jenkins/plugin/JobConfigurationServiceTest.java src/test/java/org/quality/gates/jenkins/plugin/QGBuilderTest.java src/test/java/org/quality/gates/jenkins/plugin/QGPublisherTest.java http://jenkins-ci.org/commit/sonar-quality-gates-plugin/94c560be01748e69bc4e5e431e54403bf7334b95 Log: JENKINS-48816 Inserted combo to choose job status when analyse fail. 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-49545) Make enum values case-insensitive
Title: Message Title Tatiana Didik created an issue Jenkins / JENKINS-49545 Make enum values case-insensitive Issue Type: Improvement Assignee: Tatiana Didik Components: sonar-gerrit-plugin Created: 2018-02-14 02:19 Priority: Minor Reporter: Tatiana Didik 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-48816) Add an option to choose behaviour
Title: Message Title Rafael Ramos updated JENKINS-48816 Jenkins / JENKINS-48816 Add an option to choose behaviour Change By: Rafael Ramos 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-49516) Blue-Ocean multibranch pipeline projects ignore system ssh_config
Title: Message Title Michael Neale commented on JENKINS-49516 Re: Blue-Ocean multibranch pipeline projects ignore system ssh_config David Raison I can't recall a doc/issue, but I think this is partly by design. The credentials are per user, vs shared... however this is confusing. 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-29977) Git Plugin truncates changelog
Title: Message Title Chris Kloehn commented on JENKINS-29977 Re: Git Plugin truncates changelog I will do that, as well as spin up a linux environment to try and match your set up. If all this fails though I don't have a way to run any manual tests, unless you know of any other ways to load my version of the plugin into Jenkins. 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-29977) Git Plugin truncates changelog
Title: Message Title Mark Waite commented on JENKINS-29977 Re: Git Plugin truncates changelog The `mvn clean install` ran to completion for me in that environment. I even removed the ~/.m2 directory completely and ran it again just to be sure. My Windows machines have all been "touched" by my development work, so I'm not sure any of them can be cleaned enough to duplicate your setup. You may need to move the ~/.m2 directory temporarily to another location as an alternate test. 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-49529) retry at stage level in declarative pipeline fails
Title: Message Title Andrew Bayer resolved as Not A Defect That was added in Declarative 1.2.6 Jenkins / JENKINS-49529 retry at stage level in declarative pipeline fails Change By: Andrew Bayer Status: Open Resolved 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
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title pixman20 edited a comment on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits You can try checking what you put in the "Committers to Ignore" field against the committer in git...make sure you're using the right name, for example using the actual username instead of display name in some instances.FWIW, this is the Bitbucket add-on that is firing the events back to Jenkins, and that's what Jenkins updates: [https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview] In short, the Bitbucket Branch Source Plugin in Jenkins updates the webhooks in Bitbucket. When a matching event is figured fired (see your webhook configuration), it notifies Jenkins by posting content to a some URL endpoint (can't remember off-hand what it is ). This is where you can try to add Jenkins loggers to see what it's getting. Fortunately, since it's receiving data that you don't want, it's easier to dig into than not receiving data that you do want :) ...hopefully.My guess is though that it's either a Bitbucket add-on bug or more likely a mismatch between the committers to ignore field and the actual committer id that shows up in the git log 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-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title pixman20 commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits You can try checking what you put in the "Committers to Ignore" field against the committer in git...make sure you're using the right name, for example using the actual username instead of display name in some instances. FWIW, this is the Bitbucket add-on that is firing the events back to Jenkins, and that's what Jenkins updates: https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview In short, the Bitbucket Branch Source Plugin in Jenkins updates the webhooks in Bitbucket. When a matching event is figured (see your webhook configuration), it notifies Jenkins by posting content to a URL (can't remember off-hand). This is where you can try to add Jenkins loggers to see what it's getting. Fortunately, since it's receiving data that you don't want, it's easier to dig into than not receiving data that you do want ...hopefully. My guess is though that it's either a Bitbucket add-on bug or more likely a mismatch between the committers to ignore field and the actual committer id that shows up in the git log 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-49466) job directory empty when using declarative pipeline
Title: Message Title Will Yardley commented on JENKINS-49466 Re: job directory empty when using declarative pipeline I don't think this is a dupe of JENKINS-40862 – the error in the comment only shows up if I try to work around the problem by adding "checkout scm" in the Jenkinsfile. 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-49466) job directory empty when using declarative pipeline
Title: Message Title Will Yardley reopened an issue Jenkins / JENKINS-49466 job directory empty when using declarative pipeline Change By: Will Yardley Resolution: Duplicate Status: Resolved 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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title Tim McNally updated an issue Jenkins / JENKINS-49543 Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl Change By: Tim McNally Environment: Centos 6. 7 9 Oracle JRE 1.8.0_112Tomcat 8Jenkins 2.105 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-29977) Git Plugin truncates changelog
Title: Message Title Chris Kloehn commented on JENKINS-29977 Re: Git Plugin truncates changelog I have a similar output C:\Users\kloehnc\Desktop\temp>git clone https://github.com/kloehnc/git-plugin.git Cloning into 'git-plugin'... remote: Counting objects: 25687, done. remote: Total 25687 (delta 0), reused 0 (delta 0), pack-reused 25687 Receiving objects: 100% (25687/25687), 5.22 MiB | 1.04 MiB/s, done. Resolving deltas: 100% (9883/9883), done. C:\Users\kloehnc\Desktop\temp>cd git-plugin C:\Users\kloehnc\Desktop\temp\git-plugin>mvn --version Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T02:58:13-05:00) Maven home: C:\Program Files\Apache\maven\apache-maven-3.5.2\bin\.. Java version: 9.0.4, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk-9.0.4 Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" C:\Users\kloehnc\Desktop\temp\git-plugin>mvn clean install However its the clean install that fails with no such file exceptions 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.
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title
Mark Waite edited a comment on JENKINS-29977
Re: Git Plugin truncates changelog
Here is the output I see from commands that I used:{noformat}private@ wheezy64b stretch :~/tmp$ git clone https://github.com/jenkinsci/git-pluginCloning into 'git-plugin'...remote: Counting objects: 25687, done.remote: Total 25687 (delta 0), reused 0 (delta 0), pack-reused 25687Receiving objects: 100% (25687/25687), 5.22 MiB | 8.65 MiB/s, done.Resolving deltas: 100% (9883/9883), done.private@ wheezy64b stretch :~/tmp$ cd git-plugin/private@ wheezy64b stretch :~/tmp/git-plugin$ mvn --versionApache Maven 3.3.9Maven home: /usr/share/mavenJava version: 1.8.0_161, vendor: Oracle CorporationJava home: /usr/lib/jvm/java-8-oracle/jreDefault locale: en_US, platform encoding: UTF-8OS name: "linux", version: "4.9.0-5-amd64", arch: "amd64", family: "unix"private@ wheezy64b stretch :~/tmp/git-plugin$ mvn clean install{noformat}At that point, a chunk of the internet is downloaded to my local cache.
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-29977) Git Plugin truncates changelog
Title: Message Title Mark Waite commented on JENKINS-29977 Re: Git Plugin truncates changelog Here is the output I see from commands that I used: private@wheezy64b:~/tmp$ git clone https://github.com/jenkinsci/git-plugin Cloning into 'git-plugin'... remote: Counting objects: 25687, done. remote: Total 25687 (delta 0), reused 0 (delta 0), pack-reused 25687 Receiving objects: 100% (25687/25687), 5.22 MiB | 8.65 MiB/s, done. Resolving deltas: 100% (9883/9883), done. private@wheezy64b:~/tmp$ cd git-plugin/ private@wheezy64b:~/tmp/git-plugin$ mvn --version Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_161, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-oracle/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.9.0-5-amd64", arch: "amd64", family: "unix" private@wheezy64b:~/tmp/git-plugin$ mvn clean install At that point, a chunk of the internet is downloaded to my local cache. 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu edited a comment on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Hi Oleg~After some job config cleanup and retry,now I'm able to see:***Met Qualification Automatically promoted immediately after the build because parameter was matched***Unmet QualificationManual Approval***Refer to the screensot attachment.I'd think the issue right now it's the code is using boolean ' * AND * ' to chain-up the criterias.But it should use boolean ' * OR * ' to meet the description meaning of " * Promote immediately once the build is complete based on build parameters * " . 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu commented on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Hi Oleg~ After some job config cleanup and retry, now I'm able to see: *** Met Qualification Automatically promoted immediately after the build because parameter was matched *** Unmet Qualification Manual Approval *** Refer to the screensot attachment. I'd think the issue right now it's the code is using boolean 'AND' to chain-up the criterias. But it should use boolean 'OR' to meet the description of "Promote immediately once the build is complete based on build parameters" 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: Selection_003.png Attachment: Selection_004.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-29977) Git Plugin truncates changelog
Title: Message Title Chris Kloehn commented on JENKINS-29977 Re: Git Plugin truncates changelog So I was able to get a successful build out of Intelllij, but it did not produce an .hpi file. My command line is still not wanting to build properly and because of that I am not finding a way to debug the plugin as suggested at the debugging a plugin section. Thank you for all the help thus far 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-33610) IOException with Clover 4.6 plugin
Title: Message Title Marek Parfianowicz resolved as Fixed Jenkins / JENKINS-33610 IOException with Clover 4.6 plugin Change By: Marek Parfianowicz 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-33610) IOException with Clover 4.6 plugin
Title: Message Title Marek Parfianowicz commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin Fix will be delivered in 4.8.1+ 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-45981) Remove empty "Manage Clover" section from Global Config
Title: Message Title Marek Parfianowicz resolved as Fixed Jenkins / JENKINS-45981 Remove empty "Manage Clover" section from Global Config Change By: Marek Parfianowicz 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-33610) IOException with Clover 4.6 plugin
Title: Message Title Marek Parfianowicz commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin I had a different exception in the log, but after my change I don't see any errors with remote agents. I think the change should fix the problem reported by you. I think that because the hudson/plugins/clover/CloverPublisher$1 was an anonymous inner class, so it had a reference to an enclosing class, i.e. the CloverPublisher which does not implement Serializable interface. And the most probably the CloverPublisher$1 (now renamed to GetPathFileCallable, which implements SlaveToMasterFileCallable) was called by the FileCallableWrapper mentioned in the bug description. 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-33610) IOException with Clover 4.6 plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin Code changed in jenkins User: Marek Parfianowicz Path: src/main/java/hudson/plugins/clover/CloverPublisher.java http://jenkins-ci.org/commit/clover-plugin/df5b18dc7a8a667464f522c8f9bc3963d645140f Log: JENKINS-33610: println 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-45981) Remove empty "Manage Clover" section from Global Config
Title: Message Title Marek Parfianowicz commented on JENKINS-45981 Re: Remove empty "Manage Clover" section from Global Config Fix will be delivered in 4.8.1+ 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-29977) Git Plugin truncates changelog
Title: Message Title Chris Kloehn commented on JENKINS-29977 Re: Git Plugin truncates changelog a command line build is what I tried at first. however this also threw errors at me for some files it couldn't find. Specifically these two files were: git-plugin\target\classes\META-INF\annotations\hudson.Extension, and git-plugin\target\classes\META-INF\exposed.stapler-beans. I will take a look at the Intellij for Jenkins and see if that helps. 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-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz resolved as Fixed Jenkins / JENKINS-34439 Clover plugin still has problems with pipeline builds Change By: Marek Parfianowicz 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-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Fix will be delivered in 4.8.1+ 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-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz started work on JENKINS-34439 Change By: Marek Parfianowicz 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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title
Tim McNally updated an issue
Jenkins / JENKINS-49543
Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Change By:
Tim McNally
When saving on the configuration page for a user (http://cool.jenkins.url/user/user.name/configure) I get the following stack trace. Adding "-Dhudson.remoting.ClassFilter=org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl" fixes the issue. This seems to also be causing issues for workflow-cps-global-lib-plugin's local git repository.Stack Trace:{noformat}java.lang.UnsupportedOperationException: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize hudson.model.User#properties for class hudson.model.User at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at
[JIRA] (JENKINS-33610) IOException with Clover 4.6 plugin
Title: Message Title Marek Parfianowicz started work on JENKINS-33610 Change By: Marek Parfianowicz 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-33610) IOException with Clover 4.6 plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin Code changed in jenkins User: Marek Parfianowicz Path: src/main/java/hudson/plugins/clover/CloverPublisher.java src/main/java/hudson/plugins/clover/slave/GetPathFileCallable.java http://jenkins-ci.org/commit/clover-plugin/c356a20e9f14da32db36194a2e80e1827ead0c44 Log: JENKINS-33610: extracted anonymous class to lop-level to get rid of NoClassDefFoundError: hudson/plugins/clover/CloverPublisher$1'; added more logging 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-49544) Cron job starting 12 hours later than scheduled
Title: Message Title Adam Rohacs created an issue Jenkins / JENKINS-49544 Cron job starting 12 hours later than scheduled Issue Type: Bug Assignee: Unassigned Components: other Created: 2018-02-13 22:17 Environment: 2.89.3 Priority: Critical Reporter: Adam Rohacs We have Jenkins jobs set to run overnight as they take hours to run. The last 2 days, the jobs kicked off as normal. The 3rd day, instead of running at 7pm-8pm (based on H in cron setting), the jobs started a full 12 hours later at 7am. The cron job looks like this: H 19 * * 0-6 The time zone is set to America/Chicago in Jenkins and on the Linux server. Add Comment
[JIRA] (JENKINS-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title Michael Neale commented on JENKINS-48204 Re: NPE in BlueOcean REST API / JIRA interaction Thanks Oleg Nenashev 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-29977) Git Plugin truncates changelog
Title: Message Title Mark Waite commented on JENKINS-29977 Re: Git Plugin truncates changelog The "Messages" classes are generated by maven at compile time. You might refer to Intellij for Jenkins or you might try compiling that project from the command line first (using Maven 3.5.0 or later - I use Maven 3.5.2). 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-22936) Move rename infrastructure from Job to AbstractItem
Title: Message Title Devin Nusbaum commented on JENKINS-22936 Re: Move rename infrastructure from Job to AbstractItem See PR 3289 for my proposal on how to fix this. 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-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Kendall Trego edited a comment on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Just ran tests from head: they pass on my system. However, the plugin is not available for download through the jenkins plugin tool, not sure what the process is to release it there.EDIT: The plugin shows in jenkins now, I hadn't checked for updates properly . Works as I expect. 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-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Kendall Trego edited a comment on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Just ran tests from head: they pass on my system. However, the plugin is not available for download through the jenkins plugin tool, not sure what the process is to release it there. EDIT: The plugin shows in jenkins now, I hadn't checked for updates properly 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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title
Tim McNally updated an issue
Jenkins / JENKINS-49543
Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Change By:
Tim McNally
When saving on the configuration page for a user I get the following stack trace. Adding "-Dhudson.remoting.ClassFilter=org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl" Fixes fixes the issue. This seems to also be causing issues for workflow-cps-global-lib-plugin 's local git repository .Stack Trace:{noformat}java.lang.UnsupportedOperationException: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize hudson.model.User#properties for class hudson.model.User at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at
[JIRA] (JENKINS-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title Tim McNally created an issue Jenkins / JENKINS-49543 Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl Issue Type: Bug Assignee: Unassigned Components: cli, workflow-cps-global-lib-plugin Created: 2018-02-13 21:54 Environment: Centos 6.7 Oracle JRE 1.8.0_112 Tomcat 8 Jenkins 2.105 Labels: JEP-200 Priority: Minor Reporter: Tim McNally When saving on the configuration page for a user I get the following stack trace. Adding "-Dhudson.remoting.ClassFilter=org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl" Fixes the issue. This seems to also be causing issues for workflow-cps-global-lib-plugin. Stack Trace: java.lang.UnsupportedOperationException: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Chris Kloehn edited a comment on JENKINS-29977 Re: Git Plugin truncates changelog [~markewaite] one last question about getting the project to build, I opened the pom.xml file with intellij and attempted a build. Unfortunately I could not find the package "hudson.plugins.git.Messages" so the project wouldn't build. I have done some searching for the file with little luck. Do you know where I might find it? The file looking for the "Messages" package is AncestryBuildChooser 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-29977) Git Plugin truncates changelog
Title: Message Title Chris Kloehn commented on JENKINS-29977 Re: Git Plugin truncates changelog Mark Waite one last question about getting the project to build, I opened the pom.xml file with intellij and attempted a build. Unfortunately I could not find the package "hudson.plugins.git.Messages" so the project wouldn't build. I have done some searching for the file with little luck. Do you know where I might find 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-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title Thomas K commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits Your plugin appears to work - it updates the webhook in Bitbucket as expected. However, whenever Jenkins pushes its commits, Bitbucket still fires push events back to Jenkins. I assume I'm doing something wrong somewhere, but I can't figure out what. Jenkins sets the git user.email equal to the e-mail address of a registered Bitbucket account, so I was hoping that would be enough for it to recognize the user, but apparently not. Unfortunately I don't know enough about how this all works, and I'm not the admin of our Bitbucket Server instance, so I can't just tune the log levels to figure out what Bitbucket is picking up. 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-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor commented on JENKINS-47321 Re: Quality Gates Sonarqube: projectKey Illegal character Ivana Sh Eleni Grozdani Dimitar Pop Dimitrov We had this issue on the wrong component(we thought it was the Sonar quality gates plugin). Would it be possible to take a look at https://github.com/jenkinsci/quality-gates-plugin/pull/57 and then potentially merge it? Seems like a quick win 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-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor reopened an issue Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Alex Taylor Resolution: Won't Do Status: Closed Reopened Assignee: Rafael Ramos Ivana Sh 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-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Alex Taylor Component/s: quality-gates-plugin Component/s: sonar-quality-gates-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-40518) Give the unzip step a parameter to suppress verbose output
Title: Message Title Matthew Brenner commented on JENKINS-40518 Re: Give the unzip step a parameter to suppress verbose output I submitted a PR for this which was merged this morning. I'm not familiar with this process, so I don't know when an update with this will actually get pushed out, but once it is the unzip step will have an extra parameter 'quiet', which when set to true will suppress all that `Extracting src/file -> dest/file`. 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-48816) Add an option to choose behaviour
Title: Message Title Rafael Ramos started work on JENKINS-48816 Change By: Rafael Ramos 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-48816) Add an option to choose behaviour
Title: Message Title Rafael Ramos commented on JENKINS-48816 Re: Add an option to choose behaviour Nice sugestion. 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-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title pixman20 edited a comment on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits [~thomaskasene], You can comment on [the main plugin page|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] or you can create an issue for the bitbucket-branch-source-plugin component (same as this issue), but I'm guessing it's just an issue with your configuration.You may have already done this, but be sure that you have configured your Jenkins instance (or your Bitbucket project job in Jenkins ) to update webhooks. Just to be sure I just verified our instance is working correctly on my instance.If Jenkins is actually creating the web hook on a Bitbucket Server instance, but the "Committers to ignore" field is not getting updated, then that may be an issue with the unofficial plugin. Either way, you may have to add some loggers to see what's going on if that's the case. 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-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title pixman20 commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits Thomas K, You can comment on the main plugin page or you can create an issue for the bitbucket-branch-source-plugin component (same as this issue), but I'm guessing it's just an issue with your configuration. You may have already done this, but be sure that you have configured your Jenkins instance (or your Bitbucket project) to update webhooks. Just to be sure I just verified our instance is working correctly on my instance. If Jenkins is actually creating the web hook on a Bitbucket Server instance, but the "Committers to ignore" field is not getting updated, then that may be an issue with the unofficial plugin. Either way, you may have to add some loggers to see what's going on if that's the case. 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-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Rafael Ramos closed an issue as Won't Do Issue opened in wrong component Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Rafael Ramos Status: Open Closed Resolution: Won't Do 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-49130) Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103
Title: Message Title Oleg Nenashev updated JENKINS-49130 It has been released in 1.2.0 Jenkins / JENKINS-49130 Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103 Change By: Oleg Nenashev Status: In Review Resolved 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-49130) Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103
Title: Message Title Rafael Ramos commented on JENKINS-49130 Re: Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103 New version released with this correction. 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Stephen McCants commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Dimitar Sakarov, as stated in JENKINS-32167, there is no owner or maintainer of this plugin. There is a workaround provided in comments under JENKINS-32167. Jesse Glick provided some better feedback code, but I don't think that has ever shipped. I looked at it and wrote a test case demonstrating the problem, but solving it was too complicated for the time I could devote to it. I don't think anything has changed since then. Wish someone would step up and fix it for us users, but I'm not expecting it until the SVN plugin is totally busted. 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-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Joshua Hoblitt created an issue Jenkins / JENKINS-49542 Scripts not permitted to use method java.util.Map isEmpty Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-02-13 19:58 Environment: jenkins 2.89.3 (LTS) workflow-cps 2.43 Priority: Minor Reporter: Joshua Hoblitt [:].isEmpty() triggers the wrath of the sandbox. Add Comment
[JIRA] (JENKINS-49130) Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49130 Re: Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103 Code changed in jenkins User: Rafael Ramos Path: docker-test/docker-compose.yml pom.xml http://jenkins-ci.org/commit/sonar-quality-gates-plugin/1213569a01cc66d367afb9068259237e6c2112f4 Log: JENKINS-49130 - Testing solution. update docker-compose.yml to test update parent version org.jenkins-ci.plugins:plugin:3.4 update version to 1.2.0-SNAPSHOT update jenkins version to 2.89.3 update dependencies 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-49130) Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49130 Re: Sonar Quality Gates run fails after upgrade to Jenkins 2.102/2.103 Code changed in jenkins User: Rafael Ramos Path: docker-test/docker-compose.yml pom.xml http://jenkins-ci.org/commit/sonar-quality-gates-plugin/0b4a50747dd897c5219b446cc7818092df736559 Log: Merge pull request #11 from arkanjoms/master Testing JENKINS-49130 and updating dependencies Compare: https://github.com/jenkinsci/sonar-quality-gates-plugin/compare/cf24945af8e7...0b4a50747dd8 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-49541) Force Build on Specific Branch
Title: Message Title Aaron Jensen created an issue Jenkins / JENKINS-49541 Force Build on Specific Branch Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-02-13 19:41 Priority: Minor Reporter: Aaron Jensen We have an application A that is dependent on another, application B. During the build, application A pulls in the latest version of application B's binaries. Application A always has to be rebuilt after application B. However, the branch from which application A gets built isn't always the same. (There are four branches that could need to be rebuilt: develop, release/minor, release/major, and master.) The job is configured to build every branch (i.e. its branch specifier is "origin/**"). When I click the "Force Build" button, I'd like the ability to choose what branch to force a build on. Currently, Jenkins rebuilds on the branch of the last build. Our current solution is to commit a fake/dummy change to the branch that needs to get rebuilt. This has created a lot of extra commits in our repository's history. Add Comment
[JIRA] (JENKINS-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Rafael Ramos updated JENKINS-47321 Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Rafael Ramos Status: Reopened Open 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-49540) Rebuild Commit
Title: Message Title Aaron Jensen created an issue Jenkins / JENKINS-49540 Rebuild Commit Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-02-13 19:37 Priority: Minor Reporter: Aaron Jensen We need to be able to rebuild commits/builds. * On the build results page, one of the options in the left menu should be "Rebuild Commit" or "Try Again" or "Run Again". When I click that button, that build should re-run on the same commit and branch of the original build. Build number would still increment. When I'm on a project's page, with the build history on the left, when I click the arrow to the right of a build name/number, and the action menu pops up, the same "Rebuild Commit"/"Try Again"/"Run Again" option should be available. We have one build per repository. Builds trigger whenever a change is pushed to any branch in a repository (e.g. our branch specifier is "origin/**"). When a build fails for a reason that has nothing to do with code in the repository (e.g. disk fills up, some external resource is temporarily down, etc.), the only way to re-build that branch is to make some change to the repository, usually adding/removing some whitespace. Most other build servers I've used (TeamCity and Appveyor) let you rebuild a commit. We do not use Jenkins pipelines, nor have any plans to do so.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title Thomas K commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits I can confirm that I was able to build and install your unofficial plugin pixman20 - and it seems to be working! However, I'm unable to get the "Committers to ignore"-part of the webhook actually working, but I suppose that's a question for the Bitbucket Branch Source plugin... Any idea where I might post issues for that plugin? It doesn't seem to be available through GitHub, possibly because it's a fork. 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-49539) Jenkins cannot trigger load runner scenario
Title: Message Title Yojana Joshi created an issue Jenkins / JENKINS-49539 Jenkins cannot trigger load runner scenario Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-02-13 19:32 Environment: What is your Jenkins master OS and Jenkins version? Windows server 2012, Jenkins 2.60.2 What is your Jenkins slave OS and Jenkins version? Windows server 2012, Jenkins 2.60.2 What is your Jenkins plugin version? 5.1.0.2-beta Does the issue occur with all Jenkins jobs or this one specifically? All the jobs trying to do LR scenario Priority: Blocker Reporter: Yojana Joshi We have jenkins server setup internally and Jenkins agent is setup on a load runner machine. We have a job setup to run a LR scenario from file server. LR scenario is setup to have at least 1 SLA and "Run too completion" is not setup as required by Jenkins. When triggered, this jenkins job picks up the scenario correctly and starts executing it. But, eventually sends following error and exits the job execution 13:40:27 Preparing scenario **\New_Scenario_for_Jenkins.lrs for execution.*13:40:59 Test result: Error
[JIRA] (JENKINS-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title Jesse Glick commented on JENKINS-38381 Re: Optimize log handling in Pipeline and Durable Task workflow-durable-task-step #65 covers everything I have updated recently: there is now a set of independently mergeable PRs for: push rather than pull of durable task output proper handling of Unicode (JENKINS-31096) both of those together (so they could be merged in either order) workflow-job #27 is now downstream of those changes, and continues to encapsulate the broader rewrite: single log sink for all Pipeline steps SPI to allow that sink be an external service redesign of step console annotations for a more usable display in the classic UI (this requires the first item) 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-49531) Docker ps command output is empty when adding a command to the image.run() section
Title: Message Title
Maksim Gerasimenko updated an issue
Jenkins / JENKINS-49531
Docker ps command output is empty when adding a command to the image.run() section
Change By:
Maksim Gerasimenko
*Scenario 1:*I try to run the Selenoid image via Jenkinsfile with the following command:{code:java}stage('Start services') {docker.image('aerokube/selenoid').run('--name selenoid ' + '-p : ' + '-v C:/workspace/selenoid:/etc/selenoid ' + '-v C:/workspace/output:/opt/selenoid/video ' + '-v //var/run/docker.sock:/var/run/docker.sock ' + '-e "OVERRIDE_VIDEO_OUTPUT_DIR=/C/workspace/output/"','-video-output-dir /output')}{code}After the completion of this code and run the {code:java}docker ps{code} I don't see any information related to the selenoid. When I try to run this command from my PC manually I see the following: {code:java}docker: Error response from daemon: Conflict. The container name "/selenoid" is already in use by container "ce43d0476d5d388d8471e6891b981df8b2e52206f94c3f7f2b81180ae95de821". You have to remove (or rename) that container to be able to reuse that name.{code}Please see the docker logs for this container:{code:java}2018/02/13 14:13:32 Loading configuration files...2018/02/13 14:13:32 /usr/bin/selenoid: browsers config: read error: open config/browsers.json: no such file or directory{code} *Scenario 2:*If I delete the next command{code:java} '-video-output-dir /output'{code} selenoid runs and I see it in the docker ps output. But without this parameters, I'm unable to link the video to the output dir. Please see the following logs: {code:java}2018/02/13 14:10:37 Loading configuration files...2018/02/13 14:10:37 Loaded configuration from [/etc/selenoid/browsers.json]2018/02/13 14:10:37 Using default containers log configuration because of: read error: open config/container-logs.json: no such file or directory2018/02/13 14:10:37 Timezone: Local2018/02/13 14:10:37 Video Dir: /opt/selenoid/video2018/02/13 14:10:37 Listening on :2018/02/13 14:12:02 [NEW_REQUEST]2018/02/13 14:12:02 [NEW_REQUEST_ACCEPTED]2018/02/13 14:12:02 [0] [LOCATING_SERVICE] [chrome-]2018/02/13 14:12:02 Using default version: 62.02018/02/13 14:12:02 [0] [USING_DOCKER] [chrome-62.0]2018/02/13 14:12:02 [0] [CREATING_CONTAINER] [selenoid/vnc:chrome_62.0]2018/02/13 14:12:02 [0] [STARTING_CONTAINER] [selenoid/vnc:chrome_62.0] [bd843e51d94563a69a8e54651b4cc71cd6543684c1af08460e738823e23610b9]2018/02/13 14:12:03 [0] [CONTAINER_STARTED] [selenoid/vnc:chrome_62.0] [bd843e51d94563a69a8e54651b4cc71cd6543684c1af08460e738823e23610b9] [1.2498233s]2018/02/13 14:12:03 [0] [CREATING_VIDEO_CONTAINER] [selenoid/video-recorder]2018/02/13 14:12:04 [0] [REMOVING_CONTAINER] [bd843e51d94563a69a8e54651b4cc71cd6543684c1af08460e738823e23610b9]2018/02/13 14:12:05 [0] [CONTAINER_REMOVED] [bd843e51d94563a69a8e54651b4cc71cd6543684c1af08460e738823e23610b9]2018/02/13 14:12:05 [0]
[JIRA] (JENKINS-44430) p4 authenticity of 'perforce:1666' can't be established
Title: Message Title Jay Spang commented on JENKINS-44430 Re: p4 authenticity of 'perforce:1666' can't be established I believe I'm seeing this error too (Jenkins 2.89.3, P4 Plugin 1.8.4). For clarification: It occurs on existing (working) connections. I'm not setting up a new connection here. It's intermittent. It happens 1/20 builds or so, and retrying always succeeds. The reported "mismatched" fingerprint does match what I have configured. It never changes. I think Allister's guess is on the right track. It seems like maybe a concurrency issue or race condition? 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen edited a comment on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' REPOENING REOPENING ISSUE.. broke other things containing slash '/', see previous comment. 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen edited a comment on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' REPOENING ISSUE .. broke other things containing slash '/', see previous comment. 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen edited a comment on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' This fix seriously broke something. We've been at it for a week – it still will not find Jenkinsfile in subdirectories. Started by user P*** S (p**.***) [Thu Jan 25 10:00:01 CET 2018] Starting branch indexing... Connecting to [http://***.***.**.se|http://%2A%2A%2A.%2A%2A%2A.%2A%2A.se/] using allowed.user/**Repository type: Git Looking up asd/asd_stuff for branches Checking branch feature/asd-things from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not found Skipped Checking branch feature/ASD-123-test-doit from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not found Skipped .. although the file is clearly present and worked before this patch. Jenkinsfile in root path of a repo will work just fine, in a subdirectory, not so fine. To clarify: If you specify Jenkinsfile in a subdirectory, that will no longer work. I've reproduced this numerous times before re-opening this issue on my own repos. 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen reopened an issue .. broke other things containing slash '/', see comment. Jenkins / JENKINS-47978 Lightweight checkout not working for branches that contain forward slash '/' Change By: bjorn rohlen Resolution: Fixed Status: Resolved 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,
[JIRA] (JENKINS-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen edited a comment on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' This fix seriously broke something. We've been at it for a week – it still will not find Jenkinsfile in subdirectories. Started by user P*** S (p**.***) [Thu Jan 25 10:00:01 CET 2018] Starting branch indexing... Connecting to [http://***.***.**.se|http://%2A%2A%2A.%2A%2A%2A.%2A%2A.se/] using allowed.user/**Repository type: Git Looking up asd/asd_stuff for branches Checking branch feature/asd-things from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not found Skipped Checking branch feature/ASD-123-test-doit from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not found Skipped .. although the file is clearly present and worked before this patch. Jenkinsfile in root path of a repo will work just fine, in a subdirectory, not so fine. 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen commented on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' This fix seriously broke something. We've been at it for weeks – it still will not find Jenkinsfile in subdirectories. Started by user P*** S (p*.**) [Thu Jan 25 10:00:01 CET 2018] Starting branch indexing... Connecting to http://***.***.**.se using allowed.user/**Repository type: Git Looking up asd/asd_stuff for branches Checking branch feature/asd-things from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not found Skipped Checking branch feature/ASD-123-test-doit from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not found Skipped ... ... although the file is clearly present and worked before this patch. 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title bjorn rohlen edited a comment on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' This fix seriously broke something. We've been at it for weeks a week – it still will not find Jenkinsfile in subdirectories. Started by user P*** S (p**.***)[Thu Jan 25 10:00:01 CET 2018] Starting branch indexing...Connecting to [ http://***.***.**.se |http://%2A%2A%2A.%2A%2A%2A.%2A%2A.se/] using allowed.user/**Repository type: GitLooking up asd/asd_stuff for branchesChecking branch feature/asd-things from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not foundSkippedChecking branch feature/ASD-123-test-doit from asd/asd_stuff ‘javaproject/asd-stuff-autotest/Jenkinsfile’ not foundSkipped.. although the file is clearly present and worked before this patch. 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Mike Ellery commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once I would like to point out that this would be particularly useful for powershell scripts since the proposed workaround of "just redirect your stuff to a file" just doesn't work in powershell. I've tried umpteen different ways to get powershell to just log all my output and it won't have any of it. Start/Stop Transcript, classic redirection, none of them work consistently or reliably in the jenkins pipeline. Just having the ability to capture the output AND the return code to know if we failed would be outstanding. As it stands right now, I either get my output or I get an exception and I have to do some pipeline trickery to handle both cases. Ugh. 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-35026) Pipeline script from SCM triggers builds on sub pipeline change
Title: Message Title Jerald Sabu commented on JENKINS-35026 Re: Pipeline script from SCM triggers builds on sub pipeline change Any update on this issue ? I get all 7 builds triggered at the same time even when I commit a change to the pipeline script of other builds where scm polling is not even 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-28321) Method pointer operator (.&) broken
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28321 Re: Method pointer operator (.&) broken Code changed in jenkins User: Andrew Bayer Path: src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/ee83ee52d5d14e30cc2c3092ae5463add860ab73 Log: JENKINS-28321 Verify that whitelisted method pointers can be used. 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-41248) Infinite loop / Stack overflow when using a setter in pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41248 Re: Infinite loop / Stack overflow when using a setter in pipeline Code changed in jenkins User: Andrew Bayer Path: src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/85d032587f4765036c3ee05c9c46c23b2287067c Log: JENKINS-41248 Verify that explicit setter methods take priority. 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-27916) GString not flattened to String by DSL inside a map
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27916 Re: GString not flattened to String by DSL inside a map Code changed in jenkins User: Andrew Bayer Path: src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/329f900d776c96f4f91576bb7bda3bbde31a26e1 Log: JENKINS-27916 Test verifying use of GStrings in map keys 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-38052) Pipeline parallel map not supporting curried closures
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38052 Re: Pipeline parallel map not supporting curried closures Code changed in jenkins User: Andrew Bayer Path: src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/37e3fdde8a0ee5470924ff09ba3957ec421d29f5 Log: JENKINS-38052 Test verifying that JENKINS-38052 is 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-47756) GitHub plugin triggers builds when changes pushed to global pipeline
Title: Message Title Jerald Sabu commented on JENKINS-47756 Re: GitHub plugin triggers builds when changes pushed to global pipeline Any update on this issue ? I get all 7 builds triggered at the same time even when I commit a change to the pipeline script of other builds where scm polling is not even 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-44598) git workspace should be reset before build PR merged with base branch
Title: Message Title andrew morton commented on JENKINS-44598 Re: git workspace should be reset before build PR merged with base branch The clean before build worked for me. The sparse checkout option didn't seem to have any effect on this issue. 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-49538) Release plugin doesn't appear at all
Title: Message Title Oleg Nenashev commented on JENKINS-49538 Re: Release plugin doesn't appear at all Do you see any errors in the Jenkins log on startup? 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-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Kendall Trego edited a comment on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Just ran tests from head: they pass on my system. The However, the plugin is not available for download through the jenkins plugin tool, however not sure what the process is to release it 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-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Kendall Trego edited a comment on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Just ran tests from head: they pass on my system. The plugin is not available for download through the jenkins plugin tool, however. 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-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Kendall Trego commented on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Just ran tests from head: they pass on my system. 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-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Nicolas De Loof commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation Nothing planned yet, not even agreement on implementation decisions. 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-49538) Release plugin doesn't appear at all
Title: Message Title rherrick created an issue Jenkins / JENKINS-49538 Release plugin doesn't appear at all Issue Type: Bug Assignee: Oleg Nenashev Attachments: Screen Shot 2018-02-13 at 11.45.47 AM.png, Screen Shot 2018-02-13 at 11.50.04 AM.png Components: release-plugin Created: 2018-02-13 17:57 Environment: CentOS 7.4.1708, Jenkins ver. 2.106, Release plugin v2.10 Priority: Major Reporter: rherrick We've had the release plugin working on our Jenkins installation for quite a while and used the lastSuccessfulReleaseBuild permalink as a way to publish our downloads. A couple weeks ago this just stopped working. I'm not sure if it was the upgrade to v2.10 or not, although that happened in close proximity time-wise to when the problem started occurring. When I started looking into it, I realized that nothing from the release plugin was working: we don't have the lastSuccessfulReleaseBuild permalink, the Release option is no longer available in pop-ups, and previous release builds are no longer marked as release builds (although they are still marked as "keep forever"). I included a screen shot of one of our projects where you can see the lack of lastSuccessfulReleaseBuild permalink as well as a build marked "keep forever" that was our previous 1.7.4.1 release. I've tried removing the release plugin and reinstalling it with no change. I've removed it, completely deleted it from the plugins folder (release.jpi, release.hpi.pinned and the release folder), and reinstalled it. No change. There are no errors relating to the release plugin in the jenkins.log that I can
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Steve Todorov commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation This seems like it will fix a lot of the issues we're having with running maven builds in docker containers. What is the approximate timeline for having this feature released - I'm guessing a few months? 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-49537) "Waiting for next available executor on master" solved by *looking* at other jobs
Title: Message Title
Niklas Hambuechen created an issue
Jenkins / JENKINS-49537
"Waiting for next available executor on master" solved by *looking* at other jobs
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2018-02-13 17:52
Environment:
Jenins 2.95, on NixOS
Priority:
Minor
Reporter:
Niklas Hambuechen
OK so this is a weird one. Once a week or so, by Jenkins builds get stuck with Waiting for next available executor on master. E.g. now, the a build got stuck for 2 days this way. The funny thing is: I can resolve this bug simply by read-only-browsing around in the Jenkins UI. Once I view the console output of the finished build before the hanging build, the hanging build suddenly starts building. So, "looking angry at Jenkins" makes the issue go away. I could reproduce this 4 times so far, but it takes a week or so to happen again so it's not exactly easy to reproduce. After short consideration if you have any idea what might cause this, please advise how I can gather more information to figure this out. Thanks! (I've filed the bug as `core` but don't know if it might be caused by a different plugin.)
Jenkins 2.95 Plugins: {{ org.jenkins-ci.main:jenkins-war:2.95 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.jenkins-ci.modules:instance-identity:2.1 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 com.github.jnr:jnr-constants:0.9.8 org.jenkins-ci.modules:windows-slave-installer:1.9.2
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Dimitar Sakarov commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Is this problem resolved in some other way, e.g. by using a newer Jenkins / SVN plugin / Credentials plugin? Is there a workaround other than just restarting the job (additional credentials didn't make it work)? And if the answers for both questions is No, then is there at least an ETA for the issue to be fixed anytime soon? 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.
