[JIRA] (JENKINS-27581) JaCoCo Coverage Trend not displayed
Title: Message Title hu david updated JENKINS-27581 Jenkins / JENKINS-27581 JaCoCo Coverage Trend not displayed Change By: hu david Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27581) JaCoCo Coverage Trend not displayed
Title: Message Title hu david commented on JENKINS-27581 Re: JaCoCo Coverage Trend not displayed yum install dejavu-serif-fonts & restart tomcat then the problem resolvced。 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57165) Jenkins job fails on Agent with error java.lang.OutOfMemoryError: Java heap space
Title: Message Title Nikita Porwal updated an issue Jenkins / JENKINS-57165 Jenkins job fails on Agent with error java.lang.OutOfMemoryError: Java heap space Change By: Nikita Porwal Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title
Zeki Yureti edited a comment on JENKINS-56676
Re: Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
I've done some more testing, and found that 5.7 works ok (runs, but does not find all test instances in the test set) when running an ALM *Test Set* without spaces, but not an ALM *Test Instance* without spaces.When running a test instance, it gives the error "Specified test not found on ALM, please check your test path". I used the path:{noformat}Root\Tests\MFJenkins\[1]InstantPass{noformat}That works with plugin version 5.6.2, but with version 5.7 gives the following (also, the output does not use usual ALM terminology like Test Set / Instance / Folder) {noformat}"Started..."Timeout is set to: -1Run mode is set to: RUN_LOCALtestName: [1]InstantPasstestSuiteName: MFJenkinstsPath: Root\TestsStarting test set executionTest set name: MFJenkins, Test set id: 4901Number of tests in set: 0Error: Specified test not found on ALM, please check your test path.Run status: Job failed, total tests: 0, succeeded: 0, failures: 0, errors: 0Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sFinished: FAILURE{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title Zeki Yureti commented on JENKINS-56676 Re: Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException I've done some more testing, and found that 5.7 works ok (runs, but does not find all test instances in the test set) when running an ALM Test Set without spaces, but not an ALM Test Instance without spaces. When running a test instance, it gives the error "Specified test not found on ALM, please check your test path". I used the path: Root\Tests\MFJenkins\[1]InstantPass That works with plugin version 5.6.2, but with version 5.7 gives the following (also, the output does not use usual ALM terminology like Test Set / Instance / Folder) "Started..." Timeout is set to: -1 Run mode is set to: RUN_LOCAL testName: [1]InstantPass testSuiteName: MFJenkins tsPath: Root\Tests Starting test set execution Test set name: MFJenkins, Test set id: 4901 Number of tests in set: 0 Error: Specified test not found on ALM, please check your test path. Run status: Job failed, total tests: 0, succeeded: 0, failures: 0, errors: 0 Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57190) Getting error in presend script section in POST action
Title: Message Title
Shreyas Arjun created an issue
Jenkins / JENKINS-57190
Getting error in presend script section in POST action
Issue Type:
Task
Assignee:
David van Laatum
Components:
email-ext-plugin
Created:
2019-04-26 02:32
Environment:
Local
Labels:
presendScript post-actions declarative jenkinspipeline
Priority:
Minor
Reporter:
Shreyas Arjun
My post section code as follows post { always { emailext attachmentsPattern: "Serenity_Test_Results_${env.BUILD_NUMBER}.zip" , presendScript: "def reportPath=${workspace}.child(\"target/serenity-summary.html\")msg.setContents(reportPath.readToString(), \"text/html\")", body: "${currentBuild.currentResult}: Job ${env.JOB_NAME} build ${env.BUILD_NUMBER}", subject: "Testing: Jenkins Job Results - Build # ${env.BUILD_NUMBER}", mimeType: 'text/html', to: "x...@abc.com" } } I am getting below error [Pipeline] { (Declarative: Post Actions) [Pipeline] emailext groovy.lang.MissingPropertyException: No such property: jenkins for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264) at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty$0.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Gavin Mogan resolved as Fixed Jenkins / JENKINS-56773 High master CPU usage introduced by Blue Ocean 1.14.0 Change By: Gavin Mogan Status: Open Resolved Resolution: Fixed Released As: 1.15.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46193) New test failures are reported as both new test failures and existing test failures.
Title: Message Title Gavin Mogan updated JENKINS-46193 Jenkins / JENKINS-46193 New test failures are reported as both new test failures and existing test failures. Change By: Gavin Mogan Status: Fixed but Unreleased Resolved Released As: 1.15.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-56773 High master CPU usage introduced by Blue Ocean 1.14.0 Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Gavin Mogan resolved as Fixed Jenkins / JENKINS-56672 Artifacts tab in blue ocean does not have link to view an artifact Change By: Gavin Mogan Status: In Progress Resolved Resolution: Fixed Released As: 1.15.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46914) Better indicate implied permissions in the checkbox grid
Title: Message Title Daniel Beck started work on JENKINS-46914 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46914) Better indicate implied permissions in the checkbox grid
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-46914 Better indicate implied permissions in the checkbox grid Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 After having our Jenkins instance go down 4 times today we rolled back to 2.150.3 and immediately dropped from pegging the 4GB heap limit we have set to comfortably hovering around 2GB. I've collected several thread dumps over the last couple of weeks and will start trying to track down where the issue is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57189) Sauce Labs Test Publisher cannot find build
Title: Message Title Aaron Quan created an issue Jenkins / JENKINS-57189 Sauce Labs Test Publisher cannot find build Issue Type: Bug Assignee: Yeh Fang Components: sauce-ondemand-plugin Created: 2019-04-25 21:48 Environment: Sauce OnDemand Plugin v1.184 Jenkins ver. 2.164.2 Priority: Critical Reporter: Aaron Quan We recently upgraded our Jenkins and Sauce OnDemand plugin and noticed that we are getting issues when we have the Sauce Labs Test Publisher added in our post build steps. In the logs, it looks like its trying to find the build, but the build name is incorrect. We set the build name to be something like "foo [build number]" (eg. foo [123]) From what we see in the logs, the name its looking for is jenkins-foo-123, and i guess this is because the name gets sanitized in SauceEnvironmentUtil.getSanitizedBuildNumber(). Is there something changed in how we are suppose to set the build information in the DesiredCapabilities? We have to disable all our jobs from using the publisher now because it fails our jenkins job.
[JIRA] (JENKINS-51208) Execution time of parallel steps displayed as max time among all steps in block
Title: Message Title Damien Jiang edited a comment on JENKINS-51208 Re: Execution time of parallel steps displayed as max time among all steps in block Bump; looks like there are no plans to fix this problem? It makes monitoring / optimizing pipelines much more annoying.Btw, before the parallel block is completely finished, each parallelized step _does_ report the right runtime! It's only update updated to the "runtime of the whole parallel block" at the end of the block. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51208) Execution time of parallel steps displayed as max time among all steps in block
Title: Message Title Damien Jiang commented on JENKINS-51208 Re: Execution time of parallel steps displayed as max time among all steps in block Bump; looks like there are no plans to fix this problem? It makes monitoring / optimizing pipelines much more annoying. Btw, before the parallel block is completely finished, each parallelized step does report the right runtime! It's only update to the "runtime of the whole parallel block" at the end of the block. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick updated JENKINS-54186 Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48865) JNLP Agents/Slaves Disconnecting Unpredictably
Title: Message Title Jeff Thompson commented on JENKINS-48865 Re: JNLP Agents/Slaves Disconnecting Unpredictably Yes, disconnect issues can be very difficult to track down. They're usually due to something closing the connection at the TCP layer. Or one end being overloaded and unable to maintain its side. I think we should re-close this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick started work on JENKINS-54186 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick stopped work on JENKINS-54186 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Jesse Glick Assignee: Sam Van Oort Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54046) GitHub branch souce plugin fails to move temporary files
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-54046 GitHub branch souce plugin fails to move temporary files Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Liam Newman updated JENKINS-44715 Jenkins / JENKINS-44715 Pipeline plugin won't get updated PR github title Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52397) Org Scan blows up when repository has no tags
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-52397 Org Scan blows up when repository has no tags Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50323) PullRequestSCMHead and PullRequestSCMRevision external use
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-50323 PullRequestSCMHead and PullRequestSCMRevision external use Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-50777 Exported API for SCMRevisionAction & SCMSource Change By: Liam Newman Status: Resolved Closed Assignee: Jesse Glick Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47775) Optimized event processing of pull requests does not detect closed PRs as closed
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-47775 Optimized event processing of pull requests does not detect closed PRs as closed Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-50777 Exported API for SCMRevisionAction & SCMSource Change By: Jesse Glick Assignee: Mark Waite Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46967) Upgrade parent POM and upgrade the baseline for github-branch-source
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-46967 Upgrade parent POM and upgrade the baseline for github-branch-source Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46364) GitHub Branch Source Plugin can't create status if credential restricted by spec
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-46364 GitHub Branch Source Plugin can't create status if credential restricted by spec Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46203) Add LICENSE file to GitHub repo of plugin
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-46203 Add LICENSE file to GitHub repo of plugin Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46449) NPE on build PR head revision
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-46449 NPE on build PR head revision Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48865) JNLP Agents/Slaves Disconnecting Unpredictably
Title: Message Title Alfred Wong commented on JENKINS-48865 Re: JNLP Agents/Slaves Disconnecting Unpredictably Sure, I can create a new JIRA, I think the original problem I got was the disconnect and it is still happening a few times a day. Our vendor OpenShift and our container team has been spending the last few weeks investigating the issue. I will put the re-connection issue in another JIRA. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin edited a comment on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Ok, so here an update. If that patch sticks and will not be backed out again, we will land the Firefox patch for Firefox 69 on May 14th or 15th. Which means it will ride the trains through beta, and will be finally be released on Sep 3rd. If by that time there are still users who running a Jenkins LTS release earlier than 2.164.3, they will have to use Firefox 68 ESR. That ESR version will be maintained for another year, and will never have this patch included. Details see [https://bugzilla.mozilla.org/show_bug.cgi?id=1370630#c41] and following. Thanks a lot again for the patch! It will unblock us from landing several features which are all blocked by this particular issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Ok, so here an update. If that patch sticks and will not be backed out again, we will land the Firefox patch for Firefox 69 on May 14th or 15th. Which means it will ride the trains through beta, and will be finally be released on Sep 3rd. If by that time there are still users who running a Jenkins LTS release earlier than 2.164.3, they will have to use Firefox 68 ESR. That ESR version will be maintained for another year, and will never have this patch included. Details see https://bugzilla.mozilla.org/show_bug.cgi?id=1370630#c41 and following. Thanks a lot again for the patch! It will unblock us from landing several features which are all blocked by this particular issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56560) Slave logs full of remoting error: "unable to read a command"
Title: Message Title Jeff Thompson commented on JENKINS-56560 Re: Slave logs full of remoting error: "unable to read a command" ProxyOutputStream should be loadable. Check that your agent (slave) jar files are up-to-date and not corrupted or mismanaged. Double-check your Java versions on master and agent. They need to be consistent. Here are some earlier issues similar descriptions. The solutions and discussion there might be relevant for you. JENKINS-4656, JENKINS-5149, JENKINS-29405 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jeff Thompson commented on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU That's an odd one. Nothing obvious comes to mind. On my system, I see one instance of "0 scheduled tasks to process" occur per second. That seems like a reasonable rate and shouldn't impact system load significantly. Can you check your log messages to verify the rate and provide more information about what the log messages are showing? How fast is that check occurring? I'm not entirely sure what your VisualVM images are showing. They seem to be showing that the thread is spending a fair bit of time waiting on the `select()` but not that it's spending a lot of CPU time. More information would certainly be needed to diagnose any issues here. Unfortunately, I don't have any additional specific requests for info or ideas what would be useful. Maybe you could collect more information about what the system and Jenkins are doing and try to correlate that with CPU usage. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44892) Ability to override reflective metadata in DescribableModel
Title: Message Title Devin Nusbaum updated JENKINS-44892 The new CustomDescribableModel API was just released in version 1.18 of Structs. Jenkins / JENKINS-44892 Ability to override reflective metadata in DescribableModel Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: structs 1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22931) Colorize "Disabled" differently from "Not Built"
Title: Message Title Daniel Beck commented on JENKINS-22931 Re: Colorize "Disabled" differently from "Not Built" Alternative PR: https://github.com/jenkinsci/jenkins/pull/3996 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22931) Colorize "Disabled" differently from "Not Built"
Title: Message Title Daniel Beck started work on JENKINS-22931 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57010) Build agent offline with "FATAL: java.nio.channels.ClosedChannelException"
Title: Message Title Jeff Thompson commented on JENKINS-57010 Re: Build agent offline with "FATAL: java.nio.channels.ClosedChannelException" Ewelina Wilkosz, does it commonly fail at that some point, with `EnvironmentVariablesNodeLoader`? Or something similar? Generally a `ClosedChannelException` is caused by system, network, or environmental issues. Something outside the agent / remoting connection causes the TCP connection to drop. The messages in Jenkins indicate that has happened but do not have any information about the external cause of the disconnection. A heavily loaded master or other resources can cause network connections to drop. I recommend investigating whether the failures share any common characteristics, including stack trace, system type, load, or anything else. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57188) EC2 fleet machines fail to spin up.
Title: Message Title Nick Spor created an issue Jenkins / JENKINS-57188 EC2 fleet machines fail to spin up. Issue Type: Bug Assignee: Chad Schmutzer Components: ec2-fleet-plugin Created: 2019-04-25 17:22 Environment: Jenkins ver. 2.150.3 Priority: Major Reporter: Nick Spor After 2 retries (i have it set to 10) I consistently get this failure when a slave attempts to start. After this error pops up, i am able to manually launch the slave. I have connection timeout set to 180, seconds to wait in between set to 120. Both ssh and fleet plugin are at the latest available. This is a blocker for us as the ec2 fleet plugin is required to run our more expensive builds ERROR: null java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at hudson.plugins.sshslaves.SSHLauncher Add Comment
[JIRA] (JENKINS-57185) "Execute shell" configure dialog hangs on changes
Title: Message Title Daniel Mish edited a comment on JENKINS-57185 Re: "Execute shell" configure dialog hangs on changes It appears that buttons on the configuration page also have this issue, not isolated to the " Build " section only. The General Description multi-line text box does not exhibit this issue, but any multi-line text box in the build section does. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57185) "Execute shell" configure dialog hangs on changes
Title: Message Title Daniel Mish commented on JENKINS-57185 Re: "Execute shell" configure dialog hangs on changes It appears that buttons on the configuration also have this issue, not isolated to the Build section only. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56955) Uninstalling Blueocean Plugin 1.4.0 plugin doesnt resolve dependency errors
Title: Message Title Gavin Mogan closed an issue as Fixed Jenkins / JENKINS-56955 Uninstalling Blueocean Plugin 1.4.0 plugin doesnt resolve dependency errors Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48466) Provide JUnit 5 support for JenkinsRule
Title: Message Title Ulli Hafner commented on JENKINS-48466 Re: Provide JUnit 5 support for JenkinsRule Has someone the spare time to provide these ideas as a PR for the test harness? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48431) Pipeline script from SCM should support build parameters using Lightweight checkout
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48431 Pipeline script from SCM should support build parameters using Lightweight checkout Change By: Jesse Glick Component/s: scm-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-42971 Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48431) Pipeline script from SCM should support build parameters using Lightweight checkout
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48431 Pipeline script from SCM should support build parameters using Lightweight checkout Change By: Jesse Glick Component/s: workflow-cps-plugin Component/s: pipeline Component/s: scm-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Jesse Glick commented on JENKINS-57085 Re: Stack Traces with complex file names cannot be deserialized by XStream Solved with test in workflow-cps-global-lib, but manually confirmed that the fix also corrects stack traces for the original Declarative example. (I did not bother to go through the full reproduction case involving Blue Ocean.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Jesse Glick commented on JENKINS-57085 Re: Stack Traces with complex file names cannot be deserialized by XStream Solved with test in workflow-cps-global-lib, but manually confirmed that the fix also corrects stack traces for the original Declarative example. (I did not bother to go through the full reproduction case involving Blue Ocean.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Jesse Glick updated JENKINS-57085 Jenkins / JENKINS-57085 Stack Traces with complex file names cannot be deserialized by XStream Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31838) Virtual thread dump uses phony filenames
Title: Message Title Jesse Glick commented on JENKINS-31838 Re: Virtual thread dump uses phony filenames As per JENKINS-57085, any file name chosen must be without path. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Oleg Nenashev updated JENKINS-57096 The target Jenkins release is 2.175, LTS backporting is not clear for packaging. CC Oliver Gondža Jenkins / JENKINS-57096 The latest debian installers 2.164+ do not work with java 11. Change By: Oleg Nenashev Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56403) Renaming jenkins agents persists previously named agent on restart
Title: Message Title Oleg Nenashev updated JENKINS-56403 Jenkins / JENKINS-56403 Renaming jenkins agents persists previously named agent on restart Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: 2.174 (tentative) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57185) "Execute shell" configure dialog hangs on changes
Title: Message Title Daniel Mish updated an issue Jenkins / JENKINS-57185 "Execute shell" configure dialog hangs on changes Change By: Daniel Mish When editing a configuration build step, clicking in the "Execute shell" command text box, clicking the "Advanced" button or selecting an option from "Add build step" causes the screen to hang for up to two minutes. Editing may resume normally after this, however, if the text box looses focus the hang occurs again when focus returns to the text box. This only occurs in the "Execute shell" text box. This appears to be an issue with buttons and multi-line text boxes in the "Build" configuration as I have been able to replicate with the "Invoke top-level Maven targets", but only when it is in multi-line mode. I am only seeing this issue in the "Build" section. I am able to access Jenkins from another tab or session in the same browser while the hang is occurring.I have cleared cookies and cache for the site and restarted the Jenkins instance . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57187) Graphs issue with Robot Framework plugin version 1.6.5 in Jenkins ver. 2.164.2
Title: Message Title Kamlesh Gupta created an issue Jenkins / JENKINS-57187 Graphs issue with Robot Framework plugin version 1.6.5 in Jenkins ver. 2.164.2 Issue Type: Bug Assignee: jpiironen Components: robot-plugin Created: 2019-04-25 15:31 Labels: Robot-Framework-plugin-version-1.6.5 Priority: Critical Reporter: Kamlesh Gupta Hi team, I am using Robot Framework plugin version 1.6.5 with Jenkins 2.164.2. its working fine but the issue is I am not getting graphs graphs image is broken and throwing error. A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NoClassDefFoundError: com/mercury/ftjadin/hooks/interfaces/EventListenerListHookQTJA at javax.swing.event.EventListenerList.add(EventListenerList.java:205) at org.jfree.data.general.AbstractDataset.addChangeListener(AbstractDataset.java:126) at org.jfree.chart.plot.CategoryPlot.(CategoryPlot.java:458) at org.jfree.chart.ChartFactory.createStackedAreaChart(ChartFactory.java:1121) at hudson.plugins.robot.graph.RobotGraph.createGraph(RobotGraph.java:103)
[JIRA] (JENKINS-56971) Images for Test Case trends is broken and generate exception
Title: Message Title Kamlesh Gupta edited a comment on JENKINS-56971 Re: Images for Test Case trends is broken and generate exception I am also getting same issue. non of the graphs are generating and showing same error. I am using [Jenkins ver. 2.164.2|https://jenkins.io/] and [Robot Framework plugin|http://wiki.jenkins-ci.org/display/JENKINS/Robot+Framework+Plugin] version 1.6.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56971) Images for Test Case trends is broken and generate exception
Title: Message Title Kamlesh Gupta commented on JENKINS-56971 Re: Images for Test Case trends is broken and generate exception I am also getting same issue. non of the graphs are generating and showing same error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57186) New View href does not include "${rootURL}/"
Title: Message Title
Napoleon BlownApart created an issue
Jenkins / JENKINS-57186
New View href does not include "${rootURL}/"
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-04-25 15:12
Environment:
Jenkins 2.164.2
Labels:
jenkins
Priority:
Minor
Reporter:
Napoleon BlownApart
The href of the "New View" link in the left panel is constructed differently from the other links. The sidepanel2.jelly file seems to be missing ${rootURL}/. I've only noticed this issue because our Jenkins server is setup behind a VPN & SSH, and we use two domain name variants to access Jenkins depending on whether the user is in the lab (thus using "jenkins.int") or outside the lab (thus using "jenkins.vpn"). The consequence of this is that when an external user accesses the Jenkins server via VPN/SSH, the "New View" link points to "jenkins.int/newView" instead of "jenkins.vpn/newView". This means that external users get a 404 error (Server not found) and need to manually correct the url. (Minor/trivial bug.)
[JIRA] (JENKINS-42836) Build parameter not expanded in script path
Title: Message Title Fabian Holler edited a comment on JENKINS-42836 Re: Build parameter not expanded in script path It works only when 'lightweight checkout' is disabled. There is the ticket https://issues.jenkins-ci.org/browse/JENKINS-42971 for the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title
Fabian Holler edited a comment on JENKINS-42971
Re: Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
We have I can confirm that it works if "lightweight checkout" is disabled for git SCM with 'Workflow: Job' 2.32 installed with and Jenkins 2.173 and it does not work . It behaves exactly like in Should the ticket description with GIT as SCM. be closed? ("lightweight checkout" is disabled)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title Fabian Holler updated an issue Jenkins / JENKINS-42971 Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts Change By: Fabian Holler Comment: I can confirm that it works if "lightweight checkout" is disabled for git SCM with 'Workflow: Job' 2.32 and Jenkins 2.173.Should the ticket be closed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42836) Build parameter not expanded in script path
Title: Message Title Fabian Holler commented on JENKINS-42836 Re: Build parameter not expanded in script path There is the ticket https://issues.jenkins-ci.org/browse/JENKINS-42971 for the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title
Fabian Holler commented on JENKINS-42971
Re: Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
We have 'Workflow: Job' 2.32 installed with Jenkins 2.173 and it does not work. It behaves exactly like in the ticket description with GIT as SCM. ("lightweight checkout" is disabled)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title steve nolen commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly we are also seeing this happen randomly among multibranch pipeline builds as well. For branches where we make use of the build history, it can be extremely frustrating to restore/recover. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57185) "Execute shell" configure dialog hangs on changes
Title: Message Title Daniel Mish created an issue Jenkins / JENKINS-57185 "Execute shell" configure dialog hangs on changes Issue Type: Bug Assignee: Unassigned Attachments: JenkinsThreadDump-20190425.log Components: core Created: 2019-04-25 14:58 Environment: Jenkins ver. 2.164.2 Plugins: Apache HttpComponents Client 4.x API Plugin 4.5.5-3.0 Bitbucket Plugin 1.1.8 bouncycastle API Plugin 2.17 Branch API Plugin 2.4.0 Clover plugin 4.10.0 Command Agent Launcher Plugin 1.3 Credentials Plugin 2.1.18 Display URL API 2.3.1 Durable Task Plugin 1.29 External Monitor Job Type Plugin 1.7 FitNesse plugin 1.28 Folders Plugin 6.8 Git client 2.7.6 Git plugin 3.9.3 Gradle Plugin 1.31 Green Balls 1.15 Groovy 2.2 Jackson 2 API Plugin 2.9.8 Javadoc Plugin 1.5 _javascript_ GUI Lib: ACE Editor bundle plugin 1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin 1.2.1 JDK Tool Plugin 1.2 Jira Issue Updater 1.18 JIRA plugin 3.0.6 jQuery plugin 1.12.4-0 JSch dependency plugin 0.1.55 JUnit Attachments Plugin 1.5 JUnit Plugin 1.27 LDAP Plugin 1.20 Mailer Plugin 1.23 Matrix Authorization Strategy Plugin 2.3 Matrix Project Plugin 1.14 Maven Integration plugin 3.2 Mercurial 2.5 OWASP Markup Formatter Plugin 1.5 PAM Authentication plugin 1.5 Pipeline: API 2.33 Pipeline: Basic Steps 2.15 Pipeline: Groovy 2.65 Pipeline: Job 2.32 Pipeline: Nodes and Processes 2.30 Pipeline: SCM Step 2.7 Pipeline: Step API 2.19 Pipeline: Supporting APIs 3.2 Run Condition Plugin 1.2 Sauce OnDemand plugin 1.184 SCM API Plugin 2.4.1 Script Security 1.56 SSH Credentials 1.15 Structs Plugin 1.17 Throttle Concurrent Builds Plug-in 2.0.1 Token Macro Plugin 2.7 WMI Windows Agents Plugin 1.4 OS: GNU/Linux kernel 3.10.0-957.5.1.el7.x86_64 Client OS: Mac OSX 10.14.4 Java: 1.8.0_91-b14 Browser: Chrome 73.0.3683.103, 64 bit Labels: configuration jenkins Priority:
[JIRA] (JENKINS-27494) Support for PHPUnit 4.* reports
Title: Message Title Nikolas Falco updated JENKINS-27494 Jenkins / JENKINS-27494 Support for PHPUnit 4.* reports Change By: Nikolas Falco Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27494) Support for PHPUnit 4.* reports
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-27494 Support for PHPUnit 4.* reports Change By: Nikolas Falco Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title
Jesse Glick commented on JENKINS-57085
Re: Stack Traces with complex file names cannot be deserialized by XStream
For SourceUnit.name to have this form seems normal:
/**
* Initializes the SourceUnit from the specified URL.
*/
public SourceUnit(URL source, CompilerConfiguration configuration, GroovyClassLoader loader, ErrorCollector er) {
this(source.toExternalForm(), new URLReaderSource(source, configuration), configuration, loader, er);
}
CpsTransformer.makeBuilder then compiles it into a runtime construction of a MethodLocation with a URL as its fileName, from which later a StackTraceElement would be constructed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57184) Kubernetes Plugin inversely applies NodeSelector
Title: Message Title
Carlos Sanchez edited a comment on JENKINS-57184
Re: Kubernetes Plugin inversely applies NodeSelector
I can't reproduce, the pod is created with this yaml which is correct {code}apiVersion: v1kind: Podmetadata: creationTimestamp: "2019-04-25T14:42:23Z" labels:jenkins: slavejenkins/node-selector-test: "true" name: node-selector-test-59d36 namespace: jx...spec:... nodeSelector:jenkins-slave: "true" priority: 0 restartPolicy: Never schedulerName: default-scheduler securityContext: {} serviceAccount: default serviceAccountName: default terminationGracePeriodSeconds: 30 tolerations: - effect: NoExecutekey: node.kubernetes.io/not-readyoperator: ExiststolerationSeconds: 300 - effect: NoExecutekey: node.kubernetes.io/unreachableoperator: ExiststolerationSeconds: 300status: conditions: - lastProbeTime: nulllastTransitionTime: "2019-04-25T14:42:23Z"message: '0/1 nodes are available: 1 node(s) didn''t match node selector.'reason: Unschedulablestatus: "False"type: PodScheduled phase: Pending qosClass: BestEffort{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57184) Kubernetes Plugin inversely applies NodeSelector
Title: Message Title
Carlos Sanchez commented on JENKINS-57184
Re: Kubernetes Plugin inversely applies NodeSelector
I can't reproduce, the pod is created with this yaml
apiVersion: v1
kind: Pod
metadata:
creationTimestamp: "2019-04-25T14:42:23Z"
labels:
jenkins: slave
jenkins/node-selector-test: "true"
name: node-selector-test-59d36
namespace: jx
...
spec:
...
nodeSelector:
jenkins-slave: "true"
priority: 0
restartPolicy: Never
schedulerName: default-scheduler
securityContext: {}
serviceAccount: default
serviceAccountName: default
terminationGracePeriodSeconds: 30
tolerations:
- effect: NoExecute
key: node.kubernetes.io/not-ready
operator: Exists
tolerationSeconds: 300
- effect: NoExecute
key: node.kubernetes.io/unreachable
operator: Exists
tolerationSeconds: 300
status:
conditions:
- lastProbeTime: null
lastTransitionTime: "2019-04-25T14:42:23Z"
message: '0/1 nodes are available: 1 node(s) didn''t match node selector.'
reason: Unschedulable
status: "False"
type: PodScheduled
phase: Pending
qosClass: BestEffort
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Björn Seebeck commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered Our Jenkins is at 2.164.2, BB 5.9.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57184) Kubernetes Plugin inversely applies NodeSelector
Title: Message Title Darrien Glasser created an issue Jenkins / JENKINS-57184 Kubernetes Plugin inversely applies NodeSelector Issue Type: Bug Assignee: Carlos Sanchez Attachments: Screen Shot 2019-04-25 at 9.20.37 AM.png Components: kubernetes-plugin Created: 2019-04-25 14:16 Environment: Jenkins version 2.173 Host OS: CentOS 7 openjdk version "1.8.0_181" Kubernetes Plugin version: 1.15.1 Kubernetes version: 1.13.2 Kubernetes nodes: Container Linux by CoreOS 1911.4.0 (Rhyolite) Priority: Minor Reporter: Darrien Glasser Adding a NodeSelector to slaves provisioned with the Kubernetes appears to apply an anti-affinity to that NodeSelector rather than actually using the NodeSelector. We share our Kubernetes Cluster with Jenkins and a number of other projects. For our Jenkins slaves, we only want certain fast nodes, so they're labeled with `jenkins-slave=true` and our slow nodes do not have that corresponding label. When configuring slaves in Jenkins, we applied the NodeSelector with the given label: With the expectation it would only run on the fast nodes. But instead it only ran on the slow nodes without the label. It seems like rather than apply a NodeSelector, it's applying the opposite of the NodeSelector (anti-affinity). We can't do too much testing on our production instance of Jenkins, so for now we've just removed the NodeSelector and are letting Jenkins Slaves run everywhere, but this is very frustrating when a slave is scheduled on our slow nodes.
[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials
Title: Message Title Mark Waite edited a comment on JENKINS-47531 Re: git-lfs: allow specifying separate credentials [~amatera] that pull request has been labeled as "[Later|https://github.com/jenkinsci/git-plugin/milestone/4?closed=1]". That means that it is one of over 60 pull requests which were not progressing because they were not high enough priority for me and were not receiving significant attention from others. I labeled those pull requests and closed them so that they would not spend time in the continuous integration servers. They will be reopened when time allows me to visit them again.My current priorities are:# Resolve [git plugin 4.0 pre-release critical regressions|https://github.com/jenkinsci/git-plugin/milestone/3] and [git client plugin 3.0 pre-release critical regressions|https://github.com/jenkinsci/git-client-plugin/milestone/1]# Test and release git plugin 4.0# Resolve [BuildData bloat|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%221+-+BuildData%22+is%3Aclosed] bug (JENKINS-19022)# Test and release BuildData bloat fix# Improve [notifyCommit handling|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%222+-+notifyCommit%22+is%3Aclosed]# Test and release notifyCommit handling improvements# Improve [submodule handling|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%223+-+Submodules%22+is%3Aclosed]# Test and release submodule handling improvements# Improve [caching for large git repositories|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%224+-+Caching%22+is%3Aclosed]# Test and release git caching improvements# Improve [changelog handling|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%225+-+Changelog%22+is%3Aclosed]# Test and release changelog handling improvements# Other improvements (like this credentials improvement)If you are available to help and would like to experiment with this proposed change, you could build it yourself, install it in your environment (development or production depending on how much risk you are willing to take), and report the results of that experiment to the [pull request|https://github.com/jenkinsci/git-plugin/pull/546]. If you'd like guidance on how to build that pull request locally, I'm happy to help. I'd prefer to provide that type of help in either the jenkinsci-dev mailing list or in the jenkins gitter channel, but I'm willing to help you build it yourself for testing and use. If you test it and use it, that meets your immediate need and helps me by adding more people that are testing the code. Add Comment
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title Nancy Robertson commented on JENKINS-45579 Re: Step to set stage or parallel status Nofar Bluestein - Many thanks for looking into this. Your proposal sounds good. I am particularly interested in the handling of the unstable condition. Our pipelines are mostly scripted, and we have been using the error() function to mark failed stages, but it would help to be able to mark stages as unstable and keep going. Does your current plan include the addition of an unstable() step? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57100) Improve Communication with REST-API
Title: Message Title MicroNova MicroNova started work on JENKINS-57100 Change By: MicroNova MicroNova Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials
Title: Message Title Mark Waite commented on JENKINS-47531 Re: git-lfs: allow specifying separate credentials Andrea Matera that pull request has been labeled as "Later". That means that it is one of over 60 pull requests which were not progressing because they were not high enough priority for me and were not receiving significant attention from others. I labeled those pull requests and closed them so that they would not spend time in the continuous integration servers. They will be reopened when time allows me to visit them again. My current priorities are: Resolve git plugin 4.0 pre-release critical regressions and git client plugin 3.0 pre-release critical regressions Test and release git plugin 4.0 Resolve BuildData bloat bug (JENKINS-19022) Test and release BuildData bloat fix Improve notifyCommit handling Test and release notifyCommit handling improvements Improve submodule handling Test and release submodule handling improvements Improve caching for large git repositories Test and release git caching improvements Improve changelog handling Test and release changelog handling improvements Other improvements (like this credentials improvement) If you are available to help and would like to experiment with this proposed change, you could build it yourself, install it in your environment (development or production depending on how much risk you are willing to take), and report the results of that experiment to the pull request. Add Comment
[JIRA] (JENKINS-56886) Missing test reports when using xUnit plugin
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Jenkins / JENKINS-56886 Missing test reports when using xUnit plugin Change By: Nikolas Falco Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title
Jesse Glick commented on JENKINS-57085
Re: Stack Traces with complex file names cannot be deserialized by XStream
It is most easily visible with Declarative but not limited to that. Using
@Library('github.com/jglick/sample-pipeline-library@JENKINS-57085-diag') _
com.github.jglick.sample.Err.fail(this)
which calls
package com.github.jglick.sample
class Err {
static void fail(script) {
script.error 'oops'
}
}
you can see
"workflow-api@2.33">
"hudson.AbortException">
oops
org.jenkinsci.plugins.workflow.steps.ErrorStep$Execution.run(ErrorStep.java:63)
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
com.github.jglick.sample.Err.fail(file:/…/jobs/p/builds/…/libs/github.com/jglick/sample-pipeline-library/src/com/github/jglick/sample/Err.groovy:4)
WorkflowScript.run(WorkflowScript:2)
___cps.transform___(Native Method)
com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57183) Manage Slaves doesn't work
Title: Message Title ethorsa created an issue Jenkins / JENKINS-57183 Manage Slaves doesn't work Issue Type: Bug Assignee: rsandell Components: multi-slave-config-plugin Created: 2019-04-25 13:27 Environment: - Master: Jenkins v2.150.3 (Java 8 / Windows) - Agents: Linux (SSH) and Windows (JNLP) - Multi Slave Config Plugin v1.2.0 - Browser: Chrome 73 Priority: Major Reporter: ethorsa The Manage Slave option doesn't work on a recent Jenkins version (v2.150.3 in my case). None of the available options shows any response. Reinstallation of the plugin or restarting the master doesn't solve the problem. The other options (add / delete / configure slaves) work as far as I have used them. Expected behavior The selected action is executed. Actual behavior Nothing happens (neither execution nor any other response) Reproduction Open the plugins menu (Manage Jenkins --> Multi Slave Config Plugin) Choose Manage Slaves Select some agents --> Proceed Execute on of the actions (eg. Take slaves offline) Nothing happens Slave is still online No response or error No related errors or messages in the Jenkins log
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Govind Sureka commented on JENKINS-57181 Re: Jenkins ALM disconnection Thanks Oliver, please let me know the Component Version number and when can I download that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50394) Branch Indexing fails with MissingObjectException
Title: Message Title Mark Waite edited a comment on JENKINS-50394 Re: Branch Indexing fails with MissingObjectException Fixed in [git plugin 3.9.4|https://plugins.jenkins.io/git#GitPlugin-ChangeLog] released April 24, 2019 and in git plugin 4.0.0-beta9 released April 24, 2019. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50394) Branch Indexing fails with MissingObjectException
Title: Message Title Mark Waite updated JENKINS-50394 Fixed in git plugin 3.9.4 released April 24, 2019 Jenkins / JENKINS-50394 Branch Indexing fails with MissingObjectException Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27494) Support for PHPUnit 4.* reports
Title: Message Title Vladimir Kuznichenkov commented on JENKINS-27494 Re: Support for PHPUnit 4.* reports Nikolas Falco I attach an example of a report. Please check it. INFO: [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'tests/_output/report.xml' relative to '/home/jenkins/workspace/ches_devel' for the testing framework 'PHPUnit-3.x (default)'. WARNING: The file '/home/jenkins/workspace/ches_devel/tests/_output/report.xml' is an invalid file. WARNING: At line 4 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 5 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 6 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 7 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 8 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 9 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 10 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 11 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 12 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 13 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 14 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 15 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 16 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 17 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 18 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 19 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to appear in element 'testcase'. WARNING: At line 20 of file:/home/jenkins/workspace/ches_devel/tests/_output/report.xml:cvc-complex-type.3.2.2: Attribute 'feature' is not allowed to
[JIRA] (JENKINS-27494) Support for PHPUnit 4.* reports
Title: Message Title Vladimir Kuznichenkov reopened an issue Jenkins / JENKINS-27494 Support for PHPUnit 4.* reports Change By: Vladimir Kuznichenkov Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27494) Support for PHPUnit 4.* reports
Title: Message Title Vladimir Kuznichenkov updated an issue Jenkins / JENKINS-27494 Support for PHPUnit 4.* reports Change By: Vladimir Kuznichenkov Attachment: report.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Oliver Gondža commented on JENKINS-57181 Re: Jenkins ALM disconnection Thanks, I have fixed the component for you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Oliver Gondža assigned an issue to Daniel Gront Jenkins / JENKINS-57181 Jenkins ALM disconnection Change By: Oliver Gondža Assignee: Oliver Gondža Daniel Gront Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57088) Optional load message content from file
Title: Message Title Anton Potsyus updated JENKINS-57088 Jenkins / JENKINS-57088 Optional load message content from file Change By: Anton Potsyus Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57181 Jenkins ALM disconnection Change By: Oliver Gondža Component/s: hp-application-automation-tools-plugin Component/s: jenkins-test-harness Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Govind Sureka commented on JENKINS-57181 Re: Jenkins ALM disconnection In the Component drop down we don't have option for Jenkins Plugin/Add in: Micro Focus Application Automation Tools. We are integrating Micro Focus ALM with Jenkins for execution of UFT Automation test cases. There we are facing issue with Timeout error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57182) When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Title: Message Title
simon Wall created an issue
Jenkins / JENKINS-57182
When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
jira-steps-plugin
Created:
2019-04-25 12:54
Labels:
jcasc-compatibility
Priority:
Minor
Reporter:
simon Wall
When configuring a Jira steps site, for example: unclassified: config: sites: name: JIRA url: "[url of site]" loginType: basic userName: [username] password: ${userpass-variable} timeout: 1 readTimeout: 1 If the Jenkins service is restarted, the site is duplicated.
Add Comment
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Oliver Gondža commented on JENKINS-57181 Re: Jenkins ALM disconnection Can you provide more details? From what it is written, this does not appear to be relevant to https://github.com/jenkinsci/jenkins-test-harness as the issue component indicates. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Govind Sureka created an issue Jenkins / JENKINS-57181 Jenkins ALM disconnection Issue Type: Bug Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2019-04-25 12:47 Environment: CloudBees Jenkins Enterprise Priority: Major Reporter: Govind Sureka We have integrated UFT Automation test cases from ALM to CloudBees Jenkins Enterprise using Add Ins: Micro Focus Application Automation Tools--> Execute HPE functional tests from HPE ALM. When a particular test case ran for more than 2 hours there is disconnection between Jenkins and ALM and it gives Timeout error. The error message is Unhandled Exception: System.NullReferenceException: Your Quality Center session has been disconnected. Contact your system administrator for more information at Mercury.TD.Client.Ota.QC9.ITSTest.get_LastRun() at HpToolsLauncher.AlmTestSetsRunner.GetTestRunId(ITSTest currentTest) at HpToolsLauncher.AlmTestSetsRunner.WriteTestRunSummary(ITSTest prevTest) at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, Double timeout, QcRunMode runMode, String runHost) at HpToolsLauncher.AlmTestSetsRunner.Run() at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile) at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args) An error occured while disposing runner: Your Quality Center session has been disconnected. Contact your system administrator for more information.
[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies
Title: Message Title Jesse Glick commented on JENKINS-28942 Re: Allow plugins to declare that they do not use certain implied dependencies Baptiste Mathus are you actually working on this? My proposal of 2017-07-07 would probably be more practical for plugins using buildPlugin(configurations: buildPlugin.recommendedConfigurations()) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46540) "Open Blue Ocean" button disappers when "Block inheritance of global authorization matrix" is set in a folder
Title: Message Title Daniel Beck commented on JENKINS-46540 Re: "Open Blue Ocean" button disappers when "Block inheritance of global authorization matrix" is set in a folder FYI I asked about this in https://groups.google.com/d/msg/jenkinsci-dev/kg4UVxJ4gQQ/os-aPg85CAAJ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials
Title: Message Title Andrea Matera commented on JENKINS-47531 Re: git-lfs: allow specifying separate credentials Is possible to have some updates on this feature? Will be a very nice-to-have also for our company because we are using Bitbucket for git repos and JFrog Artifactory for git-lfs artifacs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46540) "Open Blue Ocean" button disappers when "Block inheritance of global authorization matrix" is set in a folder
Title: Message Title Jesse Glick commented on JENKINS-46540 Re: "Open Blue Ocean" button disappers when "Block inheritance of global authorization matrix" is set in a folder You need Overall/Read to do anything except use an UnprotectedRootAction, so explicitly checking it makes little sense. Anyway, I am not sure why matrix-auth would be blocking inheritance of Overall/* permissions, but it should not matter since they should only ever be checked on Jenkins to begin with. (I used to want to actually enforce PermissionScope at runtime, but there are some corner cases that would be tricky to fix compatibly.) So agreed that just removing that line from action.jelly should suffice. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Jesse Glick started work on JENKINS-57085 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
