[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title kpop commented on JENKINS-41867 Re: Scanning MultiBranchProject fails with IllegalStateException The attached plugin also fixes the issue for me. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35660) QTestLib time information is lost
Title: Message Title kpop assigned an issue to kpop Jenkins / JENKINS-35660 QTestLib time information is lost Change By: kpop Assignee: kpop Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35660) QTestLib time information is lost
Title: Message Title kpop updated an issue Jenkins / JENKINS-35660 QTestLib time information is lost Change By: kpop Component/s: xunit-plugin Component/s: junit-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35660) QTestLib time information is lost
Title: Message Title kpop assigned an issue to Unassigned Jenkins / JENKINS-35660 QTestLib time information is lost Change By: kpop Assignee: kpop Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35660) QTestLib time information is lost
Title: Message Title kpop updated an issue Jenkins / JENKINS-35660 QTestLib time information is lost Change By: kpop Environment: JUnit Plugin xUnit plugin 1. 13 102 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36244) Build number resets
Title: Message Title kpop closed an issue as Cannot Reproduce Thank you for the analysis, I'll try the suggested dead branch strategy. Jenkins / JENKINS-36244 Build number resets Change By: kpop Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50490) Provide lightweight checkout capability for Mercurial
Title: Message Title kpop created an issue Jenkins / JENKINS-50490 Provide lightweight checkout capability for Mercurial Issue Type: Bug Assignee: Unassigned Components: mercurial-plugin, pipeline Created: 2018-03-30 06:32 Environment: Jenkins 2.104 Mercurial 2.3 Priority: Minor Reporter: kpop JENKINS-33273 introduced a lightweight checkout capability to download a Jenkinsfile from source control without checkout out the entire repository, but it appears this hasn't been implemented for Mercurial: "Lightweight checkout support not available, falling back to full checkout." Add Comment
[JIRA] (JENKINS-50490) Provide lightweight checkout capability for Mercurial
Title: Message Title kpop updated an issue Jenkins / JENKINS-50490 Provide lightweight checkout capability for Mercurial Change By: kpop Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50490) Provide lightweight checkout capability for Mercurial
Title: Message Title kpop commented on JENKINS-50490 Re: Provide lightweight checkout capability for Mercurial Perhaps it's an option to use the repository browser to access the latest version of the specified Jenkinsfile? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50490) Provide lightweight checkout capability for Mercurial
Title: Message Title kpop commented on JENKINS-50490 Re: Provide lightweight checkout capability for Mercurial If my Mercurial source would be "http://myserver:8080/FolderName/RepoName" and the Jenkinsfile is located in "CI/Jenkinsfile", I'm able to get this Jenkinsfile through HTTP on "http://myserver:8080/FolderName/RepoName/raw-file/tip/CI/Jenkinsfile". Perhaps this is an easy solution to avoid the full checkout? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50663) Deadlock on jenkins startup
Title: Message Title kpop commented on JENKINS-50663 Re: Deadlock on jenkins startup Same here, workaround by Giuseppe Iannello allowed Jenkins to start again. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50663) Deadlock on jenkins startup
Title: Message Title kpop commented on JENKINS-50663 Re: Deadlock on jenkins startup On my setup, Sonar 2.7.1 fixes the startup issue. Thank you henryju for the quick fix! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50490) Provide lightweight checkout capability for Mercurial
Title: Message Title kpop commented on JENKINS-50490 Re: Provide lightweight checkout capability for Mercurial This is also described in the official documentation https://www.mercurial-scm.org/wiki/TipsAndTricks#Create_links_to_snapshots_of_files_and_tarballs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title kpop created an issue Jenkins / JENKINS-54640 Workspace folders are not unique Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-11-15 09:18 Environment: Jenkins 2.151 Priority: Critical Reporter: kpop Something changed in the naming of the workspace folders on the Jenkins Master node. Previously, the name the was suffixed with a long random (names are examples only, the exact length is different): MyProjectA1_MyBranch-ZOBMWQA2JSVUZRAPJAQ3NT3TSBIUQOS26N5CF3XJB@libs MyProjectA1_MyBranch-ZOBMWQA2JSVUZRAPJAQ3NT3TSBIUQOS26N5CF3XJB@script MyVeryLongBranchName-NHOUUZPM5MARPAN7OGASNLPNCKRLL26RQKEZIEEKC@libs MyVeryLongBranchName-NHOUUZPM5MARPAN7OGASNLPNCKRLL26RQKEZIEEKC@script MyVeryLongBranchName-TN6NSHXVGMKRKUOVV7CKNODZOK3JSHI4CQYCOR4E6@libs MyVeryLongBranchName-TN6NSHXVGMKRKUOVV7CKNODZOK3JSHI4CQYCOR4E6@script However now, this suffix seems to be removed, causing name clashes when different repositories have long but identical branch names: MyProjectA1_MyBranch@libs MyProjectA1_MyBranch@script MyVeryLongBranchName@libs<<-\ MyVeryLongBranchName@script | <<-\ MyVeryLongBranchName@libs<<-/ | MyVeryLongBranchName@script <<-/
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title kpop updated an issue Jenkins / JENKINS-54640 Workspace folders are not unique Change By: kpop Environment: Jenkins 2.151 pipeline 2.5pipeline-multibranch 2.20 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-54640) Workspace folders are not unique
Title: Message Title kpop updated an issue Jenkins / JENKINS-54640 Workspace folders are not unique Change By: kpop Component/s: pipeline-multibranch-defaults-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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title kpop commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Removing the 'garbage' at the end causes name clashes (cf. JENKINS-54540). 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title kpop commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Øyvind R, I agree: less is certainly better, but name clashes should be avoided. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title kpop edited a comment on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Removing the 'garbage' at the end causes name clashes (cf. JENKINS- 54540 54640 ). (edit: fixed issue link) 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-54640) Workspace folders are not unique
Title: Message Title kpop commented on JENKINS-54640 Re: Workspace folders are not unique Both ProjectA and ProjectB get the same directory in workspaces.txt for the two projects that build for Config1: Repo/ProjectA/Config1/BranchWithRatherLongName ktop_ID_209617_-_INSTALL_PHASE_2 Repo/ProjectB/Config1/BranchWithRatherLongName ktop_ID_209617_-_INSTALL_PHASE_2 The requested logging shows the same: 1122333 12345678901234567890123456789012 Nov 19, 2018 2:30:47 PM FINE allocating $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@bc4502 [Repo/ProjectA/Config1/BranchWithRatherLongName] Nov 19, 2018 2:33:44 PM FINER index already lists $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@bc4502 [Repo/ProjectA/Config1/BranchWithRatherLongName] Nov 19, 2018 2:40:51 PM FINE allocating $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@13f21b9[Repo/ProjectB/Config1/BranchWithRatherLongName] 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 htt
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title
kpop edited a comment on JENKINS-54640
Re: Workspace folders are not unique
Both ProjectA and ProjectB get the same directory in _workspaces.txt_ for the two projects that build for Config1:{noformat}Repo/ProjectA/Config1/BranchWithRatherLongName ktop_ID_209617_-_INSTALL_PHASE_2 Config1_BranchWithRatherLongName Repo/ProjectB/Config1/BranchWithRatherLongName ktop_ID_209617_-_INSTALL_PHASE_2 Config1_BranchWithRatherLongName {noformat}The requested logging shows the same:{noformat} 1122333 12345678901234567890123456789012Nov 19, 2018 2:30:47 PM FINE allocating $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@bc4502 [Repo/ProjectA/Config1/BranchWithRatherLongName]Nov 19, 2018 2:33:44 PM FINER index already lists $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@bc4502 [Repo/ProjectA/Config1/BranchWithRatherLongName]Nov 19, 2018 2:40:51 PM FINE allocating $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@13f21b9[Repo/ProjectB/Config1/BranchWithRatherLongName]{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-54640) Workspace folders are not unique
Title: Message Title kpop commented on JENKINS-54640 Re: Workspace folders are not unique Many thanks Jesse Glick for this quick fix! Just to be sure, I've also emptied my workspace folder. 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-54640) Workspace folders are not unique
Title: Message Title kpop closed an issue as Fixed Nov 21, 2018 8:23:35 AM FINE allocating $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@11fe5 [Repo/ProjectA/Config1/BranchWithRatherLongName] Nov 21, 2018 8:33:18 AM FINER index collision onConfig1_BranchWithRatherLongName for WorkflowJob@16ea9b8[Repo/ProjectB/Config1/BranchWithRatherLongName] Nov 21, 2018 8:33:18 AM FINE allocating $WORKSPACE/nfig1_BranchWithRatherLongName_2 for WorkflowJob@16ea9b8[Repo/ProjectB/Config1/BranchWithRatherLongName] The above log illustrates that collisions as correctly resolved by appending a something to the folder name to make it unique. That unique name is also correctly stored in workspaces.txt. Jenkins / JENKINS-54640 Workspace folders are not unique Change By: kpop Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title kpop commented on JENKINS-54640 Re: Workspace folders are not unique Lars-Magnus Skog, I believe that cutting of the folder names is intentional behavior. I see the same without loss of functionality. The workspaces.txt lists the full project name and project path, as well as the folder that is allocated for it. Josh Soref, check if the workspaces.txt still contains duplicate folder names. I've cleared my entire workspace and also removed that file to get it working. But it might also be sufficient to remove all duplicates in workspaces.txt and the corresponding folders. New collisions are avoided, but I'm unsure if existing collisions are also fixed automatically. 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-51287) Stage view overlaps test overview
Title: Message Title
kpop created an issue
Jenkins / JENKINS-51287
Stage view overlaps test overview
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
stage view overlaps test results.png
Components:
pipeline-stage-view-plugin
Created:
2018-05-14 07:53
Environment:
Jenkins v2.120 Pipeline: Stage View Plugin 2.10
Priority:
Minor
Reporter:
kpop
As shown on the attached screenshot, the stage view overlaps the test results, thus blocking access to the links in the test results ("show test # and failure #" and "enlarge").
Add Comment
[JIRA] [junit-plugin] (JENKINS-35660) QTestLib time information is lost
Title: Message Title kpop created an issue Jenkins / JENKINS-35660 QTestLib time information is lost Issue Type: Bug Assignee: Unassigned Attachments: MyTests_junit.xml, MyTests_qtestlib.xml Components: junit-plugin Created: 2016/Jun/13 6:56 AM Environment: JUnit Plugin 1.13 Priority: Major Reporter: kpop Although the original qtestlib files contain time information, the converted file does not. See attached MyTests_qtestlib.xml and MyTests_junit.xml
[JIRA] (JENKINS-35660) QTestLib time information is lost
Title: Message Title kpop commented on JENKINS-35660 Re: QTestLib time information is lost See 40184a9df572fa5d0ee4701517e92e556d58cf7b for possible solution. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36244) Build number resets
Title: Message Title kpop created an issue Jenkins / JENKINS-36244 Build number resets Issue Type: Bug Assignee: Matthew DeTullio Attachments: jenkins.log.1 Components: multi-branch-project-plugin Created: 2016/Jun/27 2:23 PM Environment: Jenkins 2.10 Priority: Minor Reporter: kpop For some reason the previous 87 builds for the CodeTests_all/default (CodeTests (all branches) default) were removed and the counter resets to 1. We'd like to keep the history. Can the attached log file indicate what caused this? Please advise. Line 2895 Jun 24, 2016 3:08:11 PM hudson.model.Run execute Line 2896 INFO: CodeTests_all/default #92 main build action completed: SUCCESS ... Line 4261 Jun 26, 2016 6:30:54 AM hudson.model.Run execute Line 4262 INFO: CodeTests_all/default #1 main build action completed: SUCCESS
[JIRA] (JENKINS-36244) Build number resets
Title: Message Title kpop updated an issue Jenkins / JENKINS-36244 Build number resets Change By: kpop Environment: Jenkins 2.10 , Multi-branch 0.4.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title kpop created an issue Jenkins / JENKINS-60644 scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2020-01-06 09:07 Environment: Ubuntu 14.04, Jenkins 2.212, Script Security Plugin 1.68 Priority: Blocker Reporter: kpop java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:183) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:189) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:193) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:100) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.c
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title kpop commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Many thanks for the quick response and new release. It's working fine on my installation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.3281.1578378300409%40Atlassian.JIRA.
[JIRA] (JENKINS-51287) Stage view overlaps test overview
Title: Message Title kpop commented on JENKINS-51287 Re: Stage view overlaps test overview I removed my workaround and it appears to be working correctly in version 2.12 of the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190621.1526284437000.8484.1571207222188%40Atlassian.JIRA.
