Prohibit Jenkins from creating @temp directory

Is there a way to prohibit Jenkins from using @temp directories for artifacts, or avoid deleting them at the end of the build? -- 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,

workflow Jira -> Jenkins

Hello all, I am drafting a high-level workflow diagram that shows how to achieve a “more software development” oriented version of CI/CD. My goal is to show the interoperability between Jira, Jenkins, GitHub, AWX , F5, etc. How JIRA approvals will play a part in the process, how we recommend

Blue Ocean Status Update

There has been some confusion for a while about the status of Blue Ocean. As the product manager for Jenkins at CloudBees I would like to provide an update on CloudBees point of view with regards to the status of Blue Ocean. CloudBees Point of View Jenkins is not going anywhere and it needs a

Re: several issues

Thanks a lot to all who've replied, this mailing list rocks! I'll try to summarize: I've asked here, because the wiki page "How to report an issue" tells me "The Jenkins JIRA is not a support site. If you need assistance or have general questions, visit us in chat ,

Re: Blue Ocean Status Update

Thank you Peter for your feedback. I don't expect subversion support to be added to Blue Ocean, but once you switch to Git it will hopefully be a useful addition to you On Thursday, November 28, 2019 at 3:54:44 AM UTC+1, Peter wrote: > > Followed the blue ocean attempt for some time, but

Re: Help with configuration of Jenkins

Hi, I was able to fix the issue. the home directory of the user, as 777, I got the clue from one of the logs in /var/log/messages; /var/log/audit/audit.log. thank you, ./Antonio/. On Wednesday, November 27, 2019 at 4:48:37 PM UTC-6, Antonio Prado wrote: > Hi, > > > > I am having

Re: upgrade jenkins from 1.6 to 2.206

Going from 1.6 to 2.206 is not really a good idea. That is several years difference. On Wed, Nov 27, 2019, 15:48 Antonio Prado wrote: > Can you please tell me, if for me to upgrade from one version to another, > all I have to do is, > download the war file, > place it in the same location as

Re: upgrade jenkins from 1.6 to 2.206

Do you have a lot of configuration in your 1.6 install? If not, it might be best to start fresh and recreate things. If you do, it might be best to go to 2.0 first and then upgrade, or maybe some other intermediate steps along the way. I'm not sure there is a current recommended approach to moving

Re: Blue Ocean Status Update

Followed the blue ocean attempt for some time, but missing support for subversion makes it impossible to integrate in our environment (until we'll switch to git). Cool stuff, anyways. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To

upgrade jenkins from 1.6 to 2.206

Can you please tell me, if for me to upgrade from one version to another, all I have to do is, download the war file, place it in the same location as previously, restart Jenkins? I did do this process, however, it keeps on creating a new directory (you can see in the configuration form).

Help with configuration of Jenkins

Hi, I am having difficulties on setting up ssh servers under Jenkins (1.6) on Redhat 5.9. We have plans on moving out of these older version, but for now it is what I have to work with it. Under: Jenkins -> Manage Jenkins -> Configure System Under the configure ssh server section:

Re: durable-dbed1d4d/script.sh: Syntax error: "(" unexpected

Hello Daniel, what do you mean by "shopt -s extglob" I don´t understand. El miércoles, 27 de noviembre de 2019, 12:13:35 (UTC+1), Daniel Beck escribió: > > Assuming bash as the default shell, you did not call `shopt -s extglob`, > so `!(pattern)` is unsupported. > > Unrelated to Jenkins. > >

Re: upgrade jenkins from 1.6 to 2.206

any guideline on this upgrade? from example, going from 1.6 to 2.0 first then 2.0 to 2.206? or any other step in between? thank you, ./Antonio/. On Wednesday, November 27, 2019 at 7:03:38 PM UTC-6, slide wrote: > Going from 1.6 to 2.206 is not really a good idea. That is several years >

Jenkins version 2.168 cannot install Pipeline plug

Thank you very much for checking, this is my current question. I use jenkins to package the same piece of code, but I found that because of using different Jenkins, the packaged code will have circular dependencies. So I wanted to reduce the jenkins version to 2.168, but found that the