Re: Workspace clean-up killed jobs
This issue is related: https://issues.jenkins-ci.org/browse/JENKINS-27329
Regards
David
On Thursday, May 2, 2019 at 9:11:53 AM UTC+1, Sarfroz Basha wrote:
>
> Hi,
>
> I am also facing same error. Have you found anything regarding this error.
> Please share the solution.
>
> Regards,
> Sarfroz
>
> On Monday, November 27, 2017 at 2:16:04 PM UTC+5:30, David Aldrich wrote:
>
>> Hi
>>
>>
>>
>> Two of our declarative script jobs have failed for similar reasons. The
>> jobs normally run with no problem. We are running Jenkins 2.91.
>>
>>
>>
>> The jobs take several hours to complete. Each one failed part way
>> through and gave the following message in its console log:
>>
>>
>>
>> ERROR: missing workspace /data/hudsonuser/workspace/_trunk on
>>
>>
>>
>>
>> The Jenkins system log shows this message that is coincident with the
>> failure:
>>
>>
>>
>> Nov 26, 2017 9:04:34 PM INFO hudson.model.AsyncPeriodicWork$1 run
>>
>> Started Workspace clean-up
>>
>> Nov 26, 2017 9:04:50 PM WARNING jenkins.branch.WorkspaceLocatorImpl locate
>>
>> JENKINS-34564 path sanitization ineffective when using legacy Workspace Root
>> Directory ‘${ITEM_ROOTDIR}/workspace’; switch to
>> ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} as in JENKINS-8446 / JENKINS-21942
>>
>>
>>
>> What is going on here and how should I fix it?
>>
>>
>>
>> Best regards
>>
>>
>>
>> David
>>
>>
>>
>
--
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/f76b2a6a-0eff-4d0a-ad60-d8063f91a022%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Workspace clean-up killed jobs
Hi,
I am also facing same error. Have you found anything regarding this error.
Please share the solution.
Regards,
Sarfroz
On Monday, November 27, 2017 at 2:16:04 PM UTC+5:30, David Aldrich wrote:
> Hi
>
>
>
> Two of our declarative script jobs have failed for similar reasons. The
> jobs normally run with no problem. We are running Jenkins 2.91.
>
>
>
> The jobs take several hours to complete. Each one failed part way through
> and gave the following message in its console log:
>
>
>
> ERROR: missing workspace /data/hudsonuser/workspace/_trunk on
>
>
>
>
> The Jenkins system log shows this message that is coincident with the
> failure:
>
>
>
> Nov 26, 2017 9:04:34 PM INFO hudson.model.AsyncPeriodicWork$1 run
>
> Started Workspace clean-up
>
> Nov 26, 2017 9:04:50 PM WARNING jenkins.branch.WorkspaceLocatorImpl locate
>
> JENKINS-34564 path sanitization ineffective when using legacy Workspace Root
> Directory ‘${ITEM_ROOTDIR}/workspace’; switch to
> ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} as in JENKINS-8446 / JENKINS-21942
>
>
>
> What is going on here and how should I fix it?
>
>
>
> Best regards
>
>
>
> David
>
>
>
--
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/5f79a2af-b066-49c5-8e24-39a2eb500a35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Workspace clean-up killed jobs
Hi
Two of our declarative script jobs have failed for similar reasons. The jobs
normally run with no problem. We are running Jenkins 2.91.
The jobs take several hours to complete. Each one failed part way through and
gave the following message in its console log:
ERROR: missing workspace /data/hudsonuser/workspace/_trunk on
The Jenkins system log shows this message that is coincident with the failure:
Nov 26, 2017 9:04:34 PM INFO hudson.model.AsyncPeriodicWork$1 run
Started Workspace clean-up
Nov 26, 2017 9:04:50 PM WARNING jenkins.branch.WorkspaceLocatorImpl locate
JENKINS-34564 path sanitization ineffective when using legacy Workspace Root
Directory '${ITEM_ROOTDIR}/workspace'; switch to
${JENKINS_HOME}/workspace/${ITEM_FULLNAME} as in JENKINS-8446 / JENKINS-21942
What is going on here and how should I fix it?
Best regards
David
--
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/0a9be99daffe43d2b1b3a84c2b1191f4%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.
