[JIRA] (JENKINS-59771) Not sending Email after build though it is SUCCESS
Title: Message Title bhaskar athikayala commented on JENKINS-59771 Re: Not sending Email after build though it is SUCCESS Apprenda Developers for Jenkins could you please help on this Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202494.1571031058000.6837.1571032380062%40Atlassian.JIRA.
[JIRA] (JENKINS-59771) Not sending Email after build though it is SUCCESS
Title: Message Title bhaskar athikayala created an issue Jenkins / JENKINS-59771 Not sending Email after build though it is SUCCESS Issue Type: Bug Assignee: bhaskar athikayala Attachments: image-2019-10-13-22-28-26-680.png, image-2019-10-13-22-28-58-907.png Components: email-ext-recipients-column-plugin Created: 2019-10-14 05:30 Priority: Major Reporter: bhaskar athikayala Hi, After build jenkins was not sending email though i configured Email list it saying no as "An attempt to send an e-mail to empty list of recipients, ignored." Add Comment
[JIRA] (JENKINS-59520) EC2 Plugin 'Maximum Total Uses' counter resets itself when Stop/Disconnect on Idle Timeout is used
Title: Message Title Raihaan Shouhell commented on JENKINS-59520 Re: EC2 Plugin 'Maximum Total Uses' counter resets itself when Stop/Disconnect on Idle Timeout is used AFAICT Stop instances does not work with maximum uses. Because when an agent is stopped jenkins forgets about its state. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202144.1569364732000.6835.1571022120201%40Atlassian.JIRA.
[JIRA] (JENKINS-59770) Show current builds on dashboard
Title: Message Title Bogdan Ilchyshyn created an issue Jenkins / JENKINS-59770 Show current builds on dashboard Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2019-10-14 02:25 Priority: Minor Reporter: Bogdan Ilchyshyn Status Quo Blue Ocean dashboard shows a list of projects + favourites. To access a build that was just triggered automatically (i.e. by a push hook), a user has to search for the project (if it was not added into favourites), click on the job to drill down, then click on the build to actually get into the build itself and monitor its execution. For organizations that embrace microservices or reusable code approaches, that would be a typical flow, as adding all the dozens of projects into favourites makes little sense. In Classic UI, the build queue (both active and pending builds) is displayed on the initial dashboard and user can get into the build with a single click. Moreover, the build queue is available from other places as well, making it easy to switch between the builds. Suggestion Add a build queue widget to the Blue Ocean dashboard, so users could drill down into the active/pending builds with a single click. Add Comment
[JIRA] (JENKINS-59769) Testing a unix Pipe fails when run using kubernetes-jenkins
Title: Message Title
Jared Patterson updated an issue
Jenkins / JENKINS-59769
Testing a unix Pipe fails when run using kubernetes-jenkins
Change By:
Jared Patterson
I have a test which creates a (interprocess-channel) unix pipe, creates and attaches a client to the pipe, and asserts that it times out after X seconds if no data is emitted over the channel.When the test is executed via a custom PodTemplate, within the kubernetes-plugin's `container()` block, it fails with the following exception:{code:java} 14:00:41 poll stdout 14:00:41 running: "/opt/fst-wasi-sdk/bin/clang" "/home/jenkins/workspace/isolation/isolation/public/lucet-wasi/tests/guests/poll.c" "-target=wasm32-unknown-wasi" "sysroot=/opt/fst-wasi-sdk/share/wasi-sysroot" "-o" "/tmp/.tmpKDJhAm/out.wasm" "-Wall" "-Werror" "-Wl,-no-threads" 14:00:41 thread 'poll' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "runtime error: Runtime fault: FaultDetails { fatal: false, trapcode: Some(Unreachable), rip_addr: 140297967098212, rip_addr_details: Some(AddrDetails{ in_module_code: true, file_name: Some(\"/tmp/.tmpKDJhAm/out.so\"), sym_name: None }) }" } {code} However, ff I have the pipeline spawn the custom pod as per usual, but sleep() right before executing the test, allowing me to jump onto the container via kubectl, and then manually run the test (executing the same target called from the pipeline) it succeeds as expected. This test also succeeds if its executed using docker-server (non kubernetes)I have confirmed the user within the container being used is root, and permissions etc are correct. The file descriptor for the pipe gets created within /tmp/Test is creating a pipe using: [https://docs.rs/nix/0.10.0/nix/unistd/fn.pipe.html] GKE: 1.14.3-gke.11 Jenkins: 2.190.1 Kubernetes Plugin: 1.20.0 Any ideas here?
Add Comment
[JIRA] (JENKINS-59769) Testing a unix Pipe fails when run using kubernetes-jenkins
Title: Message Title Jared Patterson updated an issue Jenkins / JENKINS-59769 Testing a unix Pipe fails when run using kubernetes-jenkins Change By: Jared Patterson Summary: Testing a unix Pipe fails when run via using kubernetes-jenkins integration Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202492.1571019671000.6830.1571019780063%40Atlassian.JIRA.
[JIRA] (JENKINS-59769) Testing a unix Pipe fails when run via kubernetes-jenkins integration
Title: Message Title Jared Patterson updated an issue Jenkins / JENKINS-59769 Testing a unix Pipe fails when run via kubernetes-jenkins integration Change By: Jared Patterson Summary: Tests using Testing a unix Pipe fail fails when run via kubernetes-jenkins integration Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202492.1571019671000.6829.1571019720187%40Atlassian.JIRA.
[JIRA] (JENKINS-59769) Tests using unix Pipe fail when run via kubernetes-jenkins integration
Title: Message Title
Jared Patterson created an issue
Jenkins / JENKINS-59769
Tests using unix Pipe fail when run via kubernetes-jenkins integration
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-10-14 02:21
Priority:
Minor
Reporter:
Jared Patterson
I have a test which creates a (interprocess-channel) unix pipe, creates and attaches a client to the pipe, and asserts that it times out after X seconds if no data is emitted over the channel. When the test is executed via a custom PodTemplate, within the kubernetes-plugin's `container()` block, it fails with the following exception:
14:00:41 poll stdout
14:00:41 running: "/opt/fst-wasi-sdk/bin/clang" "/home/jenkins/workspace/isolation/isolation/public/lucet-wasi/tests/guests/poll.c" "-target=wasm32-unknown-wasi" "sysroot=/opt/fst-wasi-sdk/share/wasi-sysroot" "-o" "/tmp/.tmpKDJhAm/out.wasm" "-Wall" "-Werror" "-Wl,-no-threads"
14:00:41 thread 'poll' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "runtime error: Runtime fault: FaultDetails { fatal: false, trapcode: Some(Unreachable), rip_addr: 140297967098212, rip_addr_details: Some(AddrDetails
{ in_module_code: true, file_name: Some(\"/tmp/.tmpKDJhAm/out.so\"), sym_name: None }
) }" }
However, ff I have the pipeline spawn the custom pod as per usual, but sleep() right before executing the test, allowing me to jump onto the container via kubectl, and then manually run the test (executing the same target called from the pipeline) it succeeds as expected. This test also succeeds if its executed using docker-server (non kubernetes) I have confirmed the user within the container being used is root, and
[JIRA] (JENKINS-59768) pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Title: Message Title
Mark Waite assigned an issue to Unassigned
Jenkins / JENKINS-59768
pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Change By:
Mark Waite
Assignee:
Mark Waite
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202491.1571016754000.6827.1571019120191%40Atlassian.JIRA.
[JIRA] (JENKINS-59768) pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Title: Message Title zhu rui started work on JENKINS-59768 Change By: zhu rui Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202491.1571016754000.6825.1571016900312%40Atlassian.JIRA.
[JIRA] (JENKINS-59768) pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Title: Message Title
zhu rui assigned an issue to Mark Waite
Jenkins / JENKINS-59768
pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Change By:
zhu rui
Assignee:
zhu rui Mark Waite
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202491.1571016754000.6823.1571016841241%40Atlassian.JIRA.
[JIRA] (JENKINS-59768) pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Title: Message Title
zhu rui created an issue
Jenkins / JENKINS-59768
pipeline中Jenkinsfile来源是一个gitlab项目，当配置该项目时项目名称或分支使用参数如${Parameter}时，此时git轮询就会失效，无法获取到git更新。
Issue Type:
Bug
Assignee:
zhu rui
Components:
git-plugin
Created:
2019-10-14 01:32
Environment:
Jenkins:2.150.1
Priority:
Critical
Reporter:
zhu rui
1） pipeline设置轮询策略为 * * * * *，有变更时会触发构建。 2） Jenkinsfile来源是一个gitlab项目，Jenkinsfile中监控的项目也使用gitlab 3) 在jenkinsfile中配置gitlab项目时，项目名称或分支使用参数如${Parameter} ===》》git轮询就会失效，gitlab有更新却无法触发新的构建。
Add Comment
[JIRA] (JENKINS-45001) KnownHostsFileKeyVerificationStrategy is not configurable
Title: Message Title Ivan Fernandez Calvo updated JENKINS-45001 Jenkins / JENKINS-45001 KnownHostsFileKeyVerificationStrategy is not configurable Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183088.1497971728000.6760.1571003760216%40Atlassian.JIRA.
[JIRA] (JENKINS-47510) RemoteLauncher.isUnix() is not overridden - always returns master OS
Title: Message Title Ivan Fernandez Calvo updated JENKINS-47510 Jenkins / JENKINS-47510 RemoteLauncher.isUnix() is not overridden - always returns master OS Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185967.1508353562000.6758.1571003700383%40Atlassian.JIRA.
[JIRA] (JENKINS-47510) RemoteLauncher.isUnix() is not overridden - always returns master OS
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-47510 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185967.1508353562000.6756.1571003700356%40Atlassian.JIRA.
[JIRA] (JENKINS-57453) Invalid encoded sequence when connecting Windows Agent with Bitvise SSH Server
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-57453 Re: Invalid encoded sequence when connecting Windows Agent with Bitvise SSH Server I've checked where it fails and it happens when opening the remoting channel after copy the remoting.jar file, that's what bothers me it success to open the SSH connection and to copy the file by SFTP but fails when open the java channel to the stdout and to the stderr, I have to run some test in a local environment to see if I can make something to fix it. https://github.com/jenkinsci/ssh-slaves-plugin/blob/ssh-slaves-1.29.4/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L1034 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199311.1557833375000.6754.1571001720161%40Atlassian.JIRA.
[JIRA] (JENKINS-45001) KnownHostsFileKeyVerificationStrategy is not configurable
Title: Message Title Ivan Fernandez Calvo updated JENKINS-45001 Jenkins / JENKINS-45001 KnownHostsFileKeyVerificationStrategy is not configurable Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183088.1497971728000.6751.1571000940321%40Atlassian.JIRA.
[JIRA] (JENKINS-45001) KnownHostsFileKeyVerificationStrategy is not configurable
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-45001 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183088.1497971728000.6749.1571000940295%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Issue Type: Improvement Assignee: Arnaud Héritier Attachments: Screenshot 2019-10-13 22.32.02.png, Screenshot 2019-10-13 22.33.42.png Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-13 20:34 Priority: Minor Reporter: Arnaud Héritier Instead of I would prefer to have the ability to add the emails 1 by one and having them configured as a list. Like we can see for branches in the git plugin to add/remove them Add Comment
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier started work on JENKINS-59767 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.6745.1570998900280%40Atlassian.JIRA.
[JIRA] (JENKINS-47134) Allow SSH connectivity check before marking agent online
Title: Message Title Ivan Fernandez Calvo closed an issue as Won't Do Jenkins / JENKINS-47134 Allow SSH connectivity check before marking agent online Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185536.1506433907000.6743.1570998540286%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated JENKINS-59697 Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.12 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6741.1570997880128%40Atlassian.JIRA.
[JIRA] (JENKINS-49118) SSH Slaves 1.25 Breaks
Title: Message Title Ivan Fernandez Calvo updated JENKINS-49118 It is probably related to the way the timeout was managed, this would change in the last snapshot version, also I've found JENKINS-59764 on docker-plugin that could be also related Jenkins / JENKINS-49118 SSH Slaves 1.25 Breaks Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-49118) SSH Slaves 1.25 Breaks
Title: Message Title Ivan Fernandez Calvo updated JENKINS-49118 Jenkins / JENKINS-49118 SSH Slaves 1.25 Breaks Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187953.1516729442000.6734.1570997580475%40Atlassian.JIRA.
[JIRA] (JENKINS-49118) SSH Slaves 1.25 Breaks
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-49118 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187953.1516729442000.6732.1570997580446%40Atlassian.JIRA.
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Ivan Fernandez Calvo resolved as Cannot Reproduce Jenkins / JENKINS-25858 java.io.IOException: Unexpected termination of the channel Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159433.1417508066000.6704.1570997419660%40Atlassian.JIRA.
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-25858 java.io.IOException: Unexpected termination of the channel Change By: Ivan Fernandez Calvo Assignee: Sam Van Oort Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159433.1417508066000.6678.1570997419120%40Atlassian.JIRA.
[JIRA] (JENKINS-58605) in pom.xml must not point to plugins.jenkins.io
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58605 Jenkins / JENKINS-58605 in pom.xml must not point to plugins.jenkins.io Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200765.1563823331000.6674.1570997280669%40Atlassian.JIRA.
[JIRA] (JENKINS-58589) Re-make the retry connection process
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58589 Jenkins / JENKINS-58589 Re-make the retry connection process Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200745.156373970.6671.1570997280627%40Atlassian.JIRA.
[JIRA] (JENKINS-48617) SSH Slaves should ALWAYS pass connection timeout to connection.connect()
Title: Message Title Ivan Fernandez Calvo updated JENKINS-48617 Jenkins / JENKINS-48617 SSH Slaves should ALWAYS pass connection timeout to connection.connect() Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187266.1513634884000.6668.1570997227880%40Atlassian.JIRA.
[JIRA] (JENKINS-55352) update net.i2p.crypto:eddsa
Title: Message Title Ivan Fernandez Calvo updated JENKINS-55352 Jenkins / JENKINS-55352 update net.i2p.crypto:eddsa Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196455.1546007029000.6675.1570997280696%40Atlassian.JIRA.
[JIRA] (JENKINS-59763) Remove SFTPClient
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59763 Jenkins / JENKINS-59763 Remove SFTPClient Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202486.1570965458000..1570997227683%40Atlassian.JIRA.
[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title Ivan Fernandez Calvo updated JENKINS-53810 Jenkins / JENKINS-53810 Launch Agents fails with ERROR: null java.util.concurrent.CancellationException Change By: Ivan Fernandez Calvo Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194324.1538032375000.6665.1570997227673%40Atlassian.JIRA.
[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53810 Re: Launch Agents fails with ERROR: null java.util.concurrent.CancellationException I am pretty sure is related to JENKINS-59764, I have make the PR to the docker-plugin with the solution, it'd need trilead-ssh2-build-217-jenkins-15 on Jenkins Core 2.190- or trilead-api 1.0.5 on Jenkins core 2.190.1+ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194324.1538032375000.6641.1570997160473%40Atlassian.JIRA.
[JIRA] (JENKINS-53720) JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE in some classes
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-53720 Re: JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE in some classes this starts happening on the ssh-slaves-plugin today :( it uses SpodtBugs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194219.1537564231000.6638.1570995420146%40Atlassian.JIRA.
[JIRA] (JENKINS-53720) JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE in some classes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53720 Re: JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE in some classes this starts happening on the ssh-slaves-plugin today Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194219.1537564231000.6636.1570995360164%40Atlassian.JIRA.
[JIRA] (JENKINS-59766) Add jenkins logger
Title: Message Title Ashutosh Chaudhary created an issue Jenkins / JENKINS-59766 Add jenkins logger Issue Type: Improvement Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2019-10-13 19:11 Priority: Minor Reporter: Ashutosh Chaudhary I've managed to add a jenkins console logger to be able to see detailed log. Currently, the plugins logs not much except for Jira API responses, which somethings is not as useful as to see what parameters have been passed Add Comment This
[JIRA] (JENKINS-59730) text-finder sets whole matrix job to "not built" even if only one configuration matched
Title: Message Title Christoph Berg commented on JENKINS-59730 Re: text-finder sets whole matrix job to "not built" even if only one configuration matched I have little Java experience so I can't tell how much harder than copy-pasting some similar case would be. I might give it a try, but I'll be at PGconf.EU next week, so it might take a while before I get to it, if at all. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202448.1570712752000.6631.1570991700150%40Atlassian.JIRA.
[JIRA] (JENKINS-59765) A VSCode Plugin for Jenkins Integration
Title: Message Title Sladyn Nunes created an issue Jenkins / JENKINS-59765 A VSCode Plugin for Jenkins Integration Issue Type: Task Assignee: Sladyn Nunes Components: configuration-as-code-plugin Created: 2019-10-13 18:21 Labels: plugin Priority: Minor Reporter: Sladyn Nunes This Plugin is part of the Community Bridge Project 2019. It is a plugin that is a dev-tool to JCasC plugin for the live fetching, authentication and validation of yaml files written for JCasC Add Comment
[JIRA] (JENKINS-59763) Remove SFTPClient
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-59763 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202486.1570965458000.6627.1570990380270%40Atlassian.JIRA.
[JIRA] (JENKINS-59763) Remove SFTPClient
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59763 Jenkins / JENKINS-59763 Remove SFTPClient Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202486.1570965458000.6628.1570990380316%40Atlassian.JIRA.
[JIRA] (JENKINS-59764) Connection timeout is not honored
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59764 Jenkins / JENKINS-59764 Connection timeout is not honored Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202487.1570988284000.6626.1570989180084%40Atlassian.JIRA.
[JIRA] (JENKINS-59764) Connection timeout is not honored
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-59764 Connection timeout is not honored Change By: Ivan Fernandez Calvo Summary: The connection Connection timeout is not honored Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202487.1570988284000.6625.157090070%40Atlassian.JIRA.
[JIRA] (JENKINS-59764) The connection timeout is not honored
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-59764 The connection timeout is not honored Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: docker-plugin Created: 2019-10-13 17:38 Priority: Major Reporter: Ivan Fernandez Calvo Testing the latest changes on the trilead-api that fix the use of the timeout on the SSH connection, I've found that the connector used by the docker-plugin passes the connection timeout in the wrong argument, so if the Docker container is not enough fast to start the connection would fail with the following error, notice the *after 0 seconds* INFO: Can't stop container '7bc1944f6850c40348203db9c23307cde20af1e8d1a57f27c09a06f709e86628' for node 'docker-agent-0004n38ta1rh0' as it does not exist. Oct 13, 2019 7:28:48 PM hudson.slaves.NodeProvisioner lambda$update$6 WARNING: Unexpected exception encountered while provisioning agent Image of jenkins/ssh-slave:jdk11 java.io.IOException: SSH service hadn't started after 0 seconds. at io.jenkins.docker.connector.DockerComputerSSHConnector.createLauncher(DockerComputerSSHConnector.java:261) at io.jenkins.docker.connector.DockerComputerConnector.createLauncher(DockerComputerConnector.java:91) at com.nirima.jenkins.plugins.docker.DockerTemplate.doProvisionNode(DockerTemplate.java:564) at com.nirima.jenkins.plugins.docker.DockerTemplate.provisionNode(DockerTemplate.java:526) at com.nirima.jenkins.plugins.docker.DockerCloud$1.run(DockerCloud.java:364) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[JIRA] (JENKINS-59764) The connection timeout is not honored
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-59764 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202487.1570988284000.6624.1570988340234%40Atlassian.JIRA.
[JIRA] (JENKINS-16731) Common slave service for multiple masters
Title: Message Title Jason Pyeron commented on JENKINS-16731 Re: Common slave service for multiple masters Thoughts on the design pattern: On resource management, the slave has a # of concurrent executors, this value needs to be the same across all masters Can this property be set on the slave and queried by the master, not set? A master should only have detailed job status for its job A master would need to know of a foreign job execution status, at a minimum Job name Job number Master (public/login) URL job start time On authentication The node may want a shared or individual authentication key for each master Individual keys could support an easy way of identifying / tagging jobs to a master? While not needed at first, a queuing ticket issuance for master/master job ordering. Think like a bakery, take a number and wait. For now, think hungry hungry hippos game, if you get the slot, you have a scheduled job - someone will get it and eventually you should get one Are there other ways to minimize the impact/change to the master/node protocol? Add Comment
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-59759 Re: localhost not allowed for jeknins with gitlab-branch-source-plugin Hi ebundy ebundy, looks like we didn't consider this case. Thanks for catching it. We need to check if the api supports this. Would you be able to build the plugin from source and test it for me? (as currently I am away from GitLab server setup on my local machine). To test it, you only need to remove this line - https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/a17a990ee98fbd4952dbc974474db8e815897e63/src/main/java/io/jenkins/plugins/gitlabbranchsource/GitLabHookCreator.java#L154 And build the plugin and install in your Jenkins instance manually after uninstalling the already installed version. If the web hook is created then we know that gitlab4j api supports and I will send a fix once you confirm it. Let me know if this is possible. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202482.1570880817000.6620.1570969560195%40Atlassian.JIRA.
[JIRA] (JENKINS-59762) Static initialization block prevents mocking CpsThread
Title: Message Title Kamil Szymański commented on JENKINS-59762 Re: Static initialization block prevents mocking CpsThread I've submitted a PR that fixes CpsThread mocking issue: https://github.com/jenkinsci/workflow-cps-plugin/pull/328 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202485.1570964663000.6618.1570968600059%40Atlassian.JIRA.
[JIRA] (JENKINS-48617) SSH Slaves should ALWAYS pass connection timeout to connection.connect()
Title: Message Title Ivan Fernandez Calvo updated JENKINS-48617 Jenkins / JENKINS-48617 SSH Slaves should ALWAYS pass connection timeout to connection.connect() Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187266.1513634884000.6617.1570965600511%40Atlassian.JIRA.
[JIRA] (JENKINS-58589) Re-make the retry connection process
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58589 Jenkins / JENKINS-58589 Re-make the retry connection process Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200745.156373970.6615.1570965600473%40Atlassian.JIRA.
[JIRA] (JENKINS-59763) Remove SFTPClient
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-59763 Remove SFTPClient Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: ssh-agent-plugin, trilead-api-plugin Created: 2019-10-13 11:17 Priority: Minor Reporter: Ivan Fernandez Calvo We have to remove a leftover of the split of trilead-api-plugin, there is a class in ssh-slaves-plugin that it is also in trilead-api-plugin, so we have to remove it from ssh-slaves-plugin. com.trilead.ssh2.jenkins.SFTPClient Add Comment
[JIRA] (JENKINS-59761) Security update notifications list plugins w/ a name that can't be found in the available updates
Title: Message Title Daniel Beck commented on JENKINS-59761 Re: Security update notifications list plugins w/ a name that can't be found in the available updates Really not sure what to do about this. There are two components involved here, core and the update site, which independently attempt to strip redundant parts out of plugin names. The server side is (mostly) at https://github.com/jenkins-infra/update-center2/blob/b82c5dac759a868042e9b3c42b017bdc0bda40ae/src/main/java/org/jvnet/hudson/update_center/Plugin.java#L395-L403 with some particularly bad examples at https://github.com/jenkins-infra/update-center2/blob/ef26174817aad3cd838ba188a97374fad3cf7567/src/test/java/org/jvnet/hudson/update_center/PluginTest.java While client side we only do https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginWrapper.java#L437 I like the aggressive approach a lot better because the results are cleaner, even if the results are not always great in case of really insane plugin names. It is however not an approach well suited for software that gets published and used indefinitely on new inputs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198069.1551996008000.6610.1570965240198%40Atlassian.JIRA.
[JIRA] (JENKINS-59762) Static initialization block prevents mocking CpsThread
Title: Message Title Kamil Szymański created an issue Jenkins / JENKINS-59762 Static initialization block prevents mocking CpsThread Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-10-13 11:04 Labels: testing Priority: Minor Reporter: Kamil Szymański This causes trouble for scripted pipelines testing, e.g. when using jenkins-spock library: Could not initialize class org.jenkinsci.plugins.workflow.cps.CpsThread java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.workflow.cps.CpsThread at org.jenkinsci.plugins.workflow.cps.CpsScript.(CpsScript.java:69) at org.spockframework.mock.runtime.MockInstantiator.instantiate(MockInstantiator.java:33) at org.spockframework.mock.runtime.ProxyBasedMockFactory$CglibMockFactory.createMock(ProxyBasedMockFactory.java:155) at org.spockframework.mock.runtime.ProxyBasedMockFactory.create(ProxyBasedMockFactory.java:68) at org.spockframework.mock.runtime.JavaMockFactory.createInternal(JavaMockFactory.java:59) at org.spockframework.mock.runtime.JavaMockFactory.create(JavaMockFactory.java:40) at org.spockframework.mock.runtime.CompositeMockFactory.create(CompositeMockFactory.java:44) at org.spockframework.lang.SpecInternals.createMock(SpecInternals.java:51) at org.spockframework.lang.SpecInternals.createMockImpl(SpecInternals.java:296) at org.spockframework.lang.SpecInternals.createMockImpl(SpecInternals.java:286) at org.spockframework.lang.SpecInternals.SpyImpl(SpecInternals.java:161) at
[JIRA] (JENKINS-59761) Security update notifications list plugins w/ a name that can't be found in the available updates
Title: Message Title Daniel Beck moved an issue Jenkins / JENKINS-59761 Security update notifications list plugins w/ a name that can't be found in the available updates Change By: Daniel Beck Project: Infrastructure Jenkins Key: INFRA JENKINS - 2047 59761 Issue Type: Task Bug Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: update-center Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-54012) File handle leak in Groovy Script
Title: Message Title Marco Pensallorto edited a comment on JENKINS-54012 Re: File handle leak in Groovy Script We encountered the very same problem. In our case, the file leak was in a shared bit of code ran by several jobs and overtime the number of open files grew in the hundrends hundreds of thousands (!). After rewriting that bit of code bypassing .enviroment the problem is gone. This is definitely a bug. Version 2.150.3 LTS here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194625.1539249121000.6597.1570957020154%40Atlassian.JIRA.
[JIRA] (JENKINS-54012) File handle leak in Groovy Script
Title: Message Title Marco Pensallorto updated an issue Jenkins / JENKINS-54012 File handle leak in Groovy Script Change By: Marco Pensallorto Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194625.1539249121000.6588.1570956960581%40Atlassian.JIRA.
[JIRA] (JENKINS-54012) File handle leak in Groovy Script
Title: Message Title Marco Pensallorto commented on JENKINS-54012 Re: File handle leak in Groovy Script We encountered the very same problem. In our case, the file leak was in a shared bit of code ran by several jobs and overtime the number of open files grew in the hundrends of thousands . After rewriting that bit of code bypassing .enviroment the problem is gone. This is definitely a bug. Version 2.150.3 LTS here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194625.1539249121000.6594.1570956960763%40Atlassian.JIRA.
[JIRA] (JENKINS-54012) File handle leak in Groovy Script
Title: Message Title Marco Pensallorto updated an issue Jenkins / JENKINS-54012 File handle leak in Groovy Script Change By: Marco Pensallorto Environment: Jenkins ver. 2.145 Jenkins ver. 2.150.3 LTS Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194625.1539249121000.6591.1570956960698%40Atlassian.JIRA.
