anton kropp added a comment - 2015-07-08 21:52 +1

Yuri Govorushchenko added a comment - 2017-12-28 22:44 - edited Is there any workaround? My shell scripts wrapped by insideImage create several root -owned folders (e.g. node-modules/ ) in the workspace and jenkins user is not able to clean them on the next build via git clean .

Mark Waite added a comment - 2017-12-28 23:00 One alternative might be to configure docker so that it runs as the same user that is running the agent. It should then create the files as that user, rather than creating them as root. Otherwise, you could create some form of separate program (script, compiled executable, etc.) which is called before the SCM checkout and cleans the directory as root.

Yuri Govorushchenko added a comment - 2017-12-29 06:07 - edited Thank you for the suggestions! One alternative might be to configure docker so that it runs as the same user that is running the agent. It should then create the files as that user, rather than creating them as root. Unfortunately I have to run docker container with `-u root` explicitly because I had some problems due to JENKINS-38438 . Otherwise, you could create some form of separate program (script, compiled executable, etc.) which is called before the SCM checkout and cleans the directory as root. But I suppose the script will be still run by jenkins user so it cannot act as root ? I ended up adding jenkins user to sudoers and calling my command with sudo explicitly: sudo git clean . For future reference these are the steps to make jenkins a sudoer: sudo -u root bash (login as root) EDITOR=nano visudo (edit sudoers using nano editor instead of default vi) Add these lines and exit (Ctrl+x, y): ## CUSTOM: allow jenkins user to sudo without password jenkins ALL=(ALL) NOPASSWD: ALL

Yuri Govorushchenko added a comment - 2017-12-30 02:00 Another workaround (that doesn't require making jenkins a sudoer) is to clean the workspace inside the image: // Given arbitrary string returns a strongly escaped shell string literal. // I.e. it will be in single quotes which turns off interpolation of $(...), etc. // E.g.: 1 '2\3\' 4 5 "6 (groovy string) -> '1' \ ''2\3\' \ ''4 5" 6' (groovy string which can be safely pasted into shell command). // Pretty much a HACK: track https://issues.jenkins-ci.org/browse/JENKINS-44231. def shellString(s) { // Replace ' with ' \ '' (https://unix.stackexchange.com/a/187654/260156). Then enclose with ' ...'. // 1) Why not replace \ with \\? Because '...' does not treat backslashes in a special way. // 2) And why not use ANSI-C quoting? I.e. we could replace ' with \' // and enclose using $ '...' (https://stackoverflow.com/a/8254156/4839573). // Because ANSI-C quoting is not yet supported by Dash ( default shell in Ubuntu & Debian) (https://unix.stackexchange.com/a/371873). '\' ' + s.replace(' \ '', ' \ '\\\' \ '') + ' \'' } // ... node { stage( 'Checkout' ) { checkout(scm) } def pathsToClean = sh(returnStdout: true , script: 'git clean -fdx --dry-run --exclude node_modules | sed "s/Would remove //" ' ).split( '\n' ) // ... myImage.inside( "..." ) { stage( 'Git Clean' ) { // We don't call `git clean ...` here directly // because it requires injecting SCM credentials into the image which is cumbersome. pathsToClean.each { sh( 'rm -rf ' + shellString(it)) } } // ... } }

pata nouk added a comment - 2018-04-19 07:55 - edited Same problem here. A quick and dirty fix I found was to do this:   pipeline {     ...     post {        always {         sh "chmod -R 777 ."            cleanWs() } } }   It allows anyone to modify workspace files so that Jenkins can clean it.