How do we Cleanup old and no longer used Credentials
Simply, how do we cleanup credentials in Jenkins that are not longer used by ANY pipelines, whether in a Jenkinsfile or in the Jenkins UI pipeline? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b8ebe1b3-8834-42f1-8416-fc64ea4df18fn%40googlegroups.com.
Re: Slave Node PATHJ environment variable cached
It seems that the Jenkins Coveirty Plugin is not compatible with Java 17 yet I suspect. I am waiting for Coverity Support to get back to me to verify. Who do I contact to report this BUG? On Tuesday, September 13, 2022 at 10:19:47 AM UTC-4 Chris Hardy wrote: > The slave node PATH value was changed on the node. The Jenkins master has > the old value cached. I have rebooted the slave node, restarted Jenkins, > disconnected/reconnected slave node in Jenkins, deleted/recreated slave > node. After all that the PATH is still cached to original value. I have > confirmed that the PATH has changed on the slave node. > > I am out of sorts on this and have researched the issue. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2730185e-009e-4ffd-991d-18a5d0618b75n%40googlegroups.com.
Slave Node PATHJ environment variable cached
The slave node PATH value was changed on the node. The Jenkins master has the old value cached. I have rebooted the slave node, restarted Jenkins, disconnected/reconnected slave node in Jenkins, deleted/recreated slave node. After all that the PATH is still cached to original value. I have confirmed that the PATH has changed on the slave node. I am out of sorts on this and have researched the issue. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/90b0cce2-d147-473a-98fe-2ef6ddb6795en%40googlegroups.com.
Re: Jenkins Test Connection with Artifactory error
Thanks, we realized on Friday that we did not need the Distribution, but needed to set up the CA Certs properly. Thanks for the response. On Friday, May 27, 2022 at 12:00:28 PM UTC-4 lesterp wrote: > Are you wanting to integrate with JFrog Pipelines (separate product), or > Artifactory? If Artifactory, you'll want to click the 'Add JFrog Platform > Instance' from your screenshot and configure/test the instance there. > > On Thursday, May 26, 2022 at 11:32:32 AM UTC-7 christop...@gmail.com > wrote: > >> We get the following error when trying to connect Jenkins to Artifactory. >> It has worked in old Jenkins Server, but with the latest version we get >> this error as follows: >> >> "Error occurred while requesting version information: Attempted read from >> closed stream." >> >> Attachment is full pic of the Plugin configuration from Jenkins. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/da85fc94-86b0-4b0c-a8c9-4e0fe41dd081n%40googlegroups.com.
