Hi,
so what is happening:
1. Jenkins starts up a docker container.
2. It connects as jenkins user
3. In your case, you try to create a workspace +aux. dirs on / (root
level) as this user.
While the real workspace is bind-mounted, jenkins attempts to create the
aux.dir loca
Is it possible to use absolute paths for the workspace at the time the
docker container is being created/run with declarative pipeline? I have
done this before with mesos docker cloud, but I am hoping to replicate that
ability locally, without having a mesos cluster on my localhost.
An example
On Sun, Mar 18, 2018 at 5:40 PM Sean Talts wrote:
> Thank you both! I particularly like the idea of just deleting before the
> job instead of after. I managed to get something else working too, though I
> think it could be masking the problem. I now run attrib -r -s /s /d before
> deleting (befor
Thank you both! I particularly like the idea of just deleting before the
job instead of after. I managed to get something else working too, though I
think it could be masking the problem. I now run attrib -r -s /s /d before
deleting (before the run and after, just in case). Seems to be pretty qu
In a declarative pipeline's Jenkinsfile it is possible to add a timeout
option both global as well as override it per stage. E.g.:
stage ("SonarQube analysis") {
options {
timeout(time: 5, unit: 'MINUTES')
}
steps {
script {
STAGE_NAME = "SonarQube analysis"
withSon
