[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Hokwang Lee commented on JENKINS-58639 Re: pipeline job runs every two minutes Karl Wirth Any comments? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200807.156396953.1529.1564120260199%40Atlassian.JIRA.
[JIRA] (JENKINS-58481) Duplicate copies of SCM Traits entries
Title: Message Title Parichay Barpanda updated JENKINS-58481 Jenkins / JENKINS-58481 Duplicate copies of SCM Traits entries Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200617.1562993342000.1527.1564119960100%40Atlassian.JIRA.
[JIRA] (JENKINS-58666) Add Trusted contributor trait to ForkMRTraits
Title: Message Title Parichay Barpanda started work on JENKINS-58666 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200948.156408612.1526.1564118160083%40Atlassian.JIRA.
[JIRA] (JENKINS-58627) jenkins agent getting terminated with version 2.176.2
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-58627 jenkins agent getting terminated with version 2.176.2 Change By: Alex Earl Summary: jenkins slave agent getting terminated with version 2.176.2 Hi,Jenkins slave agent is geting terminated with new version 2.176.2 as explained below OS - windows 2012 R2 (both Master and Slave agent )Java - 1.8.0_211 (both Mater and Salve slave )Jenkins Version - 2.176.2Launch Method - Java Web start, JNLP(Launch by connecting it to the Master) Issue - I have a project in Jenkins which fails mainly because the slave agent terminates after 'Starting ServiceWrapper in the CLI mode' during execution.Finds a child process conhost.exe and failed due to Killing as fallback.This is happening only for a project/ pipeline, where I have python script which pings a internal URL (https://URL/ping), invokes the network emulator tool installed, adjust the network latency and also write to a file/ push to ELK. I have a internet proxy set up using .pac file. It completes all the steps in project, at the end the slave agent terminates, marking the build as failure Note - We also have another old version of jenkins 2.76 installed where the same project/ pipeline works with out any issue. Now we want to upgrade to latest jenkins we are seeing issue with slave agent getting terminated. I now have to close the network emulator tool every time and restart the jenkins service to bring it back online. Error as obsreved in Jenkins-slave.wrapper.log:-2019-07-24 03:51:59,751 INFO - Stopping jenkinsslave-e__jenkins2019-07-24 03:51:59,751 DEBUG - ProcessKill 68722019-07-24 03:51:59,860 INFO - Found child process: 6408 Name: conhost.exe2019-07-24 03:51:59,892 INFO - Stopping process 64082019-07-24 03:51:59,907 INFO - Send SIGINT 64082019-07-24 03:51:59,907 WARN - SIGINT to 6408 failed - Killing as fallback2019-07-24 03:51:59,907 INFO - Stopping process 68722019-07-24 03:51:59,907 INFO - Send SIGINT 68722019-07-24 03:51:59,907 WARN - SIGINT to 6872 failed - Killing as fallback2019-07-24 03:51:59,907 INFO - Finished jenkinsslave-e__jenkins2019-07-24 03:51:59,907 DEBUG - Completed. Exit code is 0 Error as obsreved in jenkins-slave.error.log:-Jul 24, 2019 3:57:23 AM hudson.remoting.jnlp.Main$CuiListener statusJul 24, 2019 3:57:23 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedJul 24, 2019 3:57:23 AM hudson.util.ProcessTree getWARNING: Error while determining if vetoers existhudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1040) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209) at
[JIRA] (JENKINS-58659) ZipExtractionInstaller should ignore timestamp if URL changes
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-58659 ZipExtractionInstaller should ignore timestamp if URL changes Change By: Alex Earl Component/s: customtools-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200940.1564060967000.1523.1564111440163%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat updated JENKINS-58419 Jenkins / JENKINS-58419 CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Change By: evernat Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200546.1562746885000.1514.1564100340873%40Atlassian.JIRA.
[JIRA] (JENKINS-58388) `report` link in monitoring plugin description doesn't work
Title: Message Title evernat updated JENKINS-58388 Jenkins / JENKINS-58388 `report` link in monitoring plugin description doesn't work Change By: evernat Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200512.1562601973000.1518.1564100341584%40Atlassian.JIRA.
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title Florian Klink commented on JENKINS-56569 Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set It looks like this is already implemented in https://github.com/jenkinsci/git-client-plugin/commit/853603cccd4434b116ef9b8e094c3f5b815aa75a - however, the git lfs pull doesn't seem to properly replace lfs pointers… Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198184.1552593939000.1511.1564098480126%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Paulo Almeida commented on JENKINS-57351 Re: Support for making Jenkins a "GitHub App" Hi guys, I'm the author of the pull request that adds Github App integration to the kohsuke/github-api source code. Let me know if I can assist you guys on anything to get it merged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.1503.1564097700194%40Atlassian.JIRA.
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
Florian Klink commented on JENKINS-56569
Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set
If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails.
Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too.
If lfs files shall not be pulled at all, there is no way to configure this in the plugin.
Why don't you want your lfs pointers to be resolved while checking out? If that smudge filter is installed system-wide, why should jenkins override that behaviour at all, or silently flip its default?
I therefore suggest to always set the environment variable {{GIT_LFS_SKIP_SMUDGE=1}}even if no "GitLFSPull" option was specified. This makes sure that no "git lfs" commands that are not controlled by the git-client-plugin are launched and thus resolves the issue that the checkout fails in case the remote server requires authentication. This also prevents pulling lfs files regardless of a system's configuration and requires to explicitly pull lfs files via the "GitLFSPull" option.
Again, this really sounds more like a broken LFS backend on your side, than something that should be changed on Jenkins' side. This would also be problematic with declarative pipelines, for which there's currently no way to enable the GitLFSPull option.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58479) Failing to retrieve teams
Title: Message Title Kote Mushegiani commented on JENKINS-58479 Re: Failing to retrieve teams Has anyone taken a look at this? Or are there any updates? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.1479.1564093920221%40Atlassian.JIRA.
[JIRA] (JENKINS-47870) git changelog compared to arbitrary reference
Title: Message Title ipleten commented on JENKINS-47870 Re: git changelog compared to arbitrary reference Is there any update on this? I need to get diff between two tags Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186385.1510084866000.1474.1564092840155%40Atlassian.JIRA.
[JIRA] (JENKINS-47717) Allow different "Discard Old Build" options per branch on multibranch pipelines
Title: Message Title
Roman Muntyanu edited a comment on JENKINS-47717
Re: Allow different "Discard Old Build" options per branch on multibranch pipelines
A more sophisticated example of a per-branch clean-up policy workaround . Multibranch Pipeline. Declarative build.jenkinsfile.The policy:{code:none}| Branch name | # Builds | # Artifacts ||-|--|-|| master | 100 | 1 || test| 10 | 1 || production | 10 | 5 || feature/* |5 | 1 || bug/* |5 | 1 || |1 | 0 |{code}The solution:{code:groovy}pipeline {options {buildDiscarder(logRotator(// number of builds to keepnumToKeepStr: env.BRANCH_NAME ==~ /master/ ? '100' : env.BRANCH_NAME ==~ /production|test/ ? '10' : env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '5' : '1',// number of builds to keep the artifacts fromartifactNumToKeepStr: env.BRANCH_NAME ==~ /master|test/ ? '1' : env.BRANCH_NAME ==~ /production/ ? '5' : env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '1' : '0'))}.}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186203.1509215223000.1456.1564091160820%40Atlassian.JIRA.
[JIRA] (JENKINS-47717) Allow different "Discard Old Build" options per branch on multibranch pipelines
Title: Message Title
Roman Muntyanu edited a comment on JENKINS-47717
Re: Allow different "Discard Old Build" options per branch on multibranch pipelines
A more sophisticated example of a per-branch clean-up policy workaround (thank you, [~richajam]!) . Multibranch Pipeline. Declarative build.jenkinsfile.The policy:{code:none}| Branch name | # Builds | # Artifacts ||-|--|-|| master | 100 | 1 || test| 10 | 1 || production | 10 | 5 || feature/* |5 | 1 || bug/* |5 | 1 || |1 | 0 |{code}The solution:{code:groovy}pipeline {options {buildDiscarder(logRotator(// number of builds to keepnumToKeepStr: env.BRANCH_NAME ==~ /master/ ? '100' : env.BRANCH_NAME ==~ /production|test/ ? '10' : env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '5' : '1',// number of builds to keep the artifacts fromartifactNumToKeepStr: env.BRANCH_NAME ==~ /master|test/ ? '1' : env.BRANCH_NAME ==~ /production/ ? '5' : env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '1' : '0'))}.}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186203.1509215223000.1459.1564091160868%40Atlassian.JIRA.
[JIRA] (JENKINS-47717) Allow different "Discard Old Build" options per branch on multibranch pipelines
Title: Message Title
Roman Muntyanu edited a comment on JENKINS-47717
Re: Allow different "Discard Old Build" options per branch on multibranch pipelines
A more sophisticated example of a per-branch clean-up policy. Multibranch Pipeline. Declarative build.jenkinsfile.The policy:{code:none}| Branch name | # Builds | # Artifacts ||-|--|-|| master | 100 | 1 || test| 10 | 1 || production | 10 | 5 || feature/* |5 | 1 || bug/* |5 | 1 || |1 | 0 |{code}The solution:{code: gradle groovy }pipeline {options {buildDiscarder(logRotator(// number of builds to keepnumToKeepStr: env.BRANCH_NAME ==~ /master/ ? '100' : env.BRANCH_NAME ==~ /production|test/ ? '10' : env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '5' : '1',// number of builds to keep the artifacts fromartifactNumToKeepStr: env.BRANCH_NAME ==~ /master|test/ ? '1' : env.BRANCH_NAME ==~ /production/ ? '5' : env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '1' : '0'))}.}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186203.1509215223000.1435.1564091101141%40Atlassian.JIRA.
[JIRA] (JENKINS-47717) Allow different "Discard Old Build" options per branch on multibranch pipelines
Title: Message Title
Roman Muntyanu commented on JENKINS-47717
Re: Allow different "Discard Old Build" options per branch on multibranch pipelines
A more sophisticated example of a per-branch clean-up policy. Multibranch Pipeline. Declarative build.jenkinsfile. The policy:
| Branch name | # Builds | # Artifacts |
|-|--|-|
| master | 100 | 1 |
| test| 10 | 1 |
| production | 10 | 5 |
| feature/* |5 | 1 |
| bug/* |5 | 1 |
| |1 | 0 |
The solution:
Unable to find source-code formatter for language: gradle. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, _javascript_, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
pipeline {
options {
buildDiscarder(logRotator(
// number of builds to keep
numToKeepStr: env.BRANCH_NAME ==~ /master/ ? '100' :
env.BRANCH_NAME ==~ /production|test/ ? '10' :
env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '5' : '1',
// number of builds to keep the artifacts from
artifactNumToKeepStr: env.BRANCH_NAME ==~ /master|test/ ? '1' :
env.BRANCH_NAME ==~ /production/ ? '5' :
env.BRANCH_NAME ==~ /feature\/.*|bug\/.*/ ? '1' : '0'
))
}
.
}
Add Comment
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title steve bussetti commented on JENKINS-41929 Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found Has there been any traction on this? Honestly if someone could point me at the code responsible for reading the Jenkinsfile from the scm I could write a simple plugin that just adds a "Refresh Job Definition" button to the sidebar of a job. Most of the folks I see run into this are less concerned with the first-time triggered build than they are about being unable to modify new parameters after updating a particular job which means they're manually executing a Pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178785.1486740246000.1420.1564088644327%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Simon Tunnat, you are welcome to request this change be backported. Since supjac m, determined their continued failures were unrelated I no longer object to backporting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.1291.1564087080466%40Atlassian.JIRA.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jeff Thompson commented on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU Interesting. It would be great if this resolves the issues you are seeing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.1288.1564086900172%40Atlassian.JIRA.
[JIRA] (JENKINS-58648) Dependency-check publisher 5.0.2 does not show Results
Title: Message Title Steve Springett commented on JENKINS-58648 Re: Dependency-check publisher 5.0.2 does not show Results This is the clue: [DependencyCheck] Unable to find Dependency-Check reports to parse What does the job configuration have for 'artifact'? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200917.1563994217000.1286.1564086300155%40Atlassian.JIRA.
[JIRA] (JENKINS-58653) Add discover subgroups trait
Title: Message Title Parichay Barpanda updated JENKINS-58653 Jenkins / JENKINS-58653 Add discover subgroups trait Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200933.1564021125000.1277.1564086180386%40Atlassian.JIRA.
[JIRA] (JENKINS-58666) Add Trusted contributor trait to ForkMRTraits
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58666 Add Trusted contributor trait to ForkMRTraits Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-25 20:22 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Upon request of Oleg to add Trust contributor traits for Fork Merge Request Traits which enables only users with required permssion i.e. Developer, Maintainer, Owner permission to build their MR. Add Comment
[JIRA] (JENKINS-58636) Tests failing with mvn package with jdk8
Title: Message Title ikedam updated an issue Jenkins / JENKINS-58636 Tests failing with mvn package with jdk8 Change By: ikedam Summary: Tests failing with mvn package with jdk8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200804.1563962522000.1273.1564085880163%40Atlassian.JIRA.
[JIRA] (JENKINS-58636) Tests failing with mvn package
Title: Message Title ikedam updated an issue Jenkins / JENKINS-58636 Tests failing with mvn package Change By: ikedam Issue Type: Bug Task Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200804.1563962522000.1270.1564085760303%40Atlassian.JIRA.
[JIRA] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
Title: Message Title JT Moree commented on JENKINS-17418 Re: Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors +1 on improving the groovy editor experience. It is extremely painful to use since the bootstrap based layout of the application wont let me widen the editor. I can make it taller but not wider. I can use the DOM editor to remove (class="col-md-offset-2 col-md-20") but it is not a permanent fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148252.136467088.1244.1564084920259%40Atlassian.JIRA.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Jesse Glick commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Karol Gil better to file a fresh bug report with as much detail as you can and Link it to this one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196500.1546530449000.1204.1564084200750%40Atlassian.JIRA.
[JIRA] (JENKINS-58637) .jenkinsignore
Title: Message Title Jesse Glick commented on JENKINS-58637 Re: .jenkinsignore That was fast! https://github.com/jenkinsci/multibranch-build-strategy-extension-plugin/commit/df5033974de58e4f21798621da3e0e136b2bf15c I will try it out and see if we can get it running on ci.jenkins.io. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200805.1563962839000.1201.1564084140212%40Atlassian.JIRA.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Devin Nusbaum resolved as Fixed Version 2.5.4 of Branch API plugin was just released. This version undeprecates the original property (and two others that were deprecated at the same time) and disables the automatic migration going forward (but does not try to reverse it automatically to avoid making things worse). Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: Devin Nusbaum Status: Open Resolved Assignee: Devin Nusbaum Resolution: Fixed Released As: branch-api 2.5.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57442) Parameterized Trigger Plugin should print link to running job
Title: Message Title Tim Armstrong updated JENKINS-57442 Jenkins / JENKINS-57442 Parameterized Trigger Plugin should print link to running job Change By: Tim Armstrong Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199255.1557794112000.1176.1564082400129%40Atlassian.JIRA.
[JIRA] (JENKINS-57442) Parameterized Trigger Plugin should print link to running job
Title: Message Title Tim Armstrong updated an issue Jenkins / JENKINS-57442 Parameterized Trigger Plugin should print link to running job https://github.com/jenkinsci/parameterized-trigger-plugin/pull/125 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199255.1557794112000.1177.1564082400165%40Atlassian.JIRA.
[JIRA] (JENKINS-58539) Tool always exits with value of 1
Title: Message Title Natasha Stopa commented on JENKINS-58539 Re: Tool always exits with value of 1 Fixed in PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/39 Added exceptions and exiting in: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/43 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200688.1563427958000.1174.1564079880118%40Atlassian.JIRA.
[JIRA] (JENKINS-58539) Tool always exits with value of 1
Title: Message Title Natasha Stopa updated JENKINS-58539 Jenkins / JENKINS-58539 Tool always exits with value of 1 Change By: Natasha Stopa Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200688.1563427958000.1175.1564079880148%40Atlassian.JIRA.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa updated JENKINS-58216 Jenkins / JENKINS-58216 Issues with Failed Download Output File in Docker Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200276.156156802.1173.1564079100205%40Atlassian.JIRA.
[JIRA] (JENKINS-58126) Make Parsing for Plugin Manager CLI More Robust
Title: Message Title Natasha Stopa updated JENKINS-58126 Jenkins / JENKINS-58126 Make Parsing for Plugin Manager CLI More Robust Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200171.156105741.1171.1564079040167%40Atlassian.JIRA.
[JIRA] (JENKINS-58664) Add pipeline function to obscure credentials inFile
Title: Message Title
citizenkahn created an issue
Jenkins / JENKINS-58664
Add pipeline function to obscure credentials inFile
Issue Type:
New Feature
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2019-07-25 18:22
Priority:
Minor
Reporter:
citizenkahn
Problem The plugin hides secrets from the jenkins console but when a using complex tool chain the secrets may be stored in some tool's log and later published as build output. For example: the following uses ansible and a junit output callback to generate junit xml which will include secrets.
withCredentials([usernamePassword(credentialsId: 'my-test-user',
passwordVariable: 'USER',
usernameVariable: 'PASSWORD')]) {
withEnv([
"ANSIBLE_STDOUT_CALLBACK=junit",
"JUNIT_OUTPUT_DIR=${env.WORKSPACE}"
]) {
try {
ansiblePlaybook(
playbook:"ansible/playbooks/steps.yml",
extraVars: [
user: USER,
password: PASSWORD
]
)
} finally {
junit 'steps.*xml'
}
}
}
Recommendation Whereas
It seem unreasonable/impossible for the plugin to understand all tool chains
Only the binding plugin can properly know all secrets to hide
The addition of an exposed
[JIRA] (JENKINS-58637) .jenkinsignore
Title: Message Title Igal Gluh commented on JENKINS-58637 Re: .jenkinsignore Jesse Hi, Is it solved your problem? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200805.1563962839000.1169.1564077300238%40Atlassian.JIRA.
[JIRA] (JENKINS-58663) Keep Forever Not Propogated to child builds
Title: Message Title christopher Decker created an issue Jenkins / JENKINS-58663 Keep Forever Not Propogated to child builds Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2019-07-25 17:30 Priority: Major Reporter: christopher Decker I have confirmed this behavior in 1.13. When marking the parent job as keep forever this dose not propagate to the child jobs. This is a critical issue for me due to the fact that the artifacts are archived in the child jobs and there is no way to arrogate them into the parent. This means there is currently no way to automate keeping the artifacts forever. Add Comment
[JIRA] (JENKINS-53366) `keep forever` is no longer inherit to sub configurations
Title: Message Title christopher Decker commented on JENKINS-53366 Re: `keep forever` is no longer inherit to sub configurations have confirmed this is an issue in Matrix Build 1.13 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193453.1535715978000.1163.1564075440205%40Atlassian.JIRA.
[JIRA] (JENKINS-58636) Tests failing with mvn package
Title: Message Title AB S commented on JENKINS-58636 Re: Tests failing with mvn package Update I changed access level of before and after methods to public in file GroovyLabelAssignmentJenkinsRule. Now the error is: [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java:[103,20] unreported exception java.lang.Exception; must be caught or declared to be thrown [INFO] 1 error [INFO] - [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 20.598 s [INFO] Finished at: 2019-07-25T22:35:04+05:30 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:testCompile (default-testCompile) on project groovy-label-assignment: Compilation failure [ERROR] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java:[103,20] unreported exception java.lang.Exception; must be caught or declared to be thrown Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200804.1563962522000.1160.1564074540146%40Atlassian.JIRA.
[JIRA] (JENKINS-58636) Tests failing with mvn package
Title: Message Title AB S updated JENKINS-58636 Jenkins / JENKINS-58636 Tests failing with mvn package Change By: AB S Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200804.1563962522000.1158.1564073880174%40Atlassian.JIRA.
[JIRA] (JENKINS-58636) Tests failing with mvn package
Title: Message Title AB S commented on JENKINS-58636 Re: Tests failing with mvn package I tried to change the following in plugin POM and try 'mvn clean package': 1- 6 (was 5 by default), did not work. Same error as in this Jira issue description 2- 1.557 1.557 (earlier 1.509), now its giving the error: [INFO] — maven-compiler-plugin:3.3:testCompile (default-testCompile) @ groovy-label-assignment — [INFO] Changes detected - recompiling the module! [INFO] Compiling 3 source files to C:\Users\abhinavkumar.singh\Downloads\groovy-label-assignment-plugin-master\target\test-classes [INFO] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java: C:\Users\abhinavkumar.singh\Downloads\groovy-label-assignment-plugin-master\src\test\java\jp\ikedam\jenkins\plugins\groovy_label_assignment\GroovyLabelAssignmentJenkinsRule.java uses or overrides a deprecated API. [INFO] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java: Recompile with -Xlint:deprecation for details. [INFO] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/target/generated-test-sources/injected/InjectedTest.java: C:\Users\abhinavkumar.singh\Downloads\groovy-label-assignment-plugin-master\target\generated-test-sources\injected\InjectedTest.java uses unchecked or unsafe operations. [INFO] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/target/generated-test-sources/injected/InjectedTest.java: Recompile with -Xlint:unchecked for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java:[58,20] before() in jp.ikedam.jenkins.plugins.groovy_label_assignment.GroovyLabelAssignmentJenkinsRule cannot override before() in org.jvnet.hudson.test.JenkinsRule attempting to assign weaker access privileges; was public [ERROR] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java:[93,20] after() in jp.ikedam.jenkins.plugins.groovy_label_assignment.GroovyLabelAssignmentJenkinsRule cannot override after() in org.jvnet.hudson.test.JenkinsRule attempting to assign weaker access privileges; was public [INFO] 2 errors [INFO] - [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 02:46 min [INFO] Finished at: 2019-07-25T22:17:36+05:30 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:testCompile (default-testCompile) on project groovy-label-assignment: Compilation failure: Compilation failure: [ERROR] /C:/Users/abhinavkumar.singh/Downloads/groovy-label-assignment-plugin-master/src/test/java/jp/ikedam/jenkins/plugins/groovy_label_assignment/GroovyLabelAssignmentJenkinsRule.java:[58,20] before() in jp.ikedam.jenkins.plugins.groovy_label_assignment.GroovyLabelAssignmentJenkinsRule cannot override before() in org.jvnet.hudson.test.JenkinsRule [ERROR]
[JIRA] (JENKINS-58646) Autocomplete not working in latest azure ad plugin
Title: Message Title anjana raghavendra p closed an issue as Not A Defect Its a configuration issue as documented in https://github.com/jenkinsci/azure-ad-plugin/issues/46 Jenkins / JENKINS-58646 Autocomplete not working in latest azure ad plugin Change By: anjana raghavendra p Status: Open Closed Resolution: Not A Defect Released As: https://github.com/jenkinsci/azure-ad-plugin/issues/46 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-47333) file parameter not working in pipeline job
Title: Message Title Mark Waite edited a comment on JENKINS-47333 Re: file parameter not working in pipeline job JENKINS-27413 comments describe why it does not work today and give a strong indication that it won't work in the future.I created a [small test case|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-47333/Jenkinsfile#L11] that I used to interactively verify the issue exists. The file parameter is accepted as part of the Declarative Pipeline job definition and the job accepts the uploaded file, but the file does not seem to be placed anywhere that I could detect. It was not placed in the workspace of the agent running the job, nor was it placed on the master file system. I believe that the comments from Jesse Glick in JENKINS-27413 explain why the file is not stored anywhere. Removed from documentation on jenkins.io July 25, 2019 by [PR-2388|https://github.com/jenkins-infra/jenkins.io/pull/2388] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185762.1507483631000.1038.1564072982315%40Atlassian.JIRA.
[JIRA] (JENKINS-58646) Autocomplete not working in latest azure ad plugin
Title: Message Title anjana raghavendra p commented on JENKINS-58646 Re: Autocomplete not working in latest azure ad plugin Sorry, its working after those permissions. Its just taking time to replicate. Thanks for your help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200915.1563988435000.1054.1564072982565%40Atlassian.JIRA.
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title Mark Waite commented on JENKINS-27413 Re: Handle file parameters Removed from documentation on jenkins.io July 25, 2019 by PR-2388 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161212.1426248363000.1056.1564072982612%40Atlassian.JIRA.
[JIRA] (JENKINS-58646) Autocomplete not working in latest azure ad plugin
Title: Message Title anjana raghavendra p updated an issue Jenkins / JENKINS-58646 Autocomplete not working in latest azure ad plugin Change By: anjana raghavendra p Attachment: image-2019-07-25-22-06-59-675.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200915.1563988435000.1029.1564072680179%40Atlassian.JIRA.
[JIRA] (JENKINS-58646) Autocomplete not working in latest azure ad plugin
Title: Message Title anjana raghavendra p commented on JENKINS-58646 Re: Autocomplete not working in latest azure ad plugin I have given the permissions as mentioned in the ticket https://github.com/jenkinsci/azure-ad-plugin/issues/46 but still not able to do auto-complete and getting permissions error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200915.1563988435000.1031.1564072680213%40Atlassian.JIRA.
[JIRA] (JENKINS-58662) Allow users to specify a mirror URL which would point to an internal mirror of the public plugin repo
Title: Message Title Justin Harringa commented on JENKINS-58662 Re: Allow users to specify a mirror URL which would point to an internal mirror of the public plugin repo I didn't add this to the GSoC epic and didn't add the GSoC label because I thought I would leave that up to the group on whether this would be in scope. Note: Oleg Nenashev mentioned that Custom WAR Packager does something like this. He also mentioned "Will change in 2.0.0 tho, I will integrate the Plugin Manager Lib there" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200944.1564072122000.1027.1564072320128%40Atlassian.JIRA.
[JIRA] (JENKINS-58662) Allow users to specify a mirror URL which would point to an internal mirror of the public plugin repo
Title: Message Title Justin Harringa created an issue Jenkins / JENKINS-58662 Allow users to specify a mirror URL which would point to an internal mirror of the public plugin repo Issue Type: New Feature Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-25 16:28 Labels: plugin-manager Priority: Minor Reporter: Justin Harringa It would be nice to be able to provide a single mirror URL to override the normal Jenkins public infrastructure. Background: Some companies run something like Sonatype Nexus Repository or Artifactory to mirror public Maven repositories. While they could run an internal update center, some organizations choose not to because of the extra management. Add Comment
[JIRA] (JENKINS-47333) file parameter not working in pipeline job
Title: Message Title Mark Waite commented on JENKINS-47333 Re: file parameter not working in pipeline job JENKINS-27413 comments describe why it does not work today and give a strong indication that it won't work in the future. I created a small test case that I used to interactively verify the issue exists. The file parameter is accepted as part of the Declarative Pipeline job definition and the job accepts the uploaded file, but the file does not seem to be placed anywhere that I could detect. It was not placed in the workspace of the agent running the job, nor was it placed on the master file system. I believe that the comments from Jesse Glick in JENKINS-27413 explain why the file is not stored anywhere. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185762.1507483631000.1009.1564071780559%40Atlassian.JIRA.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Karol Gil commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN We are running into the same issue with version 1.17.2 with no `containerLog` steps used - every time is happens it's on `sh` step. Increasing max connections, even to absurd numbers (100k or more) does not help at all. If I can provide any logs or information that could be useful in finally solving that please let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196500.1546530449000.972.1564070401023%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Steven Terrana commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod For what it's worth, the Templating Engine Plugin had almost the exact same issue where objects created and injected into the binding were throwing CPS Mismatch warnings. we're refactoring anything placed in the binding that's going to be invoking methods to be CPS transformed before being placed injected. After doing this - the only CpsMismatch warnings we got were around metaprogramming examples such as using InvokerHelper to invoke methods, or by taking advantage of groovy's methodMissing functionality. those use cases are being addressed in https://github.com/cloudbees/groovy-cps/pull/99 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200910.1563983113000.969.1564069680215%40Atlassian.JIRA.
[JIRA] (JENKINS-58030) TFS plugin failing in Jenkins
Title: Message Title prav teja updated an issue Jenkins / JENKINS-58030 TFS plugin failing in Jenkins Change By: prav teja Labels: jenkins pipeline plugins tfs-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199979.1560368858000.963.1564069080540%40Atlassian.JIRA.
[JIRA] (JENKINS-58030) TFS plugin failing in Jenkins
Title: Message Title prav teja updated an issue Jenkins / JENKINS-58030 TFS plugin failing in Jenkins Change By: prav teja Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199979.1560368858000.961.1564069080497%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Andreas Sieferlinger commented on JENKINS-57351 Re: Support for making Jenkins a "GitHub App" Hope that PR will go through soon. Maybe Liam Newman could merge it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.951.1564066980342%40Atlassian.JIRA.
[JIRA] (JENKINS-58661) No DSL support for build monitor view filter job by match value FULL NAME
Title: Message Title Shubhangi Vishwakarma created an issue Jenkins / JENKINS-58661 No DSL support for build monitor view filter job by match value FULL NAME Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-07-25 at 16.44.29.png, Screenshot 2019-07-25 at 16.44.57.png Components: build-monitor-plugin Created: 2019-07-25 14:56 Environment: Jenkins - 2.176.2 Build Monitor View - 1.12+build.201809061734 Java - JDK 11 Labels: plugin dsl Priority: Minor Reporter: Shubhangi Vishwakarma I have a setup with multibranch pipeline in jenkins. The folder name corresponds to project name and the jobs inside this folder are named with respect to branch name. I want to filter some of these jobs from build monitor view. In Jenkins UI, I have an option to apply job filter by regex, so I specify .project-name. and select Full Name in match value. This works. Just selecting name, however, does not works as the name of job will be branch name (master, etc.) and I wish to filter out a complete project. I am handling Jenkins configuration via job dsl and I do not find the same option in DSL as in UI. All options, except Full Name, are present in DSL. Attaching screenshot of both UI and DSL.
[JIRA] (JENKINS-58660) Errors running OWASP Dependency-Check plugin cause non-obvious failures of the build
Title: Message Title Oliver Lockwood created an issue Jenkins / JENKINS-58660 Errors running OWASP Dependency-Check plugin cause non-obvious failures of the build Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-25 14:33 Environment: Jenkins 2.181 Dependency-check plugin 5.2.0 Priority: Minor Reporter: Oliver Lockwood If any errors occur in the Dependency-Check plugin (i.e. the CLI tool exits with a non-zero return code) then the Jenkins build result is set to failure, as per this code https://github.com/jenkinsci/dependency-check-plugin/blob/master/src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckToolBuilder.java#L157 final boolean success = (exitCode == 0); build.setResult(success ? Result.SUCCESS : Result.FAILURE); I have two concerns with this. When this happens, it is far from obvious that the reason for the build failure is the Dependency-Check plugin. The build may well continue and do many more stages, so parsing build output to determine the root cause is much more onerous than it needs to be. I believe it ought to be possible to configure (through plugin invocation parameters) the effect on the build of any errors running the plugin. For example, it may be more appropriate to make the build UNSTABLE, or even not
[JIRA] (JENKINS-58632) LR Controller job not generating LRR, LRA and HTML folder in workspace
Title: Message Title Rolando-Mihai Vlad edited a comment on JENKINS-58632 Re: LR Controller job not generating LRR, LRA and HTML folder in workspace Hello Govind,Did you add the "Always archieve and publish test reports (LR only) step in post-build actions ? Regards,Rolando Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200800.1563956084000.944.1564064760178%40Atlassian.JIRA.
[JIRA] (JENKINS-58632) LR Controller job not generating LRR, LRA and HTML folder in workspace
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-58632 Re: LR Controller job not generating LRR, LRA and HTML folder in workspace Hello Govind, Did you add the "Always archieve and publish test reports (LR only) step? Regards, Rolando Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200800.1563956084000.942.1564064700175%40Atlassian.JIRA.
[JIRA] (JENKINS-56759) Unexpected executor death prevents builds
Title: Message Title James Rubino edited a comment on JENKINS-56759 Re: Unexpected executor death prevents builds I experienced this error during a server change-over today.I see that this error has been gone over at least once before and a bug report filed and resolved in the JENKINS-29902 issue. I have tried to take slaves off and back online and this did not resolve the error.I have tried changing job build numbers and this did not resolve the error. JobClass jobClass : FreestyleJenkins Ver: 2.176.1Master Node OS: Debian 9Windows Slave OS: Windows 7 Pro service pack 1The same configuration is used successfully using a different Debian 9 server with the same slave unit machines.The windows jenkins service user permissions appear correct via the service properties menu. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198402.1553603985000.939.1564064100212%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Reinhold Füreder commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Devin Nusbaum Sorry, I guess you are right => I'll adapt the issue links Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.924.1564063860375%40Atlassian.JIRA.
[JIRA] (JENKINS-57725) Proc.executor inherits ContextClassLoader dynamically
Title: Message Title Devin Nusbaum commented on JENKINS-57725 Re: Proc.executor inherits ContextClassLoader dynamically Kyle Manna It looks like you have a distinct issue with two aspects: One, something is causing a bunch of timer threads to be created and not cleaned up, and two, those timer threads are inheriting their context class loader dynamically. The first issue is more serious, to investigate it I would search the jenkinsci organization on GitHub for all uses of java.util.Timer, cross-check that with the set of plugins you have installed, and then examine the ways that the plugins you have installed are using java.util.Timer based on the search. My guess is that something is repeatedly calling new Timer rather than storing a single timer somewhere and reusing it (maybe also better to switch to using an ExecutorService if that is the problem). Either way I'd go ahead and open a separate issue for your problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199668.1559071263000.905.1564063380331%40Atlassian.JIRA.
[JIRA] (JENKINS-27494) Support for PHPUnit 4.* reports
Title: Message Title Nochum Sossonko commented on JENKINS-27494 Re: Support for PHPUnit 4.* reports I believe this broke compatibility with older versions of PHP Unit and Codeception. I had to rollback to 2.3.3 for it to work again Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161296.1426709669000.899.1564063260189%40Atlassian.JIRA.
[JIRA] (JENKINS-58632) LR Controller job not generating LRR, LRA and HTML folder in workspace
Title: Message Title Govind Sureka commented on JENKINS-58632 Re: LR Controller job not generating LRR, LRA and HTML folder in workspace Hello Rolando, Please let me know if you need any other details. Thanks, Govind Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200800.1563956084000.896.1564063140395%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-58085
Re: BlueOcean UI stuck in "Waiting for run to start"
{quote}Based on the BlueOcean changelog one naively assumes that this issue is actually caused by JENKINS-39203{quote}I'd be surprised if that was related, any problems with that change should just cause the wrong result status for a single stage, so the fact that in the description the API is returning an empty array for the steps in a stage makes me think something else is broken. Looking at the [changelog|https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.17.0], I suspect it is related to the [fix|https://github.com/jenkinsci/blueocean-plugin/pull/1961] for JENKINS-53816, especially given some of the comments on that ticket mentioning that it might have made things worse in some cases. [~rmorrise] I think you are running into JENKINS-55308, which is unrelated as far as I know.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.892.1564061521665%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Based on the BlueOcean changelog one naively assumes that this issue is actually caused by JENKINS-39203 I'd be surprised if that was related, any problems with that change should just cause the wrong result status for a single stage, so the fact that in the description the API is returning an empty array for the steps in a stage makes me think something else is broken. Looking at the changelog, I suspect it is related to the fix for JENKINS-53816, especially given some of the comments on that ticket mentioning that it might have made things worse in some cases. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.864.1564061401405%40Atlassian.JIRA.
[JIRA] (JENKINS-58659) ZipExtractionInstaller should ignore timestamp if URL changes
Title: Message Title Anders Hammar created an issue Jenkins / JENKINS-58659 ZipExtractionInstaller should ignore timestamp if URL changes Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-07-25 13:22 Environment: Jenkins LTS 2.176.2 RedHat OpenJDK 1.8.0 RHEL 7 Priority: Minor Reporter: Anders Hammar Background: We're using the Custom Tools Plugin to define misc custom tools in our Jenkins environment. Typically we use "Install automatically" and use the "Extract .zip/.tar.gz" installer to download the tool archive. The archive is typically hosted in our Nexus instance and we specify the exact version, like this: http://nexus.acme.org/content/repositories/releases/org/acme/jenkins/nifty-tool/1.0.0/nifty-tool-1.0.0.tar.gz (In this example we're pointing at a Maven artifact, but it could be any URL.) When there is a new version of the tool we just update the ULR and Jenkins will update automatically. Problem: The problem is when we want to downgrade to an earlier version. For example, we have http://nexus.acme.org/content/repositories/releases/org/acme/jenkins/nifty-tool/1.0.1/nifty-tool-1.0.1.tar.gz but want to change back to the old http://nexus.acme.org/content/repositories/releases/org/acme/jenkins/nifty-tool/1.0.0/nifty-tool-1.0.0.tar.gz In this case the older version is not automatically installed, but we need to manually go in on every slave and remove the .timestamp file to force a downgrade. Suggested Improvement: The current behavior where only a newer archive is doenloaded and installed is suitable when the URL doesn't change but one just updates the archive (overwriting the old file). But if the URL changes, the archive should be installed regardless of the timestamp. A different URL should always indicate a different archive.
[JIRA] (JENKINS-58540) Console output of pipeline extra stars
Title: Message Title Sebastian Wojas commented on JENKINS-58540 Re: Console output of pipeline extra stars Any updates here ? we have exactly the same problem on our end. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200689.1563433318000.858.1564060860205%40Atlassian.JIRA.
[JIRA] (JENKINS-57743) Add calculate algorithms for types of days
Title: Message Title Jeff Pearce resolved as Won't Do Jenkins / JENKINS-57743 Add calculate algorithms for types of days Change By: Jeff Pearce Status: In Progress Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199688.1559142414000.856.1564060440152%40Atlassian.JIRA.
[JIRA] (JENKINS-58363) Add backend API for fetching date presets.
Title: Message Title Jeff Pearce updated JENKINS-58363 Jenkins / JENKINS-58363 Add backend API for fetching date presets. Change By: Jeff Pearce Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200478.1562338782000.854.1564060380267%40Atlassian.JIRA.
[JIRA] (JENKINS-58347) Complete exclude function
Title: Message Title Jeff Pearce updated JENKINS-58347 Jenkins / JENKINS-58347 Complete exclude function Change By: Jeff Pearce Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200462.1562252859000.852.1564060380240%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a restart I can confirm missing updates of the config file. What my problems looked like: I had to change the configuration of the Jira server (moved to a new host). My first experience of the fault was, in some magic way the setting changed back to the old one. I tried to manually correct the setting in the config file, which was the place were I found the old settings. Since that, the settings entirely disappeared (but still lived in the config file). I can still not confirm the time points when the settings changed back: I intentionally restarted jenjkins several times due to jenkins - and/or plugin updates and I can't remember a correlation between those restarts and broken Jira settings. Unfortunately this is a production system. Therefore I reverted the plugin back to 3.0.6 and can't play around with it to find out more relations. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.845.1564060260247%40Atlassian.JIRA.
[JIRA] (JENKINS-44142) Step jobDsl can be used at most once in pipeline with DELETE
Title: Message Title Lucie Votypkova commented on JENKINS-44142 Re: Step jobDsl can be used at most once in pipeline with DELETE Hello, it is connected with problem with multiple job dsl action - action with generated objects is added for every job dsl build step, so there is the same number of actions as job-dsl steps. If option DELETE is checked, it compares generated items of current build (if there is unreferenced job/view/config - jobs/views ... which were created by this seed job, but are not included in generated objects by job dsl step). But this comparison contains only generated items from one action not from the all actions from all job dsl steps because getAction(Class returns only the first hit. Including them into one action (so do not create action for every job dsl step, but include generated objects into existing action) should fix the problem, but only in case that you use DELETE option only in your last build job dsl step (because generation of all jobs/views/config is not finished if there any job dsl step reminds to execute). my pull request is there https://github.com/jenkinsci/job-dsl-plugin/pull/1190, you can check it or comment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181769.1494322919000.837.1564059360388%40Atlassian.JIRA.
[JIRA] (JENKINS-29784) DSL Job View shows many copies of Generated Items
Title: Message Title Lucie Votypkova commented on JENKINS-29784 Re: DSL Job View shows many copies of Generated Items Hello, I fixed it in this pull request https://github.com/jenkinsci/job-dsl-plugin/pull/1190. Your problem is caused by multiple job-dsl build step - everyone adds its own action - so there is many actions of added items instead of one action with all. I changed it the way that if action for given build exists, it is not added the new one - new generated objects are included by the old one. It should fix the problem with removing all jobs (views...) created by previous steps when Action for removed job/views/config is checked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164360.1438702015000.826.1564058640450%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Reinhold Füreder edited a comment on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" We are also experiencing this *huge problem* (but not all the time though!?) – but are hesitating to downgrade, as 1.17 contains one really, really helpful new feature: https://issues.jenkins JENKINS - ci.org/browse/ 39203 ([~dnusbaum] Based on the BlueOcean changelog one naively assumes that this issue is actually caused by JENKINS-39203 => therefore I naively linked this issues) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.823.1564055702489%40Atlassian.JIRA.
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-56562 Re: Parallel downstream jobs are not linked correctly We've seen that there is a request that it is not made in some cases, it is completely random, I did not find any pattern !Screenshot 2019-07-25 at 12.00.40.png|thumbnail! !Screenshot 2019-07-25 at 12.01.14.png|thumbnail! This build does not link downstream jobshttps://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/36/pipeline/ 78 80 /This build is OKhttps://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/34/pipeline/ 78 80 I have captured a couple of HAR files from the job that works and the one that does not works [^har-ok.json] [^fail-har.json] this is the current pipeline https://github.com/elastic/apm-integration-testing/blob/6ee572b5efbb593204f97427139421727684bb6e/.ci/Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.807.1564055340612%40Atlassian.JIRA.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding edited a comment on JENKINS-58339 Re: Support new types of credentials Hi Enrique,Ah yes, I had overlooked that some plugins might only be able to handle certain credential types. The weight of legacy I suppose.I’m thinking of a way of supporting multiple credential types that would at least keep the important part of the credential (the Secret) compatible with non-Jenkins apps like it is today.Something like the following: * The secretString remains like it is now - a simple string (or byte array). Not JSON. * The extra fields (eg username for SSH key or X509 cert) are added as tags on the AWS Secret. This is fine, because most of those extra fields should be non-secret anyway. * The only secret extra field I’m aware of is a passphrase on a private key or cert. This, however, is only really relevant for local on-disk credentials stores - in a remote store like Secrets Manager the passphrase loses its protective power, as it would have to be stored inside... the key it’s protecting, so if an attacker got the key out of SM then they’d have got the passphrase with it. Therefore we’d just populate the passphrase field of the Credential constructor with blank or null. * When a Secret is loaded we determine the type by parsing the secretString and tags, maybe with a chain pattern or ADT: If the secretString contains the SSH ASCII armor construct an SSH key credential (get username from tags), if it contains the X509 header etc then construct a client cert credential (get username from tags), and so on.With this approach, the core bit of the Secret is still readable by any application using Secrets Manager (not just Jenkins), but the extra non-secret bits can be stored there for Jenkins’ sake. And we don’t need an artificial ‘type’ field/string to be stored either - the chain decoder doesn’t need it.Off the top of my head this should work for: * Secret text (there’s no extra fields to store) * SSH key (secretString format test + AWS tags) * Client cert (secretString format test + AWS tags) * Username / password (if doesn’t pass any secretString format tests, and there’s a username field in the AWS tags then it ) * Secret text (if didn ’ s a username / password pair t match any of the above criteria )Thoughts? (This is only a first take on the idea, and there might be other credentials types that I’ve overlooked.) Add Comment
[JIRA] (JENKINS-58658) GitHub Plugin should maintain job history and not re-execute pipelines on repository rename.
Title: Message Title Gordon Shankman updated an issue Jenkins / JENKINS-58658 GitHub Plugin should maintain job history and not re-execute pipelines on repository rename. Change By: Gordon Shankman Component/s: github-plugin Component/s: github-organization-folder-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200939.1564051846000.686.1564051980911%40Atlassian.JIRA.
[JIRA] (JENKINS-58658) GitHub Plugin should maintain job history and not re-execute pipelines on repository rename.
Title: Message Title Gordon Shankman created an issue Jenkins / JENKINS-58658 GitHub Plugin should maintain job history and not re-execute pipelines on repository rename. Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2019-07-25 10:50 Environment: Jenkins 2.164.2 GitHub plugin 1.29.4 GitHub Branch Source Plugin 2.4.5 GitHub API Plugin 1.95 Priority: Blocker Reporter: Gordon Shankman I am currently using an enterprise installation of GitHub and Jenkins, both of which are managed by another team so I have no control over plugin versions. It looks like there is a related issue to this (JENKINS-46068), but it is not quite the same thing as it deals with running jobs under both the old and new names after a rename. Not sure if the fix for that takes care of this request as well. We use git tags and pipeline builds to manage deployment to several production environments and have requirements to rename several of our repositories. When we renamed the first one, it re-executed builds for all current branches and a significant number of tags, triggering conflicting deployments to multiple environments. Fortunately, that repository was a support library and we were able to correct the issues without an application outage. We have several other repositories that need to be renamed and, at the moment, I have been unable to find a way to both rename the repositories and prevent Jenkins from re-executing pipelines on branches and tags which would cause unpredictable results in our environments and likely bring down a production application until we can sort the fallout. The GitHub plugin needs to be able to detect a repository rename and, at minimum, do nothing. The ideal solution is for the plugin to migrate the job
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-56562 Re: Parallel downstream jobs are not linked correctly We've seen that there is a request that it is not made in some cases, it is completely random, I did not find any pattern !Screenshot 2019-07-25 at 12.00.40.png|thumbnail! !Screenshot 2019-07-25 at 12.01.14.png|thumbnail! This build does not link downstream jobshttps://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/36/pipeline/78/This build is OKhttps://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/34/pipeline/78I have captured a couple of HAR files from the job that works and the one that does not works [^har-ok.json] [^fail-har.json] this is the current pipeline https://github.com/elastic/apm-integration-testing/blob/6ee572b5efbb593204f97427139421727684bb6e/.ci/Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.677.1564050360284%40Atlassian.JIRA.
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-56562 Re: Parallel downstream jobs are not linked correctly We saw 've seen that there is a request that it is not made in some cases, it is completely random, I did not find any pattern !Screenshot 2019-07-25 at 12.00.40.png|thumbnail! !Screenshot 2019-07-25 at 12.01.14.png|thumbnail! This build does not link downstream jobshttps://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/36/pipeline/78/This build is OKhttps://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/34/pipeline/78I have captured a couple of HAR files from the job that works and the one that does not works [^har-ok.json] [^fail-har.json] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.673.1564050180329%40Atlassian.JIRA.
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-56562 Parallel downstream jobs are not linked correctly Change By: Ivan Fernandez Calvo Attachment: har-ok.json Attachment: fail-har.json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.667.1564050060997%40Atlassian.JIRA.
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-56562 Re: Parallel downstream jobs are not linked correctly We saw that there is a request that it is not made in some cases, it is completely random, I did not find any pattern This build does not link downstream jobs https://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/36/pipeline/78/ This build is OK https://apm-ci.elastic.co/blue/organizations/jenkins/apm-integration-tests/detail/7.x/34/pipeline/78 I have captured a couple of HAR files from the job that works and the one that does not works har-ok.json fail-har.json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.669.1564050061059%40Atlassian.JIRA.
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-56562 Parallel downstream jobs are not linked correctly Change By: Ivan Fernandez Calvo Attachment: Screenshot 2019-07-25 at 12.00.40.png Attachment: Screenshot 2019-07-25 at 12.01.14.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.661.1564049220285%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat updated JENKINS-58419 Jenkins / JENKINS-58419 CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200546.1562746885000.658.1564048800472%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat commented on JENKINS-58419 Re: CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Fixed by 068775a, to be released in 1.79 (soon) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200546.1562746885000.655.1564048800422%40Atlassian.JIRA.
[JIRA] (JENKINS-58514) Repo plugin detect change when there is an error in repo sync
Title: Message Title Alessio Moscatello commented on JENKINS-58514 Re: Repo plugin detect change when there is an error in repo sync Probably is the same issue as JENKINS-37819 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200658.1563280071000.624.1564048200105%40Atlassian.JIRA.
[JIRA] (JENKINS-58657) sh not working inside docker container
Title: Message Title
Oleksandr Zhyhalo created an issue
Jenkins / JENKINS-58657
sh not working inside docker container
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker
Created:
2019-07-25 09:45
Priority:
Minor
Reporter:
Oleksandr Zhyhalo
sh command not working wile specifying user to run inside contrainer. Example:
docker.image('node:latest').inside('--user node') {
stage('Pull repository') {
sh 'whoami'
}
In this case checkout and other jenkins functions is working, but not any of sh Process is pending for 5 minutes and then return:
process apparently never started in /var/lib/jenkins/workspace/contrail-ui/contrail-ui-builder@2@tmp/durable-ae2b4ade (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
Error appears to be with any container.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding edited a comment on JENKINS-58339 Re: Support new types of credentials Hi Enrique,Ah yes, I had overlooked that some plugins might only be able to handle certain credential types. The weight of legacy I suppose.I’m thinking of a way of supporting multiple credential types that would at least keep the important part of the credential (the Secret) compatible with non-Jenkins apps like it is today.Something like the following: * The secretString remains like it is now - a simple string (or byte array). Not JSON. * The extra fields (eg username for SSH key or X509 cert) are added as tags on the AWS Secret. This is fine, because most of those extra fields should be non-secret anyway. * The only secret extra field I’m aware of is a passphrase on a private key or cert. This, however, is only really relevant for local on-disk credentials stores - in a remote store like Secrets Manager the passphrase loses its protective power, as it would have to be stored inside... the key it’s protecting, so if an attacker got the key out of SM then they’d have got the passphrase with it. Therefore we’d just populate the passphrase field of the Credential constructor with blank or null. * When a Secret is loaded we determine the type by parsing the secretString and tags, maybe with a chain pattern or ADT: If the secretString contains the SSH ASCII armor construct an SSH key credential (get username from tags), if it contains the X509 header etc then construct a client cert credential (get username from tags), and so on.With this approach, the core bit of the Secret is still readable by any application using Secrets Manager (not just Jenkins), but the extra non-secret bits can be stored there for Jenkins’ sake. And we don’t need an artificial ‘type’ field/string to be stored either - the chain decoder doesn’t need it.Off the top of my head this should work for: * Secret text (there’s no extra fields to store) * SSH key (secretString format test + AWS tags) * Client cert (secretString format test + AWS tags) * Username / password (if doesn’t pass any secretString format tests, and there’s a username field in the AWS tags then it’s a username / password pair)Thoughts? (This is only a first take on the idea, and there might be other credentials types that I’ve overlooked.) Add Comment
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding commented on JENKINS-58339 Re: Support new types of credentials Hi Enrique, Ah yes, I had overlooked that some plugins might only be able to handle certain credential types. The weight of legacy I suppose. I’m thinking of a way of supporting multiple credential types that would at least keep the important part of the credential (the Secret) compatible with non-Jenkins apps like it is today. Something like the following: The secretString remains like it is now - a simple string (or byte array). Not JSON. The extra fields (eg username for SSH key or X509 cert) are added as tags on the AWS Secret. This is fine, because most of those extra fields should be non-secret anyway. The only secret extra field I’m aware of is a passphrase on a private key or cert. This, however, is only really relevant for local on-disk credentials stores - in a remote store like Secrets Manager the passphrase loses its protective power, as it would have to be stored inside... the key it’s protecting, so if an attacker got the key out of SM then they’d have got the passphrase with it. Therefore we’d just populate the passphrase field with blank or null. When a Secret is loaded we determine the type by parsing the secretString and tags, maybe with a chain pattern or ADT: If the secretString contains the SSH ASCII armor construct an SSH key credential (get username from tags), if it contains the X509 header etc then construct a client cert credential (get username from tags), and so on. With this approach, the core bit of the Secret is still readable by any application using Secrets Manager (not just Jenkins), but the extra non-secret bits can be stored there for Jenkins’ sake. And we don’t need an artificial ‘type’ field/string to be stored either - the chain decoder doesn’t need it. Off the top of my head this should work for: Secret text (there’s no extra fields to store) SSH key (secretString format test + AWS tags) Client cert (secretString format test + AWS tags) Username / password (if doesn’t pass any secretString format tests, and there’s a username field in the AWS tags then it’s a username / password pair) Thoughts? (This is only a first take on the idea, and there might be other credentials types that I’ve overlooked.)
[JIRA] (JENKINS-47349) Parallel stage tool tip shows 0s for every stage irrespective of the execution time.
Title: Message Title Vlad Aginsky commented on JENKINS-47349 Re: Parallel stage tool tip shows 0s for every stage irrespective of the execution time. same at my setup, raising prio, my customers are very confused. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185781.1507548004000.602.1564046100576%40Atlassian.JIRA.
[JIRA] (JENKINS-47349) Parallel stage tool tip shows 0s for every stage irrespective of the execution time.
Title: Message Title Vlad Aginsky updated an issue Jenkins / JENKINS-47349 Parallel stage tool tip shows 0s for every stage irrespective of the execution time. Change By: Vlad Aginsky Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185781.1507548004000.572.1564046041999%40Atlassian.JIRA.
[JIRA] (JENKINS-58601) Allow deletion of one or more entries from job's config history
Title: Message Title Stefan Brausch assigned an issue to Robin Schulz Jenkins / JENKINS-58601 Allow deletion of one or more entries from job's config history Change By: Stefan Brausch Assignee: Stefan Brausch Robin Schulz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200761.1563800501000.570.1564045200631%40Atlassian.JIRA.
[JIRA] (JENKINS-58633) Losing Metadata if upload file bigger than 100MB
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-58633 Losing Metadata if upload file bigger than 100MB Change By: Jie Shen Status: Open Resolved Resolution: Fixed Released As: 1.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200801.1563958272000.567.1564044360231%40Atlassian.JIRA.
[JIRA] (JENKINS-57204) Provision failures does not clean up deployments
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-57204 Provision failures does not clean up deployments Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 1.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198961.155637878.565.1564041600365%40Atlassian.JIRA.
[JIRA] (JENKINS-22794) Option to remove from log: "Seen branch in repository blah blah blah"
Title: Message Title Jordan Sokolic commented on JENKINS-22794 Re: Option to remove from log: "Seen branch in repository blah blah blah" Setting the system property either via script console or via /etc/default/jenkins does not work for me. We have several thousand branches in our repository and they are printed upon every triggered build. This is really unnecessary. Jenkins version: 2.176.1 Git client plugin version: 2.8.0 Jenkins cmdline: /usr/bin/java -Xmx10g -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --httpListenAddress=127.0.0.1 --sessionTimeout=1440 --sessionEviction=43200 -Dorg.jenkinsci.plugins.gitclient.GitClient.quietRemoteBranches=true Any help would be much appreciated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154608.1398720056000.555.1564040521892%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title
Carroll Chiou updated an issue
Jenkins / JENKINS-58656
Wrapper process leaves zombie when no init process present
Change By:
Carroll Chiou
The merge of [PR-98|https://github.com/jenkinsci/durable-task-plugin/pull/98] moved the wrapper process to the background but to allow the launching process to quickly exit. However , as a result, zombies it that very act will orphan the wrapper process . This is only a problem in environments where there is no {{init}} process (e.g. docker containers that are run with no {{--init}} flag). Unit tests did not discover this bug due to a race condition of when the last {{ps}} was called and when the wrapper process exited. If another {{ps}} is called after the test detects that the script as finished running, the zombie state of the wrapper process is revealed.I'm not sure how much of an issue this really is as there are numerous solutions on enabling zombie-reaping for containers, but as there is an explicit check for zombies in the unit tests, it seemed worth mentioning.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Simon Tunnat commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I have the same problem with Jenkins LTS 2.176.2. Could you please fix that version as well? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.540.1564039081199%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Carroll Chiou created an issue Jenkins / JENKINS-58656 Wrapper process leaves zombie when no init process present Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-07-25 07:16 Environment: Running version 1.30-rc422.f179f78e479f Priority: Minor Reporter: Carroll Chiou The merge of PR-98 moved the wrapper process to the background but, as a result, zombies it. This is only a problem in environments where there is no init process (e.g. docker containers that are run with no --init flag). Unit tests did not discover this bug due to a race condition of when the last ps was called and when the wrapper process exited. If another ps is called after the test detects that the script as finished running, the zombie state of the wrapper process is revealed. I'm not sure how much of an issue this really is as there are numerous solutions on enabling zombie-reaping for containers, but as there is an explicit check for zombies in the unit tests, it seemed worth mentioning.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jörg Sautter edited a comment on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU I think this [https://stackoverflow.com/questions/9939989/java-nio-selector-select-returns-0-although-channels-are-ready] is the reason why the IOHub is taking all of our CPU power.The current implementation relies on the returned number of ready channels, but this is not the total number of ready channel. It is only the number of channels gone ready while the select is performed. We now changed the impementation from checking the returned number to keys.isEmpty() and evaluate this on our Jenkins installations.I will keep you updated and will do a PR in somedays some days , if the issue is fixed by this change. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.514.1564038241492%40Atlassian.JIRA.
