parameterized-trigger-plugin update 2.35.2 -> 2.36 not starting jobs in postbuild

2020-05-12 Thread Michael Augustin
Hi reader, I use the parameterized-trigger-plugin to trigger other jobs as post-build actions in a Template-job using the template-project-plugin in version 1.5.2 . This was working fine since months. My setup with many jobs like JOB1 using a common build-configuration from a Template job. JO

Re: How to cleanup workspace built from docker

2020-05-12 Thread Den
If I omit -u root then jenkins uses 'docker run -t -d -u 993:990 -v $HOME/.m2:/root/.m2' command to run the image. That works, but it will download all dependencies every time. When using root user, the repository is mounted and maven uses already downloaded dependencies. Am Dienstag, 12. Mai 2

Re: How to cleanup workspace built from docker

2020-05-12 Thread Den
And how to mount .m2 directory then? Currently I do: args '-u root -v $HOME/.m2:/root/.m2' Am Dienstag, 12. Mai 2020 10:21:52 UTC+2 schrieb Gianluca: > > The best solution is not run any command as root inside docker. > Use the environment variables UID and GID and run the docker with a user > c

Re: How to cleanup workspace built from docker

2020-05-12 Thread Gianluca
The best solution is not run any command as root inside docker. Use the environment variables UID and GID and run the docker with a user corresponding to the UID and GIU; something like "--user $UID:$GID" instead of root On Tuesday, 12 May 2020 08:51:43 UTC+1, Den wrote: > > Hi, > > I'm buildi

Re: Jenkins not starting

2020-05-12 Thread Mai Waly
This is a duplicate issue, already a post open. On Tuesday, May 12, 2020 at 5:45:33 AM UTC+2, Mai Waly wrote: > > Hi All, > > > > Please advise what happen as Jenkins is no longer starting and showing > error, there is no gui any more. > > > ay 10, 2020 7:48:13 AM hudson.util.BootFailure publis

How to cleanup workspace built from docker

2020-05-12 Thread Den
Hi, I'm building artifacts in docker image and if I'm aborting a build, the deleteDir function fails to delete artifacts since they were created with root user in docker and the function is called by jenkins user outside of docker. Is there any workaround? pipeline { agent {label 'docker'}