[JIRA] (JENKINS-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Jonas Lindström edited a comment on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect [~oleg_nenashev] Still unfixed with client 3.12. 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-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47625 Swarm client 3.6: disableSslVerification has no effect Change By: Oleg Nenashev Labels: newbie-friendly regression remoting 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-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Oleg Nenashev commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect That's why I asked to ping me. Sorry, I receive more requests than I can handle so some things get missed. 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-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Jonas Lindström commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect No problem 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-50265) TasksScannerPublisher : multiple reports
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50265 Re: TasksScannerPublisher : multiple reports Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java http://jenkins-ci.org/commit/pipeline-maven-plugin/1258b4a349f8f15f437f4a70737448b0b6b5c7cb Log: Merge pull request #135 from netceler/master JENKINS-50265 : Fix multiple reports created by TasksScannerPublisher Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/a9345d3abb3b...1258b4a349f8 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-50265) TasksScannerPublisher : multiple reports
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50265 Re: TasksScannerPublisher : multiple reports Code changed in jenkins User: Benoit Guerin Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java http://jenkins-ci.org/commit/pipeline-maven-plugin/1d9436e45564f89b1db8db3f537254befe82bd44 Log: JENKINS-50265 : Fix multiple reports created by TasksScannerPublisher 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-45650) CLI known_hosts support fails on non-standard SSH ports
Title: Message Title Seba Pien commented on JENKINS-45650 Re: CLI known_hosts support fails on non-standard SSH ports Hi I'm using Jenkins ver 2.107.1 and this issue is still present. /Seba 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Josh McDonald started work on JENKINS-50406 Change By: Josh McDonald 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Josh McDonald commented on JENKINS-50406 Re: "Triggered Build" links broken with cloudbees-folder https://github.com/jenkinsci/blueocean-plugin/pull/1699 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Josh McDonald updated JENKINS-50406 Jenkins / JENKINS-50406 "Triggered Build" links broken with cloudbees-folder Change By: Josh McDonald 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-50367) SAMLException: Identity provider has no single sign on service available for the selected
Title: Message Title Michael D commented on JENKINS-50367 Re: SAMLException: Identity provider has no single sign on service available for the selected Can be closed, SingleSignOnService information was missing in idp metadata 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-50422) RestartJenkinsRule gets a new rootDir for each step when using @LocalData
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-50422
RestartJenkinsRule gets a new rootDir for each step when using @LocalData
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
jenkins-test-harness
Created:
2018-03-27 08:22
Environment:
JTH 2.34
Priority:
Major
Reporter:
Baptiste Mathus
Issue When using RestartJenkinsRule, one expects to keep using the same JENKINS_HOME. This is the case normally, but not when using both RestartableJenkinsRule and @LocalData. Expected behaviour Jenkins.getRootDir() should stay the same during the execution of a given test, not be a new one for each step. How to reproduce I have created a test project to help understand/reproduce, but this is very easy to do.
Create a test class with a @Rule RestartableJenkinsRule story ...
Put the following in a test: story.then(rule -> System.out.println("ROOTDIR: "+rule.jenkins.getRootDir()));
You will see that the printing above will display different, or the same values, if you respectively use or do not use @LocalData.
[JIRA] (JENKINS-50422) RestartJenkinsRule gets a new rootDir for each step when using @LocalData
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-50422
RestartJenkinsRule gets a new rootDir for each step when using @LocalData
Change By:
Baptiste Mathus
h3. IssueWhen using {{RestartJenkinsRule}}, one expects to keep using the same {{JENKINS_HOME}}.This is the case normally, but *not* when using both {{RestartableJenkinsRule}} and {{@LocalData}}.h3. Expected behaviourJenkins.getRootDir() should stay the same during the execution of a given test, not be a new one for each step.h3. How to reproduceI have created a test project to help understand/reproduce, but this is very easy to do.* Create a test class with a {{@Rule RestartableJenkinsRule story ...}}* Put the following in a test: {{story.then(rule -> System.out.println("ROOTDIR: "+rule.jenkins.getRootDir()));}}You will see that the printing above will display different, or the same values, if you respectively use or do not use {{@LocalData}}. h4. Reproducerhttps://github.com/batmat/localdata-jenkinsruleCurrrently fails (as _expected_) this way:{noformat}...[INFO] Running InjectedTest[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.03 s - in InjectedTest[INFO] Running io.jenkins.plugins.ZeTest[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.455 s <<< FAILURE! - in io.jenkins.plugins.ZeTest[ERROR] withLocalData(io.jenkins.plugins.ZeTest) Time elapsed: 1.75 s <<< FAILURE!java.lang.AssertionErrorat org.junit.Assert.fail(Assert.java:86)at org.junit.Assert.assertTrue(Assert.java:41)at org.junit.Assert.assertTrue(Assert.java:52)at io.jenkins.plugins.ZeTest.lambda$withLocalData$3(ZeTest.java:47)at org.jvnet.hudson.test.RestartableJenkinsRule$3.evaluate(RestartableJenkinsRule.java:135)at org.jvnet.hudson.test.RestartableJenkinsRule$5.evaluate(RestartableJenkinsRule.java:162)at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:548)at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.lang.Thread.run(Thread.java:748)[INFO][INFO] Results:[INFO][ERROR] Failures:[ERROR] ZeTest.lambda$withLocalData$3:47[INFO][ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0[INFO][INFO] [INFO] BUILD FAILURE[INFO] [INFO] Total time: 18.022 s[INFO] Finished at: 2018-03-27T10:27:33+02:00[INFO] Final Memory: 52M/832M[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project localdata-jenkinsrule: There are test failures.[ERROR][ERROR] Please refer to /home/tiste/localdata/localdata-jenkinsrule/target/surefire-r
[JIRA] (JENKINS-50423) Please stop removing stable releases
Title: Message Title Onno van der Straaten created an issue Jenkins / JENKINS-50423 Please stop removing stable releases Issue Type: Improvement Assignee: Unassigned Components: jenkins-cloudformation Created: 2018-03-27 08:34 Priority: Minor Reporter: Onno van der Straaten I noticed again the practice by Jenkins community to remove stable releases from yum and debian repository. A release should be stable or not. Save / recommended to use or not. If you remove stable releases this makes it harder / impossible to upgrade in a save way because Jenkins engineers will not be able to recreate a Jenkins server. For simple reason, the software is no longer available. You force untested upgrades. Do you feel lucky today? Add Comment
[JIRA] (JENKINS-50421) Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration
Title: Message Title Cyrille Le Clerc commented on JENKINS-50421 Re: Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-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-50421) Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50421 Re: Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration [~bingshiao] Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-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-49721) withMaven requires maven argument when using with takari wrapper
Title: Message Title Cyrille Le Clerc commented on JENKINS-49721 Re: withMaven requires maven argument when using with takari wrapper dan tran Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-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-50414) Add healthy/unhealthy thresholds to the Open Task Scanner publisher
Title: Message Title Cyrille Le Clerc commented on JENKINS-50414 Re: Add healthy/unhealthy thresholds to the Open Task Scanner publisher Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-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-49227) Cannot configure findbugs reporter to mark build as unstable for findbugs failures
Title: Message Title Cyrille Le Clerc commented on JENKINS-49227 Re: Cannot configure findbugs reporter to mark build as unstable for findbugs failures Stephen Connolly Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-1 I have added some healthy/unhealthy settings, not all of them as there where many. can you share with us a sample of the settings you want to use? 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-50241) Add Maven details tab to build result page
Title: Message Title Cyrille Le Clerc commented on JENKINS-50241 Re: Add Maven details tab to build result page Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-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-50265) TasksScannerPublisher : multiple reports
Title: Message Title Cyrille Le Clerc commented on JENKINS-50265 Re: TasksScannerPublisher : multiple reports benoit guerin Please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.0-beta-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-50385) Jenkins Cloud Foundry plugin error: Organization does not exist
Title: Message Title Muthuganesh Gnanasekar commented on JENKINS-50385 Re: Jenkins Cloud Foundry plugin error: Organization does not exist Got this issue fixed by replacing the & characters in the organization name to the string 'and'. So a correct org name for my case is "_A_and_B_Ants_and_Bananas_ABC_AB_ABC-AB-C-D-LoremIpsum-DolorSit-100_" 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-50385) Jenkins Cloud Foundry plugin error: Organization does not exist
Title: Message Title Muthuganesh Gnanasekar closed an issue as Incomplete Closing the issue since an alternate solution had been found. Jenkins / JENKINS-50385 Jenkins Cloud Foundry plugin error: Organization does not exist Change By: Muthuganesh Gnanasekar Status: Open Closed Resolution: Incomplete 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-50385) Jenkins Cloud Foundry plugin error: Organization does not exist
Title: Message Title Muthuganesh Gnanasekar edited a comment on JENKINS-50385 Re: Jenkins Cloud Foundry plugin error: Organization does not exist Got this issue fixed by replacing the & characters in the organization name to the string 'and'. So a correct org name for my case is " _A_and_B_Ants_and_Bananas_ABC_AB_ABC A_and_B_Ants_and_Bananas_ABC_AB_ABC -AB-C-D-LoremIpsum-_DolorSit_- 100_ 100 " 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-45437) DomainName attribute
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45437 Re: DomainName attribute Code changed in jenkins User: Ivan Fernandez Calvo Path: src/main/java/org/jenkinsci/plugins/saml/SamlSecurityRealm.java src/main/java/org/jenkinsci/plugins/saml/conf/Attribute.java src/main/java/org/jenkinsci/plugins/saml/conf/AttributeEntry.java src/main/java/org/jenkinsci/plugins/saml/user/SamlCustomProperty.java src/main/resources/org/jenkinsci/plugins/saml/SamlSecurityRealm/config.jelly src/main/resources/org/jenkinsci/plugins/saml/conf/Attribute/config.jelly src/main/resources/org/jenkinsci/plugins/saml/user/SamlCustomProperty/config.jelly src/main/webapp/help/customAttributes.html src/test/java/org/jenkinsci/plugins/saml/OpenSamlWrapperTest.java http://jenkins-ci.org/commit/saml-plugin/814dab17e19de991f27e85306565d704d21c42b6 Log: JENKINS-45437 load SAML custom attributes (#43) JENKINS-45437 load SAML custom attributes fix 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-50367) SAMLException: Identity provider has no single sign on service available for the selected
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50367 Re: SAMLException: Identity provider has no single sign on service available for the selected thx, I added this to the troubleshooting guide for future users. 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-50367) SAMLException: Identity provider has no single sign on service available for the selected
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-50367 SAMLException: Identity provider has no single sign on service available for the selected Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45437) DomainName attribute
Title: Message Title Ivan Fernandez Calvo updated JENKINS-45437 Jenkins / JENKINS-45437 DomainName attribute Change By: Ivan Fernandez Calvo 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-50416) git parameter plugin does not working with shared workspace plugin
Title: Message Title Boguslaw Klimas commented on JENKINS-50416 Re: git parameter plugin does not working with shared workspace plugin Hi, This issue was resolved in version 0.7.0 JENKINS-37370, I do not support old plugin versions 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-50416) git parameter plugin does not working with shared workspace plugin
Title: Message Title Boguslaw Klimas resolved as Duplicate Jenkins / JENKINS-50416 git parameter plugin does not working with shared workspace plugin Change By: Boguslaw Klimas Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44286) Matrix jobs are not built on assigned node
Title: Message Title Oliver Gondža commented on JENKINS-44286 Re: Matrix jobs are not built on assigned node Note "Restrict where this project can be run" specifies where the parent build runs and does not influence children in any way. If you want to specify when children should run, use label (_expression_) axis. 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-48721) I/O error writing PNG file
Title: Message Title Sorin Sbarnea commented on JENKINS-48721 Re: I/O error writing PNG file We got a very similar error after upgrading our Jenkins from 2.73 LTS to 2.89 LTS. See log at https://gist.github.com/ssbarnea/aec8ea4500c1103c2611bea556a81c31 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-48721) I/O error writing PNG file
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-48721 Re: I/O error writing PNG file We got a very similar error after upgrading our Jenkins from 2.73 LTS to 2.89 LTS.See log at [ https://gist.github.com/ssbarnea/aec8ea4500c1103c2611bea556a81c31 ]Any idea what is causing it and if there is a workaround? For the moment we disabled the graph generation inside BFA config. Looking at the trace I have reasons to believe that is not a BFA bug. 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-50398) Error when running browserstack jobs in folders
Title: Message Title David Sanftenberg commented on JENKINS-50398 Re: Error when running browserstack jobs in folders We've just ran into this too. The job is indeed in a folder. Any eta on a fix? 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-46219) Should fetch origin/refs even if repository exists in work tree
Title: Message Title pjdarton commented on JENKINS-46219 Re: Should fetch origin/refs even if repository exists in work tree Have a Git repository that isn't empty. Have a Windows slave (we're using Windows 7 x64, in case that makes a difference) separate from the Jenkins master. Configure Jenkins' Git tool with the URL of a zip of "PortableGit" version 2.10.0 for Windows so that Jenkins can auto-install Git on slaves that need it. Have a Jenkins build job configured to read its source code from the git repo and to poll the SCM for changes. Have a single build step that just lists all the files out. Tell Jenkins to restrict where that build can run so that it'll only ever run on the Windows slave mentioned above. Jenkins should detect that it's never built the build before and build it. It'll auto-install git, then use it to grab the source code from the git repository into the Jenkins workspace. That should all work and, in the console output of the build, you'll see the .git folder there plus the contents of the Git repository. Now make and commit a change into the Git repository. After a while, Jenkins should detect the change and re-trigger the build. That'll run on the same Windows slave as before, in the same workspace folder, which has the .git folder left over from the previous build and hence has a clone of the repository that contains all the changes except for the one that was just committed. What I see, in this scenario, is that the git checkout fails - it doesn't pull changes from the git repo so that when it later tries to checkout the latest revision, it can't (as the local .git folder doesn't contain the latest code). (if there's any of the above that needs clarifying, let me know and I'll add more detail) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50424) Testfairy plugin Failed to deserialize response UserRequest
Title: Message Title Levente Simon created an issue Jenkins / JENKINS-50424 Testfairy plugin Failed to deserialize response UserRequest Issue Type: Bug Assignee: Unassigned Components: testfairy-plugin Created: 2018-03-27 10:17 Labels: JEP-200 Priority: Minor Reporter: Levente Simon This exception appears when the Testfairy plugin finishes an upload: ERROR: Failed to deserialize response to UserRequest:org.jenkinsci.plugins.testfairy.TestFairyIosRecorder$IosRemoteRecorder@36ebc088: java.lang.SecurityException: Rejected: net.sf.json.JSONObject; see https://jenkins.io/redirect/class-filter/ com.testfairy.uploader.TestFairyException: Failed to deserialize response to UserRequest:org.jenkinsci.plugins.testfairy.TestFairyIosRecorder$IosRemoteRecorder@36ebc088: java.lang.SecurityException: Rejected: net.sf.json.JSONObject; see https://jenkins.io/redirect/class-filter/ at org.jenkinsci.plugins.testfairy.TestFairyIosRecorder.perform(TestFairyIosRecorder.java:61) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1752) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.io.
[JIRA] (JENKINS-50265) TasksScannerPublisher : multiple reports
Title: Message Title benoit guerin commented on JENKINS-50265 Re: TasksScannerPublisher : multiple reports Done. Looks good, thanks ! 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-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title Paul Allen commented on JENKINS-50393 Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable The only significant change introduced in 1.8.7 was from pull request https://github.com/jenkinsci/p4-plugin/pull/70 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-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Esben Madsen commented on JENKINS-50019 Re: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer We have just seen the same issue on one specific slave after an IT update caused the machine to restart. The node is running windows 7, Java 1.8.0_161 (32 bit), and this paticular one is started with web start. The node has been failing for several days (since the udate + reset). Restarting the slave seems to have fixed it for now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50424) Testfairy plugin Failed to deserialize response UserRequest
Title: Message Title Levente Simon assigned an issue to Gil Megidish Jenkins / JENKINS-50424 Testfairy plugin Failed to deserialize response UserRequest Change By: Levente Simon Assignee: Gil Megidish 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-50424) Testfairy plugin Failed to deserialize response UserRequest
Title: Message Title
Levente Simon updated an issue
Jenkins / JENKINS-50424
Testfairy plugin Failed to deserialize response UserRequest
Change By:
Levente Simon
This exception appears when the Testfairy plugin finishes an upload:{noformat} TestFairy iOS/Android Uploader... v 4.2, run on Loading changeLog from source controlUploading App...--add (file) apk_file: /Volumes/Data/JenkinsWorkspace/workspace/VerticalFarm_Trunk_TestFairy/VerticalFarm.ipa--add api_key: 68a6***998--add changelog: No changes since last build--add video-quality: high--add screenshot-interval: 1--add max-duration: 10m--add testers-groups: VerticalFarm, Publishing--add data-only-wifi: off--add record-on-background: off--add video: off--add auto-update: off--add notify: on--add instrumentation: offMetrics: logcatpost finished {"status":"ok","app_name":"FarmOn!Dev","app_version":"1.2.0debug","file_size":62887373,"build_url":"https://app.testfairy.com/projects/3724851-farmon/builds/7874951","instrumented_url":"http://my.testfairy.com/download/6WW3ED1S6MRJTC1DT29QC5DZ8F4NKXRFWV02FPHX7E20YJQ6/getapp","download_page_url":"https://tsfr.io/wC4faA","app_url":"https://my.testfairy.com/download/6WW3ED1S6MRJTC1DT29QC5DZ8F4NKXRFWV02FPHX7E20YJQ6/getapp","invite_testers_url":"https://app.testfairy.com/projects/3724851-farmon/builds/7874951/invite","icon_url":"https://s3.amazonaws.com/testfairy/icons/106045/20c93c9f3e14cc4373f9e298da7f4fd00a83ad18.png","notified_testers_groups":""}Check the new build : https://app.testfairy.com/projects/3724851-farmon/builds/7874951 ERROR: Failed to deserialize response to UserRequest:org.jenkinsci.plugins.testfairy.TestFairyIosRecorder$IosRemoteRecorder@36ebc088: java.lang.SecurityException: Rejected: net.sf.json.JSONObject; see https://jenkins.io/redirect/class-filter/com.testfairy.uploader.TestFairyException: Failed to deserialize response to UserRequest:org.jenkinsci.plugins.testfairy.TestFairyIosRecorder$IosRemoteRecorder@36ebc088: java.lang.SecurityException: Rejected: net.sf.json.JSONObject; see https://jenkins.io/redirect/class-filter/ at org.jenkinsci.plugins.testfairy.TestFairyIosRecorder.perform(TestFairyIosRecorder.java:61) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1752) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.io.IOException: Failed to deserialize response to UserRequest:org.jenkinsci.plugins.testfairy.TestFairyIosRecorder$IosRemoteRecorder@36ebc088: java.lang.SecurityException: Rejected: net.sf.json.JSONObject; see https://jenkins.io/redirect/class-filter/ at hu
[JIRA] (JENKINS-50422) RestartableJenkinsRule gets a new rootDir for each step when using @LocalData
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50422 RestartableJenkinsRule gets a new rootDir for each step when using @LocalData Change By: Baptiste Mathus Summary: RestartJenkinsRule RestartableJenkinsRule gets a new rootDir for each step when using @LocalData 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-46219) Should fetch origin/refs even if repository exists in work tree
Title: Message Title pjdarton edited a comment on JENKINS-46219 Re: Should fetch origin/refs even if repository exists in work tree Have a Git repository that isn't empty.Have a Windows slave (we're using Windows 7 x64, in case that makes a difference) separate from the Jenkins master.Configure Jenkins' Git tool with the URL of a zip of "PortableGit" version 2.10.0 for Windows so that Jenkins can auto-install Git on slaves that need it.Have a Jenkins build job configured to read its source code from the git repo and to poll the SCM for changes. Have a single build step that just lists all the files out. Tell Jenkins to : - restrict where that build this project can run so that it'll only ever run on the Windows slave mentioned above. - Source Code Management = Git. ** Specify one repository ** name "origin" ** no refspec ** Branches to build is "*/master" ** Repository browser is "(Auto)" ** no additional behaviours. - Build Triggers = poll SCM ** Schedule = "H/2 * * * *" - Do _not_ "Delete workspace before build starts". - have a single build step that just lists all the files out. Jenkins should detect that it's never built the build before and build it. It'll auto-install git, then use it to grab the source code from the git repository into the Jenkins workspace. That should all work and, in the console output of the build, you'll see the .git folder there plus the contents of the Git repository.Now make and commit a change into the Git repository.After a while, Jenkins should detect the change and re-trigger the build. That'll run on the same Windows slave as before, in the same workspace folder, which has the .git folder left over from the previous build and hence has a clone of the repository that contains all the changes except for the one that was just committed. What I see, in this scenario, is that the git checkout fails - it doesn't pull changes from the git repo so that when it later tries to checkout the latest revision, it can't (as the local .git folder doesn't contain the latest code). (if there's any of the above that needs clarifying, let me know and I'll add more detail) Add Comment This message was sent by Atlass
[JIRA] (JENKINS-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-50393 P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable Change By: Karl Wirth Labels: P4_VERIFY 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-50425) UFT SVN Integration - deleted test from existing svn repository are not detected by discovery job.
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-50425 UFT SVN Integration - deleted test from existing svn repository are not detected by discovery job. Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-03-27 11:03 Labels: octane uft-integration Priority: Major Reporter: Michael Seldin defect #600012 : UFT SVN Integration - deleted test from existing svn repository are not detected by discovery job. Add Comment
[JIRA] (JENKINS-50425) UFT SVN Integration - deleted test from existing svn repository are not detected by discovery job.
Title: Message Title Michael Seldin updated an issue Jenkins / JENKINS-50425 UFT SVN Integration - deleted test from existing svn repository are not detected by discovery job. Change By: Michael Seldin Labels: 5.3.5-beta octane uft-integration 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-50426) New tests added to existing svn scm repository are detedcted by discovery job but not injected to octane (defect #600010 )
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-50426 New tests added to existing svn scm repository are detedcted by discovery job but not injected to octane (defect #600010 ) Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-03-27 11:10 Labels: octane uft-integration 5.3.5-beta Priority: Major Reporter: Michael Seldin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title
Karl Wirth edited a comment on JENKINS-50393
Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Confirm reproduction steps(1) Create a Folder(2) Create Freestyle johb under folder(3) Use recomended workspace naming convention 'jenkins-$\{NODE_NAME}-$\{JOB_NAME}-$\{EXECUTOR_NUMBER}' when setting up Perforce connection.(4) 'Build Now'Error as mentioned above is because the folder is part of the JOB_NAME but in the name it '/' is replaced with '-' but not in the view:{code:java}ERROR: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.Mapping '//jenkins-master-Folder2/FreestyleUnderFolder-1/...' is not under '//jenkins-master-Folder2-FreestyleUnderFolder-1/...'.{code}
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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50237 Re: [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/jenkins/security/whitelisted-classes.txt http://jenkins-ci.org/commit/jenkins/834fa97e7aeb24eb7765e37a34989bf6788062c5 Log: Merge pull request #3372 from oleg-nenashev/stable-2.107-JENKINS-50237-port JENKINS-50237 - Backport: Whitelist org.apache.tools.ant.Location for serialization Compare: https://github.com/jenkinsci/jenkins/compare/5d4a76d28423...834fa97e7aeb 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-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title
Karl Wirth commented on JENKINS-50393
Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Confirm reproduction steps (1) Create a Folder (2) Create Freestyle johb under folder (3) Use recomended workspace naming convention 'jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}' when setting up Perforce connection. (4) 'Build Now' Error as mentioned above is because the folder is part of the JOB_NAME but in the name it is replaced with '-' but not in the view:
ERROR: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//jenkins-master-Folder2/FreestyleUnderFolder-1/...' is not under '//jenkins-master-Folder2-FreestyleUnderFolder-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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50237 Re: [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/jenkins/security/whitelisted-classes.txt http://jenkins-ci.org/commit/jenkins/a277b58adca24068347d952c85288470a09b611c Log: JENKINS-50237 - Whitelist org.apache.tools.ant.Location for serialization (cherry picked from commit 300fbc3715f1f96a67300e22ab2dc3a7f1556746) 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-50386) Job configuration Save/Apply buttons missing
Title: Message Title Tuukka Mustonen commented on JENKINS-50386 Re: Job configuration Save/Apply buttons missing Potentially duplicate of JENKINS-46653 (though the workaround of uninstalling extra JDKs there doesn't work). 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-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title Oleg Nenashev commented on JENKINS-50291 Re: Customize where AsyncPeriodicWork are logged There is no ETA for that in JENKINS-38313. Currently I am working on the redesign of this proposal in order to reduce the scope. Aperiodic Work logging will be likely excluded from the first iteration. No ETA for that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49622) Support Stride
Title: Message Title Tanguy Crusson commented on JENKINS-49622 Re: Support Stride Hi all, Tanguy from the Stride product team. Based on user demand we've decided to build a Jenkins plugin for Stride. You can track the progress in this ticket: https://jira.atlassian.com/browse/STRIDE-1973 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-50381) ECS plugin fails to use label expression
Title: Message Title Dmytro Kryvenko updated JENKINS-50381 Jenkins / JENKINS-50381 ECS plugin fails to use label _expression_ Change By: Dmytro Kryvenko 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-50381) ECS plugin fails to use label expression
Title: Message Title Dmytro Kryvenko started work on JENKINS-50381 Change By: Dmytro Kryvenko 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-50381) ECS plugin fails to use label expression
Title: Message Title Dmytro Kryvenko updated JENKINS-50381 Jenkins / JENKINS-50381 ECS plugin fails to use label _expression_ Change By: Dmytro Kryvenko 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-50424) Testfairy plugin Failed to deserialize response UserRequest
Title: Message Title Oleg Nenashev commented on JENKINS-50424 Re: Testfairy plugin Failed to deserialize response UserRequest Yes, it is clearly a JEP-200 regression in the plugin. And it's a valid one, because JSONObject is sent over Remoting. This type is explicitly blacklisted, it is not recommended to allow it. Stats about TestFairy: 285 installations Last release available in Jenkins UC is 4.2 Last release in the repo in 4.11: https://github.com/jenkinsci/testfairy-plugin . Distribution management is misconfigured there afaict. Not sure what has happened with newer releases (CC Daniel Beck) Plugin POM is generally obsolete as well. A facelift is required in order to build/test it efficiently (e.g. to run Plugin Compat Tester or to have CI on ci.jenkins.io) The plugin could be recovered and fixed, but it would be great to get a response from Gil Megidish before doing 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-50424) Testfairy plugin Failed to deserialize response UserRequest
Title: Message Title Jesse Glick commented on JENKINS-50424 Re: Testfairy plugin Failed to deserialize response UserRequest Generally these issues are fixed very easily by sending a String rather than JSONObject. 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-49392) Violations plugin freezes project settings screen
Title: Message Title Javier Canillas commented on JENKINS-49392 Re: Violations plugin freezes project settings screen Recommendation from David Santos works like a charm. A bugfix over this would be awesome, or at least remove the Violation dependency from the Warnings 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-46940) Build pipeline plugin duplicates static linked jobs in view
Title: Message Title Javier Canillas commented on JENKINS-46940 Re: Build pipeline plugin duplicates static linked jobs in view Anyone has a workaround? Voted. 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-44285) Kubernetes Plugin , Tool Location overwrites not preserved
Title: Message Title Aytunc BEKEN commented on JENKINS-44285 Re: Kubernetes Plugin , Tool Location overwrites not preserved Hi Is there any news on this issue ? I do not know plugin development but if is there anything to help let me know ? 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-49392) Violations plugin freezes project settings screen
Title: Message Title Daniel Beck commented on JENKINS-49392 Re: Violations plugin freezes project settings screen remove the Violation dependency from the Warnings plugin It's optional to support migration. You can install Warnings without installing Violations. The related UI problem is tracked as JENKINS-33843. 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-50424) Testfairy plugin Failed to deserialize response UserRequest
Title: Message Title Oleg Nenashev commented on JENKINS-50424 Re: Testfairy plugin Failed to deserialize response UserRequest Yes, the fix itself should be easy. But there is a significant overhead to recover the plugin and to make it releaseable. We would need a buy-in from maintainers to do it for a plugin in the current state. 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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50237 [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Change By: Oleg Nenashev Labels: 2.107.2-fixed JEP-200 lts-candidate regression 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-50427) Libvirt Slaves Plugin needs updating to 2.x
Title: Message Title Glenn Burkhardt created an issue Jenkins / JENKINS-50427 Libvirt Slaves Plugin needs updating to 2.x Issue Type: Bug Assignee: Philipp Bartsch Components: libvirt-slave-plugin Created: 2018-03-27 12:16 Environment: Jenkins ver. 2.108; libvirt-slave 1.8.5 Priority: Major Reporter: Glenn Burkhardt The libvirt slave plugin was built with a very old version of Jenkins, and it can't support current functionality for slaves. In particular, 'workDir' and 'remoteDir' in the slave configuration are not transferred to the slave during startup (see also [https://issues.jenkins-ci.org/browse/JENKINS-47834|http://example.com).] The JNLPLauncher class that was used to build the plugin in 2015 doesn't contain the "RemotingWorkDirSettings workDirSettings" field, and the VirtualMachineLauncher class defined in the plugin doesn't support the fields required by "slave-agent.jnlp.jelly". Add Comment
[JIRA] (JENKINS-49709) Proxy Config broken in Bitbucket Branch Source Plugin
Title: Message Title Thomas Kalmár commented on JENKINS-49709 Re: Proxy Config broken in Bitbucket Branch Source Plugin Hi Jaco, URI.create(...) does not throw an MalformedURLException. The JavaDoc of the getHttpClient Mehtod states: @param host must be of format: scheme://host:port. e.g. http://localhost:7990 which should be validated on the Configuration page. If you have an invalid host your whole setup is broken. BTW. poor mans solution is entering the scheme://host:port in the proxy exception list :/. If your solution should work you also have to strip the port from the URL. (Pattern ^.?://([^:]) ) 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-50428) Adjust support-core to the now configuratable location for tasks logging
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-50428 Adjust support-core to the now configuratable location for tasks logging Change By: Baptiste Mathus Assignee: Emilio Escobar Baptiste Mathus 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-50428) Adjust support-core to the now configuratable location for tasks logging
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50428 Adjust support-core to the now configuratable location for tasks logging Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-03-27 12:26 Labels: essentials Priority: Critical Reporter: Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50428) Adjust support-core to the now configuratable location for tasks logging
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50428 Adjust support-core to the now configuratable location for tasks logging Change By: Baptiste Mathus Once JENKINS-50291 is merged, we need to adapt https://github.com/jenkinsci/support-core-plugin/blob/16f4358073093ea2e07c28b199723b1f0140e245/src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java#L114 to take the new system property into account. 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-50427) Libvirt Slaves Plugin needs updating to 2.x
Title: Message Title Oleg Nenashev commented on JENKINS-50427 Re: Libvirt Slaves Plugin needs updating to 2.x The related ML thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/w66m_3LTAxs 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte created an issue Jenkins / JENKINS-50429 Shell command are really slower than before Issue Type: Bug Assignee: Unassigned Components: workflow-durable-task-step-plugin Created: 2018-03-27 12:34 Environment: jenkins 2.111, workflow-durable-task-step 2.19 Priority: Minor Reporter: Pascal Laporte We have recently updated our Jenkins installation from 2.101 to 2.111 including every plugin related to pipeline. Since this update every shell «sh» invocation is really slower than before. shell invocation was taking few millisecond before. it is now taking seconds. So job that were taking 1:30 minutes or taking up to 25:00 minutes. We are trying to figure out which plugin is related Add Comment
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50429 Shell command are really slower than before Change By: Oleg Nenashev Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Oleg Nenashev commented on JENKINS-50429 Re: Shell command are really slower than before Could it be related to changes in Cheetah Sam Van Oort? https://jenkins.io/blog/2018/02/22/cheetah/ Pascal Laporte it would be definitely great to have more information about your scripts and use-cases to triage the 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-50189) Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2
Title: Message Title Giuseppe Iannello commented on JENKINS-50189 Re: Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2 Oliver Lockwood is your sh step using returnStdout: true ? In our setup, normal sh steps are working just fine, while those that are configured to returnStdout are failing with that error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50430) Make list items clickable
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-50430 Make list items clickable Issue Type: Improvement Assignee: Andrey Shevtsov Components: mission-control-view-plugin Created: 2018-03-27 12:53 Priority: Minor Reporter: Giuseppe Iannello List items should be clickable and redirecting to the specific build/job/node. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50431) Add stage indication in the job list
Title: Message Title Giuseppe Iannello created an issue Jenkins / JENKINS-50431 Add stage indication in the job list Issue Type: Improvement Assignee: Andrey Shevtsov Components: mission-control-view-plugin Created: 2018-03-27 12:55 Priority: Minor Reporter: Giuseppe Iannello Add a new column to the Build history table containing the current stage in case of pipeline jobs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49211 Re: Build gets stuck on Publish Over CIFS Code changed in jenkins User: Alex Earl Path: src/main/java/jenkins/plugins/publish_over_cifs/CifsBuilderPlugin.java http://jenkins-ci.org/commit/publish-over-cifs-plugin/7fe5315e680c671604272ab62af350b4b3cedb03 Log: Merge pull request #9 from Skosnowich/bugfix/JENKINS-49211 fix empty "CIFS Share" drop down list for build step (JENKINS-49211) Compare: https://github.com/jenkinsci/publish-over-cifs-plugin/compare/802515853dec...7fe5315e680c 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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-50432 Global limit of maximum agents that can be dynamically allocated in a docker swarm Issue Type: Bug Assignee: surya gaddipati Components: docker-swarm-plugin Created: 2018-03-27 13:08 Environment: Docker: 17.04-ce Linux: OpenSUSE Jenkins: 2.111 Docker Swarm Plugin: 1.5 Labels: docker swarm Priority: Major Reporter: Steve Todorov We have been using this plugin to dynamically provision our agents in a docker container for our builds. Everything has been working quite well so far! However, the is one small issue we're hitting - you can have unlimited jobs which request agents. This is an awesome feature, but our bare-metal cloud is definitely not unlimited so we eventually hit the limit to the machines every now and then. Would it be possible to have a field in which you can set a global limit for the maximum amount of containers the swarm can handle? And when you get over the limit the plugin would wait until the running containers are below that number.
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Glenn Burkhardt commented on JENKINS-47834 Re: Add the support for Remoting work dir configuration of JNLP Launcher See also: https://issues.jenkins-ci.org/browse/JENKINS-50427 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47834 Add the support for Remoting work dir configuration of JNLP Launcher Change By: Oleg Nenashev Component/s: libvirt-slave-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-42144) Publish HP test result Failed with java.lang.NumberFormatException
Title: Message Title Weston Dyer commented on JENKINS-42144 Re: Publish HP test result Failed with java.lang.NumberFormatException Full stack sent. Jenkins, Controller, and LG are on the same Win 7 node. 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-50265) TasksScannerPublisher : multiple reports
Title: Message Title benoit guerin updated JENKINS-50265 Jenkins / JENKINS-50265 TasksScannerPublisher : multiple reports Change By: benoit guerin 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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-50432 Global limit of maximum agents that can be dynamically allocated in a docker swarm Change By: Steve Todorov Issue Type: Bug Improvement 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-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Baptiste Mathus stopped work on JENKINS-49406 Change By: Baptiste Mathus Status: In Progress 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-49805) Prototype error telemetry logging with a Java Util Logger configuration
Title: Message Title Baptiste Mathus started work on JENKINS-49805 Change By: Baptiste Mathus 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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title surya gaddipati updated an issue Jenkins / JENKINS-50432 Global limit of maximum agents that can be dynamically allocated in a docker swarm Change By: surya gaddipati Attachment: screenshot-1.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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title surya gaddipati edited a comment on JENKINS-50432 Re: Global limit of maximum agents that can be dynamically allocated in a docker swarm Hi Steve, You can set limits and reservations per label ( see attached: screenshot). We do this to avoid scheduling unlimited number for containers. Let me know if that solves the problem you are facing. 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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title surya gaddipati commented on JENKINS-50432 Re: Global limit of maximum agents that can be dynamically allocated in a docker swarm Hi Steve, You can set limits and reservations per label ( see attached: screenshot). We do this to avoid scheduling unlimited number for containers. 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-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Issue Type: Task Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2018-03-27 13:56 Priority: Minor Reporter: Sorin Sbarnea It seems that is not possible to load a shared library from a CRs gerrit branch, mostly because current GitSCMSource plugin fails to see gerrit branches, and tuning the rawRefSpecs parameter seems to have no effect on it. library identifier: 'temp-lib@master', retriever: modernSCM( [$class: 'GitSCMSource', remote: 'https://review.gerrithub.io/rhos-infra/foobar', excludes: '', includes: '*', rawRefSpecs: '+refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/remotes/origin/tags/* +refs/changes/*:refs/remotes/changes/*' ]) Example of using git ls-remote on gerrit repository: git ls-remote git ls-remote https://review.gerrithub.io/rhos-infra/foobar 558aca4bf8d2eb357caa72292abb94b3b87cc41f HEAD a6b8fced01ebdd09930ff75768d3c437567e2f81 refs/changes/78/386678/1 ad71ed9c8a225eb11531322ef928b89ca74eba5e refs/changes/82/386682/1 73969f31bbc57a53b903b3c16ade1b991cbf11f7 refs/changes/82/386682/2 cd404f64f7840bf2d92a830186159c809ff2450e refs/changes/84/386684/1 f05cf74695e6c5731ccbeb5d98de113031ff0c70 refs/changes/84/386684/2 65e65cae35fc55779db0afe56e9bd28554e5c074 refs/changes/85/386685/1 c96845ab149d8f1908f46ad279088e4fb1a77dae refs/changes/85/386685/2 89fbd1f054b2d1f3d0c417235b0e37299a36c078 refs/
[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally
Title: Message Title Neil Sleightholm commented on JENKINS-50287 Re: Make as-it-is checkout only files initally In my case this has introduced a problem, I want a clean workspace to be updated to infinity and then my build process will remove some files and I want this to be the "as-it-is" state. This defect has now broken this behaviour - can I request that this change is regressed? 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-50287) Make as-it-is checkout only files initally
Title: Message Title Neil Sleightholm reopened an issue Jenkins / JENKINS-50287 Make as-it-is checkout only files initally Change By: Neil Sleightholm Resolution: Done 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-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Component/s: git-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-50433) unable to load shared library from gerrit pull request branch
Title: Message Title
Sorin Sbarnea updated an issue
Jenkins / JENKINS-50433
unable to load shared library from gerrit pull request branch
Change By:
Sorin Sbarnea
It seems that is not possible to load a shared library from a CRs gerrit branch, mostly because current *GitSCMSource* plugin fails to see gerrit branches, and tuning the rawRefSpecs parameter seems to have no effect on it. {code:java}library identifier: 'temp-lib@master', retriever: modernSCM([$class: 'GitSCMSource',remote: 'https://review.gerrithub.io/rhos-infra/foobar',excludes: '',includes: '*',rawRefSpecs: '+refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/remotes/origin/tags/* +refs/changes/*:refs/remotes/changes/*']){code}Example of using git ls-remote on gerrit repository: {code:java}git ls-remote git ls-remote https://review.gerrithub.io/rhos-infra/foobar558aca4bf8d2eb357caa72292abb94b3b87cc41f HEADa6b8fced01ebdd09930ff75768d3c437567e2f81 refs/changes/78/386678/1ad71ed9c8a225eb11531322ef928b89ca74eba5e refs/changes/82/386682/173969f31bbc57a53b903b3c16ade1b991cbf11f7 refs/changes/82/386682/2cd404f64f7840bf2d92a830186159c809ff2450e refs/changes/84/386684/1f05cf74695e6c5731ccbeb5d98de113031ff0c70 refs/changes/84/386684/265e65cae35fc55779db0afe56e9bd28554e5c074 refs/changes/85/386685/1c96845ab149d8f1908f46ad279088e4fb1a77dae refs/changes/85/386685/289fbd1f054b2d1f3d0c417235b0e37299a36c078 refs/changes/85/386685/3558aca4bf8d2eb357caa72292abb94b3b87cc41f refs/heads/master{code}As you can see, ls-remote is able to detect gerrit branches without problems. Still, I we check the console log of the job, we will find that Jenkins is trying to perform a "git ls-remote -t -h ..." which is filtering out the remote branches that we are interested about.I was not able to find any option to tell it not to do this.
Add Comment
[JIRA] (JENKINS-50189) Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2
Title: Message Title Oliver Lockwood commented on JENKINS-50189 Re: Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2 Giuseppe Iannello no, my script was exactly as I had it above, without specifying `returnStdout`. I haven't tested with plugin versions 1.3.3 or 1.4, however, so the nature of the bug may have changed. Carlos Sanchez have you made any headway diagnosing 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-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title Heiko Nardmann created an issue Jenkins / JENKINS-50434 Misbehaviour of feature: Pin the workspace to the build host Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 2018-03-27 14:13 Environment: Jenkins v2.62, p4-plugin v1.8.4, freestyle jobs Priority: Major Reporter: Heiko Nardmann I'm using a Manual (custom view) setup for my freestyle jobs so far (see screenshot of an example job). I have problems with the feature Pin the workspace to the build host: when looking at the workspaces I often see that workspaces get the wrong host set. This leads to synching problems and in the end typically to (C++) linker errors. I've created a Python script report_p4_workspaces_with_wrong_host_assignment.py for this. It gives me e.g.: jenkins_frinavci_FRI00040598D_spine2d.w64-vc14-qt56x.debug-coverage: FRIjenkins04 jenkins_frinavci_FRI00040598D_stp-makospine.w64-vc14-qt5.9.4-release: FRNAVDEV01 jenkins_frinavci_FRI00903207D_shared-communications-sfb_unit.w64-vc14-qt56x: FRNAVDEV01 jenkins_frinavci_FRI00903207D_shared-render_engine.w64-vc14-qt56x.debug-coverage: FRINAVDEV01 jenkins_frinavci_frijenkins04_ce.win64-vc14-qt56: FRNAVDEV01 jenkins_frinavci_frijenkins04_shared-report_engine.w64-vc14-qt56x: FRNAVDEV01 jenkins_frinavci_frijenkins04_Tools-f8scope.w64-vc14-qt56x: FRNAVDEV01 jenkins_frinavci_frijenkins06_Linux_Jobs-shared-threading-testframe.Linux: frijenkins11 jenkins_frinavci_frijenkins06_Linux_Jobs-spine2d.linux64-gcc-qt56x: frijenkins11 jenkins_frinavci_frijenkins08_fess.w64-vc14-qt56x: FRNAVDEV01 jenkins_frinavci_frijenkins08_plugins-import.w64-vc14-qt
[JIRA] (JENKINS-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title Heiko Nardmann updated an issue Jenkins / JENKINS-50434 Misbehaviour of feature: Pin the workspace to the build host Change By: Heiko Nardmann Attachment: Job-SCM-Config.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-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Environment: git-3.7.0jenkins-2.89 (LTS) 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Sorin Sbarnea commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Few minutes ago I raised https://issues.jenkins-ci.org/browse/JENKINS-50433 which states that there is no way to tell git plugin to pull gerrit branches because there is no way to convince it to remove "-h" from "git ls-remote". Any tricks/workarounds to make this work? 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-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title Heiko Nardmann updated an issue Jenkins / JENKINS-50434 Misbehaviour of feature: Pin the workspace to the build host Change By: Heiko Nardmann Attachment: report_p4_workspaces_with_wrong_host_assignment.py 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.
