On Tuesday, December 19, 2017 at 2:10:36 PM UTC+1, Reinhold Füreder wrote:
>
> Hi Vincent,
>
>
>
> does it work most of the times? If so, could it be related to
> https://issues.jenkins-ci.org/browse/JENKINS-27329
> <https://www.google.com/url?q=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-27329&sa=D&sntz=1&usg=AFQjCNEjbyK7RmdnoA-1cwWTE19530X3hw>
>
> “WorkspaceCleanupThread may delete workspaces of running jobs”?
>
Indeed it works most of the time and the problem only happens from time to
time. The issue you reference could well be the cause, thanks for pointing
it (I'll try to workaround mentioned in it).
Thanks
-Vincent
>
>
> HTH Reinhold
>
>
>
> *From:* jenkins...@googlegroups.com <javascript:> [mailto:
> jenkins...@googlegroups.com <javascript:>] *On Behalf Of *Vincent Massol
> *Sent:* Dienstag, 19. Dezember 2017 14:07
> *To:* Jenkins Users <jenkins...@googlegroups.com <javascript:>>
> *Subject:* Re: "ERROR: missing workspace" and chaining builds
>
>
>
> Could it be that the workspace is deleted once the node() ends and that it
> happens that some other node() calls happen to run on the same node and
> that Jenkins would allocate a workspace only once per job? That would be
> strange though.
>
>
>
> Thanks
>
> -Vincent
>
>
> On Tuesday, December 19, 2017 at 2:01:32 PM UTC+1, Vincent Massol wrote:
>
> Hi guys,
>
>
>
> I regularly get the following errors in our Jenkins pipeline on XWiki:
>
>
>
> ERROR: missing workspace /home/hudsonagent/jenkins_root/workspace/
> XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA
>
> on agent-2-1
>
>
>
> [main] Caused by: java.io.IOException: /home/hudsonagent/jenkins_root/
> workspace/XWiki_xwiki-platform_master-
> ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA/xwiki-platform-core/
> xwiki-platform-flamingo/xwiki-platform-flamingo-themes/xwiki-platform-
> flamingo-theme-test/xwiki-platform-flamingo-theme-test-tests/target/xwiki
> doesn't exist.
>
>
> Our Jenkins file does this:
>
>
>
> stage ('Platform Builds') {
> parallel(
> 'main': {
> build(
> name: 'Main',
> goals: 'clean deploy',
> profiles: 'legacy,integration-tests,office-tests,snapshotModules',
> properties: '-Dxwiki.checkstyle.skip=true
> -Dxwiki.surefire.captureconsole.skip=true -Dxwiki.revapi.skip=true'
> )
> build(
> name: 'Distribution',
> goals: 'clean deploy',
> profiles: 'legacy,integration-tests,office-tests,snapshotModules',
> pom: 'xwiki-platform-distribution/pom.xml'
> )
> build(), ...
> }, ...
>
>
>
> (Full file here:
> https://github.com/xwiki/xwiki-platform/blob/40cf4cf65e73728d53ee30ffcabd1534640dc9c5/Jenkinsfile#L26
>
> )
>
>
>
> And build() is running Maven on a node() (xwikiBuild() is pipeline library
> running Maven):
>
>
>
> def build(map)
> {
> node {
> xwikiBuild(map.name) {
> ...
> }
>
> }
> }
>
>
> In this situation, do you see any reason for Jenkins to delete a workspace
> on "main" and a reason for each node() call to not request a new workspace?
> So in short I guess I'm asking for some clarification on when workspaces
> are initialized.
>
>
>
> Thanks!
>
> -Vincent
>
>
>
>
>
> --
> 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-use...@googlegroups.com <javascript:>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e9c23914-c1cc-43db-86b2-e30c06d70583%40googlegroups.com
>
> <https://groups.google.com/d/msgid/jenkinsci-users/e9c23914-c1cc-43db-86b2-e30c06d70583%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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/bb9aaa32-c83e-4f87-9e08-c1a725bf806d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
