[JIRA] (JENKINS-56863) Cloud stats persistence file grows continually
Title: Message Title Dennis Keitzel commented on JENKINS-56863 Re: Cloud stats persistence file grows continually To add on this: There is actually a default limit of 100 entries to be logged. This is indeed true and corresponds with the persistence file: xmlstarlet sel -t -v 'count(//org.jenkinsci.plugins.cloudstats.CloudStatistics/log/data/org.jenkinsci.plugins.cloudstats.ProvisioningActivity)' org.jenkinsci.plugins.cloudstats.CloudStatistics.xml.bak 100 However, there are lots of active provisionings in that 150MB file: xmlstarlet sel -t -v 'count(//org.jenkinsci.plugins.cloudstats.CloudStatistics/active/org.jenkinsci.plugins.cloudstats.ProvisioningActivity)' org.jenkinsci.plugins.cloudstats.CloudStatistics.xml.bak 52680 24h after purging the persistence file, the number of active provisionings already reached 3225. 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-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Matt Dee commented on JENKINS-54278 Re: Pipeline builds fail when cleanWs() in post stage Having the exact same problem, seems completely random when it happens. Cannot reliably reproduce. Very annoying. Jenkins ver. 2.150.3 ws-cleanup 0.37 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-42614) Pipeline support in EnvInject
Title: Message Title Swanand Gajendragadkar commented on JENKINS-42614 Re: Pipeline support in EnvInject As per description, there are multiple workarounds. Can anybody put link to workaround page, or mention some workarounds here? 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-56392) blue-ocean links from classic do not use https
Title: Message Title Björn Pedersen commented on JENKINS-56392 Re: blue-ocean links from classic do not use https Yes, in the current version the redirect goes to https. But it still does not work correctly: Link in the classic UI to blue ocean: https://forge.frm2.tum.de/jenkins/blue/organizations/jenkins/Administration%2FDeployWebapps First response is (note that now the escaped slash has been expanded): HTTP/1.1 302 Found Date: Thu, 04 Apr 2019 05:15:22 GMT Server: Jetty(9.4.z-SNAPSHOT) X-Content-Type-Options: nosniff X-Blueocean-Refresher: f4df0e2b Location: https://forge.frm2.tum.de/jenkins/blue/organizations/jenkins/Administration/DeployWebapps/ Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Setup: Apache in front of jenkins, so it seems it is the redirect to append the missing slash at the end that causes this behaviour (Manually add the slash results in a successful page load) 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-56865) Password to access InfluxDB is stored unencrypted on disk
Title: Message Title Aleksi Simell commented on JENKINS-56865 Re: Password to access InfluxDB is stored unencrypted on disk You're absolutely true. It should use Jenkins credentials instead. I'll see what I can do. 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-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title Josh McDonald stopped work on JENKINS-55605 Change By: Josh McDonald Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title Josh McDonald commented on JENKINS-55605 Re: can only click on the first active parallel stage, others running but cannot click This part of the codebase is too brittle, I'm putting this issue back on the shelf for now. 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-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title Josh McDonald edited a comment on JENKINS-55605 Re: can only click on the first active parallel stage, others running but cannot click -I think I've got it solved without breaking anything :)- -- -It's a bit of a maze in that part of the codebase, and the issue was caused by some old code trying to grok the graph that was unaware of the relatively new support for sequential-stage parallel branches.- -- -PR here- [-https://github.com/jenkinsci/blueocean-plugin/pull/1941-] 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-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title Josh McDonald edited a comment on JENKINS-55605 Re: can only click on the first active parallel stage, others running but cannot click - I think I've got it solved without breaking anything :) - -- - It's a bit of a maze in that part of the codebase, and the issue was caused by some old code trying to grok the graph that was unaware of the relatively new support for sequential-stage parallel branches. - -- - PR here - [ - https://github.com/jenkinsci/blueocean-plugin/pull/1941 - ] 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-7976) Aggregate downstream test results does not work for Matrix projects
Title: Message Title trejkaz edited a comment on JENKINS-7976 Re: Aggregate downstream test results does not work for Matrix projects Happens for us too.Jenkins ver. 2.170Matrix Project Plugin 1.12JUnit 1.26.1More info:* /job/matrix-job/563/ says "Test Result (no tests)"* /job/matrix-job/563/testReport/ shows the row for "os=windows,test=lib/metadata_item#Derby" but the test counts all say 0* If you click the link on that row it goes to /job/matrix-job/563/os=windows,test=lib%2Fmetadata_item%23Derby/testReport/ which shows the proper stats. Similar deal when viewing from the API.* /job/matrix-job/563/api/xml contains all 0 for MatrixTestResult* /job/matrix-job/563/testReport/api/xml shows all the expected elements for downstream reports, but counts are all 0* /job/matrix-job/563/os=windows,test=lib%2Fmetadata_item%23Derby/testReport/api/xml shows the proper counts So it's really like the aggregation gets all the links to individual test reports correct, but always shows 0 for the total tests run? 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-7976) Aggregate downstream test results does not work for Matrix projects
Title: Message Title trejkaz edited a comment on JENKINS-7976 Re: Aggregate downstream test results does not work for Matrix projects Happens for us too.Jenkins ver. 2.170Matrix Project Plugin 1.12JUnit 1.26.1More info:* /job/matrix-job/563/ says "Test Result (no tests)"* /job/matrix-job/563/ testReport/ shows the row for "os=windows,test=lib/metadata_item#Derby" but the test counts all say 0* If you click the link on that row it goes to /job/matrix-job/563/os=windows,test=lib%2Fmetadata_item%23Derby/testReport/ which shows the proper stats.So it's really like the aggregation gets all the links to individual test reports correct, but always shows 0 for the total tests run? 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-7976) Aggregate downstream test results does not work for Matrix projects
Title: Message Title trejkaz commented on JENKINS-7976 Re: Aggregate downstream test results does not work for Matrix projects Happens for us too. Jenkins ver. 2.170 Matrix Project Plugin 1.12 JUnit 1.26.1 More info: /job/matrix-job/563/testReport/ shows the row for "os=windows,test=lib/metadata_item#Derby" but the test counts all say 0 If you click the link on that row it goes to /job/matrix-job/563/os=windows,test=lib%2Fmetadata_item%23Derby/testReport/ which shows the proper stats. So it's really like the aggregation gets all the links to individual test reports correct, but always shows 0 for the total tests run? 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-55658) Can't install nvm wrapper version 0.1.6
Title: Message Title Tomas Salazar commented on JENKINS-55658 Re: Can't install nvm wrapper version 0.1.6 OMG I tried this on a clear install, I was able to replicate this. 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-55658) Can't install nvm wrapper version 0.1.6
Title: Message Title Tomas Salazar updated an issue Jenkins / JENKINS-55658 Can't install nvm wrapper version 0.1.6 Change By: Tomas Salazar Attachment: image-2019-04-03-19-55-19-187.png 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-56870) Flaky test: hudson.model.UpdateCenter2Test
Title: Message Title Josh Soref updated JENKINS-56870 Turns out I waited too long to file this and it was fixed Jenkins / JENKINS-56870 Flaky test: hudson.model.UpdateCenter2Test Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56392) blue-ocean links from classic do not use https
Title: Message Title Gavin Mogan commented on JENKINS-56392 Re: blue-ocean links from classic do not use https hi Björn Pedersen There's nowhere in blueocean that we redirect directly to a url. All of our urls are relative. Thinking about the problem, I'm thinking you do SSL termination inside of jetty, I'm not familiar with jetty so I'm not sure I can help much. Can you make sure your Jenkins > Manage > "Jenkins URL" is set to https? 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-55599) Blue Ocean markup formatter
Title: Message Title Gavin Mogan commented on JENKINS-55599 Re: Blue Ocean markup formatter A PR (https://github.com/jenkinsci/blueocean-plugin/pull/1940) came in to allow html in some fields. It wasn't the safe way to solve this problem but a bunch of notes came up. I've copied the comments, with a few lines deleted that don't make sense out of context. I think this is a newbie friendly task, so I want to make sure all the ideas are documented dvdliao commented 12 days ago We are setting the build description in our own jenkins library that does the gcs uploading currentBuild.description = "Artifacts are available here" Definitely cant be putting JSX in here halkeye commented 12 days ago If we could safely guarentee that the run.description is safe html, then https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/js/components/karaoke/components/RunDescription.jsx#L16 could be updated to something like: } /> But I don't think any of us are comfortably blindly trusting any user input at all to be html. It would have to go through the sanitizer first. halkeye commented 12 days ago I don't know the API offhand, but a quick search of jenkins codebase I found: https://github.com/jenkinsci/jenkins/blob/0795e89b308ec7fcbda097858d58763d8531be8c/core/src/main/java/hudson/model/ParameterDefinition.java#L141-L152 So i'd say the blueocean rest api needs to be updated to escape description everywhere, then ui needs to be updated to trust description everywhere. I'd say its a pretty quick task, maybe a day or two, perfect for a new contributor. the CB blueocean people probably won't get to it anytime soon, we are working on stability and bug fixes mainly for the immediate future. halkeye commented 9 days ago I would also make a new @exported field that is like filteredDescription or something, so we don't ever accidently forget a description somewhere and accidently cause xss Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message
[JIRA] (JENKINS-56871) EC2 Plugin fails to terminate spot instances after agent deleted
Title: Message Title Gordon Shieh created an issue Jenkins / JENKINS-56871 EC2 Plugin fails to terminate spot instances after agent deleted Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-04-04 00:34 Environment: CJE Managed Master 2.138.1.2-rolling EC2Plugin 1.42 Priority: Critical Reporter: Gordon Shieh We had a case where idle instances that were supposedly deleted still running on EC2. To reproduce: Launch EC2 template with spot instance enabled Immediately delete that instance. On the Spot request console, the request will be "cancelled" But the associated EC2 instance is still running, and orphaned. We had a case where we had so many of these orphaned instances that we reached the instance cap of our account. Add Comment
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Denys Digtiar assigned an issue to Mark Waite Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Denys Digtiar Assignee: Denys Digtiar Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56870) Flaky test: hudson.model.UpdateCenter2Test
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56870 Flaky test: hudson.model.UpdateCenter2Test Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-03 23:40 Priority: Minor Reporter: Josh Soref https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-3925/16/tests New failing - 4 Windows-jdk8 / Windows Publishing / installInvalidChecksum – hudson.model.UpdateCenter2Test 24s Stacktrace java.lang.NullPointerExceptionat hudson.model.UpdateCenter2Test.installInvalidChecksum(UpdateCenter2Test.java:69)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:554)at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.lang.Thread.run(Thread.java:748) Standard Output
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Sam Duke assigned an issue to Denys Digtiar Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Sam Duke Assignee: Denys Digtiar 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-53387) ssh-add - Text file busy
Title: Message Title phgr100x phgr100x commented on JENKINS-53387 Re: ssh-add - Text file busy https://issues.jenkins-ci.org/browse/JENKINS-48258?focusedCommentId=324590=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-324590 > The issue here appears to be caused by a Java bug, https://bugs.openjdk.java.net/browse/JDK-8068370. The issue is possible when multiple threads open a file for writing, close it, and then execute them (each thread using its own file). Even if all files are closed "properly", due to how file handles work around fork/exec, a child process in one thread may inherit the handle to anther thread's open file, and thus break that thread's later subprocess call. 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-52177) ArrayIndexOutOfBoundsException retriving Test Result Trend Chart
Title: Message Title Matthew Miling commented on JENKINS-52177 Re: ArrayIndexOutOfBoundsException retriving Test Result Trend Chart Hello I experience the same issue when I build a Java 8 Maven project using the Maven Surefire plugin to generate the surefire reports. Not sure if this helps but the Junit XML output from Surefire plugin does not have as the toplevel tag, but instead it has a collection of XML files that have as the top level tag. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title phgr100x phgr100x updated an issue Jenkins / JENKINS-48258 git client plugin occasionally fails with "text file busy" error Change By: phgr100x phgr100x Comment: This is probably caused by https://bugs.openjdk.java.net/browse/JDK-8068370 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title phgr100x phgr100x commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error This is probably caused by https://bugs.openjdk.java.net/browse/JDK-8068370 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-19195) Add description field to Release JIRA version action
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-19195 Add description field to Release JIRA version action Change By: Olivier Lamy Labels: jira-plugin-3.0.7 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-56715) Add unit tests for Include/ExcludeMessageFilter
Title: Message Title Ulli Hafner updated JENKINS-56715 Jenkins / JENKINS-56715 Add unit tests for Include/ExcludeMessageFilter Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44892) Ability to override reflective metadata in DescribableModel
Title: Message Title Jesse Glick commented on JENKINS-44892 Re: Ability to override reflective metadata in DescribableModel JEP-205 is another proposal to define a new standard for databinding. It is strictly declarative, which has some obvious advantages—certainly kinds of tools can be written which rely on it, and introspection can happen outside the Jenkins JVM—but which also renders it impractical for solving particular customizations such as for JENKINS-51638. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44892) Ability to override reflective metadata in DescribableModel
Title: Message Title Jesse Glick commented on JENKINS-44892 Re: Ability to override reflective metadata in DescribableModel Besides Pipeline and Job DSL, the other major potential consumer of this sort of API would be the configuration-as-code plugin, for YAML-based global configuration. Unfortunately it does not use structs / DescribableModel for whatever reason, so it would not be able to honor these customizations unless that were changed. CC Ewelina Wilkosz Nicolas De Loof 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-56705) Add unit test for SeverityTrendChart that uses Severity.ERROR
Title: Message Title Artem Polovyi started work on JENKINS-56705 Change By: Artem Polovyi Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Yufen Kuo commented on JENKINS-56858 Re: unable to load plugins Unzipping the war file into and set -w works. But setting -w option to directory contains war file does not work, setting -w option to full path to war file does not work either. setting -v 2.164.1 instead of -w option fails too. Running pipeline on jenkins 2.164.1 1.405 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api) java.io.IOException: Pipeline: Step API v2.19 failed to load. You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626) at hudson.PluginManager$2$1$1.run(PluginManager.java:513) 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-56869) Conditionals allOf anyOf and not behaving backwards
Title: Message Title R. Tyler Croy assigned an issue to Andrew Bayer These types of tickets are best suited for the JENKINS project in Jira. INFRA is for project infrastructure only, I've moved this over and re-assigned it Jenkins / JENKINS-56869 Conditionals allOf anyOf and not behaving backwards Change By: R. Tyler Croy Assignee: R. Tyler Croy Andrew Bayer 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-56869) Conditionals allOf anyOf and not behaving backwards
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-56869 Conditionals allOf anyOf and not behaving backwards Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 2067 56869 Workflow: classic default workflow JNJira + In-Review Component/s: pipeline Component/s: pipeline-library 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-56868) No information for AIX processes not owned by running user
Title: Message Title Robert Shade created an issue Jenkins / JENKINS-56868 No information for AIX processes not owned by running user Issue Type: Bug Assignee: Robert Shade Components: core Created: 2019-04-03 18:04 Priority: Minor Reporter: Robert Shade /proc//status is only readable by the process owner. This was causing an IOException to be thrown and no information to be returned about processes not owned by the running user. Processes owned by the current user would show a null parent instead of the real pid (ex. init). Add Comment
[JIRA] (JENKINS-56259) Allow input timeout parameter
Title: Message Title Steve Todorov commented on JENKINS-56259 Re: Allow input timeout parameter Mark Vinkx Yes, you could wrap the input like that, but unfortunately this means that you will allocate an agent and have it do nothing for 5 minutes. Also the Blue Ocean UI would display this stage as "passed" (green) which will be (and is) confusing, because you never know if the stage has actually passed or it has been skipped/not approved - you will need to specifically go into the stage to check the steps, whereas if you have it as a stage input it would show in the UI as skipped. Jesse Glick yes, you've understood me correctly 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-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Patrick Ruckstuhl commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Jesse Glick maybe I'm missing something but to me this looks totally normal to use in pipeline jobs. We have some linux slaves and some windows slaves and they each have a different location of the reference repo. I can even think of cases where you have e.g. linux nodes which for whatever reason have different paths to the reference repo. Having this configurable on a slave level and then just use it in the multibranch config is perfect, that way the pipeline does not care about how the checkout happens. 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-46485) Pre-send script not working in extemail step
Title: Message Title John Kuzniar commented on JENKINS-46485 Re: Pre-send script not working in extemail step Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56722) Add unit tests for ReferenceDetailsModel
Title: Message Title Colin Kaschel started work on JENKINS-56722 Change By: Colin Kaschel Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56867) Jenkins does not allocate workspace for neither declarative pipeline nor scripted pipeline jobs
Title: Message Title
Sergey Zhemzhitsky updated an issue
Jenkins / JENKINS-56867
Jenkins does not allocate workspace for neither declarative pipeline nor scripted pipeline jobs
Change By:
Sergey Zhemzhitsky
Pipeline jobs do not allocate workspace automaticallySteps to reproduce for *scripted pipeline* # Create pipeline job # Put the following script into "Pipeline Script" field{code:java}node { stage('Prepare') {echo "WS: ${pwd()}, EXISTS: ${new File(pwd()).exists()}"echo "WS_TMP: ${pwd(tmp: true)} , EXISTS : ${new File(pwd(tmp: true)).exists()}"echo "CWD: ${new File('.').absolutePath}"echo "USER_DIR: ${System.getProperty('user.dir')}" }} {code} # Uncheck "Use Groovy Sandbox" # Run the jobExpected result: workspace directory existsActual result: workspace directory does not exist{code:java}Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/jobs/automation/jobs/test2/workspace[Pipeline] {[Pipeline] stage[Pipeline] { (Prepare)[Pipeline] pwd[Pipeline] pwd[Pipeline] echoWS: /var/lib/jenkins/jobs/automation/jobs/test2/workspace, EXISTS: false[Pipeline] pwd[Pipeline] pwd[Pipeline] echoWS_TMP: /var/lib/jenkins/jobs/automation/jobs/test2/workspace@tmp , EXISTS : false[Pipeline] echoCWD: /.[Pipeline] echoUSER_DIR: /[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS {code} Steps to reproduce for *declarative* *pipeline* # Create pipeline job # Put the following script into "Pipeline Script" field{code:java} pipeline {agent anystages {stage ('Prepare') {steps {echo "WS: ${pwd()}, EXISTS: ${new File(pwd()).exists()}"echo "WS_TMP: ${pwd(tmp: true)} , EXISTS : ${new File(pwd(tmp: true)).exists()}"echo "CWD: ${new File('.').absolutePath}"echo "USER_DIR: ${System.getProperty('user.dir')}"}}}}{code} # Uncheck "Use Groovy Sandbox" # Run the jobExpected result: workspace directory existsActual result: workspace directory does not exist{code:java} Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/jobs/automation/jobs/test/workspace[Pipeline] {[Pipeline] stage[Pipeline] { (Prepare)[Pipeline] pwd[Pipeline] pwd[Pipeline] echoWS: /var/lib/jenkins/jobs/automation/jobs/test/workspace, EXISTS: false[Pipeline] pwd[Pipeline] pwd[Pipeline] echoWS_TMP: /var/lib/jenkins/jobs/automation/jobs/test/workspace@tmp , EXISTS : false[Pipeline] echoCWD: /.[Pipeline] echoUSER_DIR: /[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}
[JIRA] (JENKINS-56867) Jenkins does not allocate workspace for neither declarative pipeline nor scripted pipeline jobs
Title: Message Title
Sergey Zhemzhitsky created an issue
Jenkins / JENKINS-56867
Jenkins does not allocate workspace for neither declarative pipeline nor scripted pipeline jobs
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-04-03 16:14
Environment:
*OS* {code} NAME="Ubuntu" VERSION="14.04.5 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.5 LTS" VERSION_ID="14.04" {code} *JVM* {code} java version "1.8.0_101" Java(TM) SE Runtime Environment (build 1.8.0_101-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode) {code} *Jenkins* {code} ver. 2.168 {code} *Plugins* {code} Pipeline 2.6 Pipeline Graph Analysis Plugin 1.9 Pipeline Utility Steps 2.3.0 Pipeline: API 2.33 Pipeline: Basic Steps 2.15 Pipeline: Build Step 2.8 Pipeline: Declarative 1.3.7 Pipeline: Declarative Agent API 1.1.1 Pipeline: Declarative Extension Points API 1.3.7 Pipeline: Groovy 2.64 Pipeline: Input Step 2.10 Pipeline: Job 2.32 Pipeline: Milestone Step 1.3.1 Pipeline: Model API 1.3.7 Pipeline: Multibranch 2.21 Pipeline: Multibranch with defaults 2.0 Pipeline: Nodes and Processes 2.29 Pipeline: REST API Plugin 2.10 Pipeline: SCM Step 2.7 Pipeline: Shared Groovy Libraries 2.13 Pipeline: Stage Step 2.3 Pipeline: Stage Tags Metadata 1.3.7 Pipeline: Stage View Plugin 2.10 Pipeline: Step API 2.19 Pipeline: Supporting APIs 3.2 {code}
Priority:
Critical
Reporter:
Sergey Zhemzhitsky
Pipeline jobs do not allocate workspace automatically Steps to reproduce for scripted pipeline
Create pipeline job
Put the following script into
[JIRA] (JENKINS-46485) Pre-send script not working in extemail step
Title: Message Title Alex Earl commented on JENKINS-46485 Re: Pre-send script not working in extemail step 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-43194) Lightweight checkout for PR merge jobs
Title: Message Title Vivek Pandey updated JENKINS-43194 Jenkins / JENKINS-43194 Lightweight checkout for PR merge jobs Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs
Title: Message Title Vivek Pandey started work on JENKINS-43194 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46485) Pre-send script not working in extemail step
Title: Message Title John Kuzniar commented on JENKINS-46485 Re: Pre-send script not working in extemail step Could the documentation in the wiki be updated? If pipeline is just the exception, at least make a note of this. This information would have saved me a lot of time, so I'm sure it would be valuable to others. Thanks. Pre-send Script The pre-send script is a feature which allows you to write a script that can modify the MimeMessage object prior to sending. This would allow adding custom headers, modifying the body, etc. Predefined variables include: msg - the MimeMessage object which can be modified logger - a PrintStream and will write to the job's log. build - the build this message belongs to cancel - a boolean, which when set to true will cancel the sending of the email 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-56510) Provide generic issue parser for custom tools
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56510
Re: Provide generic issue parser for custom tools
# We need a new parser tool class e.g. {{AnalysisReport}} (subclass of {{ReportScanningTool}}) in the warnings-ng project, see {{Detekt}} for an example. This class creates a new parser in the {{createParser}} method. # We need a new parser class e.g. of new class {{ReportParser}} (extending {{IssueParser}}) in the {{createParser}} method . The {{parse}} method of this class should use the same code as {{AnalysisResult.readIssues()}}. The code in {{AnalysisResult}} already reads a report with several issues, so we basically need to reuse or extract that part.
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-56510) Provide generic issue parser for custom tools
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56510
Re: Provide generic issue parser for custom tools
We need a new parser class e.g. ` {{ AnalysisReport ` }} (subclass of ` {{ ReportScanningTool ` }} ) in the warnings-ng project, see ` {{ Detekt ` }} for an example. This class creates a new parser e.g. of new class ` {{ ReportParser ` }} (extending ` {{ IssueParser ` }} ) in the ` {{ createParser ` }} method. The ` {{ parse ` }} method of this class should use the same code as ` {{ AnalysisResult.readIssues() ` }} . The code in ` {{ AnalysisResult ` }} already reads a report with several issues, so we basically need to reuse or extract that part.
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-56510) Provide generic issue parser for custom tools
Title: Message Title Ulli Hafner commented on JENKINS-56510 Re: Provide generic issue parser for custom tools We need a new parser class e.g. `AnalysisReport` (subclass of `ReportScanningTool`) in the warnings-ng project, see `Detekt` for an example. This class creates a new parser e.g. of new class `ReportParser` (extending `IssueParser`) in the `createParser` method. The `parse` method of this class should use the same code as `AnalysisResult.readIssues()`. The code in `AnalysisResult` already reads a report with several issues, so we basically need to reuse or extract that part. 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-56866) Everything is favourite, it is not useful
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-56866 Everything is favourite, it is not useful Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-04-03 15:39 Priority: Minor Reporter: Ivan Fernandez Calvo The way that favorite works it is a little odd, and it is possible that you have all the jobs in your Jenkins as favorites without doing anything, it is my case, I make PRs to ever repository on our organization so every time I make a PR BO adds this build related (multibranch pipelines) as favorite, here is were Jenkins and I start fighting to remove favorites from my user profile and it adding more, he wins always and I have all projects as favorites. My suggestion is to remove this feature that adds PR as favorites or at least enables some way to disable the feature for every user or one user https://jenkins.io/doc/book/blueocean/dashboard/#favorites-list >Blue Ocean automatically adds branches or PRs to this list when a they contain a run that has changes authored by the current user. Add Comment
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Jesse Glick commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo By the way the use case described in the issue description seems like a bad idea to me. More straightforward to have the script determine the Git commit being built, and then rather than running checkout scm on each node, explicitly construct a GitSCM configured exactly the way you want, according to whatever Groovy logic you need. The kind of plugin-based environment variable expansion seen in this PR should only be necessary in freestyle projects. 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-56510) Provide generic issue parser for custom tools
Title: Message Title Raphael Furch commented on JENKINS-56510 Re: Provide generic issue parser for custom tools Ulli Hafner I don't know exactly what to do here. Can you give me a hint please? 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-56715) Add unit tests for Include/ExcludeMessageFilter
Title: Message Title Andreas Neumeier started work on JENKINS-56715 Change By: Andreas Neumeier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19195) Add description field to Release JIRA version action
Title: Message Title Mathieu Paré updated JENKINS-19195 Jenkins / JENKINS-19195 Add description field to Release JIRA version action Change By: Mathieu Paré Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56718) Add unit tests for BlameFactory
Title: Message Title Ulli Hafner commented on JENKINS-56718 Re: Add unit tests for BlameFactory Yes, you are allowed to change the class to make it easier to test. 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-56698) Use LookaheadParser for NagFortranParser
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56698 Use LookaheadParser for NagFortranParser Change By: Ulli Hafner Summary: Use RegexpLineParser LookaheadParser for NagFortranParser 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-56702) Use LookaheadParser for YuiCompressorParser
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56702 Use LookaheadParser for YuiCompressorParser Change By: Ulli Hafner Summary: Use RegexpLineParser LookaheadParser for YuiCompressorParser 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-56701) Use LookaheadParser for GnuFortranParser
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56701 Use LookaheadParser for GnuFortranParser Change By: Ulli Hafner Summary: Use RegexpLineParser LookaheadParser for GnuFortranParser 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-56700) Use LookaheadParser for GhsMultiParser
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56700 Use LookaheadParser for GhsMultiParser Change By: Ulli Hafner Summary: Use RegexpLineParser LookaheadParser for GhsMultiParser 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-56700) Use RegexpLineParser for GhsMultiParser
Title: Message Title Ulli Hafner commented on JENKINS-56700 Re: Use RegexpLineParser for GhsMultiParser have a few questions regarding the requested improvement. Is an implementation of this Parser using the RegexpLineParser even possible with its current interface? The Pattern Matched by the GhsMultiParser matches multiple lines at once to group the issue message properly. It is possible to just match the Start of the issue without the message but that would skip the following lines containing the issue message. The RegexpLineParser does not offer a interface to access addtional lines. Would it be okay to use the LookaheadParser directly instead? This would allow the GhsMultiParser to read the issue message correctly and proccess the message lines before continuing parsing. Yes, you are right. I need to change the title of the issue. You need to use the LookaheadParser. Split the regex into two pieces: first part matches the first line. Use this regexp for the LookaheadParser. Then you can decide how many additional lines to read (and if you need the rest of the regexp). Regarding the severity error request, does this just mean if the error contains the type error the Serverity.ERROR should be used instead of Severity.WARNING_HIGH ? Well, a warning should be mapped to a WARNING_NORMAL. An error to ERROR. You can use the method guessSeverity on the IssueBuilder instance and remove the current mapPriority method. Maybe you even find an example in the internet that shows a log of the parser that contains an error (if not, create a fake one). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because
[JIRA] (JENKINS-56707) Improve unit tests for LinesChartModel
Title: Message Title Lorenz Munsch started work on JENKINS-56707 Change By: Lorenz Munsch Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56865) Password to access InfluxDB is stored unencrypted on disk
Title: Message Title Michel Zanini created an issue Jenkins / JENKINS-56865 Password to access InfluxDB is stored unencrypted on disk Issue Type: Task Assignee: Aleksi Simell Attachments: Screen Shot 2019-04-03 at 11.22.52.png Components: influxdb-plugin Created: 2019-04-03 14:25 Environment: Version 1.20.4, Jenkins 2.170 Priority: Minor Reporter: Michel Zanini When configuring the plugin on "Configure System", the username and password are typed directly in a field - see attached screen shot. When saving, the user/password to access InfluxDB are saved in jenkinsci.plugins.influxdb.InfluxDbPublisher.xml unencrypted. This plugin should make use of Jenkins credentials, and have a dropbox here to select the correct username/password credentials. This is a security issue in my opinion and needs to be fixed ASAP. Thanks.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Jesse Glick commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax Contra Olivier Lamy’s comment there I consider this a bug. Blue Ocean should pay attention to the build metadata as provided by official Pipeline APIs and may not make assumptions about the mechanism used to run a build, except insofar as that is intrinsically required for a certain feature. (For example, a stage restart button should only appear next to a Declarative stage, because the feature of restarting a stage is tied to Declarative semantics.) Regardless of how the issue is classified, the question of whether it will be fixed or not depends entirely on the development team’s time and priorities. 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-43336) Allow locking multiple stages in declarative pipeline
Title: Message Title
Philipp Abraham edited a comment on JENKINS-43336
Re: Allow locking multiple stages in declarative pipeline
` {{ env ` }} is not available in ` {{ options ` }} I think, but you could try getting the node name from the API: {code:java} ``` stage('Parent') { options { lock("${currentBuild.getRawBuild().getExecutor().getOwner().getDisplayName()}") } stages { stage('first child') { ... } stage('second child') \ { ... } } } ``` }{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43336) Allow locking multiple stages in declarative pipeline
Title: Message Title
Philipp Abraham edited a comment on JENKINS-43336
Re: Allow locking multiple stages in declarative pipeline
`env` ist is not available in ` options ` I think, but you could try getting the node name from the API:```stage('Parent') { options { lock("${currentBuild.getRawBuild().getExecutor().getOwner().getDisplayName()}") } stages { stage('first child') { { ... } stage('second child') \ { ... } }}```
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-43336) Allow locking multiple stages in declarative pipeline
Title: Message Title
Philipp Abraham commented on JENKINS-43336
Re: Allow locking multiple stages in declarative pipeline
`env` ist not available in options but you could try getting the node name from the API: ``` stage('Parent') { options { lock("${currentBuild.getRawBuild().getExecutor().getOwner().getDisplayName()}") } stages { stage('first child') { ... } stage('second child') { ... } } } ```
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-56700) Use RegexpLineParser for GhsMultiParser
Title: Message Title Sebastian Heunke commented on JENKINS-56700 Re: Use RegexpLineParser for GhsMultiParser Hello Ulli Hafner, I have a few questions regarding the requested improvement. Is an implementation of this Parser using the RegexpLineParser even possible with its current interface? The Pattern Matched by the GhsMultiParser matches multiple lines at once to group the issue message properly. It is possible to just match the Start of the issue without the message but that would skip the following lines containing the issue message. The RegexpLineParser does not offer a interface to access addtional lines. Would it be okay to use the LookaheadParser directly instead? This would allow the GhsMultiParser to read the issue message correctly and proccess the message lines before continuing parsing. Regarding the severity error request, does this just mean if the error contains the type error the Serverity.ERROR should be used instead of Severity.WARNING_HIGH ? Greetings Sebastian 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-56718) Add unit tests for BlameFactory
Title: Message Title Ulli Hafner commented on JENKINS-56718 Re: Add unit tests for BlameFactory Yes, this actually is required (and that is the concept around the facade if you have a look at some other usages). When you refactor the method just create an additional overloaded method (package private access with @VisisbleForTesting annotation) so the current client code does not need to change. 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-56718) Add unit tests for BlameFactory
Title: Message Title Andreas Reiser commented on JENKINS-56718 Re: Add unit tests for BlameFactory Actually I think I can do it without an extra argument. I just noticed the @VisibleForTesting annotation and will use that to prevent public API changes, but I still need to change the original class a bit. 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-56718) Add unit tests for BlameFactory
Title: Message Title Andreas Reiser commented on JENKINS-56718 Re: Add unit tests for BlameFactory I have trouble testing this class because it invokes calls to JenkinsFacade that try to access the jenkins instance (which is null and leads to NullPointerExceptions in tests). Is it ok to refactor the createBlamer() method so that the JenkinsFacade gets passed as an argument and can be mocked? Otherwise there is no possibility of unit testing this class. 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-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Andreas Reiser assigned an issue to Andreas Reiser Jenkins / JENKINS-56714 Add unit tests for IssuesChartPortlet Change By: Andreas Reiser Assignee: Andreas Reiser 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-56718) Add unit tests for BlameFactory
Title: Message Title Andreas Reiser assigned an issue to Andreas Reiser Jenkins / JENKINS-56718 Add unit tests for BlameFactory Change By: Andreas Reiser Assignee: Andreas Reiser 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-56864) "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM
Title: Message Title Daniel Gront assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-56864 "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM Change By: Daniel Gront Assignee: Daniel Gront Anda Sorina Laakso 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-56864) "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-56864 "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM Change By: Daniel Gront Priority: Major Critical 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-56864) "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM
Title: Message Title Milagros Manalo created an issue Jenkins / JENKINS-56864 "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM Issue Type: Bug Assignee: Daniel Gront Attachments: ALM run UFT test on Jenkins slave.jpg Components: hp-application-automation-tools-plugin Created: 2019-04-03 11:59 Environment: Jenkins ver 2.7.4 Micro Focus Application Automation Tools plugin 5.7.1-beta Micro Focus 12.53 Micro Focus UFT 14.5 Labels: UFT ALM Priority: Major Reporter: Milagros Manalo "No certificate available" popup is displayed on slave machine when we build job for executing functional tests from Micro Focus ALM. I tried clicking "OK" button and job failed. I tried clicking "Cancel" button and job failed. I also tried not to confirm the popup, job failed because timeout was reached. Below is the failed message in console output. Kindly advise! Thanks! Id: 195, Execution status: Running Id: 195, Execution status: Unknown, Message: Unable to connect the testing tool to the requested ALM/QC server.
[JIRA] (JENKINS-56834) Build permission on agents is not working
Title: Message Title Luis Piedra-Márquez commented on JENKINS-56834 Re: Build permission on agents is not working No error logged. It's just the build does not enter any slave altought it should have permissions to do so, and points it in the cause of blockage. 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-56858) unable to load plugins
Title: Message Title Evaristo Gutierrez commented on JENKINS-56858 Re: unable to load plugins Hi Yufen Kuo, thanks for using Jenkinsfile Runner! I see you have used "-w /local/test/jenkins" while you unzipped the WAR file in "/local/test/jenkins/jenkins_home". Could you please unzip the WAR in the first one and see whats is the result after that? Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Evaristo Gutierrez updated an issue Jenkins / JENKINS-56858 unable to load plugins Change By: Evaristo Gutierrez Labels: triaged 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Dennis Keitzel commented on JENKINS-48490 Re: Intermittently slow docker provisioning with no errors For reference: We hit a similar issue where the cloud-stats-plugin was the cause. See JENKINS-56863. 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-56863) Cloud stats persistence file grows continually
Title: Message Title Dennis Keitzel created an issue Jenkins / JENKINS-56863 Cloud stats persistence file grows continually Issue Type: Bug Assignee: Oliver Gondža Components: cloud-stats-plugin Created: 2019-04-03 10:49 Environment: Operating System: RHEL 7.4 Linux 64 bit, Kernel 4.4.114-94.11-default JDK: OpenJDK 1.8.0_161-b14 Jenkins version: 2.150.2 cloud-stats-plugin version: 0.22 Priority: Minor Reporter: Dennis Keitzel Hey, the cloud-stats-plugin keeps track of every provisioning activity in order to create a statistic that is accessible via /cloud-stats/. The underlying data is persistet in /org.jenkinsci.plugins.cloudstats.CloudStatistics.xml. However, there seems to be no rotation mechanism, causing that file to grow continually. In our case that file reached 150 MB which caused various issues: Provisioning time took up to 15 minutes, depending on the number of currently requested agents to provision. There are about 50 short-lived (per build) agents connected at any time. CPU usage was going through the roof. Jenkins (the master only) is running on a 24 core machine with 128 Gig of RAM and used about 800%-2000% of all CPUs. I assume that most of that CPU-time is spent on XML serialization as well as sychronization operations. Workaround: Manually delete the persistence file and restart Jenkins. After pruning that persistence file, our CPU-Usage went down to 20%-200%. Provisioning times went down to about 10 seconds, regardless of load.
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Sam Duke updated an issue Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Sam Duke Priority: Minor Major 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-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Sam Duke updated an issue Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Sam Duke Labels: feature-improvement 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-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Sam Duke reopened an issue Is there any chance this could be looked at again with a view to changing Lightweight Checkout to be able to substitute in the variables? Our checkout is very slow so this really hurts us! Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Sam Duke Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56711) Add unit tests for PieChartModel
Title: Message Title Nils Engelbrecht started work on JENKINS-56711 Change By: Nils Engelbrecht Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Olivier Jacques commented on JENKINS-56773 Re: High master CPU usage introduced by Blue Ocean 1.14.0 Thanks Gavin Mogan. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56834) Build permission on agents is not working
Title: Message Title runze xia commented on JENKINS-56834 Re: Build permission on agents is not working Hi What is the log after the failure？ Luis Piedra-Márquez 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-56858) unable to load plugins
Title: Message Title Baptiste Mathus assigned an issue to Evaristo Gutierrez Jenkins / JENKINS-56858 unable to load plugins Change By: Baptiste Mathus Assignee: Evaristo Gutierrez 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-10191) JDK selection is hidden even when a JDK is configured
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-10191 JDK selection is hidden even when a JDK is configured Change By: Isa Vilacides Labels: java11 java11-compatibility triaged 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-56700) Use RegexpLineParser for GhsMultiParser
Title: Message Title Sebastian Heunke started work on JENKINS-56700 Change By: Sebastian Heunke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40522) "Started by" link on downstream jobs does not work correctly
Title: Message Title Marco Jacob edited a comment on JENKINS-40522 Re: "Started by" link on downstream jobs does not work correctly We have the same problem in Jenkins 2 . 150.3. For some projects it works and for others it doesn't work.In cases aa_messaging-trunk #1349 (failed) > aa_jif-trunk #2052 (modified, success) aa_emailversand-trunk #1616 (succcess) > aa_emailversand_client-trunk #819 (success) > aa_jif-trunk #2052the link *doesn't* work in aa_messaging, aa_emailversand and aa_emailversand_client, but it works in aa_jif-trunk #2052.In cases ko_gewerbe-trunk #764 (Tests failed) > ko_kern-trunk #8059 (success)the link works and points to ko_kern-trunk pollingLog job/ko_kern-trunk/8059/pollingLog. The link doesn't work for all the builds of aa_emailversand and aa_messaging and works for all ko_gewerbe and fi_ilis.Maybe it depends on the job configuration? With aa_jif we have not changed the configuration sind 2017 and increased Jenkins-Version. The configurations of ko_kern and ko_gewerbe were changed in 2019-02. 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-40522) "Started by" link on downstream jobs does not work correctly
Title: Message Title Marco Jacob edited a comment on JENKINS-40522 Re: "Started by" link on downstream jobs does not work correctly We have the same problem in Jenkins 2.150.3. For some projects it works and for others it doesn't work.In cases aa_messaging-trunk #1349 (failed) > aa_jif-trunk #2052 (modified, success) aa_emailversand-trunk #1616 (succcess) > aa_emailversand_client-trunk #819 (success) > aa_jif-trunk #2052the link *doesn't* work in aa_messaging, aa_emailversand and aa_emailversand_client, but it works in aa_jif-trunk #2052.In cases ko_gewerbe-trunk #764 (Tests failed) > ko_kern-trunk #8059 (success)the link works and points to ko_kern-trunk pollingLog job/ko_kern-trunk/8059/pollingLog. The link doesn't work for all the builds of aa_emailversand and aa_messaging and works for all ko_gewerbe and fi_ilis.Maybe it depends on the job configuration? With aa_jif we have not changed the configuration sind since 2017 and increased Jenkins-Version several times . The configurations of ko_kern and ko_gewerbe were changed in 2019-02. 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-42643) Conditional application of triggers in Declarative
Title: Message Title Andreas Sieferlinger commented on JENKINS-42643 Re: Conditional application of triggers in Declarative Has there been any progress on this? 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-40522) "Started by" link on downstream jobs does not work correctly
Title: Message Title Marco Jacob edited a comment on JENKINS-40522 Re: "Started by" link on downstream jobs does not work correctly We have the same problem. For some projects it works and for others it doesn't work.In cases aa_messaging-trunk #1349 (failed) > aa_jif-trunk #2052 (modified, success) aa_emailversand-trunk #1616 (succcess) > aa_emailversand_client-trunk #819 (success) > aa_jif-trunk #2052the link *doesn't* work in aa_messaging, aa_emailversand and aa_emailversand_client, but it works in aa_jif-trunk #2052.In cases ko_gewerbe-trunk #764 (Tests failed) > ko_kern-trunk #8059 (success)the link works and points to ko_kern-trunk pollingLog job/ko_kern-trunk/8059/pollingLog. The link doesn't work for all the builds of aa_emailversand and aa_messaging and works for all ko_gewerbe and fi_ilis.Maybe it depends on the job configuration? With aa_jif we have not changed the configuration sind 2017 and increased Jenkins-Version. The configuration configurations of ko_kern and ko_gewerbe were changed in 2019-02. 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-40522) "Started by" link on downstream jobs does not work correctly
Title: Message Title Marco Jacob edited a comment on JENKINS-40522 Re: "Started by" link on downstream jobs does not work correctly We have the same problem. For some projects it works and for others it doesn't work.In cases aa_messaging-trunk #1349 (failed) > aa_jif-trunk #2052 (modified, success) aa_emailversand-trunk #1616 (succcess) > aa_emailversand_client-trunk #819 (success) > aa_jif-trunk #2052the link *doesn't* work in aa_messaging, aa_emailversand and aa_emailversand_client, but it works in aa_jif-trunk #2052.In cases ko_gewerbe-trunk #764 (Tests failed) > ko_kern-trunk #8059 (success)the link works and points to ko_kern-trunk pollingLog job/ko_kern-trunk/8059/pollingLog. The link doesn't work for all the builds of aa_emailversand and aa_messaging and works for all ko_gewerbe and fi_ilis.Maybe it depends on the job configuration? With aa_jif we have not changed the configuration sind 2017 and increased Jenkins-Version. The configuration of ko_kern and ko_gewerbe were changed in 2019-02. 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-40522) "Started by" link on downstream jobs does not work correctly
Title: Message Title Marco Jacob commented on JENKINS-40522 Re: "Started by" link on downstream jobs does not work correctly We have the same problem. For some projects it works and for others it doesn't work. In cases aa_messaging-trunk #1349 (failed) > aa_jif-trunk #2052 (modified, success) aa_emailversand-trunk #1616 (succcess) > aa_emailversand_client-trunk #819 (success) > aa_jif-trunk #2052 the link doesn't work in aa_messaging, aa_emailversand and aa_emailversand_client, but it works in aa_jif-trunk #2052. In cases ko_gewerbe-trunk #764 (Tests failed) > ko_kern-trunk #8059 (success) the link works and points to ko_kern-trunk pollingLog job/ko_kern-trunk/8059/pollingLog. The link doesn't work for all the builds of aa_emailversand and aa_messaging and works for all ko_gewerbe and fi_ilis. Maybe it depends on the job configuration? With aa_jif we have not changed the configuration sind 2017 and increased Jenkins-Version. 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-56737) Java compiler warnings parser can't cope with Maven timestamps in log
Title: Message Title cristalp commented on JENKINS-56737 Re: Java compiler warnings parser can't cope with Maven timestamps in log Thanks, guys! 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-56792) Change constructor in Issue (TreeString)
Title: Message Title Nils Engelbrecht updated an issue Jenkins / JENKINS-56792 Change constructor in Issue (TreeString) Change By: Nils Engelbrecht Summary: Create additional Change constructor in Issue (TreeString) 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-56792) Create additional constructor in Issue (TreeString)
Title: Message Title
Nils Engelbrecht updated an issue
Jenkins / JENKINS-56792
Create additional constructor in Issue (TreeString)
Change By:
Nils Engelbrecht
- Issue has a constructor with {{String}} values for fileName, packageName, message, description. Another constructor is required (same number of parameters) that uses a {{TreeString}} for these arguments. - - In a second step, {{IssueBuilder}} should be refined to store the members fileName, packageName, message, description in a {{TreeString}} as well. -Issue has a constructor with {{String}} values for fileName, packageName, message, description. The constructor has to be changed to required (same number of parameters) that uses a {{TreeString}} for these arguments.All normalization and transformation logic that is currently part of the constructor of {{Issue}} should be moved to {{IssueBuilder#build}}. The {{Issue}} constructor then needs to be changed as described above.
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-56774) Support Configuration as Code
Title: Message Title Carel Combrink commented on JENKINS-56774 Re: Support Configuration as Code Allan BURDAJEWICZ Is this something that can perhaps be looked at? 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-56802) support credentials for authenticationToken
Title: Message Title Daniel Spilker assigned an issue to Unassigned Job DSL only provides configuration for existing options. This option to set the authentication token from credentials is not available in Jenkins and needs to be added in Jenkins core. So I'm changing the component to core. Depending on the implementation in core, the feature will be supported in Job DSL automatically through Dynamic DSL. Jenkins / JENKINS-56802 support credentials for authenticationToken Change By: Daniel Spilker Component/s: core Component/s: job-dsl-plugin Assignee: Daniel Spilker 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
[JIRA] (JENKINS-56593) Jenkins git clone fails intermittently
Title: Message Title Milind Sonawane commented on JENKINS-56593 Re: Jenkins git clone fails intermittently Hello Mark, We made the following changes changed the memory limit from 4GB to 8GB, that did not help. What really worked for us (partially) was downgrading the version of K8S plugin from 1.14.9 to 1.14.8. The number of failures has reduced post this change. 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.
