[JIRA] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-50557 GCR Credentials Plugin does not work Change By: Taylor Patton Comment: Are you sure you have both "Google OAuth Credentials plugin" and "Google Container Registry Auth Plugin" installed? Also make sure that your actual jenkins credential ID is not prepended with "gcr:". Those were my 2 mistakes Add Comment This 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title David van Laatum commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients I just think it logically makes sense when a new branch is created in a multi branch style job that the creation of the branch should be classified as a change which in turn would cause every other plugin that uses the list of developers/commiters to do something would pick this up. I think most users would expect this to be the case in multi branch. Not sure if the responsibility to do this lives in the multi branch plugin, scm api, the scm plugin/driver or a combination, I just think its what users would expect, I know I would, not that I have actually tested with SVN (which I use I work). I could code a special case in emailext but I think it would be better if its handled globally Add Comment This 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Mark Waite edited a comment on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients I can think of many different ways to define the set of changes which should be displayed in job creation. Some examples that immediately come to mind include:* No changes, this is the first job on the branch so there can't be any changes (current behavior)* Tip of the new branch (as requested by [~zack])* Chain of changes on the branch compared to a defined base branch (use double dot comparison notation)* Chain of changes on the branch since it diverged from a defined base branch (use triple dot comparison notation as described on [stackoverflow|https://stackoverflow.com/questions/9725531/show-commits-since-branch-creation]) - matches a common technique of creating a new branch and adding several commits to the branch before I push it to the remote git server* Fixed number of changes on the branch (branch created which was created as an [orphan|https://stackoverflow.com/questions/5689960/how-do-i-create-a-commit-without-a-parent-in-git])I'm sure there are other scenarios as well. Unfortunately, I don't intend to change the current behavior. I believe @Zack [~zack] can get the behavior he wants from within Pipeline, and others could do the same, without requiring changes to the git plugin (and the 13 installations of the 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
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Mark Waite commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients I can think of many different ways to define the set of changes which should be displayed in job creation. Some examples that immediately come to mind include: No changes, this is the first job on the branch so there can't be any changes (current behavior) Tip of the new branch (as requested by Zack Snyder) Chain of changes on the branch compared to a defined base branch (use double dot comparison notation) Chain of changes on the branch since it diverged from a defined base branch (use triple dot comparison notation as described on stackoverflow) - matches a common technique of creating a new branch and adding several commits to the branch before I push it to the remote git server Fixed number of changes on the branch (branch created which was created as an orphan) I'm sure there are other scenarios as well. Unfortunately, I don't intend to change the current behavior. I believe @Zack can get the behavior he wants from within Pipeline, and others could do the same, without requiring changes to the git plugin (and the 13 installations of the git plugin). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51352) Windows slave not getting connected
Title: Message Title Gaurav Negi updated an issue Jenkins / JENKINS-51352 Windows slave not getting connected Attached is the log Change By: Gaurav Negi Attachment: Error_log.txt Add Comment This 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-51329) Can I use multiple podTemplate not nest
Title: Message Title Hokwang Lee commented on JENKINS-51329 Re: Can I use multiple podTemplate not nest Carlos Sanchez Can you reply 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-51352) Windows slave not getting connected
Title: Message Title Gaurav Negi updated an issue Jenkins / JENKINS-51352 Windows slave not getting connected Change By: Gaurav Negi Dear All, I have got struck with an issue, I am seeing very 1st time with Jenkins. 1. I am using Jenkins Master as Ubuntu VM and Jenkins slave on Windows 10. 2. I have openssh running on window slave. 3. I am not able to bring Jenkins window slave online. It can authenticate, but running command cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar slave.jar " fails[05/15/18 19:23:50] [SSH] Copied 745,674 bytes. Expanded the channel window size to 4MB [05/15/18 19:23:50] [SSH] Starting slave process: cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>Error: Unable to access jarfile slave.jar Slave JVM has terminated. Exit code=1 [05/15/18 19:23:50] Launch failed - cleaning up connection [05/15/18 19:23:50] [SSH] Connection closed.4. I can reproduce the same by manually run following command from Jenkins masterCommand ssh user@jenkinsslave " cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar slave.jar " FailsBut If I run (with full path of slave.jar) it works. ssh user@jenkinsslave " cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar D:\jenkins\slave.jar " Can I please know what can I do to fix it? How can I change the command that Jenkins master is running to connect to slave? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title David van Laatum commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients I can see the point that when a new multi-branch job is created by the creation of a new branch it does make sense that the commit(s) that created the branch should really be counted as a change. Not sure how feasible this is though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51352) Windows slave not getting connected
Title: Message Title Gaurav Negi created an issue Jenkins / JENKINS-51352 Windows slave not getting connected Issue Type: Bug Assignee: Unassigned Components: ssh-plugin Created: 2018-05-16 02:34 Environment: Jenkins Master: Ubuntu Jenkins Slave: Windows 10 Priority: Blocker Reporter: Gaurav Negi Dear All, I have got struck with an issue, I am seeing very 1st time with Jenkins. 1. I am using Jenkins Master as Ubuntu VM and Jenkins slave on Windows 10. 2. I have openssh running on window slave. 3. I am not able to bring Jenkins window slave online. It can authenticate, but running command cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar slave.jar fails [05/15/18 19:23:50] [SSH] Copied 745,674 bytes. Expanded the channel window size to 4MB [05/15/18 19:23:50] [SSH] Starting slave process: cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>Error: Unable to access jarfile slave.jar Slave JVM has terminated. Exit code=1 [05/15/18 19:23:50] Launch failed - cleaning up connection [05/15/18 19:23:50] [SSH] Connection closed. 4. I can reproduce the same by manually run following command from Jenkins master Command cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar slave.jar Fails But If I run (with full path of slave.jar) it works. cd "D:\jenkins" && java -Xms2048m -Xmx4096m -jar D:\jenkins\slave.jar Can I please know what can I do to fix it? How can I change the command that Jenkins master is running to connect to slave?
[JIRA] (JENKINS-51346) HTML5 compliance fixes for recent testability changes
Title: Message Title Karl Shultz commented on JENKINS-51346 Re: HTML5 compliance fixes for recent testability changes Yep, a data tag is the way to go. Almost there. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51346) HTML5 compliance fixes for recent testability changes
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-51346 HTML5 compliance fixes for recent testability changes Change By: Karl Shultz Assignee: Karl Shultz Add Comment This 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-51346) HTML5 compliance fixes for recent testability changes
Title: Message Title Karl Shultz started work on JENKINS-51346 Change By: Karl Shultz 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-46145) Groovy Traits are not supported
Title: Message Title Dmytro Kryvenko commented on JENKINS-46145 Re: Groovy Traits are not supported For whoever else run into that issue: good old @Mixin seems to be working fine. It is deprecated in favor to traits, though, so dunno how long is it going to be available in the upcoming groovy versions. http://docs.groovy-lang.org/latest/html/api/groovy/lang/Mixin.html Add Comment This 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-51351) pipeline-stage-view - render new block of cells for changed stage structure
Title: Message Title Daniel Hsueh created an issue Jenkins / JENKINS-51351 pipeline-stage-view - render new block of cells for changed stage structure Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2018-05-16 00:26 Environment: jenkins 2.98 pipeline-stage-view 2.9 Priority: Minor Reporter: Daniel Hsueh I understand that if the names or structure of stages changes sufficiently, old builds are not displayed in the cell table (c.f. JENKINS-38538). How about creating a new cell table every time the structure changes sufficiently that the current table cannot be used? The previous jobs under the previous table could then be viewed. Add Comment
[JIRA] (JENKINS-51302) Classloading issues when running PCT against WARs created by CustomWarPackager when replacing libs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51302 Re: Classloading issues when running PCT against WARs created by CustomWarPackager when replacing libs Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/JenkinsWarPatcher.java http://jenkins-ci.org/commit/custom-war-packager/66768f511f9ba7f5f7dcc0b1d6319bc4d9ef6007 Log: Merge pull request #28 from oleg-nenashev/JENKINS-51302 JENKINS-51302 - Properly cleanup Metadata so that PCT does not miss metadata for running integration tests Compare: https://github.com/jenkinsci/custom-war-packager/compare/b9f7d9087153...66768f511f9b *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51302) Classloading issues when running PCT against WARs created by CustomWarPackager when replacing libs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51302 Re: Classloading issues when running PCT against WARs created by CustomWarPackager when replacing libs Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/JenkinsWarPatcher.java http://jenkins-ci.org/commit/custom-war-packager/9a011d96e759c400cab79fc7edb640c75aeee63b Log: JENKINS-51302 - Properly cleanup Metadata so that PCT does not miss metadata for running integration tests Add Comment This 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-46145) Groovy Traits are not supported
Title: Message Title Dmytro Kryvenko commented on JENKINS-46145 Re: Groovy Traits are not supported All of the sudden, I just ran into that issue. This CPS thing definitely gives a lot of benefits, but there should be a way to choose that I want to use library X with CPS but library Y is just plain Groovy. Would not be a problem, but here and there I ran into things that works in plain Groovy but do not in CPS - ending up blocked while have no benefit being CPS-ed in this particular piece of 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-50484) The Groovy Postbuild 2.4 Broken links using manager.addShortText in pipeline and freestyle
Title: Message Title ikedam commented on JENKINS-50484 Re: The Groovy Postbuild 2.4 Broken links using manager.addShortText in pipeline and freestyle Jacob Volstrup No, you can’t. Add Comment This 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Mark Waite commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Tibor, I think you'll get better results with a new bug report rather than asking questions on this closed report Add Comment This 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-45826) XUnit support for distinguishing test reports from different steps
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-45826 XUnit support for distinguishing test reports from different steps Change By: Nikolas Falco Assignee: Andrew Bayer Nikolas Falco Add Comment This 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-49344) Add support for categorizing tests to xunit plugin
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-49344 Add support for categorizing tests to xunit plugin Change By: Nikolas Falco Assignee: Andrew Bayer Nikolas Falco Add Comment This 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-10736) No support for UnitTest XML reporting per sub job when using matrix projects
Title: Message Title Nikolas Falco closed an issue as Duplicate Jenkins / JENKINS-10736 No support for UnitTest XML reporting per sub job when using matrix projects Change By: Nikolas Falco Status: In Progress Closed 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-34274) Duration testsuite is not read from report.
Title: Message Title Nikolas Falco commented on JENKINS-34274 Re: Duration testsuite is not read from report. Which test tools are you referring? MSTest? CTest? GoogleTest? Add Comment This 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-34274) Duration testsuite is not read from report.
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-34274 Duration testsuite is not read from report. Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This 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-35407) Time duration of testsuites and testsuite nodes not the sum of the testcase
Title: Message Title Nikolas Falco commented on JENKINS-35407 Re: Time duration of testsuites and testsuite nodes not the sum of the testcase Please give me more details about which kind of tools are you using, some example reports and so on otherwise I have to choose that close this bug as Can not reproduce Add Comment This 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-34106) xUnit crashes on Windows 10 nodes
Title: Message Title Nikolas Falco closed an issue as Not A Defect Jenkins / JENKINS-34106 xUnit crashes on Windows 10 nodes Change By: Nikolas Falco 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-13113) xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-13113 xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13113) xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13113 Re: xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped Code changed in jenkins User: Nikolas Falco Path: src/main/resources/org/jenkinsci/plugins/xunit/types/ctest-to-junit.xsl src/test/java/org/jenkinsci/plugins/xunit/types/MSTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase1/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase2/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase3/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase4/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase5/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase6/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase7/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase7/result.xml http://jenkins-ci.org/commit/xunit-plugin/5100d71b47639be65dbf916e467d181e9e11e9d9 Log: JENKINS-13113 xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped Update XSL to count NotExecuted test as skipped. Minor improvements to testsuite time duration. Compare: https://github.com/jenkinsci/xunit-plugin/compare/dd79be01562d...5100d71b4763 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title David Joo commented on JENKINS-51347 Re: Test Status "notrun" being reported as "failed" test Thanks for the fix. Will we see the changed take effect when version 1.105 is released in the future? Add Comment This 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-13113) xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-13113 xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped Change By: Nikolas Falco Summary: Xunit Plugin xUnit plugins detects MSTEST "NotExecuted" as "Passed" successed instead of "Skipped" skipped Add Comment This 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-13113) xUnit plugins detects MSTEST "NotExecuted" as successed instead of skipped
Title: Message Title Nikolas Falco started work on JENKINS-13113 Change By: Nikolas Falco Status: Reopened 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Olivier Lamy Now my build does not hang but I have a new issue with Jira plugin because when I commit with messages which matches a pattern, the Jira plugin times out immediately. Maybe in less than one second. In the Management are two sections: JIRA and JIRA Sites. The first has successful login but the second fails. Why this happens? Add Comment This 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-13113) Xunit Plugin detects MSTEST "NotExecuted" as "Passed" instead of "Skipped"
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-13113 Xunit Plugin detects MSTEST "NotExecuted" as "Passed" instead of "Skipped" Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This 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-51350) Problems with the Jenkins slave agent
Title: Message Title Brady Dalbec created an issue Jenkins / JENKINS-51350 Problems with the Jenkins slave agent Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-15 21:41 Environment: Jenkins ver. 2.122 Priority: Minor Reporter: Brady Dalbec I keep getting this error when trying to run the Jenkins slave agent on linux: java.io.IOException: Failed to load http://address:8080/computer/pc-name/slave-agent.jnlp?encrypt=true: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:496) at hudson.remoting.Launcher.run(Launcher.java:322) at hudson.remoting.Launcher.main(Launcher.java:283) Waiting 10 seconds before retry And here is the command I run: java -jar agent.jar -jnlpUrl http://address:8080/computer/ARMHF-Builder%20RPI3B/slave-agent.jnlp -secret -workDir "/home/jenkins" I have tried also the -jnlpCredentials argument and I do not want to enable anonymous access (as this is a public build server) to create or connect to Jenkins slaves. Any way to fix this at all?
[JIRA] (JENKINS-50950) Updates service should compute and return deltas based on the instance's version
Title: Message Title R. Tyler Croy updated JENKINS-50950 Jenkins / JENKINS-50950 Updates service should compute and return deltas based on the instance's version Change By: R. Tyler Croy 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-51113) Add server middleware to normalize redundant slashes in requests
Title: Message Title R. Tyler Croy updated JENKINS-51113 Jenkins / JENKINS-51113 Add server middleware to normalize redundant slashes in requests Change By: R. Tyler Croy 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-51117) Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins
Title: Message Title Henry Borchers closed an issue as Fixed Jenkins / JENKINS-51117 Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins Change By: Henry Borchers Status: Open Closed 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-51113) Add server middleware to normalize redundant slashes in requests
Title: Message Title R. Tyler Croy started work on JENKINS-51113 Change By: R. Tyler Croy 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-50950) Updates service should compute and return deltas based on the instance's version
Title: Message Title R. Tyler Croy commented on JENKINS-50950 Re: Updates service should compute and return deltas based on the instance's version This is something handled more elegantly by JEP-307 and the update level process Add Comment This 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-51328) Fix Registration error happening in the container
Title: Message Title R. Tyler Croy updated JENKINS-51328 Jenkins / JENKINS-51328 Fix Registration error happening in the container Change By: R. Tyler Croy 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-50950) Updates service should compute and return deltas based on the instance's version
Title: Message Title R. Tyler Croy started work on JENKINS-50950 Change By: R. Tyler Croy 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-51328) Fix Registration error happening in the container
Title: Message Title R. Tyler Croy started work on JENKINS-51328 Change By: R. Tyler Croy 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-37485) Propagate Job params to script does nothing
Title: Message Title Ioannis Moutsatsos commented on JENKINS-37485 Re: Propagate Job params to script does nothing Dominik Bartholdi Thanks for the guidance. Unfortunately I'm still getting errors trying to access environment variables from the scriptlet using this approach. For example: Execution of script [export_metadata_query.groovy] failed - groovy.lang.MissingPropertyException: No such property: env for class: Script1org.jenkinsci.plugins.scriptler.util.GroovyScript$ScriptlerExecutionException: groovy.lang.MissingPropertyException: No such property: env for class: Script1 at org.jenkinsci.plugins.scriptler.util.GroovyScript.call(GroovyScript.java:131) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) Add Comment This 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-44623) JNLP slave fail to connect
Title: Message Title Abubakar Mohammed commented on JENKINS-44623 Re: JNLP slave fail to connect Ok. Thank you Liora Milbaum Add Comment This 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-51349) not appearing on dashboard
Title: Message Title pratyusha kadiyala created an issue Jenkins / JENKINS-51349 not appearing on dashboard Issue Type: Bug Assignee: Henry Baez Components: adaptiveplugin Created: 2018-05-15 19:43 Priority: Trivial Reporter: pratyusha kadiyala Add Comment This 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"
[JIRA] (JENKINS-51345) Save the essentials.log.0 file after test run
Title: Message Title Baptiste Mathus resolved as Fixed Jenkins / JENKINS-51345 Save the essentials.log.0 file after test run Change By: Baptiste Mathus Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title Martin Weber commented on JENKINS-31371 Re: No tool download known for OS... (Crawler generates empty update file) Sorry, the link to the issue was wrong, corrected now. Anyway INFRA-1483 is closed 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-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title
Martin Weber edited a comment on JENKINS-31371
Re: No tool download known for OS... (Crawler generates empty update file)
[~jg_lgc] If you do not see a file {{hudson.plugins.cmake.CmakeInstaller.json}} in directory $JENKINS_HOME/updates, you are suffering from [JENKINS INFRA - 3137|https://issues 1483 . jenkins-ci.org/browse/JENKINS-31371]. If so, please vote there.As a workaround, you could manually download the file from [https://updates.jenkins-ci.org/updates/hudson.plugins.cmake.CmakeInstaller.json]
Add Comment
This 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-13113) Xunit Plugin detects MSTEST "NotExecuted" as "Passed" instead of "Skipped"
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-13113
Xunit Plugin detects MSTEST "NotExecuted" as "Passed" instead of "Skipped"
Change By:
Nikolas Falco
We had an out of memory exception while running our MSTEST unit tests which caused all subsequent tests to be NotExecuted. Unfortunately those "NotExecuted" tests were counted as passed, so the test job succeeded instead of failing.One example from the TRX file: {code:xml} {code} The transformation in the junitResult.xml file: {code:xml} NaN ConformanceWcdmaCompleteTest.BandSpecificTests TestcaseWcdmaTxIntermod_5_12__FDD9 false 0 {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-23101) xUnit plugin fails to work after upgrade
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Jenkins / JENKINS-23101 xUnit plugin fails to work after upgrade Change By: Nikolas Falco Status: Open Closed Resolution: Cannot Reproduce Add Comment This 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-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title Nikolas Falco edited a comment on JENKINS-51347 Re: Test Status "notrun" being reported as "failed" test Thank for the second complete test report file (Test_2.xml). It is useful because to prevent it prevents a bug in the duration. Add Comment This 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-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-51347 Test Status "notrun" being reported as "failed" test Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51347 Re: Test Status "notrun" being reported as "failed" test Code changed in jenkins User: Nikolas Falco Path: src/main/java/org/jenkinsci/plugins/xunit/types/CTest.java src/main/java/org/jenkinsci/plugins/xunit/types/CTestInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/CTestType.java src/main/resources/org/jenkinsci/plugins/xunit/types/ctest-to-junit.xsl src/test/java/org/jenkinsci/plugins/xunit/types/CTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase1/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase2/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase3/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase3/result.xml http://jenkins-ci.org/commit/xunit-plugin/dd79be01562d8f6c679ef42c7f86a575511d9f7f Log: JENKINS-51347 Test Status "notrun" being reported as "failed" test Fix XSL to not include in failure count also skipped tests. *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Oleg Nenashev commented on JENKINS-51326 Re: JEP-200 long data type rejected after upgrade to 2.107.3 I'd guess there is no stacktrace, right? Would it be possible to get a full log starting from the startup? Maybe the core's whitelist didn't get loaded somehow (e.g. resource loading issue). Also, do you run Jenkins in a web container? or do you use the built-in Jetty? Add Comment This 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-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-51326 JEP-200 long data type rejected after upgrade to 2.107.3 Change By: Oleg Nenashev Assignee: 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-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title Nikolas Falco started work on JENKINS-51347 Change By: Nikolas Falco 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-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title Nikolas Falco commented on JENKINS-51347 Re: Test Status "notrun" being reported as "failed" test Thank for the second complete test report file (Test_2.xml). It is useful because to prevent a bug in the duration. Add Comment This 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-51348) Editor steps need data tags, or similar, to allow for easier targeting from ATH
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-51348 Editor steps need data tags, or similar, to allow for easier targeting from ATH Issue Type: Improvement Assignee: Ivan Meredith Attachments: image-2018-05-15-14-59-45-261.png, image-2018-05-15-15-01-09-325.png, image-2018-05-15-15-01-33-401.png, image-2018-05-15-15-02-57-759.png, image-2018-05-15-15-03-24-957.png Components: blueocean-pipeline-editor-plugin Created: 2018-05-15 19:08 Labels: blueocean-testability Priority: Major Reporter: Karl Shultz Summary Steps in the sheet shown for a particular pipeline stage can be changed, reordered by dragging, or even deleted. In order to write automated tests for this, we should have selectors available which more easily distinguish one step from another. Details As of today, there are no editor ATH tests for: Deleting steps within a stage Modifying an existing step Dragging steps to reorder them When investigating how to do this, I discovered that these steps all have identical class names, which makes it tricky to distinguish them in a test. For example, take this Pipeline, which is showing a stage that contains two Shell Script steps: These two steps are not easily distinguished from each other from within an ATH test. Both have the
[JIRA] (JENKINS-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title David Joo updated an issue Jenkins / JENKINS-51347 Test Status "notrun" being reported as "failed" test Change By: David Joo Attachment: Test_2.xml Add Comment This 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-51326) JEP-200 long data type rejected after upgrade to 2.107.3
Title: Message Title Daniel Beck commented on JENKINS-51326 Re: JEP-200 long data type rejected after upgrade to 2.107.3 Oleg Nenashev Any idea? long isn't a class… Add Comment This 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-51320) Update text references in Jenkins to replace "slave" with "agent"
Title: Message Title Daniel Beck closed an issue as Duplicate Initially implemented towards 2.0 but then the effort didn't progress well. JENKINS-42816 tracks most of the known specific issues. Jenkins / JENKINS-51320 Update text references in Jenkins to replace "slave" with "agent" Change By: Daniel Beck Status: Open Closed 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
[JIRA] (JENKINS-51327) Random java.lang.NumberFormatException
Title: Message Title Daniel Beck commented on JENKINS-51327 Re: Random java.lang.NumberFormatException TBH I am not sure what our IPv6 situation is overall. Might be interesting to go with IPv4 in some of the involved components and see whether that resolves the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51327) Random java.lang.NumberFormatException
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-51327 Random java.lang.NumberFormatException Change By: Daniel Beck Hi,I'm accessing my remote Jenkins server, with HTTPS stream passing through an SSL Gateway, then the Apache server redirecting calls to the Jenkins server.I works well, but I regularly have the following error, when accessing any page :java.lang.NumberFormatException: 2a01:e35:8a4a:8c0:30a6:4764:692b:f7da at org.eclipse.jetty.util.StringUtil.toInt(StringUtil.java:724) at org.eclipse.jetty.util.HostPort.(HostPort.java:66) at org.eclipse.jetty.http.HostPortHttpField.(HostPortHttpField.java:44) Caused: org.eclipse.jetty.http.BadMessageException: 400: Bad HostPort at org.eclipse.jetty.http.HostPortHttpField.(HostPortHttpField.java:48) at org.eclipse.jetty.http.HostPortHttpField.(HostPortHttpField.java:35) at org.eclipse.jetty.server.ForwardedRequestCustomizer$RFC7239.parsedParam(ForwardedRequestCustomizer.java:485) at org.eclipse.jetty.http.QuotedCSV.addValue(QuotedCSV.java:135) at org.eclipse.jetty.server.ForwardedRequestCustomizer.customize(ForwardedRequestCustomizer.java:348) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)I have to reload the page a few times, and it eventually works, but this is very annoying as it occurs quite often.I can give you the public URL of the server in private message if required, so that you can reproduce the error with some (bad) luck. I have reproduced it with many different users.Thanks for your support Add Comment
[JIRA] (JENKINS-51319) Jenkins plugin Update failed the system.
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce Jenkins / JENKINS-51319 Jenkins plugin Update failed the system. Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce Add Comment This 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-51319) Jenkins plugin Update failed the system.
Title: Message Title Daniel Beck commented on JENKINS-51319 Re: Jenkins plugin Update failed the system. Relevant part: Caused by: java.lang.NoSuchMethodError: jenkins.AgentProtocol.isDeprecated()Z at jenkins.slaves.DeprecatedAgentProtocolMonitor.isActivated(DeprecatedAgentProtocolMonitor.java:72) However, 2.73.2 This release is 6 months outdated. Please update Jenkins, and reopen this issue if it still occurs. Add Comment This 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-51295) Project Page Timeout
Title: Message Title Daniel Beck closed an issue as Duplicate Looks like a duplicate of the issue linked by Oleg. Jenkins / JENKINS-51295 Project Page Timeout Change By: Daniel Beck Status: Open Closed 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-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Daniel Beck commented on JENKINS-51253 Re: jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency Mostyn Bramley-Moore Could you file a PR? CC Sam Van Oort who is the closest we have to a maintainer of packaging, I think. Add Comment This 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-50969) core site build is broken, needed for core taglibs reference
Title: Message Title Daniel Beck updated JENKINS-50969 A Jenkins / JENKINS-50969 core site build is broken, needed for core taglibs reference Change By: Daniel Beck 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-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title David Joo updated an issue Jenkins / JENKINS-51347 Test Status "notrun" being reported as "failed" test Change By: David Joo Attachment: snippet_test_report_file.txt Add Comment This 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-51242) Jenkins doesn't take configured JDK
Title: Message Title
Softbless Solutions commented on JENKINS-51242
Re: Jenkins doesn't take configured JDK
hi Devin Nusbaum It's a freestyle project. below is the console output :
Started by user admin
Building in workspace /opt/jenkins/apps/jenkins/jenkins_home/workspace/pkc-lkpp
> /opt/jenkins/git/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /opt/jenkins/git/bin/git config remote.origin.url http://code.softbless.com/shine/pkc-lkpp.git # timeout=10
Fetching upstream changes from http://code.softbless.com/shine/pkc-lkpp.git
> /opt/jenkins/git/bin/git --version # timeout=10
using GIT_ASKPASS to set credentials
> /opt/jenkins/git/bin/git fetch --tags --progress http://code.softbless.com/shine/pkc-lkpp.git +refs/heads/*:refs/remotes/origin/*
> /opt/jenkins/git/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> /opt/jenkins/git/bin/git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 4a7ee3cdcb324c65c40f0b6fc73518e263236090 (refs/remotes/origin/master)
> /opt/jenkins/git/bin/git config core.sparsecheckout # timeout=10
> /opt/jenkins/git/bin/git checkout -f 4a7ee3cdcb324c65c40f0b6fc73518e263236090
Commit message: "Show Latar Belakang View Content only if it's not empty"
> /opt/jenkins/git/bin/git rev-list --no-walk 4a7ee3cdcb324c65c40f0b6fc73518e263236090 # timeout=10
[pkc-lkpp] $ /opt/jenkins/apps/jenkins/jenkins_home/tools/hudson.tasks.Ant_AntInstallation/ant1.10.3/bin/ant -file liferay-plugins-sdk-6.2 clean
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Invoke Ant' marked build as failure
Finished: FAILURE
Add Comment
[JIRA] (JENKINS-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title Nikolas Falco commented on JENKINS-51347 Re: Test Status "notrun" being reported as "failed" test Please attach report files Add Comment This 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-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Scott Williams edited a comment on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Same here with an internal Docker registry. Docker login now fails with "401 unauthorized" after upgrading to 1.16.Reverting to 1.15.1 fixes works, so this appears to be a significant regression with 1 . 16. Add Comment This 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-51342) Link Google Drive and Timeline from the project page on jenkins.io
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51342 Re: Link Google Drive and Timeline from the project page on jenkins.io Code changed in jenkins User: Oleg Nenashev Path: content/projects/gsoc/2018/remoting-over-message-bus.adoc http://jenkins-ci.org/commit/jenkins.io/a6f63599fe4cb282f68672a155a3b0988611b572 Log: Merge pull request #1543 from pvtuan10/WEBSITE-486/update-project-info JENKINS-51342 Link Google Drive and Timeline from the project page on jenkins.io Compare: https://github.com/jenkins-infra/jenkins.io/compare/46ccf4d4ed03...a6f63599fe4c *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Scott Williams commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Same here with an internal Docker registry. Docker login now fails with "401 unauthorized" after upgrading to 1.16. Reverting to 1.15.1 fixes works, so this appears to be a significant 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-51347) Test Status "notrun" being reported as "failed" test
Title: Message Title David Joo created an issue Jenkins / JENKINS-51347 Test Status "notrun" being reported as "failed" test Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-05-15 17:42 Environment: Jenkins: 1. xunit-plugin: 1.104 Ubuntu 14.04 Java: 1.7 Priority: Minor Reporter: David Joo We're running tests through ctest. Test engine is googletest We "disable" tests through prefixing tests with "DISABLED" Those test are not run, and the status field is as such "" However, this status is reported as a failed test through the xunit plugin. This isn't a failed test for us. The xunit-plugin choice used to report test results is "CTest-Version N/A" Add Comment
[JIRA] (JENKINS-19621) Plug-in configuration is inflexible and counter-intuitive
Title: Message Title Phil Brown commented on JENKINS-19621 Re: Plug-in configuration is inflexible and counter-intuitive Adding to the third point- I would like the ability to reference an environment variable for the configuration fields in the plugin. I keep a file containing the exclusions for the file filters, and locally have a way to parse this file out, however I prefer using this plugin because it will consume all of the output files and show the information intuitively. Add Comment This 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-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick updated JENKINS-51247 Jenkins / JENKINS-51247 Move flattened POM into target directory Change By: Jesse Glick 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-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title
Gabriel Loewen edited a comment on JENKINS-50840
Re: Powershell script execution broken in powershellHelper.ps1
This edge case seems to be happening only with powershell format cmdlets, such as Format-Table, etc... Are you using one of these cmdlets? You can fix it temporarily by piping any calls to Foramt Format -* cmdlets to Out-String:e.g.{code:java}$Data | Format-Table | Out-String{code}Meanwhile, it should be fixed in my PR: [https://github.com/jenkinsci/durable-task-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-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title
Gabriel Loewen edited a comment on JENKINS-50840
Re: Powershell script execution broken in powershellHelper.ps1
This edge case seems to be happening only with powershell format cmdlets, such as Format-Table, etc... Are you using one of these cmdlets? You can fix it temporarily by piping any calls to Foramt-* cmdlets to Out-String:e.g. {code:java}$Data | Format-Table | Out-String{code}Meanwhile, it should be fixed in my PR: [ https://github.com/jenkinsci/durable-task-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-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title Gabriel Loewen commented on JENKINS-50840 Re: Powershell script execution broken in powershellHelper.ps1 This edge case seems to be happening only with powershell format cmdlets, such as Format-Table, etc... Are you using one of these cmdlets? You can fix it temporarily by piping any calls to Foramt-* cmdlets to Out-String: e.g. $Data | Format-Table | Out-String Meanwhile, it should be fixed in my PR: https://github.com/jenkinsci/durable-task-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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov updated an issue Jenkins / JENKINS-51341 Suite name is not shown on the main page and method results page Change By: Vladimir Sitnikov Attachment: failed_configs.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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov updated an issue Jenkins / JENKINS-51341 Suite name is not shown on the main page and method results page Change By: Vladimir Sitnikov Attachment: failed_configs.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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov updated an issue Jenkins / JENKINS-51341 Suite name is not shown on the main page and method results page Change By: Vladimir Sitnikov Comment: A side note: I would move "Failed Configurations" to the top (right after "total tests"), as it is likely to be more important than "skipped/failed" tests. "Failed configurations" might cause tests to be skipped not the other way around. !failed_configs.png|thumbnail! Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov updated an issue Jenkins / JENKINS-51341 Suite name is not shown on the main page and method results page Change By: Vladimir Sitnikov Attachment: failed_configs.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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Mark Waite commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients Zack Snyder I think there are several different ways to get the information you want. You could save the return value of the checkout step and use the GIT_* entries in that map (though see JENKINS-45489 for a bug which may affect that technique for your case). That is described in a Jenkins Minute video and in the documentation You could call git log -n 1 and read the output of git log for the author name. Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov commented on JENKINS-51341 Re: Suite name is not shown on the main page and method results page A side note: I would move "Failed Configurations" to the top (right after "total tests"), as it is likely to be more important than "skipped/failed" tests. "Failed configurations" might cause tests to be skipped not the other way around. Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov commented on JENKINS-51341 Re: Suite name is not shown on the main page and method results page A side note: I would move "Failed Configurations" to the top (right after "total tests"), as it is likely to be more important than "skipped/failed" tests. "Failed configurations" might cause tests to be skipped not the other way around. Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov updated an issue Jenkins / JENKINS-51341 Suite name is not shown on the main page and method results page Change By: Vladimir Sitnikov Attachment: failed_configs.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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov commented on JENKINS-51341 Re: Suite name is not shown on the main page and method results page There are quite a few tests: And it turns out certain test is listed 3 times: , , and Note: those are different executions of the same test method (there are just multiple suite xml files that list the same method name with different suite parameters), so the result file is parsed properly. It is just representation that makes the whole thing hard to reason about. Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Vladimir Sitnikov updated an issue Jenkins / JENKINS-51341 Suite name is not shown on the main page and method results page Change By: Vladimir Sitnikov Attachment: 3of3.png Attachment: 2of3.png Attachment: 1of3.png Attachment: overall.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
[JIRA] (JENKINS-51339) Create JIRA tasks for the defined steps
Title: Message Title Pham Vu Tuan started work on JENKINS-51339 Change By: Pham Vu Tuan 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-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Peter Sosnowski edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Jenkins: 2.120I have the this issue happening on all my slaves. -This started once i configured Jenkins to work over HTTPS (HTTP disabled).- This is happening regardless whether configured to run over HTTP or HTTPSAll Java Web Start Agent protocols disabled except for protocol/4.By launching jenkins slave manually via javaws, I can see no issues and the slaves connect, however when I install it as a windows service that's where the issue appears. SEVERE: The server rejected the connection: None of the protocols were accepted java.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:296) at hudson.remoting.Engine.run(Engine.java:267) EDIT (UPDATE): I was able to fix my issue. When I upgraded jenkins to version 2+ I never cleared the working dir of the slaves (so all the files including jenkins-slave.xml, jenkins-slave.exe, etc remained.) After deleting the all the contents, I installed the jenkins slave as a windows service again and I no longer get the error, the slave connects as expected Add Comment This 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-51346) HTML5 compliance fixes for recent testability changes
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-51346 HTML5 compliance fixes for recent testability changes Issue Type: Improvement Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2018-05-15 16:03 Priority: Minor Reporter: Karl Shultz Summary PR 1733 included some changes to EditorPipelineGraph.jsx. These changes provided an id for automated tests, so that stages could be targeted by their stage name. Ivan Meredith correctly pointed out that IDs should not have spaces in them, and as things stand, they could. This ticket is being created to fix that up. Possible fixes There are two ways we could do this. Add some string substitution to the ID, to remove spaces Switch instead to a data tag. Something along the lines of data-stage-name="stage name with spaces in it" The data tag approach makes more sense to me. If, in the confines of the test, a stage is created with the name my stage name with spaces, we'd have the JS side doing something to convert the spaces to something else. But we'd also have to change subsequent test code, to look for the "corrected" stage name. In other words, you can't just pass around a string with the value my stage name with spaces, because the editor will have removed those spaces. It seems the test code will need to be aware of this and do a conversion of its own. Here's the example from PR 1733, in the order the steps get executed: Initialize a variable with the name of our stage, with spaces in it Create the stage Later, we
[JIRA] (JENKINS-51342) Link Google Drive and Timeline from the project page on jenkins.io
Title: Message Title Pham Vu Tuan commented on JENKINS-51342 Re: Link Google Drive and Timeline from the project page on jenkins.io Oleg Nenashev I submitted a PR for this task https://github.com/jenkins-infra/jenkins.io/pull/1543 Add Comment This 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-51290) Builds fail to start with: IOException: repo/branch #5 did not yet start
Title: Message Title Sam Van Oort commented on JENKINS-51290 Re: Builds fail to start with: IOException: repo/branch #5 did not yet start Second question Christoph Obexer do you have anything in your Jenkins logs along the lines of: "Nulling out FlowExecution due to error in build" or "failed to wait for"? Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Nalin Makar edited a comment on JENKINS-51341 Re: Suite name is not shown on the main page and method results page You are right, this plugin is up for adoption. But, if you make a pull request, I can help release it. Please add tests for your changes. And, can you add a screenshot of the problem you are encountering? Reading from the description, I would lean towards solution 2, but it'll be useful to understand what does that mean as an overall experience for 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-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Peter Sosnowski edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Jenkins: 2.120I have the this issue happening on all my slaves. - This started once i configured Jenkins to work over HTTPS (HTTP disabled). - This is happening regardless whether configured to run over HTTP or HTTPS All Java Web Start Agent protocols disabled except for protocol/4.By launching jenkins slave manually via javaws, I can see no issues and the slaves connect, however when I install it as a windows service that's where the issue appears. SEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:296) at hudson.remoting.Engine.run(Engine.java:267) Add Comment This 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-51341) Suite name is not shown on the main page and method results page
Title: Message Title Nalin Makar commented on JENKINS-51341 Re: Suite name is not shown on the main page and method results page You are right, this plugin is up for adoption. But, if you make a pull request, I can help release it. Please add tests for your changes. Add Comment This 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-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Peter Sosnowski commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Jenkins: 2.120 I have the this issue happening on all my slaves. This started once i configured Jenkins to work over HTTPS (HTTP disabled). All Java Web Start Agent protocols disabled except for protocol/4. By launching jenkins slave manually via javaws, I can see no issues and the slaves connect, however when I install it as a windows service that's where the issue appears. SEVERE: The server rejected the connection: None of the protocols were accepted java.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:296) at hudson.remoting.Engine.run(Engine.java:267) Add Comment This 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-27329) WorkspaceCleanupThread may delete workspaces of running jobs
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-27329
Re: WorkspaceCleanupThread may delete workspaces of running jobs
Also experienced for scripted pipeline (on master-only Jenkins installation): I think this issue should really just be fixed (instead of being addressed by implementing one of the various possible and more or less nice workarounds), especially because I hope it should not be too difficult for a Jenkins (core) developer? => I dare to put my money on [~jglick] ;-)According to https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/WorkspaceCleanupThread.java (see {{#shouldBeDeleted()}} method) there is "only special" support for {{AbstractProject}} (and thus {{FreeStyleProject}}) -- but even that is IMHO not 100% safe (only the workspace on the node of the last build is kept, i.e. in case of concurrently running builds it may delete the non-last still running one too)...My naive search in Jenkins JavaDoc only showed a very easy (but unfortunately also non-perfect) possibility, based onhttp://javadoc.jenkins-ci.org/hudson/model/Job.html#isBuilding--{code:java}if (item instanceof Job) { Job j = (Job) item; if (j.isBuilding()) {return false; }}{code}Here the problem might be that old workspaces on other nodes might never be deleted, I think. (Maybe that might be nonetheless still better than the current behaviour.)=> Actually only in case when {{Job#isBuilding()}} returns true, then all the (possible concurrent) running builds need to be checked and only their (active) workspace should be skipped from deletion? {color:#707070}=> Therefore still hoping and praying for Jesse...{color} (Very) naive PR: https://github.com/jenkinsci/jenkins/pull/3444
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
