[JIRA] (JENKINS-62233) View Job Filter SCM RegEx Support Pipeline projects
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-62233 View Job Filter SCM RegEx Support Pipeline projects Issue Type: Bug Assignee: Sven Schoenung Components: view-job-filters-plugin Created: 2020-05-10 14:12 Priority: Minor Reporter: Sverre Moe The view-job-filters-plugin does not support Pipeline projects for filtering with Regular _expression_ SCM Configuration. It only supports three types of projects, instances of AbstractProject, SCMTriggerItem, and SCMedItem. https://github.com/jenkinsci/view-job-filters-plugin/blob/master/src/main/java/hudson/views/RegExJobFilter.java Need to support both MultibranchProject and WorkflowJob List MultibranchProject.getSCMSources() Collection WorkflowJob.getSCMs() Add Comment
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title Sverre Moe commented on JENKINS-29991 Re: view-job-filters-plugin with SCM Job Configuration not working I looked at the source code for the plugin. It does not support Pipeline og Multibranch Pipeline project. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.164570.1439858379000.24174.1589118480188%40Atlassian.JIRA.
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title Sverre Moe commented on JENKINS-29991 Re: view-job-filters-plugin with SCM Job Configuration not working We are using Jenkins LTS 2.222.3 and this does not work. The SCM filtering does not work as documented Regular _expression_ Job Filter: * SCM Configuration - this one is perhaps the best bang for the buck - put in something like "./my-office-name/." to automatically include all jobs that are organized under source control already by office. At least it does not work for the URL we are using ssh://g...@git.company.com/namespace/project.git regex: ./namespace/. It does not filter using this configuration. I have also tried with other regex patterns. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.164570.1439858379000.24032.1589103960297%40Atlassian.JIRA.
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title
Sverre Moe edited a comment on JENKINS-29991
Re: view-job-filters-plugin with SCM Job Configuration not working
We are using Jenkins LTS 2.222.3 and this does not work for Multibranch Pipelines .The SCM filtering does not work as documented{noformat}Regular _expression_ Job Filter:* SCM Configuration - this one is perhaps the best bang for the buck - put in something like "./my-office-name/." to automatically include all jobs that are organized under source control already by office.{noformat}At least it does not work for the URL we are using ssh://g...@git.company.com/namespace/project.gitregex: ./namespace/.It does not filter using this configuration. I have also tried with other regex patterns.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.164570.1439858379000.24037.1589103960437%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Sverre Moe edited a comment on JENKINS-26354 Re: First time build does not show changelog This issue has also been experienced on branches that had been rebased.If you rebase N-commits, for which thos commits was a part of the last builds changeset, then it will treat the new build as a first time build.Using ChangelogToBranch could work, but it will add additional boilerplate code to our pipeline, instead of just calling checkout scm.For use it is useless to configure it for the job, because we do not know the base branch (compareTarget) until the job has started. Does the git plugin check for changes using the git commit hash or message?If it detects "first time build", then it should use the latest commit as changeset.Build #1> Commit message: "fix: Correct this method"> First time build. Skipping changelogRebase commit, new hash, same message.Build #2> Commit message: "fix: Correct this method"> First time build. Skipping changelog Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.160018.1420800265000.21112.1588595940449%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Sverre Moe commented on JENKINS-26354 Re: First time build does not show changelog This issue has also been experienced on branches that had been rebased. If you rebase N-commits, for which thos commits was a part of the last builds changeset, then it will treat the new build as a first time build. Using ChangelogToBranch could work, but it will add additional boilerplate code to our pipeline, instead of just calling checkout scm. For use it is useless to configure it for the job, because we do not know the base branch (compareTarget) until the job has started. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.160018.1420800265000.21020.1588590600513%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Sverre Moe commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Cleaned up, how? We also have experienced this problem that past few months. Recently we upgraded our Jenkins server Linux distribution from SLES12.3 to SLES15.0. This was done by creating a new VM and copied over the JENKINS_HOME. It has been running for 4 days now and we have not gotten the OutOfMemoryError. More time will tell if it is truly stable again. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.7235.1566412800681%40Atlassian.JIRA.
[JIRA] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
Title: Message Title Sverre Moe commented on JENKINS-21099 Re: Don't give useless build time estimates by considering failed builds' durations An very old issue. Is there anyone who could do anything to implement this? We would like failed build to be excluded as well from the average calculation. Perhaps a way to configure this would be preferable, so that it would work as before, but allow others to add excludes criteria. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152661.138748788.7773.1564994700517%40Atlassian.JIRA.
[JIRA] (JENKINS-53139) pipeline stage view plugin should be officially deprecated in favor of Blue Ocean
Title: Message Title Sverre Moe commented on JENKINS-53139 Re: pipeline stage view plugin should be officially deprecated in favor of Blue Ocean As some are still using Jenkins Classic UI this plugin is still needed. Blue Ocean though cannot show stage build times for each builds in a matrix like this plugin does. You can only see the total build time in Blue Ocean for a specific job. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193141.1534778467000.7770.1564994281062%40Atlassian.JIRA.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Sverre Moe commented on JENKINS-57158 Re: Pipeline is green but shows red in stage view We have noticed the same on our Multibranch pipelines. All stages are good, but Stage View still shows the build as failed. It is very rare when it occurs. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198908.1556031734000.7764.1564994040355%40Atlassian.JIRA.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) There is another issue I have been tracking I think can be related to our problem of slowness. JENKINS-49319 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.736.1562146921678%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I can test the incremental release on our Test Jenkins instance. I dare not install it in production. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.266.1562099580979%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Looking forward to testing it out. Our developers are getting frustrated. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.168.1562089021091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) We have disabled the Remember Me option and still experience the slowness. The slowness only happens when users are not logged in. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.12157.1561806600944%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-58130 JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Change By: Sverre Moe Component/s: coverity-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200175.1561064567000.10825.1561654200389%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Sverre Moe commented on JENKINS-58130 Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException I changed the component to synopsys-coverity-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200175.1561064567000.10827.1561654200421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-58130 JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Change By: Sverre Moe Component/s: synopsys-coverity-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200175.1561064567000.10822.1561654200355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Sverre Moe commented on JENKINS-58130 Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException It would seem the new Coverity Plugin has similar shortcomings running on Jenkins with Java 11. 1) Error injecting constructor, java.lang.NoClassDefFoundError: javax/xml/ws/WebServiceException at com.synopsys.integration.jenkins.coverity.extensions.wrap.CoverityEnvironmentWrapper$DescriptorImpl.(CoverityEnvironmen tWrapper.java:169) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200175.1561064567000.10818.1561654080127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Sverre Moe commented on JENKINS-58130 Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Thanks. I wasn't aware of that. I guess then this is a no issue. Will try the new plugin and see if it is running fine with Java 11. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200175.1561064567000.10815.1561653780185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-56243 Jenkins GUI is slow -removing cookie fixes it (temporarily) Change By: Sverre Moe Labels: user-experience 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.5305.1561106403471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title
Sverre Moe edited a comment on JENKINS-56243
Re: Jenkins GUI is slow -removing cookie fixes it (temporarily)
The last remaining loading on Multibranch Pipeline branch project. Developer Tools in my browser showed me what was remaining trying to load.{code}ajax 200 xhr prototype.js:1585 310 B 15 msruns?since=%232=true&_=1561103938220 200 xhr jquery2.js:998 48.8 KB 18 m ms {code}These two repeated several times for about 30+ seconds until the page was actually finished loading.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.5298.1561104781483%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title
Sverre Moe edited a comment on JENKINS-56243
Re: Jenkins GUI is slow -removing cookie fixes it (temporarily)
The last remaining loading on Multibranch Pipeline branch project. Developer Tools in my browser showed me what was remaining trying to load. {code} ajax 200 xhr prototype.js:1585 310 B 15 msruns?since=%232=true&_=1561103938220 200 xhr jquery2.js:998 48.8 KB 18 m {code} These two repeated several times for about 30+ seconds until the page was actually finished loading.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.5263.1561104722528%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) The last remaining loading on Multibranch Pipeline branch project. Developer Tools in my browser showed me what was remaining trying to load. ajax 200 xhr prototype.js:1585 310 B 15 ms runs?since=%232=true&_=1561103938220 200 xhr jquery2.js:998 48.8 KB 18 m These two repeated several times for about 30+ seconds until the page was actually finished loading. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.5195.1561104720763%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49319) Old Prototype library causes problems with modern UI frameworks
Title: Message Title Sverre Moe commented on JENKINS-49319 Re: Old Prototype library causes problems with modern UI frameworks This issue caught my eye, when I was trying to solve the Jenkins slow loading problem reported in JENKINS-56243. After upgrading to Jenkins 2.181 loading was fast again, but for some multibranch projects loading a branch seemd to load completely, but hang in there for 30+ seconds and it seems prototype.js was the culprit that did not quite finish. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188182.1517516764000.5185.1561102620180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I have been trying Jenkins 2.181 on our Jenkins Test server. Really fast loading of UI, not seeing any slowness.Though the Jenkins Test server does not have as much build history, the real test would be to upgrade our Jenkins Production server.Edit: Until I went to Manage Jenkins, then loading the icons just hanging page loading.Edit: Opening a multibranch project branch, the page seems to have loaded completely, but loading is still ongoing for some more ~30 seconds. Looked at what was loading and seems to be prototype.js. There was an fix for this in JENKINS-49319, but it was reverted.Firefox is having much more problems than browsers with the Chromium engine. So it seems to be a _javascript_ problem that last loading. Edit:All good things must come to an end: Now I am getting the same problem in Chrome. Several resources are not loading. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.5115.1561102382040%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I have been trying Jenkins 2.181 on our Jenkins Test server. Really fast loading of UI, not seeing any slowness.Though the Jenkins Test server does not have as much build history, the real test would be to upgrade our Jenkins Production server.Edit: Until I went to Manage Jenkins, then loading the icons just hanging page loading. Edit: Opening a multibranch project branch, the page seems to have loaded completely, but loading is still ongoing for some more ~30 seconds. Looked at what was loading and seems to be prototype.js. There was an fix for this in JENKINS-49319, but it was reverted.Firefox is having much more problems than browsers with the Chromium engine. So it seems to be a _javascript_ problem that last loading. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.5080.1561102261707%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-58130 JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Issue Type: Bug Assignee: Synopsys SIG Components: core, coverity-plugin Created: 2019-06-20 21:02 Labels: java11-compatibility Priority: Minor Reporter: Sverre Moe Running Jenkins 2.181 got an ClassNotFoundException from CoverityPublisher on javax.xml.ws.WebServiceException. Add Comment
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I have been trying Jenkins 2.181 on our Jenkins Test server. Really fast loading of UI, not seeing any slowness.Though the Jenkins Test server does not have as much build history, the real test would be to upgrade our Jenkins Production server. Edit: Until I went to Manage Jenkins, then loading the icons just hanging page loading. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.4920.1561063800660%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I have been trying Jenkins 2.181 on our Jenkins Test server. Really fast loading of UI, not seeing any slowness. Though the Jenkins Test server does not have as much build history, the real test would be to upgrade our Jenkins Production server. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.4817.1561062780834%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57819) Blue Ocean does not show all steps in stage
Title: Message Title
Sverre Moe created an issue
Jenkins / JENKINS-57819
Blue Ocean does not show all steps in stage
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screenshot_20190603_141521.png, Screenshot_20190603_141527.png
Components:
blueocean-plugin
Created:
2019-06-03 12:17
Labels:
blueocean steps
Priority:
Major
Reporter:
Sverre Moe
Blue Ocean only shows up to 100 steps on Stage
stage("Stage") {
node("master") {
for (int i = 0; i < 120; i++) {
println "Loop number " + i
}
}
}
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) We have tried several workarounds. None of them works. Disable security LDAP (Logged-in users can do anything) LDAP (Anyone can do anything) Disable remember me Downgrade to Jenkins LTS 2.150.1 Our users still experience that Jenkins UI is slow and loading takes time, sometimes hang. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.17314.1559302380857%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Sverre Moe commented on JENKINS-39343 Re: Persistent search/overviews/filtered views I welcome this feature to Blue Ocean. It is an old issue and I hope it is not been ignored or worse dismissed. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Well if it doesn't , the downgrading to Jenkins LTS 2.150.1 worked on our Test Jenkins, so we have that to fall back to if it doesn't work. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Well if it doesn't downgrading to Jenkins LTS 2.150.1 worked on our Test Jenkins, so we have that to fall back to if it doesn't work. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So the workaround -Djenkins.security.seed.UserSeedProperty.disableUserSeed=true will not fix this issue?It says its a workaround for SECURITY-901 which mentioned in the description here caused the regression. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So the workaround -Djenkins.security.seed.UserSeedProperty.disableUserSeed=true will not fix this issue? It says its a workaround for SECURITY-901 which mentioned in the description caused the regression. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I was unaware of the opensuse-stable builds. So this is the Jenkins LTS releases.I tried to downgrade to the 2.150.1 LTS and it worked with our installed plugins. The LTS upgrade guide seems to have a workaround for this bughttps://jenkins.io/doc/upgrade-guide/2.150/ 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I was unaware of the opensuse-stable builds. So this is the Jenkins LTS releases. I tried to downgrade to the 2.150.1 LTS and it worked with our installed plugins. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I cannot find a 2.150.2, mentioned above but 2.150-1.2https://pkg.jenkins.io/opensuse/jenkins-2.150-1.2.noarch.rpmI Just tried to downgrade to 2.149 and it did not go so well, as several plugins do not work now.Our users are having serous serious trouble with slow Jenkins user experience. I hope this can be fixed soon. 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I cannot find a 2.150.2, mentioned above but 2.150-1.2 https://pkg.jenkins.io/opensuse/jenkins-2.150-1.2.noarch.rpm I Just tried to downgrade to 2.149 and it did not go so well, as several plugins do not work now. Our users are having serous trouble with slow Jenkins user experience. I hope this can be fixed soon. 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Sverre Moe commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free An installer for JDK from AdoptOpenJDK would be a welcoming addition. The Oracle OpenJDK 11 LTS builds will only receive updates for 6 months, while AdoptOpenJDK will commit to providing builds until LTS EOL. OpenJDK provides a new feature release every six months, and a maintenance/security update based upon each active release every three months. We will follow this schedule for publishing binary releases from AdoptOpenJDK to ensure you get the latest, most secure builds. In addition, every three years one feature release will be designated as the Long Term Supported (LTS) release. We will produce LTS releases for at least four years. This assurance will allow you to stay on a well-defined code stream, and give you time to migrate to the next, new, stable, LTS release when it becomes available. Though we still need the Oracle JDK Installer, for those who still use an older JDK. We have some legacy application using JDK 1.6 and JDK 1.7. I like Baptiste Mathus suggestion of Using a repository manager like Nexus to get the JDK. Then you could get the JDK from your preferred source. 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout()def stderr = returnObj.getStderr(){code}Using a Map you would need to know the keys therein, but with a POJO you can use the javadoc to know the getters.Perhaps the parameter flags returnStatus, returnStdout, returnStderr would not be necessary. It would could just return the POJO, and you could either use it or not.
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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout() def stderr = returnObj.getStderr() {code}Using a Map you would need to know the keys therein, but with a POJO you can use the javadoc to know the getters.Perhaps the parameter flags returnStatus, returnStdout, returnStderr would not be necessary. It would just return the POJO, and you could either use it or not.
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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout(){code}Using a Map you would need to know the keys therein, but with a POJO you can use the javadoc to know the getters. Perhaps the parameter flags returnStatus, returnStdout, returnStderr would not be necessary. It would just return the POJO, and you could either use it or not.
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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout(){code}Using a Map you would need to know the values keys therein, but with a POJO you can use the javadoc to know the getters.
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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Sverre Moe commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once It would be better using a specific POJO than a Map. def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches") def status = returnObj.getStatus() def stdout = returnObj.getStdout() Using a Map you would need to know the values therein, but with a POJO you can use the javadoc to know the getters. 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-54104) Blueocean cannot display 10 downstream jobs
Title: Message Title Sverre Moe edited a comment on JENKINS-54104 Re: Blueocean cannot display 10 downstream jobs I wonder if this could be related to a problem I am having with Blue Ocean.We do not trigger build on downstream projects, but instead in a verification stage, iterates through all downstream dependencies and build them (it is a lot faster than starting independent builds) . There are roughly 6 steps per downstream, building 20-30+ projects. Blue Ocean does not show all the steps in this stage, it cuts off after a certain number. 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-54104) Blueocean cannot display 10 downstream jobs
Title: Message Title Sverre Moe commented on JENKINS-54104 Re: Blueocean cannot display 10 downstream jobs I wonder if this could be related to a problem I am having with Blue Ocean. We do not trigger build on downstream projects, but instead in a verification stage, iterates through all downstream dependencies and build them. There are roughly 6 steps per downstream, building 20-30+ projects. Blue Ocean does not show all the steps in this stage, it cuts off after a certain number. 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-54104) Blueocean cannot display 10 downstream jobs
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-54104 Blueocean cannot display 10 downstream jobs Change By: Sverre Moe Comment: I have seen the same problem. Starting 20-30+ downstream jobs in sequence it does not show them all in Blue Ocean. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54104) Blueocean cannot display 10 downstream jobs
Title: Message Title Sverre Moe commented on JENKINS-54104 Re: Blueocean cannot display 10 downstream jobs I have seen the same problem. Starting 20-30+ downstream jobs in sequence it does not show them all in Blue Ocean. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44834) Gradle pipeline support: withGradle and ConsoleAnnotator
Title: Message Title Sverre Moe commented on JENKINS-44834 Re: Gradle pipeline support: withGradle and ConsoleAnnotator What is the status for this feature? Will it be done, and when can we expect it to be done? 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Sverre Moe commented on JENKINS-48300 Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 We are using durable-task-plugin 1.23, but are still seeing this problem. According to the changelog it was fixed in version 1.18 A few(4-5) weeks ago we didn't have this problem, then yesterday we upgraded Jenkins and all our plugins. Now it fails building on Windows. [Native master-windows7-x86_64] wrapper script does not seem to be touching the log file in C:\cygwin64\home\build\jenkins\workspace\applicationA_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp\durable-0ead6a5b [Native master-windows7-x86_64] (JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) Is the workaround mentioned above the actual fix that was fixed in version 1.18? We have been using it for months without seeing a problem. We are not having the problem now when started Jenkins with that system property. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45614) Activity tab is really slow
Title: Message Title Sverre Moe edited a comment on JENKINS-45614 Re: Activity tab is really slow [~olamy] Very few of our projects have actually test results that are published by Jenkins with JUnitResultArchiver. Most of our projects are C/C++ with Google Test, but few creates a test output to publish in Jenkins. Even projects without any tests results recorded by Jenkins take a long time to load initially. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45614) Activity tab is really slow
Title: Message Title Sverre Moe commented on JENKINS-45614 Re: Activity tab is really slow Olivier Lamy Very few of our projects have actually test results that are published by Jenkins with JUnitResultArchiver. Even projects without any tests results recorded by Jenkins take a long time to load initially. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Sverre Moe commented on JENKINS-37369 Re: Multibranch Pipeline: Last build information is not propagated to Jenkins View It seems this is halfway implemented. We get information on Last Success and Last Duration, but not Last Failure, that is still showing N/A. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24353) "UI Themes" plugin
Title: Message Title Sverre Moe commented on JENKINS-24353 Re: "UI Themes" plugin This plugin looks dead https://github.com/jenkinsci/jenkins/pull/1524 The plugin URL is dead from Jenkins PluginManager http://jenkins-ci.org/plugin/uithemes-pom/uithemes/ https://github.com/jenkinsci/uithemes-plugin During startup we are getting the following warning Apr 26, 2018 7:59:16 AM jenkins.model.Jenkins$5 runTask WARNING: Initializing plugin uithemes failed perhaps due to plugin dependency issues java.lang.NoSuchMethodError: org.jenkins.ui.icon.Icon.setUseCSSRendering(Z)Lorg/jenkins/ui/icon/Icon; at org.jenkinsci.plugins.uithemes.UIThemesPlugin.postInitialize(UIThemesPlugin.java:44) at hudson.PluginManager$2$1$2.run(PluginManager.java:540) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1062) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Though since we didn't use the plugin we have now uinstalled it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-15355) AdjunctManager: exception upon startup
Title: Message Title Sverre Moe commented on JENKINS-15355 Re: AdjunctManager: exception upon startup We are getting this in every startup with Jenkins. We just upgraded to 2.118 and it is still there. WARNING: AdjunctManager is not installed for this application. Skipping tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:397) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:64) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:169) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at
[JIRA] (JENKINS-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Title: Message Title Sverre Moe commented on JENKINS-17488 Re: java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Can we get this addressed? This warning is filling up almost 90% of our Jenkins log. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50923) Blue Ocean: When step failed, the last step also marked failed
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-50923 Blue Ocean: When step failed, the last step also marked failed Change By: Sverre Moe Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50923) Blue Ocean: When step failed, the last step also marked failed
Title: Message Title Sverre Moe commented on JENKINS-50923 Re: Blue Ocean: When step failed, the last step also marked failed This issue might be ralted to JENKINS-46551. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50923) Blue Ocean: When step failed, the last step also marked failed
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-50923 Blue Ocean: When step failed, the last step also marked failed Issue Type: New Feature Assignee: Unassigned Attachments: Spectacle.TJ7537.png Components: blueocean-plugin, pipeline Created: 2018-04-21 09:22 Environment: Jenkins 2.117 Pipeline latest versions at issue creation Blue Ocean 1.5.0 Oracle Java 8u144 SUSE Linux Enterprise Server 12 SP3 Chromium 64 Priority: Minor Reporter: Sverre Moe In Blue Ocean the last step is always marked failed when a different step has failed. The step that actually failed is a few steps earlier. I have deleteDir() at the very last in try-catch-finally on every parallel build node. This on order to clean up. It says this step has failed, even though it has not. "Recursively delete the current directory from the workspace" Blue Ocean has this step marked as failed. It is always the last step that fails, in addition to the actually failed step. If I remove deleteDir() it is the previous step that now is marked as failed. The steps that are executed after the actual failed step is within a finally clause of try-catch.
[JIRA] (JENKINS-45614) Activity tab is really slow
Title: Message Title Sverre Moe commented on JENKINS-45614 Re: Activity tab is really slow This is really a cause for concern for us. It is hard to sell Jenkins to our developers with this load time. It was still slow after upgrading to Blue Ocean v1.5, running Jenkins 2.117 on Java 8u144. I sent Vivek Pandey a HAR recording from our Jenkins a few days ago. I am going to try a fresh install of Jenkins and set up all our pipelines and see if Blue Ocean is still slow after a few runs. Considering that Cloudbees own public dogfood Jenkins server loads Blue Ocean pretty fast, it might perhaps be some problem with our configuration or some of the installed plugins. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29913) Generalize DependencyGraph to Job (or ParameterizedJobMixIn)
Title: Message Title
Sverre Moe commented on JENKINS-29913
Re: Generalize DependencyGraph to Job (or ParameterizedJobMixIn)
A much needed feature. A solution has been made for the Pipeline Maven Plugin and its PipelineGraphPublisher, but that will not helps us where the majority of our projects are C/C++. For C/C++ projects where build requirements are stored in RPM spec files we must implement some solution in our pipeline shared library. In our pipeline we iterate through all projects in Jenkins build view, check out and parse their RPM spec file, find all downstream dependencies from the extracted build requirements. Then executes verification builds on each of them. This adds unnecessary complexity and build time to our build pipeline. However this does only give us direct dependencies, and not all transitive dependencies, so I even considered taking the code from DependencyGraph to use in our Pipeline, but it was not feasible. If we had the DependencyGraph for Pipeline and Multibranch Pipeline projects we could just at every SCM change update the projects upstream dependencies. Then later in the pipeline trigger build of all transitive dependencies.
stage("checkout") {
checkout scm
def downstreamProjects = findAllDownstreamProjects()
currentBuild.setDownstreamProjects(downstreamProjects)
build()
}
stage("verify") {
def deps = currentBuild.getTransitiveDownstream()
deps.each { dep -> build name: dep }
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title
Sverre Moe commented on JENKINS-41845
Re: Suppress default pipeline output
Examples for using the CSS class pipeline-annotated would be nice.
.pipeline-annotated {
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Title: Message Title Sverre Moe commented on JENKINS-17488 Re: java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult We have this problem also. A slightly different stack trace looks like problem is relatated to BlueOcean Running Jenkins 2.114 BlueOcean 1.4.2 TAP Plugin 2.2.1 step([$class: "TapPublisher", testResults: "test-suite.log"]) Mar 08, 2018 1:40:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving https://build-ci.company.com:8443/view/systems/job/packageA/job/master/tapResults/graph java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at
[JIRA] (JENKINS-38264) Add support for Jenkins Pipeline to the doxygen-plugin
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-38264 Add support for Jenkins Pipeline to the doxygen-plugin Change By: Sverre Moe Labels: pipeline 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-38264) Add support for Jenkins Pipeline to the doxygen-plugin
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-38264 Add support for Jenkins Pipeline to the doxygen-plugin Issue Type: Improvement Assignee: Lionel Cabasson Components: doxygen-plugin Created: 2016/Sep/16 8:54 AM Priority: Minor Reporter: Sverre Moe 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
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-31155 Workflow shared library improvements Change By: Sverre Moe Comment: Is the change backward compatible? If I upgrade would workflowLibs.git still work or do I need to change it to use library step? 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-31155) Workflow shared library improvements
Title: Message Title Sverre Moe commented on JENKINS-31155 Re: Workflow shared library improvements Is the change backward compatible? If I upgrade would workflowLibs.git still work or do I need to change it to use library step? 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-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-35096 Add support for Jenkins Pipeline to the cppcheck-plugin Change By: Sverre Moe Issue Type: Bug Improvement 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe Component/s: workflow-multibranch-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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe An SCM Change is no longer depicted in Build History as a badge icon.Instead it shows a Question mark badge icon with the tooltip "Branch indexing".Using Jenkins URL notifyCommit to notify of SCM changes. https://jenkins.company.com:8443/git/notifyCommit?url=""> Want the ++/-- SCM change badge icon to indicate when a build is triggered from an SCM change. 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe An SCM Change is no longer depicted in Build History as a badge icon.Instead it shows a Question mark badge icon with the tooltip "Branch indexing".Using Jenkins URL notifyCommit to notify of SCM changes.https://jenkins.company.com:8443/git/notifyCommit?url=""> .git Want the ++/-- SCM change badge icon to indicate when a build is triggered from an SCM change. 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe Attachment: pipelinescmchange1.png 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/15 6:40 AM Environment: Jenkins 2.17 workflow-multibranch 2.8 Labels: Pipeline Priority: Minor Reporter: Sverre Moe An SCM Change is no longer depicted in Build History as a badge icon. Instead it shows a Question mark badge icon with the tooltip "Branch indexing". Using Jenkins URL notifyCommit to notify of SCM changes. Want the ++/-- SCM change badge icon to indicate when a build is triggered from an SCM change. Add Comment
[JIRA] (JENKINS-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Sverre Moe Attachment: jenkinspipeline1.png 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Sverre Moe Attachment: jenkinspipeline2.png 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Issue Type: Improvement Assignee: stephenconnolly Components: branch-api-plugin, workflow-multibranch-plugin Created: 2016/Aug/12 7:21 AM Environment: Jenkins 2.17, workflow-multibranch 2.8 Labels: Pipeline Priority: Minor Reporter: Sverre Moe The build information Last Success, Last Failure and Last Duration is not propagated to the Jenkins view. The Jenkins view showing the multibranch pipeline folder always shows N/A. The latest built branch should propagate this build information to the outside view. Add Comment
[JIRA] (JENKINS-32354) Provide support of Coverity runs from Workflow plugin
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-32354 Provide support of Coverity runs from Workflow plugin Change By: Sverre Moe Labels: Pipeline workflow 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-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title
Sverre Moe edited a comment on JENKINS-30206
Re: Multibranch plugin: Modified properties do not propagate to existing branches
What is I had the status of this issue?Defined parameters are same problem accessing the defined parameter. The parameter was not accessible and an an environment parameter. I am stuck with further development of my build script without this found an example that worked for me . {code} Unless this is a different issue from my problem def param = false To define parameters within Jenkinsfile will update the branch project and make it parameterized if (getBinding() . However the next build does not pass that parameter. Accessing it with env.PARAM is always null. hasVariable("MY_PARAM")) {param = MY_PARAM}{code}
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-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-34981 Make valgrind-plugin compatible with pipeline Change By: Sverre Moe Labels: Pipeline 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-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Sverre Moe edited a comment on JENKINS-30206 Re: Multibranch plugin: Modified properties do not propagate to existing branches What is the status of this issue?Defined parameters are not accessible and I am stuck with further development of my build script without this. Unless this is a different issue from my problemTo define parameters within Jenkinsfile will update the branch project and make it parameterized. However the next build does not pass that parameter. Accessing it with env.PARAM is always null. 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-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Sverre Moe commented on JENKINS-30206 Re: Multibranch plugin: Modified properties do not propagate to existing branches What is the status of this issue? Defined parameters are not accessible and I am stuck with further development of my build script without this. 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-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-35096 Add support for Jenkins Pipeline to the cppcheck-plugin Change By: Sverre Moe Labels: Pipeline workflow 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-35256) Pipeline script fails with files camelCased in workflowLibs.git/vars
Title: Message Title
Sverre Moe edited a comment on JENKINS-35256
Re: Pipeline script fails with files camelCased in workflowLibs.git/vars
Running on Linux.vars/myTestFile.groovy{code}def getValue() { return "Hello World"} {code} src/Build.groovy{code}def value = myTestFile.getValue(){code}I no longer have the problem. Not sure what fixed it.
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-35256) Pipeline script fails with files camelCased in workflowLibs.git/vars
Title: Message Title
Sverre Moe commented on JENKINS-35256
Re: Pipeline script fails with files camelCased in workflowLibs.git/vars
Running on Linux. vars/myTestFile.groovy
def getValue() {
return "Hello World"
}
src/Build.groovy
def value = myTestFile.getValue()
I no longer have the problem. Not sure what fixed it.
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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Sverre Moe commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) How do you run postbuild from within jenkinsfile itself, the "manager" object is not available when it runs The manager object should be available if you have installed the Groovy Postbuild 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-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Sverre Moe edited a comment on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin The GitHub Cobertura issues#50 at https://github.com/jenkinsci/cobertura-plugin/issues/50 shows an update 6 hours ago by [~mbarrien] referencing this issue 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-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Sverre Moe commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin The GitHub Cobertura issues#50 at https://github.com/jenkinsci/cobertura-plugin/issues/50 shows an update 6 hours ago by Michael Barrientos 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] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title Sverre Moe commented on JENKINS-34943 Re: Add support for Jenkins Pipeline Jesse Glick Mentioned something about this implementation on GitHub And whoever did this integration seems to have done it incorrectly. There is a dedicated NexusArtifactUploaderStep producing a nexusArtifactUploader step; and NexusArtifactUploader was made to implement SimpleBuildStep, meaning it will appear as an option to the step metastep. You only want to do one or the other, not both. There are other problems in the integration, especially that nexusPassword is passed as a String, which is insecure (must use Credentials instead), but that does not matter here for purposes of recording what the integration consisted of. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25164) Provide a short $JOB_NAME inside a folder
Title: Message Title Sverre Moe commented on JENKINS-25164 Re: Provide a short $JOB_NAME inside a folder Not sure if it is intentional With Jenkins pipeline the JOB_BASE_NAME is same as BRANCH_NAME instead of the actual project name. BRANCH_NAME=master JOB_NAME=projectA/master JOB_BASE_NAME=master The value for JOB_BASE_NAME should be in this case projectA. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Sverre Moe commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin Old issue. Hope to see a fix soon. Now with Jenkins 2.0 pipelines will become more prevalent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Sverre Moe edited a comment on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin Old issue. Hope to see a fix soon. Now with Jenkins 2.0 , pipelines will become more prevalent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-35487) Add support for Jenkins Pipeline to the cobertura-plugin
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-35487 Add support for Jenkins Pipeline to the cobertura-plugin Issue Type: Improvement Assignee: stephenconnolly Components: cobertura-plugin Created: 2016/Jun/09 7:05 AM Labels: Pipeline Priority: Minor Reporter: Sverre Moe Add support for Jenkins pipeline Add Comment
[JIRA] [workflow-multibranch-plugin] (JENKINS-35256) Pipeline script fails with files camelCased in workflowLibs.git/vars
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-35256 Pipeline script fails with files camelCased in workflowLibs.git/vars Change By: Sverre Moe Summary: Pipeline script fails with files camelCased in workflowLib workflowLibs .git/vars Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-multibranch-plugin] (JENKINS-35256) Pipeline script fails with files camelCased in workflowLib.git/vars
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-35256 Pipeline script fails with files camelCased in workflowLib.git/vars Issue Type: Bug Assignee: Manuel Recena Soto Components: workflow-multibranch-plugin, workflow-plugin Created: 2016/Jun/01 7:39 AM Labels: pipeline Priority: Minor Reporter: Sverre Moe Scripts within workflowLib.git/vars does not work if file name convention is camelCased This naming does not work: vars/camelCased.groovy I get the following exception when calling a function camelCased.init() java.lang.NullPointerException: Cannot invoke method init() on null object This works vars/camelcased.groovy According to Pipeline Global Library documentation on GitHub The vars directory hosts scripts that define global variables accessible from Pipeline scripts. The basename of each *.groovy file should be a Groovy (~ Java) identifier, conventionally camelCased.
[JIRA] [cppcheck-plugin] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-35096 Add support for Jenkins Pipeline to the cppcheck-plugin Change By: Sverre Moe Add support for Jenkins Pipeline with Cppcheck Pluginhttps://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck-plugin] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-35096 Add support for Jenkins Pipeline to the cppcheck-plugin Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck-plugin Created: 2016/May/24 2:15 PM Labels: pipeline Priority: Minor Reporter: Sverre Moe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-26126) DSLD and/or GDSL
Title: Message Title Sverre Moe commented on JENKINS-26126 Re: DSLD and/or GDSL Any time frame when DSLD will be available in Jenkins? Running version 2.5 I still se only GDSL available. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-34943 Add support for Jenkins Pipeline Change By: Sverre Moe Add support for Jenkins Pipeline with Nexus Artifact Uploaderhttps://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
