[JIRA] (JENKINS-31449) Port Allocator Pipeline support
Title: Message Title Oliver Gondža commented on JENKINS-31449 Re: Port Allocator Pipeline support There is a pull request proposed that needs more work. As the plugin appears generally unmaintained, it takes a volunteer to have a look at that.. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56382) Only one stage visible in BlueOcean
Title: Message Title William Laszlo created an issue Jenkins / JENKINS-56382 Only one stage visible in BlueOcean Issue Type: Bug Assignee: Unassigned Attachments: a.png, old-view.png Components: blueocean-plugin Created: 2019-03-04 07:43 Environment: Jenkins ver. 2.165 Blue Ocean plugin 1.13.1 Priority: Critical Reporter: William Laszlo I've updated my plugins today, BlueOcean included, and now I'm unable to view all my stages, instead, I see only the first one. I've added an image called old-view to view all my stages. This is an old photo, but still reliable. Add Comment
[JIRA] (JENKINS-54255) xUnit sets build status incorrectly
Title: Message Title
Vlad Aginsky edited a comment on JENKINS-54255
Re: xUnit sets build status incorrectly
Nicolas, thanks for prompt response, since i am not sure how to proceed with this issue, i will make another try here before opening another one, please.I want to define following behavior:{{_Any new failed test to fail the build, if no new failures, any old failure to cause to unstable build status._ }}This is how I use Snippet Generator !image-2019-03-04-09-13-18-589.png|width=646,height=150!this is what it produces: {code:java}xunit thresholds: [failed(failureNewThreshold: '0', unstableThreshold: '0')], tools: []{code} and it is very similar to my original post. I just thought that may be precedence makes difference here (does it?) so i have then in reverse order:{code:java}xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')], ...{code} *Important note:* i see that in some cases it behaves just right, but sometimes it produces yellow status on new failed tests, just as described above. And, IMHO(really humble) what you wrote{code:java}thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0')]{code} will cause the build to fail on any failed test, new and old. please correct me. Bottom line, do you still say that i dont use thresholds in a right manner?
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-55741) Customizable number of builds in trend chart
Title: Message Title Ulli Hafner updated JENKINS-55741 Since the chart has a zoom function this configuration option might be not required anymore. Jenkins / JENKINS-55741 Customizable number of builds in trend chart Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Postponed 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-54255) xUnit sets build status incorrectly
Title: Message Title
Vlad Aginsky edited a comment on JENKINS-54255
Re: xUnit sets build status incorrectly
Nicolas, thanks for prompt response, since i am not sure how to proceed with this issue, i will make another try here before opening another one, please.I want to define following behavior: Any {{_Any new failed test to fail the build, if no new failures, any old failure to cause to unstable build status. _ }} This is how I use Snippet Generator !image-2019-03-04-09-13-18-589.png|width=646,height=150!this is what it produces: {code:java}xunit thresholds: [failed(failureNewThreshold: '0', unstableThreshold: '0')], tools: []{code} and it is very similar to my original post. I just thought that may be precedence makes difference here (does it?) so i have then in reverse order:{code:java}xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')], ...{code}And, IMHO(really humble) what you wrote{code:java}thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0')]{code} will cause the build to fail on any failed test, new and old. please correct me. Bottom line, do you still say that i dont use thresholds in a right manner?
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-55840) Doxygen parser not fully compatible with warnings-ng-plugin
Title: Message Title Ulli Hafner updated JENKINS-55840 Jenkins / JENKINS-55840 Doxygen parser not fully compatible with warnings-ng-plugin 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-54255) xUnit sets build status incorrectly
Title: Message Title
Vlad Aginsky edited a comment on JENKINS-54255
Re: xUnit sets build status incorrectly
Nicolas, thanks for prompt response, since i am not sure how to proceed with this issue, i will make another try here before opening another one, please.I want to define following behavior:Any new failed test to fail the build, if no new failures, any old failure to cause to unstable status. This is how I use Snippet Generator !image-2019-03-04-09-13-18-589.png|width=646,height=150!this is what it produces: {code:java}xunit thresholds: [failed(failureNewThreshold: '0', unstableThreshold: '0')], tools: []{code} and it is very similar to my original post. I just thought that may be precedence makes difference here (does it?) so i have then in reverse order:{code:java}xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')], ...{code}And, IMHO(really humble) what you wrote{code:java}thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0')]{code} will cause the build to fail on any failed test, new and old. please correct me. Bottom line, do you still say that i dont use thresholds in a right manner?
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-54255) xUnit sets build status incorrectly
Title: Message Title Vlad Aginsky commented on JENKINS-54255 Re: xUnit sets build status incorrectly Nicolas, thanks for prompt response, since i am not sure how to proceed with this issue, i will make another try here before opening another one, please. I want to define following behavior: Any new failed test to fail the build, if no new failures, any old failure to cause to unstable status. This is how I use Snippet Generator this is what it produces: xunit thresholds: [failed(failureNewThreshold: '0', unstableThreshold: '0')], tools: [] and it is very similar to my original post. I just thought that may be precedence makes difference here (does it?) so i have then in reverse order: xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')], ... And, IMHO(really humble) what you wrote thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0')] will cause the build to fail on any failed test, new and old. please correct me. 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
[JIRA] (JENKINS-50451) Provide badge for Cloudbees Docker Hub Notification
Title: Message Title Baptiste Mathus commented on JENKINS-50451 Re: Provide badge for Cloudbees Docker Hub Notification I lack a bit of time to do this these days, but in case anyone wants to give it a try, it is really simple. Similar PR as an example https://github.com/jenkinsci/buildtriggerbadge-plugin/pull/19 Just marked this PR as newbie-friendly. 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-50451) Provide badge for Cloudbees Docker Hub Notification
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-50451 Provide badge for Cloudbees Docker Hub Notification Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-50451) Provide badge for Cloudbees Docker Hub Notification
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50451 Provide badge for Cloudbees Docker Hub Notification Change By: Baptiste Mathus Labels: newbie-friendly 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-54255) xUnit sets build status incorrectly
Title: Message Title Vlad Aginsky updated an issue Jenkins / JENKINS-54255 xUnit sets build status incorrectly Change By: Vlad Aginsky Attachment: image-2019-03-04-09-13-18-589.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-56264) Links in trend chart must not use displayName
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56264 Links in trend chart must not use displayName I see. We need to use the display name for the axis label and the url for the URL. Change By: Ulli Hafner Summary: 404 Clicking on Links in trend graph chart must not use displayName 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-56381) 'Enter directly' should be selected by default when creating SSH key credentials
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-56381 'Enter directly' should be selected by default when creating SSH key credentials Change By: Owen Mehegan Attachment: Screen Shot 2019-03-04 at 4.28.53 pm.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-56381) 'Enter directly' should be selected by default for SSH key credentials
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-56381 'Enter directly' should be selected by default for SSH key credentials Issue Type: Improvement Assignee: Devin Nusbaum Components: ssh-credentials-plugin Created: 2019-03-04 05:36 Priority: Major Reporter: Owen Mehegan Ever since we removed the options to read SSH private keys from the master filesystem, the UI for the 'SSH username with private key' credential type has had only one remaining radio button choice: 'Enter directly.' But this choice is not selected by default, and you can save a useless credential without selecting it. I've been doing remote technical interviews where one of the steps along the way is to create this credential, and as of today ten out of ten candidates have been baffled by this UI, even when they have used Jenkins before. I almost always have to walk them through this part. I think that 'Enter directly' should just be selected by default when the credential is created, and you should not be able to save this credential type if you haven't entered a key. If there is agreement that this would be useful, I can try to create a PR. Add Comment
[JIRA] (JENKINS-56381) 'Enter directly' should be selected by default when creating SSH key credentials
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-56381 'Enter directly' should be selected by default when creating SSH key credentials Change By: Owen Mehegan Summary: 'Enter directly' should be selected by default for when creating SSH key credentials 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-56380) Last Changes plugin looking for .git in wrong location
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56380 Last Changes plugin looking for .git in wrong location Change By: Jeffrey Bennett Attachment: log 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-56380) Last Changes plugin looking for .git in wrong location
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56380 Last Changes plugin looking for .git in wrong location Change By: Jeffrey Bennett Attachment: Jenkinsfile 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-56380) Last Changes plugin looking for .git in wrong location
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-56380 Last Changes plugin looking for .git in wrong location Issue Type: Bug Assignee: Rafael Pestano Components: last-changes-plugin Created: 2019-03-04 05:19 Environment: Jenkins 2.150.3 Last Changes Plugin 2.6.8 Priority: Major Reporter: Jeffrey Bennett Receiving error: 00:00:04.421 Publishing build last changes... 00:00:04.422 ERROR: Last Changes NOT published due to the following error: Could not find previous head of repository located at /var/lib/jenkins/jobs/omni-pipeline/branches/release-3-8.d1f6no/builds/28/.git. Its your first commit? The lastChangesPlugin appears to be looking for ".git" in jobs/.../branches/.../builds rather than in workspace. This was with vcsDir: ''. I've additionally tried providing it hints via a more explicit vcsDir, but it still seems to go looking in jobs directory. Add Comment
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum commented on JENKINS-56376 Re: remoting kakfa plugin creates too many threads and takes too much cpu time Won't be able to upload the screenshots until Wed. (some issue with the firewall) I 'll see If I can get around it. But just installing the monitoring plugin and then ordering by cpu time you'll those Channel reader threads chewing all the juice 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-56379) Absorb pipeline-model-definition symbol-hetero-list.jelly into hetero-list.jelly
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56379 Absorb pipeline-model-definition symbol-hetero-list.jelly into hetero-list.jelly Issue Type: Task Assignee: Josh Soref Components: core Created: 2019-03-04 04:47 Priority: Minor Reporter: Josh Soref There are only two fairly small changes in pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/generator/DirectiveGenerator/symbol-hetero-list.jelly Right now, it lives as its own file. It would be much nicer if it were possible for it to simply extend the core functionality. (Specifically, if it were to do that, it would mean that changing the core tag from table to div would just work. Otherwise, it just breaks.) Add Comment
[JIRA] (JENKINS-56378) trigger upstream projects to watch not found triggers null pointer exception
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56378 trigger upstream projects to watch not found triggers null pointer exception Issue Type: Task Assignee: Unassigned Components: core Created: 2019-03-04 04:44 Priority: Minor Reporter: Josh Soref Load /directive-generator/ Directive: triggers Add: upstream For Projects to watch, enter a project that doesn't exist Click Generate Declarative Directive Actual results: java.lang.NullPointerException at jenkins.triggers.ReverseBuildTrigger$DescriptorImpl.doCheckUpstreamProjects(ReverseBuildTrigger.java:215) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException
[JIRA] (JENKINS-56317) Download from File Shares Seems to Not Use Ant Syntax
Title: Message Title Azure DevOps commented on JENKINS-56317 Re: Download from File Shares Seems to Not Use Ant Syntax PR created https://github.com/jenkinsci/windows-azure-storage-plugin/pull/144 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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Mark Waite edited a comment on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore The best path is to submit a separate bug report which that describes the precise conditions of the problem you're seeing. There are so many Jenkins servers in the world and so many agents in the world that I expect the case you're seeing will have some specific details which make it more uncommon than typical.Some of the attributes that might make your environment different could include:* operating system of the Jenkins master* operating system of the agent that has the issue* Jenkins master version* Java version on Jenkins master and Jenkins agent* Private key type (ed25519, rsa, ecdsa, dsa, ...)* Is FIPS mode enabled on any of the machines involved in the environment* Locale of the master and the agent* Is the private key protected by a passphrase?* Does the passphrase include shell special characters?* Plugin versions in your installation (Jenkins support pllugin can generate a bundle that includes this info) 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-56377) console log hangs in web browser after upgrade
Title: Message Title Mike Kozell created an issue Jenkins / JENKINS-56377 console log hangs in web browser after upgrade Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2019-03-04 03:16 Environment: Jenkins v2.89.4 w/ workflow-job-plugin v2.25 Jenkins v2.150.3 w/ workflow-job-plugin v2.31 Priority: Minor Reporter: Mike Kozell We recently upgraded Jenkins from 2.89.4 to 2.150.3 and then upgraded the workflow-job plugin from 2.25 to 2.31 and are now seeing an issue where the full console log in the Jenkins UI is having issues loading. We run a parallel pipeline heavy workload which results in a 13mb console log in 2.150.3 and a 46mb console log in 2.89.4. In Jenkins 2.89.4, it took 45 seconds to load the full console log file in Chrome and even less time in Firefox. In Jenkins 2.150.3 the log file took 2m 30sec in Chrome and after 5 minutes never loaded in Firefox. I kept seeing "A web page is slowing down your browser. What would you like to do? [Stop It, Wait]" and eventually Firefox became unresponsive. I used Chrome 72 and Firefox 65 in my testing.
[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Ioannis Moutsatsos now I noticed, you were using the `projectName` property of the parameter. That is a helper variable, used when the project is created via its constructor. But if it is loaded via serializer/Stapler/etc, then I am not sure if the constructor will always be called. There is a logic that tries to use that variable, but when it is not found, we fallback to locating a project with a parameter UUID (every active choices has a random UUID). However, we do not save the project to `projectName`. For the current implementation - which is a bit complex, and may need to improvements - the best way to access the Jenkins project is via the variable `jenkinsProject`, that the plugin populates automatically. Tried with a groovy script that returned `return [jenkinsProject.name]`, and it worked before & after renaming the project. Hope that makes sense? 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-51791) git polling fails to detect changes when build uses multiple repos
Title: Message Title andrew lorien commented on JENKINS-51791 Re: git polling fails to detect changes when build uses multiple repos Here too. I have tried : "Wipe out repository and Force clean" manually delete workspace directory edit /builds//build.xml and remove references to the other directory searching for /cache/git- folder which might contain wrong build information. 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-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum created an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Issue Type: Bug Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2019-03-04 01:51 Environment: Jenkins-2.165 remoting-kafka-1.1.3 Priority: Major Reporter: Federico Naum Only discovered when I moved to the production environment that the server and client side of this plugin are taking too much user CPU time. I think it is because the large number of threads (hopefully unnecessary) it spawns. Also, it might be consuming unnecessary memory. In the agent side, even when there are no jobs assigned it consumes a full cpu, and create about 30-40 threads. A naive thought is telling me that we should open as many threads as the number of executors the agent is configured with. On the server side, when I have about 8-10 kafka agent nodes it takes ~7 cpus (of my 8 cores), with kafka Channel reader threads that are opened for the agents. In addition to the 54 threads that are created for the kafka-producer-network thread In my test Jenkins instance, I observed the creation of 900+ threads I tested with the inside the docker container that is provided with the plugin and also observed it creates a high number of threads. I'll upload some screenshots.
[JIRA] (JENKINS-55439) Update Remoting in the Remoting Kafka client to the recent version
Title: Message Title Federico Naum commented on JENKINS-55439 Re: Update Remoting in the Remoting Kafka client to the recent version PR for this minor change 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-55439) Update Remoting in the Remoting Kafka client to the recent version
Title: Message Title Federico Naum assigned an issue to Federico Naum Jenkins / JENKINS-55439 Update Remoting in the Remoting Kafka client to the recent version Change By: Federico Naum Assignee: Federico Naum 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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . commented on JENKINS-56374 Re: JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins Attached visualvm dump of retained-object sizes showing the suites in memory. 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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . updated an issue Jenkins / JENKINS-56374 JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins Change By: Shevek . Attachment: jenkins-memory.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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . updated an issue Jenkins / JENKINS-56374 JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins Change By: Shevek . Environment: LinuxJava 8Jenkins 2.150.1JUnit plugin 1.27xUnit plugin 2.3.2 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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . commented on JENKINS-56374 Re: JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins After the GC-storm, we get this: num #instances #bytes class name -- 1: 208769 27421360 [C 2: 208315 4999560 java.lang.String 3: 81032 2593024 java.util.HashMap$Node 4: 37398 2486496 [Ljava.lang.Object; 5: 9331 2316560 [B 6: 18857 2092720 java.lang.Class 7: 62775 2008800 java.util.concurrent.ConcurrentHashMap$Node 8: 20596 1812448 java.lang.reflect.Method 9: 12253 1242400 [Ljava.util.HashMap$Node; 10: 11491 947256 [Ljava.util.WeakHashMap$Entry; which is a lot saner, and shows that all the data held in memory was related to the memory inefficiency/leak in the reporter, and is not part of normal operation. 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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . updated an issue Jenkins / JENKINS-56374 JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins Change By: Shevek . Labels: memory-leak 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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . commented on JENKINS-56374 Re: JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins jmap -histo:live output: num #instances #bytes class name -- 1: 2678703 2691823496 [C 2: 2678264 64278336 java.lang.String 3: 811096 58398912 hudson.tasks.junit.CaseResult 4: 319187 10213984 java.util.HashMap$Node 5: 192771 8994440 [Ljava.lang.String; 6: 42153 7186960 [Ljava.lang.Object; 7: 187092 4490208 com.thoughtworks.xstream.io.path.Path 8: 12333 2778840 [Ljava.util.HashMap$Node; 9: 18705 2075528 java.lang.Class 10: 61023 1952736 java.util.concurrent.ConcurrentHashMap$Node Where did we get 811,096 CaseResults in the heap from? They're all live objects, too. This looks like a serious memory leak. 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-56374) JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins
Title: Message Title Shevek . updated an issue Jenkins / JENKINS-56374 JUnitResultArchiver parsing XML in sort()->compare(), killing Jenkins Change By: Shevek . Summary: JUnitResultArchiver crazy resource inefficient parsing XML in sort()->compare() , killing Jenkins 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-56375) custom jnlp not working
Title: Message Title
Sushant Pradhan created an issue
Jenkins / JENKINS-56375
custom jnlp not working
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-03-03 22:14
Environment:
Jenkins: 2.150.3 Kubernetes: 1.14.3
Priority:
Major
Reporter:
Sushant Pradhan
I have this in my pipeline:
def label = "mypod-${UUID.randomUUID().toString()}"
podTemplate(label: label, yaml: """
apiVersion: v1
kind: Pod
metadata:
labels:
some-label: some-label-value
spec:
containers:
- name: jnlp
image: 1234567890.dkr.ecr.us-east-1.amazonaws.com/jenkins-slave:1.0.0
command:
- /usr/local/bin/jenkins-slave
tty: true
securityContext:
runAsUser: 1
allowPrivilegeEscalation: false
"""
) {
node (label) {
container('jnlp') {
sh "hostname"
sh "mvn --version"
}
}
}
When I execute this, i expect that the maven version from my custom jnlp image gets printed, instead I get the following error:
[Pipeline] node
Agent mypod-6cf91ebc-71db-4c56-80c8-8f332d796ccf-413hd-m09jd is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] (mypod-6cf91ebc-71db-4c56-80c8-8f332d796ccf):
* [jnlp] jenkins/jnlp-slave:alpine
yaml:
apiVersion: v1
kind: Pod
metadata:
labels:
[JIRA] (JENKINS-56374) JUnitResultArchiver crazy resource inefficient, killing Jenkins
Title: Message Title Shevek . commented on JENKINS-56374 Re: JUnitResultArchiver crazy resource inefficient, killing Jenkins Note that this is the ONLY executor running, we don't run anything else in-process, and the XML file it's failing to load is only 100Mb. Wait... are we parsing XML in the compare() routine of a sort-object? What the $BADWORD...? WAT? 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-55096) can not override jnlp container
Title: Message Title Sushant Pradhan commented on JENKINS-55096 Re: can not override jnlp container I also have similar issue. Irrespective of yaml or ui override, the plugin is always pulling jnlp:alpine even though i have my custom jnlp named as jnlp Jenkins: 2.150.3 and Kubernetes plugin: 1.14.3 Can we please reopen this ticket or explain what configuration will make my custom jnlp 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-55096) can not override jnlp container
Title: Message Title Sushant Pradhan commented on JENKINS-55096 Re: can not override jnlp container I also have similar issue. Irrespective of yaml or ui override, the plugin is always pulling jnlp:alpine even though i have my custom jnlp named as jnlp Jenkins: 2.150.3 and Kubernetes plugin: 1.14.3 Can we please reopen this ticket or explain what configuration will make my custom jnlp 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-56374) JUnitResultArchiver crazy resource inefficient, killing Jenkins
Title: Message Title Shevek . commented on JENKINS-56374 Re: JUnitResultArchiver crazy resource inefficient, killing Jenkins Related stack: ``` Mar 03, 2019 10:00:07 PM hudson.tasks.junit.TestResultAction load WARNING: Failed to load /home/jenkins/jobs/XXX-pr/builds/6739/junitResult.xml java.io.IOException: Unable to read /home/jenkins/jobs/XXX-pr/builds/6739/junitResult.xml at hudson.XmlFile.read(XmlFile.java:149) at hudson.tasks.junit.TestResultAction.load(TestResultAction.java:208) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:138) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:63) at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:252) at hudson.tasks.test.TestResult.getPreviousResult(TestResult.java:146) at hudson.tasks.junit.SuiteResult.getPreviousResult(SuiteResult.java:416) at hudson.tasks.junit.CaseResult.getPreviousResult(CaseResult.java:479) at hudson.tasks.junit.CaseResult.freeze(CaseResult.java:641) at hudson.tasks.junit.SuiteResult.freeze(SuiteResult.java:462) at hudson.tasks.junit.TestResult.freeze(TestResult.java:748) at hudson.tasks.junit.TestResultAction.load(TestResultAction.java:213) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:145) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:63) at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:252) at hudson.tasks.test.TestResult.getPreviousResult(TestResult.java:146) at hudson.tasks.junit.SuiteResult.getPreviousResult(SuiteResult.java:416) at hudson.tasks.junit.CaseResult.getPreviousResult(CaseResult.java:479) at hudson.tasks.junit.CaseResult.freeze(CaseResult.java:641) at hudson.tasks.junit.SuiteResult.freeze(SuiteResult.java:462) at hudson.tasks.junit.TestResult.freeze(TestResult.java:748) at hudson.tasks.junit.TestResultAction.load(TestResultAction.java:213) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:138) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:63) at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:252) at hudson.tasks.test.TestResult.getPreviousResult(TestResult.java:146) at hudson.tasks.junit.SuiteResult.getPreviousResult(SuiteResult.java:416) at hudson.tasks.junit.CaseResult.getPreviousResult(CaseResult.java:479) at hudson.tasks.junit.CaseResult.freeze(CaseResult.java:641) at hudson.tasks.junit.SuiteResult.freeze(SuiteResult.java:462) at hudson.tasks.junit.TestResult.freeze(TestResult.java:748) at hudson.tasks.junit.TestResultAction.load(TestResultAction.java:213) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:138) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:63) at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:252) at hudson.tasks.test.TestResult.getPreviousResult(TestResult.java:146) at hudson.tasks.junit.SuiteResult.getPreviousResult(SuiteResult.java:416) at hudson.tasks.junit.CaseResult.getPreviousResult(CaseResult.java:479) at hudson.tasks.junit.CaseResult.freeze(CaseResult.java:641) at hudson.tasks.junit.SuiteResult.freeze(SuiteResult.java:462) at hudson.tasks.junit.TestResult.freeze(TestResult.java:748) at hudson.tasks.junit.TestResultAction.load(TestResultAction.java:213) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:138) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:63) at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:252) at
[JIRA] (JENKINS-56374) JUnitResultArchiver crazy resource inefficient, killing Jenkins
Title: Message Title Shevek . updated an issue Jenkins / JENKINS-56374 JUnitResultArchiver crazy resource inefficient, killing Jenkins Change By: Shevek . Jenkins 2.150.1Jenkins dies with the JVM going into perpetual ergonomics GC. The JVM has a 4Gb heap. The biggest XML file is 180Mb. So that's not a fundamental limitation. Something dumb is going on.I _think_ it might be repeatedly parsing the same XML file again and again, because when I dump jstack, I've seen a lot of different XML parsers there. This MIGHT be triggered by a @Parameterized junit test with 50,000 cases. In any case, this has made Jenkins totally unusable.It also dies when we have a single JUnit case with a 1Gb output XML, but we have worked around that. But we cannot reduce the size of our test suite just to keep Jenkins happy.Reported critical as this has stopped us from using Jenkins. Tempted to report blocker.Here is some stack.``` at com.thoughtworks.xstream.mapper.AnnotationMapper.processAnnotations(AnnotationMapper.java:180) at com.thoughtworks.xstream.mapper.AnnotationMapper.defaultImplementationOf(AnnotationMapper.java:141) at hudson.util.xstream.MapperDelegate.defaultImplementationOf(MapperDelegate.java:59) at com.thoughtworks.xstream.mapper.MapperWrapper.defaultImplementationOf(MapperWrapper.java:46) at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:475) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:327) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:331) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at
[JIRA] (JENKINS-56374) JUnitResultArchiver crazy resource inefficient, killing Jenkins
Title: Message Title Shevek . updated an issue Jenkins / JENKINS-56374 JUnitResultArchiver crazy resource inefficient, killing Jenkins Change By: Shevek . Environment: Jenkins 2.150.1Jenkins dies with the JVM going into perpetual ergonomics GC. The JVM has a 4Gb heap. The biggest XML file is 180Mb. So that's not a fundamental limitation. Something dumb is going on.I _think_ it might be repeatedly parsing the same XML file again and again, because when I dump jstack, I've seen a lot of different XML parsers there. This MIGHT be triggered by a @Parameterized junit test with 50,000 cases. In any case, this has made Jenkins totally unusable.It also dies when we have a single JUnit case with a 1Gb output XML, but we have worked around that. But we cannot reduce the size of our test suite just to keep Jenkins happy.Reported critical as this has stopped us from using Jenkins. Tempted to report blocker.Here is some stack.```at com.thoughtworks.xstream.mapper.AnnotationMapper.processAnnotations(AnnotationMapper.java:180)at com.thoughtworks.xstream.mapper.AnnotationMapper.defaultImplementationOf(AnnotationMapper.java:141)at hudson.util.xstream.MapperDelegate.defaultImplementationOf(MapperDelegate.java:59)at com.thoughtworks.xstream.mapper.MapperWrapper.defaultImplementationOf(MapperWrapper.java:46)at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:475)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:327)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85)at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80)at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:331)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)at
[JIRA] (JENKINS-56374) JUnitResultArchiver crazy resource inefficient, killing Jenkins
Title: Message Title Shevek . created an issue Jenkins / JENKINS-56374 JUnitResultArchiver crazy resource inefficient, killing Jenkins Issue Type: Bug Assignee: Varun Menon Components: core, junit-plugin, test-results-analyzer-plugin Created: 2019-03-03 22:07 Environment: Jenkins 2.150.1 Jenkins dies with the JVM going into perpetual ergonomics GC. The JVM has a 4Gb heap. The biggest XML file is 180Mb. So that's not a fundamental limitation. Something dumb is going on. I _think_ it might be repeatedly parsing the same XML file again and again, because when I dump jstack, I've seen a lot of different XML parsers there. This MIGHT be triggered by a @Parameterized junit test with 50,000 cases. In any case, this has made Jenkins totally unusable. It also dies when we have a single JUnit case with a 1Gb output XML, but we have worked around that. But we cannot reduce the size of our test suite just to keep Jenkins happy. Reported critical as this has stopped us from using Jenkins. Tempted to report blocker. Here is some stack. ``` at com.thoughtworks.xstream.mapper.AnnotationMapper.processAnnotations(AnnotationMapper.java:180) at com.thoughtworks.xstream.mapper.AnnotationMapper.defaultImplementationOf(AnnotationMapper.java:141) at hudson.util.xstream.MapperDelegate.defaultImplementationOf(MapperDelegate.java:59) at com.thoughtworks.xstream.mapper.MapperWrapper.defaultImplementationOf(MapperWrapper.java:46) at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:475) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:327) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at
[JIRA] (JENKINS-56373) /directive-generator/ - triggers - githubPush doesn't work
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56373 /directive-generator/ - triggers - githubPush doesn't work Issue Type: Task Assignee: Kirill Merkushev Components: github-plugin Created: 2019-03-03 20:04 Priority: Minor Reporter: Josh Soref visit /directive-generator/ directive: triggers add: githubPush Result: exception: VM3002:1 Uncaught TypeError: Cannot read property 'checked' of undefined at eval (eval at exports.start (warning.js:17), :1:26) at Object.exports.start (warning.js:17) at eval (eval at geval (hudson-behavior.js:391), :6:4) at eval () at geval (hudson-behavior.js:391) at hudson-behavior.js:598 at next (hudson-behavior.js:616) at HTMLScriptElement.script.onload.script.onreadystatechange (hudson-behavior.js:2720) > $$(options.input) [] > $$(options.input).first() undefined > $$(options.input).first().checked TypeError: Cannot read property 'checked' of undefined at Object.exports.start (http://localhost:9001/static/cfe709a8/plugin/github/js/warning.js:17:39) at eval (eval at geval (http://localhost:9001/static/cfe709a8/scripts/hudson-behavior.js:391:30), :6:4) at eval () at geval
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref Labels: jira-plugin-3.0.6 pipeline-model-definition-plugin xunit 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-56372) streamline variable labels
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-56372 streamline variable labels Change By: Josh Soref Assignee: Andrew Bayer Josh Soref 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-56372) streamline variable labels
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56372 streamline variable labels Issue Type: Task Assignee: Andrew Bayer Attachments: image-2019-03-03-13-43-42-555.png Components: pipeline-model-definition-plugin Created: 2019-03-03 18:45 Priority: Minor Reporter: Josh Soref Load /directive-generator/ Select environment Scanning the two field labels is painful because they both start Variable: Add Comment
[JIRA] (JENKINS-56371) pipelines with more than 1 stage that publishes tests results in multiple "+ no issue" links per test
Title: Message Title boris ivan created an issue Jenkins / JENKINS-56371 pipelines with more than 1 stage that publishes tests results in multiple "+ no issue" links per test Issue Type: Bug Assignee: Catalin Luta Components: jiratestresultreporter-plugin Created: 2019-03-03 18:22 Priority: Major Reporter: boris ivan I have a pipeline that has multiple stages, and more than 1 of them has a junit publish step. The tests in those stages are all unique. When the pipeline is complete and I examine the test report, I notice that each failed test has 5 "+ no issue" links on the line for that test. I think that's the same number of stages that publish junit results, even though each test only exists in 1 stage. It looks like the logic that adds the "+ no issue" link must be adding it multiple times, in the scenario where a pipeline has multiple stages that have a junit publisher. Add Comment
[JIRA] (JENKINS-56370) context specific field not working with jiratestresultreporter-plugin
Title: Message Title
boris ivan created an issue
Jenkins / JENKINS-56370
context specific field not working with jiratestresultreporter-plugin
Issue Type:
Bug
Assignee:
Catalin Luta
Components:
jiratestresultreporter-plugin
Created:
2019-03-03 18:11
Priority:
Major
Reporter:
boris ivan
When trying to create an issue from the test report, a JIRA field that is context-related to a different JIRA field couldn't be set. Specifically, in the UI our 'create' screen has a few custom required fields. Two of these fields have a relationship, we have a field with a text label: "Major Area" and another field with text label "Component", both are dropdown lists of selectable values. In the JIRA UI, once I select a value for the "Major Area" field, it changes the various selectable choices for "Component". Looking at the html source, these fields have have the following values for name and id: "Major Area" – has name and id: "customfield_11100" "Component" – has name and id: "customfield_11100:1" There are other required fields (without the 'relationship' described above) that also have name/id similar to above, like "customfield_11101" and "customfield_11102", and when I wasn't setting them properly with this plugin, the plugin would show that JIRA was sending a 400 error, complaining that the fields weren't set, and I've now set those properly and those errors have stopped, so I believe I'm configuring the values for this plugin correctly. But the context-dependent field "Component" (name/id in the html shows as customfield_11100:1) doesn't want to cooperate. Here's the error I receive from this plugin, when setting that value: Error when creating issue RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors= {customfield_11100:1=Field 'customfield_11100:1' cannot be set. It is not on the appropriate screen, or unknown.} , errorMessages=[]}]} Here's what my pipeline syntax looks like: junit ( allowEmptyResults: true, testResults:
[JIRA] (JENKINS-56369) sendCIMessage - Problem accessing /pipeline-syntax/null. Reason:
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56369 sendCIMessage - Problem accessing /pipeline-syntax/null. Reason: Issue Type: Task Assignee: Scott Hebert Components: jms-messaging-plugin Created: 2019-03-03 17:54 Priority: Minor Reporter: Josh Soref Visit /pipeline-syntax/ Select sendCIMessage: Messaging Provider HTTP ERROR 404 Problem accessing /pipeline-syntax/null. Reason: Not Found Powered by Jetty:// 9.4.z-SNAPSHOT Override provider topic Message type HTTP ERROR 404 Problem accessing /pipeline-syntax/null. Reason: Not Found Powered by Jetty:// 9.4.z-SNAPSHOT Add Comment
[JIRA] (JENKINS-56366) hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107)
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-56366
hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107)
Change By:
Josh Soref
Comment:
{{sendCIMessage}} is different:{code:java}Messaging ProviderHTTP ERROR 404Problem accessing /pipeline-syntax/null. Reason:Not FoundPowered by Jetty:// 9.4.z-SNAPSHOTOverride provider topic Message typeHTTP ERROR 404Problem accessing /pipeline-syntax/null. Reason:Not FoundPowered by Jetty:// 9.4.z-SNAPSHOT {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-56366) hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107)
Title: Message Title Josh Soref commented on JENKINS-56366 Re: hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107) sendCIMessage is different: Messaging Provider HTTP ERROR 404 Problem accessing /pipeline-syntax/null. Reason: Not Found Powered by Jetty:// 9.4.z-SNAPSHOT Override provider topic Message type HTTP ERROR 404 Problem accessing /pipeline-syntax/null. Reason: Not Found Powered by Jetty:// 9.4.z-SNAPSHOT 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-56368) readTrusted: unlabeled field in /pipeline-syntax/
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56368 readTrusted: unlabeled field in /pipeline-syntax/ Issue Type: Task Assignee: Unassigned Attachments: image-2019-03-03-12-44-55-560.png Components: workflow-multibranch-plugin Created: 2019-03-03 17:45 Priority: Minor Reporter: Josh Soref Visit /pipeline-syntax/ Select readTrusted Expected: Fields should have labels Add Comment
[JIRA] (JENKINS-56367) squished dropdown
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56367 squished dropdown Issue Type: Task Assignee: Unassigned Attachments: image-2019-03-03-12-30-26-519.png Components: core, github-branch-source-plugin Created: 2019-03-03 17:32 Priority: Minor Reporter: Josh Soref visit https://ci.jenkins.io/pipeline-syntax/ sample step: library; retrieval method: modern scm I'm not sure where the fault is/what code is operative. The client might be: https://github.com/jenkinsci/github-branch-source-plugin/blob/76bfd3efcbd68ec6ceffa0c4860a55497ea45219/src/main/resources/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator/config.jelly#L4 I'm wondering if the problem is a bad interaction between some magic hoisting and jenkinsci/jenkins: core/src/main/resources/lib/form/invisibleEntry.jelly Found w/ 2.150.3 (ci.j.o) and 2.166 (localhost)
[JIRA] (JENKINS-56366) hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107)
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-56366
hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107)
Change By:
Josh Soref
# Visit /pipeline-syntax/ # Select {{hubotApprove}} or {{hubotSend}} # Get red jenkins Oops! for the {{Site Name}} field:{code:java}java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) {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
[JIRA] (JENKINS-56366) hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107)
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56366 hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107) Issue Type: Task Assignee: Naresh Rayapati Components: hubot-steps-plugin Created: 2019-03-03 17:01 Priority: Minor Reporter: Josh Soref Visit /pipeline-syntax/ Select hubotApprove Get red jenkins Oops! for the Site Name field: java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)
[JIRA] (JENKINS-49394) Allow to specify visibility on addComment
Title: Message Title Naresh Rayapati commented on JENKINS-49394 Re: Allow to specify visibility on addComment Released with 1.4.5, should make it to update center soon. https://github.com/jenkinsci/jira-steps-plugin/releases/tag/jira-steps-1.4.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49394) Allow to specify visibility on addComment
Title: Message Title Naresh Rayapati updated JENKINS-49394 Jenkins / JENKINS-49394 Allow to specify visibility on addComment Change By: Naresh Rayapati Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49394) Allow to specify visibility on addComment
Title: Message Title Naresh Rayapati commented on JENKINS-49394 Re: Allow to specify visibility on addComment Released with 1.4.5, should make it to update center soon. https://github.com/jenkinsci/jira-steps-plugin/releases/tag/jira-steps-1.4.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56365) switch /configure anchors from #section92 to #section-pluginid
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56365 switch /configure anchors from #section92 to #section-pluginid Issue Type: Task Assignee: Unassigned Attachments: image-2019-03-03-11-50-58-611.png Components: core Created: 2019-03-03 16:51 Priority: Minor Reporter: Josh Soref Currently there are anchors, but they aren't remotely portable. If any plugins are added/removed/enabled/disabled, the links will change. They also aren't human readable. At least using the internal name of a plugin would give some stability. Add Comment
[JIRA] (JENKINS-56074) [assignIssue] Set an issue to Unassigned
Title: Message Title Naresh Rayapati updated JENKINS-56074 Jenkins / JENKINS-56074 [assignIssue] Set an issue to Unassigned Change By: Naresh Rayapati Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56074) [assignIssue] Set an issue to Unassigned
Title: Message Title Naresh Rayapati commented on JENKINS-56074 Re: [assignIssue] Set an issue to Unassigned Released with 1.4.5, should make it to update center soon. https://github.com/jenkinsci/jira-steps-plugin/releases/tag/jira-steps-1.4.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56365) switch /configure anchors from #section92 to #section-pluginid
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56365 switch /configure anchors from #section92 to #section-pluginid Issue Type: Task Assignee: Unassigned Attachments: image-2019-03-03-11-50-58-611.png Components: core Created: 2019-03-03 16:51 Priority: Minor Reporter: Josh Soref Currently there are anchors, but they aren't remotely portable. If any plugins are added/removed/enabled/disabled, the links will change. They also aren't human readable. At least using the internal name of a plugin would give some stability. Add Comment
[JIRA] (JENKINS-55750) IAR parser not finding warnings of IAR ARM compiler
Title: Message Title Lorenz Aebi updated JENKINS-55750 Jenkins / JENKINS-55750 IAR parser not finding warnings of IAR ARM compiler Change By: Lorenz Aebi Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56364) /pipeline-syntax/ doesn't handle lost session
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56364 /pipeline-syntax/ doesn't handle lost session Issue Type: Task Assignee: Unassigned Components: core, workflow-cps-plugin Created: 2019-03-03 16:44 Priority: Minor Reporter: Josh Soref Visit /pipeline-syntax/ Select an item (e.g. bat) Wait for the server to restart Switch the drop down to something else The area for the selected item is cleared The area for the new item won't be updated If you switch to something that's already been cached, the area will be updated to the cached item Expected results: There is an error about the session, it should be reported to the user. Actual results: prototype.js:1585 POST http://localhost:9001/$stapler/bound/227c70ea-aa50-4471-b154-874a9ad2cae4/render 404 (Not Found)prototype.js:1585 POST http://localhost:9001/$stapler/bound/227c70ea-aa50-4471-b154-874a9ad2cae4/render 404 (Not Found) request @ prototype.js:1585 initialize @ prototype.js:1550 (anonymous) @ prototype.js:452 klass @ prototype.js:101 proxy.(anonymous function) @ bind.js:48 renderOnDemand @ hudson-behavior.js:554 updateDropDownList @ hudson-behavior.js:1127 ListPicker._handleKeyDown
[JIRA] (JENKINS-56235) Strip file:// from IDEA inspection file paths
Title: Message Title Lorenz Aebi updated JENKINS-56235 Jenkins / JENKINS-56235 Strip file:// from IDEA inspection file paths Change By: Lorenz Aebi 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-56363) Handling job name especially default state in parameters field for /pipeline-syntax/ styling needs work
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-56363
Handling job name especially default state in parameters field for /pipeline-syntax/ styling needs work
Issue Type:
Task
Assignee:
Unassigned
Attachments:
image-2019-03-03-11-24-06-733.png, image-2019-03-03-11-25-30-340.png, image-2019-03-03-11-26-29-795.png
Components:
pipeline-build-step-plugin
Created:
2019-03-03 16:31
Priority:
Minor
Reporter:
Josh Soref
Visit /pipeline-syntax/
Sample step: Build a job
Note that the parameters area is empty:
Enter a job that doesn't exist
Press tab to give the plugin a hint to update
See "No such job {jobname}"
Clear the job field
See a note about no such job:
Expected results:
There should generally be a hint about why an area is blank. Special casing the default view vs. the entered and cleared state for parameters should not happen. It's ok to not show the this field is blank for the input field.
When listing a job name in a sentence, it should be clear which is the job name,
[JIRA] (JENKINS-56235) Strip file:// from IDEA inspection file paths
Title: Message Title Lorenz Aebi started work on JENKINS-56235 Change By: Lorenz Aebi 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-56271) xUnit produce an empty report for NUnit3 type
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-56271 xUnit produce an empty report for NUnit3 type Change By: Nikolas Falco Released As: 2.3.2 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-55907) NUnit3 fails when SetUpFixture feature is used
Title: Message Title Nikolas Falco updated JENKINS-55907 Jenkins / JENKINS-55907 NUnit3 fails when SetUpFixture feature is used Change By: Nikolas Falco Status: Fixed but Unreleased Resolved Released As: 2.3.2 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-54255) xUnit sets build status incorrectly
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Vlad Aginsky your issue is not similar to this one. This one is related to new tests counting. Anyway if this is your configuration (it's not clear from your post, seems commented) xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')], the unstable build status is correct and is in accordance with what the tooltips document. Maybe you wanted to set up the threshold in this manner xunit thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0')], tools: [Cus... with failureThreshold instead of unstableThreshold Keep in mind also what failureNewThreshold means. Jenkins / JENKINS-54255 xUnit sets build status incorrectly Change By: Nikolas Falco Status: Reopened Closed Resolution: Cannot Reproduce Add Comment
[JIRA] (JENKINS-56235) Strip file:// from IDEA inspection file paths
Title: Message Title Lorenz Aebi assigned an issue to Lorenz Aebi Jenkins / JENKINS-56235 Strip file:// from IDEA inspection file paths Change By: Lorenz Aebi Assignee: Lorenz Aebi 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-54255) xUnit sets build status incorrectly
Title: Message Title
Vlad Aginsky edited a comment on JENKINS-54255
Re: xUnit sets build status incorrectly
Hi i am facing very similar issue:this is how i define xunit trasholds: {code:java}// xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')],tools: [Custom(customXSL: "${JENKINS_URL}/userContent/pytest-to-junit.xsl", deleteOutputFiles: true, failIfNotNew: true, pattern: "${env.DOWNLOADED_ARTIFACTS_PATH}/${env.TEST_RESULTS_PATH}/*.xml", skipNoTestFiles: true, stopProcessingIfError: true)]{code} I have some build new failed tests:|!https://swdvp-jnk01.anpa.corp.amazon.com:9080/static/da57df94/images/48x48/clipboard.png!|Test Result (40 failures / +17)| i expect to get failed status, but xunit still sets the build to be unstable:{code:java}01:57:59.736 INFO: Starting to record.01:57:59.736 INFO: Processing Custom Tool01:58:00.146 INFO: Stopping recording.01:58:00.147 INFO: Check 'Failed Tests' threshold.01:58:00.147 INFO: The new number of tests for the threshold 'Failed Tests' exceeds the specified "new failure threshold" value.{code} I use: * [Jenkins ver. 2.160|https://jenkins.io/] * xUnit plugin 2.3.2
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-54255) xUnit sets build status incorrectly
Title: Message Title
Vlad Aginsky edited a comment on JENKINS-54255
Re: xUnit sets build status incorrectly
Hi i am facing very similar issue:this is how i define xunit trasholds: {code:java}// xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')],tools: [Custom(customXSL: "${JENKINS_URL}/userContent/pytest-to-junit.xsl", deleteOutputFiles: true, failIfNotNew: true, pattern: "${env.DOWNLOADED_ARTIFACTS_PATH}/${env.TEST_RESULTS_PATH}/*.xml", skipNoTestFiles: true, stopProcessingIfError: true)]{code} I have some build new failed tests:|!https://swdvp-jnk01.anpa.corp.amazon.com:9080/static/da57df94/images/48x48/clipboard.png!|Test Result (40 failures / +17)| i expect to get failed status, but xunit still sets the build to be unstable: *04 {code : 38 java}01 : 05 57:59 . 965* 736 INFO: Starting to record. *04 01 : 38 57 : 05 59 . 965* 736 INFO: Processing Custom Tool *04 01 : 38 58 : 06 00 . 714* 146 INFO: Stopping recording. *04 01 : 38 58 : 06 00 . 721* 147 INFO: Check 'Failed Tests' threshold. *04 01 : 38 58 : 06 00 . 721* 147 INFO: The total new number of tests for the threshold 'Failed Tests' exceeds the specified " unstable new failure threshold" value. {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-54255) xUnit sets build status incorrectly
Title: Message Title
Vlad Aginsky reopened an issue
Hi i am facing very similar issue: this is how i define xunit trasholds:
// xunit thresholds: [failed(unstableThreshold: '0',failureNewThreshold: '0')],
tools: [Custom(customXSL: "${JENKINS_URL}/userContent/pytest-to-junit.xsl",
deleteOutputFiles: true,
failIfNotNew: true,
pattern: "${env.DOWNLOADED_ARTIFACTS_PATH}/${env.TEST_RESULTS_PATH}/*.xml",
skipNoTestFiles: true,
stopProcessingIfError: true)]
I have some build new failed tests:
Test Result (40 failures / +17)
i expect to get failed status, but xunit still sets the build to be unstable: 04:38:05.965 INFO: Starting to record.04:38:05.965 INFO: Processing Custom Tool*04:38:06.714* INFO: Stopping recording.04:38:06.721 INFO: Check 'Failed Tests' threshold.04:38:06.721 INFO: The total number of tests for the threshold 'Failed Tests' exceeds the specified "unstable threshold" value.
Jenkins / JENKINS-54255
xUnit sets build status incorrectly
Change By:
Vlad Aginsky
Resolution:
Cannot Reproduce
Status:
Closed Reopened
[JIRA] (JENKINS-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Mark Waite edited a comment on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore The best path is to submit a separate bug report which describes the precise conditions of the problem you're seeing. There are so many Jenkins server servers in the world and so many agents in the world that I expect the case you're seeing will have some specific details which make it more uncommon than typical.Some of the attributes that might make your environment different could include:* operating system of the Jenkins master* operating system of the agent that has the issue* Jenkins master version* Java version on Jenkins master and Jenkins agent* Private key type (ed25519, rsa, ecdsa, dsa, ...)* Is FIPS mode enabled on any of the machines involved in the environment* Locale of the master and the agent* Is the private key protected by a passphrase?* Does the passphrase include shell special characters? 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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Mark Waite edited a comment on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore The best path is to submit a separate bug report which describes the precise conditions of the problem you're seeing. There are so many Jenkins servers in the world and so many agents in the world that I expect the case you're seeing will have some specific details which make it more uncommon than typical.Some of the attributes that might make your environment different could include:* operating system of the Jenkins master* operating system of the agent that has the issue* Jenkins master version* Java version on Jenkins master and Jenkins agent* Private key type (ed25519, rsa, ecdsa, dsa, ...)* Is FIPS mode enabled on any of the machines involved in the environment* Locale of the master and the agent* Is the private key protected by a passphrase?* Does the passphrase include shell special characters? * Plugin versions in your installation (Jenkins support pllugin can generate a bundle that includes this info) 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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Mark Waite commented on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore The best path is to submit a separate bug report which describes the precise conditions of the problem you're seeing. There are so many Jenkins server in the world and so many agents in the world that I expect the case you're seeing will have some specific details which make it more uncommon than typical. Some of the attributes that might make your environment different could include: operating system of the Jenkins master operating system of the agent that has the issue Jenkins master version Java version on Jenkins master and Jenkins agent Private key type (ed25519, rsa, ecdsa, dsa, ...) Is FIPS mode enabled on any of the machines involved in the environment Locale of the master and the agent Is the private key protected by a passphrase? Does the passphrase include shell special characters? 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 Henjo van Rees updated an issue Jenkins / JENKINS-56243 Jenkins GUI is slow -removing cookie fixes it (temporarily) Change By: Henjo van Rees The last few week/months all our Jenkins users experience very a very slow web GUI after some time. Situation: * In a clean browser (no cache, cookies) Jenkins is very fast * After some time (workday - 8 hours of active Jenkins use), Jenkins GUI starts to slow down: Loading jobs takes 10+ seconds, loading of static resources are very long pending etc. Jenkins just isn't workable for users at that time. * Logging out + in again does not fix it for that user. * _Removing the ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE cookie fixes everything for that user and makes Jenkins blazing fast again._ So, what happens with the _ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE?_ Why does it cause the slowness after hours of use? _* [update] *_ _*SECURITY-901 / CVE-2019-1003004 in Jenkins 2.150.2 introduced a security fix, but with a side effect that after some time (hours) the Jenkins GUI for that user starts to slow down to a crawl.*_ 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
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Henjo van Rees updated an issue Jenkins / JENKINS-56243 Jenkins GUI is slow -removing cookie fixes it (temporarily) Change By: Henjo van Rees The last few week/months all our Jenkins users experience very a very slow web GUI after some time. Situation: * In a clean browser (no cache, cookies) Jenkins is very fast * After some time (workday - 8 hours of active Jenkins use), Jenkins GUI starts to slow down: Loading jobs takes 10+ seconds, loading of static resources are very long pending etc. Jenkins just isn't workable for users at that time. * Logging out + in again does not fix it for that user. * _Removing the ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE cookie fixes everything for that user and makes Jenkins blazing fast again._ So, what happens with the _ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE?_ Why does it cause the slowness after hours of use? [update] 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 Henjo van Rees updated an issue Jenkins / JENKINS-56243 Jenkins GUI is slow -removing cookie fixes it (temporarily) Change By: Henjo van Rees 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Henjo van Rees edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So, 2.150.1 doesn't seem to have the problem. 2.150.2 and higher have the problem. When I look at the 2.150.2 changelog I immediately see this fix: _ "Deleting a user in an external security realm did not invalidate their session or 'Remember me' cookie cookie_ SECURITY _SECURITY -901 / CVE-2019- 1003004 1003004_ When _When using an external security realm such as LDAP or Active Directory, deleting a user from the security realm does not result in the user losing access to Jenkins. _ While _While deleting the user record from Jenkins did invalidate the 'Remember me' cookie, there was no way to invalidate active sessions besides restarting Jenkins or terminating sessions through other means, such as Monitoring Plugin. _ Jenkins _Jenkins now encodes a per-user seed value in sessions, 'Remember me' cookies, and cached authentications of the remoting-based CLI, that can manually be reset by a user themselves, or an administrator, on the user’s configuration page. Doing so will invalidate all current sessions, 'Remember me' cookies, and cached CLI authentications, requiring credentials to be entered again to authenticate. Deleting a user record in Jenkins will now also invalidate existing sessions, as the current seed value is deleted as well." _ So, concluding: This security fix introduces are very nasty slowdown when using Remember Me and LDAP/AD.How can we escalate this issue further? 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 Henjo van Rees commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So, 2.150.1 doesn't seem to have the problem. 2.150.2 and higher have the problem. When I look at the 2.150.2 changelog I immediately see this fix: "Deleting a user in an external security realm did not invalidate their session or 'Remember me' cookie SECURITY-901 / CVE-2019-1003004 When using an external security realm such as LDAP or Active Directory, deleting a user from the security realm does not result in the user losing access to Jenkins. While deleting the user record from Jenkins did invalidate the 'Remember me' cookie, there was no way to invalidate active sessions besides restarting Jenkins or terminating sessions through other means, such as Monitoring Plugin. Jenkins now encodes a per-user seed value in sessions, 'Remember me' cookies, and cached authentications of the remoting-based CLI, that can manually be reset by a user themselves, or an administrator, on the user’s configuration page. Doing so will invalidate all current sessions, 'Remember me' cookies, and cached CLI authentications, requiring credentials to be entered again to authenticate. Deleting a user record in Jenkins will now also invalidate existing sessions, as the current seed value is deleted as well." So, concluding: This security fix introduces are very nasty slowdown when using Remember Me and LDAP/AD. How can we escalate this issue further? 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-37324) We would like a more meaningful description of a step
Title: Message Title boris avney commented on JENKINS-37324 Re: We would like a more meaningful description of a step Hi, Where can I find which BO version has this functionality? (couldn't find the PR in change log: https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+Plugin) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56362) When the Jenkins server is restarted, any DEFAULT password parameters set in jobs are getting clobbered.
Title: Message Title
MICHAEL LUPO created an issue
Jenkins / JENKINS-56362
When the Jenkins server is restarted, any DEFAULT password parameters set in jobs are getting clobbered.
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-plugin
Created:
2019-03-03 12:58
Environment:
Jenkins 2.150.3 Credentials Plugin 2.1.18
Priority:
Critical
Reporter:
MICHAEL LUPO
All of our jobs that require a password in the job execution (i.e. a codesign keychain password) we set it as a Default Password Parameter in the job config. Recently after a Jenkins update 2.150.1 to 2.150.3 the passwords appear to be getting overwritten by what appears to be an encoded string instead. For example, I print the parameter in a shell in the job config. It's supposed to be a clear text password, but instead, it's something like this: echo '{AQAAABAQu+DPUyCuv/3iI87yPZNs+tar+8vNJqHDr+uTQrlE8if=} I have a question, is the $JENKINS_HOME/secrets folder involved?
Add Comment
[JIRA] (JENKINS-56361) JGIT-octane integration - enrich line changes on SCM commits
Title: Message Title eli Emanuel created an issue Jenkins / JENKINS-56361 JGIT-octane integration - enrich line changes on SCM commits Issue Type: Improvement Assignee: eli Emanuel Components: hp-application-automation-tools-plugin Created: 2019-03-03 12:52 Priority: Minor Reporter: eli Emanuel 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-55436) Duplicate symbols break declarative pipeline engine
Title: Message Title Ulli Hafner updated JENKINS-55436 Should be fixed in 3.0.1 Jenkins / JENKINS-55436 Duplicate symbols break declarative pipeline engine Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 3.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title MICHAEL LUPO commented on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore Mark Waite, the initial import was over three years ago, so I can't comment on that. But the second time I imported that key (last week) I definitely imported the key correctly with the entire prolog. It worked fine on all jenkins_1 users until the server restart. It sounds like I might be hitting a different defect. How can I help dig in to find the root cause? 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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title
Mark Waite edited a comment on JENKINS-53954
Re: Cannot connect to slave/agent Linux anymore
[~mikelupo] I don't understand from your description if the private key which was installed earlier included the expected prologue (and epilogue) or not. Did it include the expected beginning string and ending string?{noformat}-BEGIN RSA PRIVATE KEY-{noformat}If not, then once that prologue is included, does the private key persist across Jenkins server restarts?If the prologue string is included and the agent is unable to connect after server restart, then we'll need much more detail to duplicate the problem. I restart my Jenkins server frequently and it uses private keys to connect to agents with no issue.Please describe further in a *new bug report* what you mean when you say:{quote}When the Jenkins server is restarted, any DEFAULT password parameters set in jobs are getting clobbered.{quote}Does that mean that a job which took a password as a parameter and had a default assigned to that parameter will be run without using the default? If so, please provide a numbered step by step description of the process you use to define that job type so that others can duplicate the behavior. The private key for an ssh connection to an agent is stored by Jenkins itself or by the Jenkins credentials plugin. I'm confident the same basic storage mechanism is used for both secret parameters and private keys.
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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Mark Waite commented on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore MICHAEL LUPO I don't understand from your description if the private key which was installed earlier included the expected prologue (and epilogue) or not. Did it include the expected beginning string and ending string? -BEGIN RSA PRIVATE KEY- If not, then once that prologue is included, does the private key persist across Jenkins server restarts? If the prologue string is included and the agent is unable to connect after server restart, then we'll need much more detail to duplicate the problem. I restart my Jenkins server frequently and it uses private keys to connect to agents with no issue. Please describe further in a new bug report what you mean when you say: When the Jenkins server is restarted, any DEFAULT password parameters set in jobs are getting clobbered. Does that mean that a job which took a password as a parameter and had a default assigned to that parameter will be run without using the default? If so, please provide a numbered step by step description of the process you use to define that job type so that others can duplicate the behavior. 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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title MICHAEL LUPO commented on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore We just noticed yet another anomaly. When the Jenkins server is restarted, any DEFAULT password parameters set in jobs are getting clobbered. As a workaround, we have to reset the default password parameter in the job's config, then re-save it. It will work till the Jenkins server is restarted again. Then we have to rinse-repeat. Mark Waite where do SSH keys & passwords get stored? I would think they are from different plugins, but if their storage is similar, then this might be a hint at the root cause. 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-56065) Change handling of symlinks when scanning for files in warnings-ng-plugin
Title: Message Title Ulli Hafner updated JENKINS-56065 Jenkins / JENKINS-56065 Change handling of symlinks when scanning for files in warnings-ng-plugin Change By: Ulli Hafner 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-55436) Duplicate symbols break declarative pipeline engine
Title: Message Title Matthias Fuchs commented on JENKINS-55436 Re: Duplicate symbols break declarative pipeline engine Is the issue fixed? Or does it mean that I have to live with the incompatibility? 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-56360) Sonar-octane Integration - add support for pipeline as a code
Title: Message Title eli Emanuel created an issue Jenkins / JENKINS-56360 Sonar-octane Integration - add support for pipeline as a code Issue Type: Improvement Assignee: eli Emanuel Components: hp-application-automation-tools-plugin Created: 2019-03-03 09:23 Priority: Minor Reporter: eli Emanuel 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.
