[JIRA] (JENKINS-52863) Issue while publishing results to JIRA from Jenkins
Title: Message Title Praneeth Marrikanti created an issue Jenkins / JENKINS-52863 Issue while publishing results to JIRA from Jenkins Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-07-27 at 2.03.15 PM.png Components: core Created: 2018-08-03 05:52 Priority: Major Reporter: Praneeth Marrikanti Our requirement is to publish test results to Zephyr for JIRA. We have built our scripts using selenium/java in eclipse and we have integrated them in Jenkins. So after building our suite in Jenkins the post build action is to update these results in JIRA in such a way that either it should create a new cycle with these test cases or it should add executed test cases to an existing cycle for the selected project. Hence we are doing this using zephyr for Jira test management plugin. Challenge we are facing is everything is working fine with trail version but when we are trying to replicate the same in our JIRA server showing up some JSON exception. Version details: Jenkins - 2.134(I have also checked with 2.73 to verify whether it is a compatibility issue) JIRA - 7.9.2
[JIRA] (JENKINS-52862) Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403)
Title: Message Title Olivier Lamy commented on JENKINS-52862 Re: Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403) Vivek Pandey branch blueocean-1.5.0-beta-x created https://github.com/jenkinsci/blueocean-plugin/tree/blueocean-1.5.0-beta-x containing the simple fix using Collections.synchronizedMap Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52849) this window is "Interactive Services Detection" is pop up when tomcat is up
Title: Message Title Alex Earl commented on JENKINS-52849 Re: this window is "Interactive Services Detection" is pop up when tomcat is up This is not a bug, please read the following blog for information about this popup. https://blogs.msdn.microsoft.com/patricka/2010/04/27/what-is-interactive-services-detection-and-why-is-it-blinking-at-me/ Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52849) this window is "Interactive Services Detection" is pop up when tomcat is up
Title: Message Title
jn cheng updated an issue
Jenkins / JENKINS-52849
this window is "Interactive Services Detection" is pop up when tomcat is up
Change By:
jn cheng
I write in the section "Exec command" of the Publish Over SSH Plugin:cmd /c call C:\sftp\myscript.bat $BUILD_NUMBERThe content of the file myscript.bat is as follow:Echo --begin-Echo shutdown tomcat(use port 8080)@echo offsetlocal enabledelayedexpansionfor /f "delims= tokens=1" %%i in ('netstat -aon ^| findstr "8080"') do (set a=%%igoto js):jstaskkill /f /pid "! a: ~71,5!"Echo startup tomcat@echo offC:cd C:\software\apache-tomcat-6.0.39\bincall startup.batEcho --end-issue reproduced as follow steps:1.jenkins execute myscript.bat file successfully.2.log on the windows server 2008 machine which the ssh server & tomcat is on.3.i find a window is prompt,this window is "Interactive Services Detection"4.i don't know why this window is pop up,can you give me suggestion?i also attach two 3 images to explain this question.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-52849) this window is "Interactive Services Detection" is pop up when tomcat is up
Title: Message Title jn cheng updated an issue Jenkins / JENKINS-52849 this window is "Interactive Services Detection" is pop up when tomcat is up Change By: jn cheng Attachment: 1-3.jpg Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52849) this window is "Interactive Services Detection" is pop up when tomcat is up
Title: Message Title jn cheng updated an issue Jenkins / JENKINS-52849 this window is "Interactive Services Detection" is pop up when tomcat is up Change By: jn cheng Attachment: 1-1.png Attachment: 1-2.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52849) this window is "Interactive Services Detection" is pop up when tomcat is up
Title: Message Title jn cheng updated an issue Jenkins / JENKINS-52849 this window is "Interactive Services Detection" is pop up when tomcat is up Change By: jn cheng Attachment: 2.jpg Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52849) this window is "Interactive Services Detection" is pop up when tomcat is up
Title: Message Title jn cheng updated an issue Jenkins / JENKINS-52849 this window is "Interactive Services Detection" is pop up when tomcat is up Change By: jn cheng Attachment: 1.jpg Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52851) No way to remove orphaned generated Folders
Title: Message Title Jarrad Whitaker edited a comment on JENKINS-52851 Re: No way to remove orphaned generated Folders My apologies, my this is already implemented.My checkout was configured incorrectly. I was creating folders for each branch, but not pruning remote branches meant JobDSL continued to create folders for them even after being deleted on-server. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52851) No way to remove orphaned generated Folders
Title: Message Title Jarrad Whitaker closed an issue as Fixed My apologies, my checkout was configured incorrectly. I was creating folders for each branch, but not pruning remote branches meant JobDSL continued to create folders for them even after being deleted on-server. Jenkins / JENKINS-52851 No way to remove orphaned generated Folders Change By: Jarrad Whitaker Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title KaiHsiang Chang edited a comment on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Some configurations were misled before v2.x.x, the URL of remote server configuration should be the root URL of remote jenkins , or the build number can't be fetched correctly. If you have trouble when upgrading, try to fix the configuration in your test environment or you can choose to stay in the old version if no new features are required. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title KaiHsiang Chang resolved as Not A Defect Some configurations were misled before v2.x.x, the URL of remote server configuration should be the root URL of remote jenkins or the build number can't be fetched correctly. If you have trouble when upgrading, try to fix the configuration in your test environment or you can choose to stay in the old version if no new features are required. Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: KaiHsiang Chang Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51766) Save flavor during registration and serve different manifest depending on it
Title: Message Title Mandie Smith updated JENKINS-51766 Jenkins / JENKINS-51766 Save flavor during registration and serve different manifest depending on it Change By: Mandie Smith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan edited a comment on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I'm seeing this happen again on the latest Jenkins (well, every LTS above 2.107.3, as well as latest), which are running winstone 4The issue that I'm seeing is that Jenkins fails to completely initialize the * HTTP * listener (HTTPS isn't enabled - k8s ingress takes care of HTTPS, so no need) whenever it's running on a host with >36 CPU's. If I run Jenkins on a host with 36 or fewer CPU's, it starts up just fine. I took the same kubernetes pod (tried with both latest LTS and latest non-LTS), pinned it to a 72-CPU node and it initialized, said everything was good, but never responded to HTTP requests, re-pinned it to a 20-CPU node, and it started correctly.Nothing in the logs indicates that there's an issue at all. The same thing happens both with a completely fresh jenkins_home and one that has been in use for years and has a bunch of plugins installed.For me, rolling back to 2.107.3 makes everything work again. Moving to any newer LTS version breaks everything.This is a rather frustrating issue. I need to update to pick up a bunch of vulnerability fixes. At least I can pin to nodes with fewer CPU's, but this isn't exactly the best workaround. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I'm seeing this happen again on the latest Jenkins (well, every LTS above 2.107.3, as well as latest), which are running winstone 4 The issue that I'm seeing is that Jenkins fails to completely initialize the HTTP listener whenever it's running on a host with >36 CPU's. If I run Jenkins on a host with 36 or fewer CPU's, it starts up just fine. I took the same kubernetes pod (tried with both latest LTS and latest non-LTS), pinned it to a 72-CPU node and it initialized, said everything was good, but never responded to HTTP requests, re-pinned it to a 20-CPU node, and it started correctly. Nothing in the logs indicates that there's an issue at all. The same thing happens both with a completely fresh jenkins_home and one that has been in use for years and has a bunch of plugins installed. For me, rolling back to 2.107.3 makes everything work again. Moving to any newer LTS version breaks everything. This is a rather frustrating issue. I need to update to pick up a bunch of vulnerability fixes. At least I can pin to nodes with fewer CPU's, but this isn't exactly the best workaround. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Andrew Lamonica commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Aaron Jensen, here is what we ended up doing. https://paste.ofcode.org/3aPEN9YyVDEcCGM2JmX8zw Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52862) Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403)
Title: Message Title Olivier Lamy commented on JENKINS-52862 Re: Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403) cc Sam Van Oort wdyt? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52862) Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403)
Title: Message Title Olivier Lamy commented on JENKINS-52862 Re: Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403) A temporary solution would be to use Collections.synchronizedMap on the WeakHashMap. A better solution would be to use a cache solution based on GuavaCache? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52862) Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403)
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-52862 Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403) Issue Type: Task Assignee: Olivier Lamy Components: blueocean-plugin Created: 2018-08-03 00:37 Priority: Critical Reporter: Olivier Lamy similar issue to JENKINS-47725. But in blueocean code: at java.util.WeakHashMap.get(WeakHashMap.java:403) at io.jenkins.blueocean.events.PipelineEventListener.newMessage(PipelineEventListener.java:140) at io.jenkins.blueocean.events.PipelineEventListener.onNewHead(PipelineEventListener.java:73) Add Comment
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Craig Rodrigues commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Daniel Beck This problem has been reproduced and confirmed by multiple people here: https://github.com/jenkinsci/docker/issues/702 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title
Jarrad Whitaker edited a comment on JENKINS-27517
Re: Allow access to the Jenkins instance and/or plugins
Any movement on this?My use case is not even to use plugin code, I just want to {{ @TypeCheck }} my Groovy code. Without being able to {{import hudson.plugins.git.Branch}}, I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title
Jarrad Whitaker edited a comment on JENKINS-27517
Re: Allow access to the Jenkins instance and/or plugins
Any movement on this?My use case is not even to use plugin code, I just want to {{@TypeCheck}} my Groovy code. Without being able to{{import hudson.plugins.git.Branch}}, I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title
Jarrad Whitaker edited a comment on JENKINS-27517
Re: Allow access to the Jenkins instance and/or plugins
Any movement on this?My use case is not even to use plugin code, I just want to {{@TypeCheck }} my Groovy code. Without being able to {{import hudson.plugins.git.Branch}}, I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title
Jarrad Whitaker edited a comment on JENKINS-27517
Re: Allow access to the Jenkins instance and/or plugins
Any movement on this?My use case is not even to use plugin code, I just want to {{ @TypeCheck }} my Groovy code. Without being able to {{import hudson.plugins.git.Branch}}, I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title
Jarrad Whitaker edited a comment on JENKINS-27517
Re: Allow access to the Jenkins instance and/or plugins
Any movement on this?My use case is not even to use plugin code, I just want to ` {{ @TypeCheck ` }} my Groovy code. Without being able to ` {{ import hudson.plugins.git.Branch ` }} , I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title Jarrad Whitaker commented on JENKINS-27517 Re: Allow access to the Jenkins instance and/or plugins Any movement on this? My use case is not even to use plugin code, I just want to `@TypeCheck` my Groovy code. Without being able to `import hudson.plugins.git.Branch`, I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins
Title: Message Title
Jarrad Whitaker edited a comment on JENKINS-27517
Re: Allow access to the Jenkins instance and/or plugins
Any movement on this?My use case is not even to use plugin code, I just want to {{@TypeCheck }}my Groovy code. Without being able to {{import hudson.plugins.git.Branch}}, I don't think it's possible for me to strongly type a method that takes a `Branch` parameter, even if I have no trouble getting the Branch in the first place without the import.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50481) Unable to check updates for plugins
Title: Message Title wgracelee edited a comment on JENKINS-50481 Re: Unable to check updates for plugins I got the same problem on one of my jenkins running with 2.133, on CentOS 7. My Update Site is set to [http://updates.jenkins-ci.org/update-center.json.]When hitting 'Check now' button, the screen stays in 'Checking Updates' page. When I login to the server, I can run 'wget [http://updates.jenkins-ci.org/update-center.json' fine.|http://updates.jenkins-ci.org/update-center.json.] Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50481) Unable to check updates for plugins
Title: Message Title wgracelee commented on JENKINS-50481 Re: Unable to check updates for plugins I got the same problem on one of my jenkins running with 2.133, on CentOS 7. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37849) access and display 'step' informations such as duration
Title: Message Title Sam Van Oort commented on JENKINS-37849 Re: access and display 'step' informations such as duration squalou jenkins Why do you need this information in the Pipeline itself? You can access this from the Blue Ocean UI or the Steps view (link to the left in Classic view). Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32510) SSHD relying on NativePRNG
Title: Message Title Oleg Nenashev updated JENKINS-32510 Jenkins / JENKINS-32510 SSHD relying on NativePRNG Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32510) SSHD relying on NativePRNG
Title: Message Title Oleg Nenashev started work on JENKINS-32510 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32510) SSHD relying on NativePRNG
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-32510
Re: SSHD relying on NativePRNG
SSHD's BouncyCastleRandom class only uses the SecureRandom instance to [generate an 8-byte seed|https://github.com/apache/mina-sshd/blob/83925cb70551c2b5e49f5044efa0d2e74d3180e4/sshd-core/src/main/java/org/apache/sshd/common/util/security/bouncycastle/BouncyCastleRandom.java#L44] using {{SecureRandom#generateSeed}} for a pure-Java PRNG from BouncyCastle, and the constructed BouncyCastleRandom instance is used as a singleton in SSHD, so that call should only block once. The most likely explanation is that it is using {{/dev/random}}, which is blocking occasionally when running tests.We could change the SecureRandom instance to use the NativePRNGNonBlocking provider, which will use {{/dev/urandom}} for engineGenerateSeed. Notably, it looks like SHA1PRNG's [generateSeed|http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/dddb1b026323/src/share/classes/sun/security/provider/SecureRandom.java#l139] and [nextBytes|http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/dddb1b026323/src/share/classes/sun/security/provider/SecureRandom.java#l214] methods use either {{/dev/random}} or {{/dev/urandom}} as their source based on the values of {{java.security.egd}} and {{securerandom.source}}, which we don't want to modify, so SHA1PRNG seems like a bad choice here. We could still use SHA1PRNG's engineNextBytes method, since the seed that it uses to initialize the state is [computed statically|http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/dddb1b026323/src/share/classes/sun/security/provider/SecureRandom.java#l192], and so may already be ready by the time we want to use if if someone else initialized it . , but we can't guarantee that it won't block Since NativePRNGNonBlocking always uses {{/dev/urandom}}, and unlike in JENKINS-20108 we don't care about SHA1PRNG's increased throughput, I think switching to NativePRNGNonBlocking is the best option.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
[JIRA] (JENKINS-48980) Add ability to hide skipped stages/ignore stages altogether (support DRY)
Title: Message Title
Timur Batyrshin edited a comment on JENKINS-48980
Re: Add ability to hide skipped stages/ignore stages altogether (support DRY)
[~abayer], this can could be done as an additional modificator to the pipeline, something like this:{code:java}pipeline { stages {stage('hide me') { when { _expression_ { false } } hide true steps { ... }}stage('skip me but show me') { when { _expression_ { false } }//hide false // default steps { ... }}stage('run me and show me') { when { _expression_ { true } } hide true // hiding doesn't make sense when stage is not skipped steps { ... }} }}{code}My use case is a pipeline library consisting of dozen steps which is shared across dozens different projects.Some steps are skipped based on branch name and showing them up is ok.Some steps are skipped based on project type and I would want to hide them. I could keep a copy of the pipeline for every project type but that doesn't look like very much viable option as the pipeline is 700+ LOC and I don't see much options of reducing it below 400-500 LOC which is quite much too.Copying becomes error prone and increases maintenance when doing changes to the pipeline stages common for all pipelines.So I see 2 viable options for improvement: * add the ability to hide some changes * add the ability to offload stages to external files (https://issues.jenkins-ci.org/browse/JENKINS-42224)Any thoughts?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48980) Add ability to hide skipped stages/ignore stages altogether (support DRY)
Title: Message Title
Timur Batyrshin commented on JENKINS-48980
Re: Add ability to hide skipped stages/ignore stages altogether (support DRY)
Andrew Bayer, this can be done as an additional modificator to the pipeline, something like this:
pipeline {
stages {
stage('hide me') {
when { _expression_ { false } }
hide true
steps { ... }
}
stage('skip me but show me') {
when { _expression_ { false } }
//hide false // default
steps { ... }
}
stage('run me and show me') {
when { _expression_ { true } }
hide true // hiding doesn't make sense when stage is not skipped
steps { ... }
}
}
}
My use case is a pipeline library consisting of dozen steps which is shared across dozens different projects. Some steps are skipped based on branch name and showing them up is ok. Some steps are skipped based on project type and I would want to hide them. I could keep a copy of the pipeline for every project type but that doesn't look like very much viable option as the pipeline is 700+ LOC and I don't see much options of reducing it below 400-500 LOC which is quite much too. Copying becomes error prone and increases maintenance when doing changes to the pipeline stages common for all pipelines. So I see 2 viable options for improvement:
add the ability to hide some changes
add the ability to offload stages to external files (https://issues.jenkins-ci.org/browse/JENKINS-42224)
Any thoughts?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-16950) Can't remove sort of phases in multijob project
Title: Message Title Asad Makarevic commented on JENKINS-16950 Re: Can't remove sort of phases in multijob project This is majorly annoying – please fix it ASAP Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51766) Save flavor during registration and serve different manifest depending on it
Title: Message Title Mandie Smith commented on JENKINS-51766 Re: Save flavor during registration and serve different manifest depending on it The flavor names are based on the directory names for building the containers under distribution: docker-cloud aws-ec2-cloud Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Aaron Jensen commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Here's our use-case: Developers have certain golden paths for creating specific types of applications. We have templates in Jenkins for each type. Developers run a build to create a new application. We grab the config.xml from the template, update it to use values specific to the new job, then post that config.xml to Jenkins to create the job. Switching to the two plug-ins mentioned is a big under-taking. We have to learn Groovy and/or export our entire Jenkins configuration as YAML and write automation to apply it. Given enough warning, we could do it. This feature should be rolled back, then announced that it's coming with instructions on how to migrate to some way of managing job configurations without touching config.xml files. Then the config.xml file format can become internal and you can change to 1.1 if you want and this could get refiled as "allow job configuration to include control characters". Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Aaron Jensen commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 If the config.xml file format is considered internal, Jenkins shouldn't have APIs that expose it. That's not internal. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Aaron Jensen commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Please roll this back. We automate Jenkins using .NET and it doesn't support XML 1.1. It won't even open/parse any XML 1.1 files. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24831) Executor gets assigned multiple times
Title: Message Title Katsuya Tomioka commented on JENKINS-24831 Re: Executor gets assigned multiple times I'm seeing the same issue with the nomad plugin 0.4, Jenkins 2.121.2. If two builds are started close each other (while waiting for executors to be provisioned) both jobs are assigned to the same executor. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50197) Incorporate "pre-release" builds of plugins into Jenkins Essentials
Title: Message Title R. Tyler Croy started work on JENKINS-50197 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50679) Need to provide different environments for testing of git-plugin
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Jenkins / JENKINS-50679 Need to provide different environments for testing of git-plugin Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52861) p4sync's depotSource doesn't handle exclusionary mappings
Title: Message Title
Joel Brown updated an issue
Jenkins / JENKINS-52861
p4sync's depotSource doesn't handle exclusionary mappings
Change By:
Joel Brown
See client/ViewMapHelper.getClientView() - there's no check for a leading "-".Workaround: use a template workspace.Repro: make a p4sync with "Depot Sources" with one good line and one exclusionary path//depot/cases/...-//depot/cases/diff2/.. . p4sync then has:source: depotSource('''//depot/cases/...-//depot/cases/diff2/...''')Console log errro is:P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.Error detected at line 17.Null directory (//) not allowed in '///depot/cases/diff2/...'.Null directory (//) not allowed in '///depot/cases/diff2/...'.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44720) Git Submodules parallel jobs
Title: Message Title Nik Reiman commented on JENKINS-44720 Re: Git Submodules parallel jobs PR is here: https://github.com/jenkinsci/git-client-plugin/pull/348 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52861) p4sync's depotSource doesn't handle exclusionary mappings
Title: Message Title
Joel Brown created an issue
Jenkins / JENKINS-52861
p4sync's depotSource doesn't handle exclusionary mappings
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-08-02 18:29
Priority:
Minor
Reporter:
Joel Brown
See client/ViewMapHelper.getClientView() - there's no check for a leading "-". Workaround: use a template workspace. Repro: make a p4sync with "Depot Sources" with one good line and one exclusionary path //depot/cases/... -//depot/cases/diff2/.. p4sync then has: source: depotSource('''//depot/cases/... -//depot/cases/diff2/...''') Console log errro is: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Error detected at line 17. Null directory (//) not allowed in '///depot/cases/diff2/...'. Null directory (//) not allowed in '///depot/cases/diff2/...'.
Add Comment
[JIRA] (JENKINS-44720) Git Submodules parallel jobs
Title: Message Title Nik Reiman commented on JENKINS-44720 Re: Git Submodules parallel jobs This issue is also important to me, as at my company we have a very large git repo with over 30 submodules. Cloning speeds, even with reference repositories, are quite slow (especially on Windows). We're talking ~10 minutes just for the checkout step, but I have done some basic tests and we estimate we can get this down to just a minute or two with a combination of reference repositories and the --jobs argument. Mark Waite I am sympathetic towards your workload and understand that you have other priorities. I've done some Java development in the past, and I poked around the git-plugin and git-client-plugin source code. I think I've come up with a solution, but I'll probably need some help getting it merged since it's my first contribution to any Jenkins plugin. Your help and patience would be appreciated! Let's continue this discussion at GitHub, where I will submit a pull request soon. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44720) Git Submodules parallel jobs
Title: Message Title Nik Reiman edited a comment on JENKINS-44720 Re: Git Submodules parallel jobs This issue is also important to me, as at my company we have a very large git repo with over 30 submodules. Cloning speeds, even with reference repositories, are quite slow (especially on Windows). We're talking ~10 minutes just for the checkout step, but I have done some basic tests and we estimate we can get this down to just a minute or two with a combination of reference repositories and the --jobs argument updating submodules in parallel .[~markewaite] I am sympathetic towards your workload and understand that you have other priorities. I've done some Java development in the past, and I poked around the git-plugin and git-client-plugin source code. I think I've come up with a solution, but I'll probably need some help getting it merged since it's my first contribution to any Jenkins plugin. Your help and patience would be appreciated!Let's continue this discussion at GitHub, where I will submit a pull request soon. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36624) Make combination filter multi-line if necessary
Title: Message Title Pavel Roskin commented on JENKINS-36624 Re: Make combination filter multi-line if necessary I use 3 axes, with 9*2*2 = 36 builds (soon 9 * 3 * 2 = 54 builds). It takes hours to compile the whole matrix, which means a slow turnaround for pull request. I want to have a good coverage of every axis value without testing every combination of the values. Also, I want explicit control over the combinations, I don't want randomness in pull request testing. The combination filter is totally out of control, it's a huge single line. It would be even better to have a GUI where I could use checkboxes to select the builds. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52860) Remove dependency on Build Flow
Title: Message Title Aaron Jensen created an issue Jenkins / JENKINS-52860 Remove dependency on Build Flow Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-08-02 17:49 Environment: Jenkins 2.73.3 Build Failure Analyzer Plugin 1.20.0 Windows 2012 Priority: Major Reporter: Aaron Jensen The Build Flow plugin is deprecated and has an arbitrary code execution vulnerability. I'm going to have to disable this plugin, which will increase our team's support burden as teams will have to come to use to decipher why builds are broken and what to do to fix them. Please update the build failure analyzer plugin to not depend on the Build Flow plugin. Add Comment
[JIRA] (JENKINS-52043) manager.removeBadge(index) throws UnsupportedOperationException
Title: Message Title Sagar Khushalani commented on JENKINS-52043 Re: manager.removeBadge(index) throws UnsupportedOperationException Created a potential fix: https://github.com/jenkinsci/groovy-postbuild-plugin/pull/36 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22225) Doesn't copy files with blanks in file name
Title: Message Title Alex Earl closed an issue as Not A Defect Change the pattern separator to [,] to include files with spaces. Jenkins / JENKINS-5 Doesn't copy files with blanks in file name Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22225) Doesn't copy files with blanks in file name
Title: Message Title Alex Earl commented on JENKINS-5 Re: Doesn't copy files with blanks in file name Yes, I just tested. You can specify the pattern separator as [,] and even files with spaces will be copied. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22225) Doesn't copy files with blanks in file name
Title: Message Title Alex Earl commented on JENKINS-5 Re: Doesn't copy files with blanks in file name I think you changed the pattern separator from [, ] to just [,] (no space) it would work as well. I'll spin up a test to make sure. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Title: Message Title Alexander Krysko commented on JENKINS-24767 Re: Role-based Authorization Strategy not working with sub-folders Daniel Beck, after several tries I got what I needed, thank you. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Title: Message Title Alexander Krysko updated an issue Jenkins / JENKINS-24767 Role-based Authorization Strategy not working with sub-folders Change By: Alexander Krysko Comment: Second comment is not very specific. In plugin configuration there are Global and Project roles. So * should there be Overall Read checkbox in a Global role * should there be Job Read checkbox in a Global roleMay I ask someone who succeeded in described configuration to attach screenshots? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-52847 durable-task plugin v1.23 misbehaves on BusyBox agents Change By: Devin Nusbaum Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52819) "update/create" events not pushed to evergreen-client
Title: Message Title R. Tyler Croy resolved as Fixed Temporarily reducing the replicas to 1 allows production to send events just fine Jenkins / JENKINS-52819 "update/create" events not pushed to evergreen-client Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52819) "update/create" events not pushed to evergreen-client
Title: Message Title R. Tyler Croy commented on JENKINS-52819 Re: "update/create" events not pushed to evergreen-client The problem appears to be two fold: WebSocket connections are not being handled properly through Kubernetes Service events not being synchronized between evergreen service instances, see JENKINS-52858 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52859) ps: unrecognized option: p
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-52859 ps: unrecognized option: p Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, pipeline Created: 2018-08-02 15:37 Environment: Jenkins Alpine LTS Docker image Priority: Minor Reporter: Taras Postument Hello. I'm using the Blueocean and Pipelines on Alpine linux and started seeing next error on each Pipeline SH step: [Pipeline] sh[decline_cookies_policy-testing-job] Running shell script ps: unrecognized option: p BusyBox v1.28.4 (2018-05-30 10:45:57 UTC) multi-call binary. Usage: ps [-o COL1,COL2=HEADER] Show list of processes -o COL1,COL2=HEADER Select columns for display + echo hello world[Pipeline] } Looks like plugin tries to call `ps` with unsuported for Alpine parameters on each sh step. Add Comment
[JIRA] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title
Harald Albers edited a comment on JENKINS-40336
Re: invalid login for second template in one vsphere cloud
This is kind of weird: I checked against the plugin's minimal Jenkins version (1.625.3) by running from the sources and could successfully validate a first and a second template. After upgrading the Jenkins base version to 2.60.3 in the plugin sources and upgrading plugins in the running Jenkins instance , I could reproduce the problem described above: only the first template could be verified.When {{vSphereCloudSlaveTemplate.DescriptorImpl#doTestCloneParameters}} is called on the first template, the query parameter {{credentialsId}} is correctly populated with its value from src\main\resources\org\jenkinsci\plugins\vsphere\VSphereConnectionConfig\config.groovy.When it is called on the second template, {{credentialsId}} is passed as an empty string.Strangely enough, the boolean value {{allowUntrustedCertificate}}, which is located at the same scope as {{credentialsId}}, is passed correctly in both cases.So the behaviour is influenced by dependency changes.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52858) Implement feathers-sync for sharing service events across instances in production
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-52858 Implement feathers-sync for sharing service events across instances in production Issue Type: Task Assignee: Unassigned Components: essentials Created: 2018-08-02 15:24 Priority: Minor Reporter: R. Tyler Croy https://github.com/feathersjs-ecosystem/feathers-sync This will allow the replicas in kubernetes to be increased from 1 to N, while still pushing the service events to all connected clients properly. Basically when replica1 has a create/updated event, that should be synchronized to the replica2, which should then pass the event onto the clients connected to replica2. That way everybody will properly receive service events. As a note in case I don't implement this myself. Adding a redis container to the evergreen Deployment in Kubernetes looks like the most stiraightforward approach, we just need a simple cross-container pub/sub channel Add Comment
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title KaiHsiang Chang commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins And welcome to file a PR even it's just configuration experiences or some documentation. Need you guys' help to make the documentation more complete. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title KaiHsiang Chang stopped work on JENKINS-52810 Change By: KaiHsiang Chang Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Title: Message Title Alexander Krysko commented on JENKINS-24767 Re: Role-based Authorization Strategy not working with sub-folders Second comment is not very specific. In plugin configuration there are Global and Project roles. So should there be Overall Read checkbox in a Global role should there be Job Read checkbox in a Global role May I ask someone who succeeded in described configuration to attach screenshots? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Tomonari Nakamura resolved as Fixed Jenkins / JENKINS-49396 NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Change By: Tomonari Nakamura Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Tomonari Nakamura commented on JENKINS-49396 Re: NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Sergey Berezhnoy I'm a maintainer of backlog plugin. Sorry for late reply. I've fixed this problem and released new version 2.3. Please update the backlog plugin and try again. Thank you for your report. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title KaiHsiang Chang commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Trey Bohon thx for your information. First, I have to say that it's a huge code change from 2.2.2 to 3.0.0 which maybe not that fully considered the compatibility but brought many features and bug fixes. It's user's decision to upgrade or not, although the plugin has compatibility remind already. Second, in this case, I doubt the correctness of original usage ( Dinesh). I've never tried to put the folder URL in the remote server and surprisingly it even works in the old version. All these paradoxical usages are just because the original implementation didn't get the build number in an accurate approach, or more specifically, in a right way. Furthermore, there're many bugs resulted from the wrong build number like 404 not found, wrong status, etc. So, once the approach is corrected, many of the paradoxical usages need to be changed and that's why you guys can't get over through this, and why the compatibility remind was shown in the upgrade page. IMHO, you guys should setup a testing environment before direct upgrading, and try to fix your processes. I don't think the plugin needs to be compatible with the old and wrong approach . Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Tomonari Nakamura assigned an issue to Tomonari Nakamura Jenkins / JENKINS-49396 NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Change By: Tomonari Nakamura Assignee: Tomonari Nakamura Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42411) Pipeline P4_CHANGELIST populated from Jenkinsfile changelist, not from repo p4sync mappings in Jenkinsfile
Title: Message Title
Thomas Murphy reopened an issue
Using jenkins 2.134 and P4 plugin 1.8.14, I have the problem described in the title of this bug. Using the option to pull a jenkinsfile from SCM, I find the $P4_CHANGELIST variable inside the jenkinsfile code is set to the most recent changelist for the pipeline script itself, and not for the overall project (that gets pulled in the P4 Sync stage of the pipeline). The logs show the P4 plugin does successfully pull the latest changelist (for the project) when it pulls the code in P4 Sync, but the P4_CHANGLIST variable is not reset to this changelist, and continues to identify the last change to the pipeline script. Based on the information in this bug (and the latest P4 Plugin documentation), I am using a different job name in the jenkins UI where I ask to pull the pipeline from SCM (jenkins-${NODE_NAME}${JOB_NAME}-script) and in the P4 Sync stage (jenkins${NODE_NAME}-${JOB_NAME}).
Jenkins / JENKINS-42411
Pipeline P4_CHANGELIST populated from Jenkinsfile changelist, not from repo p4sync mappings in Jenkinsfile
Change By:
Thomas Murphy
Resolution:
Not A Defect
Status:
Closed Reopened
Add Comment
[JIRA] (JENKINS-51164) JIRA plugin doesn't honor proxy excludes
Title: Message Title Dan Straw commented on JENKINS-51164 Re: JIRA plugin doesn't honor proxy excludes Olivier Lamy - what's the ETA for the Jira plugin 3.0.1 build please? It would be great to be able to upgrade the plugin past 2.5.1, as there are a load of other plugins which now require the Jira plugin 3.0+ Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Trey Bohon commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins I get a very similar error with Jenkins 2.107.1, Parameterized Remote Trigger 3.0.3, and Job DSL 1.68 (we update infrequently due to frequent breakage). However, if I manually go into the job in Jenkins UI and click save/apply before running, I don't encounter the issue. This makes me think that Job DSL is generating a job configuration that won't be interpreted correctly at execution time, but if mutated with save/apply it updates it properly. Here's my error: ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.evaluateEffectiveRemoteHost(RemoteBuildConfiguration.java:385) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:533) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:514) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Trigger a remote parameterized job' marked build as failure Here is the mutation of the parameterized remote trigger portion of the config.xml: If I manually copy in the job DSL code afterwards, reload configuration from disk, and run without save/apply it repeats the error. I downloaded the master Job DSL plugin source and it still has the old auth, so I imagine it also will fail. So from my 3rd party perspective, I'm not sure where the blame goes - Jenkins core for not interpreting the old job source, Job DSL for not updating the generated syntax, or this parameterized remote trigger plugin. Regardless, if it's not resolved in a few days we're rolling back this plugin. Add Comment
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Mark Waite thanks a lot for looking into it! I have the same settings but it fails, so maybe it is really related to OSX Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-36195
Re: Pipeline polling ignores special polling rules
I was able to reproduce this easily and also to find a workaround.h3. ReproduceI have the repo "user/repoA" that have the following Jenkinsfile:{code}node {deleteDir()dir("repoA") {checkout scm: [$class: 'GitSCM', branches: [[name: 'master']], extensions: [[$class: 'UserExclusion', excludedUsers: 'jenkinsbot']], userRemoteConfigs: [[credentialsId: 'mycredentials', url: 'https://1q2w3e4r5t6y7u8...@github.example.com/user/repoA.git']]]}dir("repoB") {checkout changelog: false, poll: false, scm: [$class: 'GitSCM', branches: [[name: 'master']], extensions: [[$class: 'IgnoreNotifyCommit']], userRemoteConfigs: [[credentialsId: 'mycredentials', url: 'https://1q2w3e4r5t6y7u8...@github.example.com/user/repoB.git']]]}dir('repoB') {try {sh "git checkout master"sh "git config --global user.name 'jenkinsbot'"sh "git config --global user.email 'jenkins...@example.com'"sh "echo ${JOB_NAME}/${BUILD_NUMBER} > test.txt"sh "git add ."sh "git commit -m 'Automated: Updating test.txt during build'"sh "git push"} catch (err) {echo "No change in test.txt"}}}{code}The Pipeline jobs looks like the following: !pipeline-without-userexclusion-not-working.png|thumbnail!*Expected Behavior* (+) Achange to "repoA" and "repoB" should trigger polling. (+) Polling should ignore "repoA" commits from the "jenkinsbot" user. (+) Polling should ignore "repoB".*Actual Behavior* (/) So a change to "repoA" and "repoB" should trigger polling. (-) Polling should ignore "repoA" commits from the "jenkinsbot" user. ( - / ) Polling should ignore "repoB". In that particular case, because the user exclusion doe snot work the job builds in loop...h3. Workaround The workaround is to *set the User Exclusion in the Pipeline Definition SCM instead of inside the Jenkinsfile*. Doing the following fix this scenario:!pipeline-with-userexclusion-working.png|thumbnail! Note: This is not required but in this case it makes sense anyway to use {{checkout scm}} in the Jenkinsfile.So it seems that the problem come from polling rules of the SCMs defined in checkout steps (vs. SCM definition in the Pipeline job). This workaround works in a scenario where the the commits that must be ignored are from the repository holding the Jenkinsfile. I have not tested a scenario where the polling rules are set to "repoB" with "poll: true".I am hoping this helps to find the root cause here.
Add Comment
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title
Allan BURDAJEWICZ commented on JENKINS-36195
Re: Pipeline polling ignores special polling rules
I was able to reproduce this easily and also to find a workaround. Reproduce I have the repo "user/repoA" that have the following Jenkinsfile:
node {
deleteDir()
dir("repoA") {
checkout scm: [$class: 'GitSCM',
branches: [[name: 'master']],
extensions: [[$class: 'UserExclusion', excludedUsers: 'jenkinsbot']],
userRemoteConfigs: [[credentialsId: 'mycredentials', url: 'https://1q2w3e4r5t6y7u8...@github.example.com/user/repoA.git']]]
}
dir("repoB") {
checkout changelog: false, poll: false, scm: [$class: 'GitSCM',
branches: [[name: 'master']],
extensions: [[$class: 'IgnoreNotifyCommit']],
userRemoteConfigs: [[credentialsId: 'mycredentials', url: 'https://1q2w3e4r5t6y7u8...@github.example.com/user/repoB.git']]
]
}
dir('repoB') {
try {
sh "git checkout master"
sh "git config --global user.name 'jenkinsbot'"
sh "git config --global user.email 'jenkins...@example.com'"
sh "echo ${JOB_NAME}/${BUILD_NUMBER} > test.txt"
sh "git add ."
sh "git commit -m 'Automated: Updating test.txt during build'"
sh "git push"
} catch (err) {
echo "No change in test.txt"
}
}
}
The Pipeline jobs looks like the following: Expected Behavior Achange to "repoA" and "repoB" should trigger polling. Polling should ignore "repoA" commits from the "jenkinsbot" user. Polling should ignore "repoB". Actual Behavior So a change to "repoA" and "repoB" should trigger polling. Polling should ignore "repoA" commits from the "jenkinsbot" user. Polling should ignore "repoB". In that particular case, because the user exclusion doe snot work the job builds in loop... Workaround The workaround is to set the User Exclusion in the Pipeline Definition SCM instead of inside the Jenkinsfile. Doing the following fix this scenario: Note: This is not required but in this case it makes sense anyway to use checkout scm in the Jenkinsfile. So it seems that the problem come from polling rules of the SCMs defined in checkout steps (vs. SCM definition in the Pipeline job). This workaround works in a scenario where the the commits that must be ignored are from the repository holding the Jenkinsfile. I have not tested a scenario where the polling rules are set to "repoB" with "poll: true". I am hoping this helps to find the root cause here.
Add
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Trey Bohon updated an issue Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Trey Bohon Attachment: image-2018-08-02-09-06-29-421.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-36195 Pipeline polling ignores special polling rules Change By: Allan BURDAJEWICZ Attachment: pipeline-without-userexclusion-not-working.png Attachment: pipeline-with-userexclusion-working.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52857 Cannot find git-lfs when it is not installed in /usr/bin/ Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite edited a comment on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ I wasn't able to duplicate the problem you're reporting, even on a JNLP based agent with git-lfs (and git) in the /usr/local/bin directory. Steps I took:# Confirm that git and git-lfs are installed in /usr/local/bin in the 'git' jail of my FreeNAS server# Configure a JNLP agent to run from a Jenkins 2.121.2 master based on the [docker-lfs image|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins]# Declare the location of the Default git tool on that agent as /usr/local/bin/git# Run Freestyle and Pipeline jobs on that agent which confirm it is able to use LFS repositoriesSee the attached picture for the configuration details !FreeNAS-JNLP-git-lfs-config.PNG|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51029) Option to ignore SSL certificate errors
Title: Message Title Karthik Duddu resolved as Fixed Merged as part of https://github.com/jenkinsci/logstash-plugin/pull/75 Jenkins / JENKINS-51029 Option to ignore SSL certificate errors Change By: Karthik Duddu Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51029) Option to ignore SSL certificate errors
Title: Message Title Karthik Duddu started work on JENKINS-51029 Change By: Karthik Duddu Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ I wasn't able to duplicate the problem you're reporting, even on a JNLP based agent with git-lfs (and git) in the /usr/local/bin directory. Steps I took: Confirm that git and git-lfs are installed in /usr/local/bin in the 'git' jail of my FreeNAS server Configure a JNLP agent to run from a Jenkins 2.121.2 master based on the docker-lfs image Declare the location of the Default git tool on that agent as /usr/local/bin/git Run Freestyle and Pipeline jobs on that agent which confirm it is able to use LFS repositories See the attached picture for the configuration details Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-52857 Cannot find git-lfs when it is not installed in /usr/bin/ Change By: Mark Waite Attachment: FreeNAS-JNLP-git-lfs-config.PNG Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ What we miss is possibility to define location of git-lfs binary, so `checkout scm` command could work Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40220) Support RobotFramework test results in blueocean
Title: Message Title Marcus H updated an issue Jenkins / JENKINS-40220 Support RobotFramework test results in blueocean Change By: Marcus H Comment: Has anyone had a chance to look into this yet? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title Devin Nusbaum commented on JENKINS-52847 Re: durable-task plugin v1.23 misbehaves on BusyBox agents We could also make durable-task support more basic ps implementations with something like https://github.com/jenkinsci/durable-task-plugin/pull/77. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Also, I don't think that mac is needed to reproduce. What is needed is git-lfs installed in /usr/local/bin and JNLP connection to the node Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret edited a comment on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Also, I don't think that mac is needed to reproduce. What is needed is git-lfs installed in /usr/local/bin and JNLP connection to the node . Mac problem is only that you cannot install anything to /usr/bin even with rooted user. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52848) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons
Title: Message Title Peter Vagedes commented on JENKINS-52848 Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons Thank you for your support. I attached the start sequence from the server log. As to the web container: We are running Jenkins in wildfly-10.0.0. Is this answering your question? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret assigned an issue to Mark Waite Jenkins / JENKINS-52857 Cannot find git-lfs when it is not installed in /usr/bin/ Change By: Serghei Moret Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ sure, git-lfs is installed. I can do: sh 'git checkout master' but not checkout scm Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52848) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons
Title: Message Title Peter Vagedes updated an issue Jenkins / JENKINS-52848 Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl for security reasons Change By: Peter Vagedes Attachment: start-sequence.log Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Since I don't have access to a Mac, I can't test the case you're describing. Can you confirm that you installed git LFS on the mac following the git-lfs instructions? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Title: Message Title Daniel Beck commented on JENKINS-24767 Re: Role-based Authorization Strategy not working with sub-folders The second comment on this issue explains what you need to do. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52857 Cannot find git-lfs when it is not installed in /usr/bin/ Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52855) Add GIT_CHECKOUT_DIR env var if Freestyle job does checkout to subdirectory
Title: Message Title Mark Waite updated JENKINS-52855 Will be included in git plugin 4.0.0 Jenkins / JENKINS-52855 Add GIT_CHECKOUT_DIR env var if Freestyle job does checkout to subdirectory Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Title: Message Title Alexander Krysko reopened an issue I'm using Jenkins 2.134 with Role-based Authorization Strategy ver. 2.8.1 + Folders Plugin of ver. 6.5.1. Structure of Jenkins projects with sub-folder structure: Platform1/Project1/Job-1 .. Job-n Platform2/Project2/Job-1 .. Job-n Platform3/Project3/Job-1 .. Job-n I'm struggling with granting Build/Configure access to an Active Directory group only for Platform1/Project1/Job-1 .. Job-n without exposing read access to Platform2/Project2/Job-1 .. Job-n and others? So that when user from AD group logs into Jenkins he see only the project he was given access to. When I remove Overall read access in Global Role for group 'users' which assigned to AD - users do not see what's matched by regexp under Project Roles. I'm using the following regular expressions to grant read/edit permissions: Platform1/Project1/.* Platform2/Project2/.*** Platform3/Project3/.*** Platform and Project are case sensitive. Jenkins / JENKINS-24767 Role-based Authorization Strategy not working with sub-folders Change By: Alexander Krysko Resolution: Not A Defect Status: Resolved Reopened Add Comment
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Serghei Moret updated an issue Jenkins / JENKINS-52857 Cannot find git-lfs when it is not installed in /usr/bin/ Change By: Serghei Moret We have an issue on our OSX nodes, where we cannot checkout a repo with git-lfs.We suppose that it is related to that `checkout scm` listens `/usr/bin/` and it is not possible to install anything there because of Apple's system integrity. Even passing a PATH=$PATH:/usr/local/bin doesn't take any effect. Tested this with a ssh nods and `git checkout` works (as we have user credentials and all the simlinks), but as all of our nodes use JNLP we would like to have a possibility to define path to git-lfs like we can do for git.Stack trace:hudson.plugins.git.GitException: Command "/usr/local/bin/git checkout -f 304f1c283e1fa22e47ea9d7be1e2582a93021819" returned status code 128:stdout: stderr: git-lfs filter-process: git-lfs: command not foundfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2301)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.31.128.169/172.31.128.169:49241 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserResponse.retrieve(UserRequest.java:389) at hudson.remoting.Channel.call(Channel.java:955) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor638.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy117.execute(Unknown Source) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1236) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused: hudson.plugins.git.GitException:
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title
Serghei Moret updated an issue
Jenkins / JENKINS-52857
Cannot find git-lfs when it is not installed in /usr/bin/
Change By:
Serghei Moret
We have an issue on our OSX nodes, where we cannot checkout a repo with git-lfs.We suppose that it is related to that `checkout scm` listens `/usr/bin/` and it is not possible to install anything there because of Apple's system integrity. Even passing a PATH=$PATH:/usr/local/bin doesn't take any effect. Tested this with a ssh nods and `git checkout` works (as we have user credentials and all the simlinks), but as all of our nodes use JNLP we would like to have a possibility to define path to git-lfs like we can do for git.Stack trace: {code:java} hudson.plugins.git.GitException: Command "/usr/local/bin/git checkout -f 304f1c283e1fa22e47ea9d7be1e2582a93021819" returned status code 128: stdout: stderr: git-lfs filter-process: git-lfs: command not found fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2301) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.31.128.169/172.31.128.169:49241 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserResponse.retrieve(UserRequest.java:389) at hudson.remoting.Channel.call(Channel.java:955) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor638.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy117.execute(Unknown Source) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1236) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused: hudson.plugins.git.GitException:
