Using custom workspaces in jenkins

[abishekg7]

No description provided.

[abishekg7]

launch jenkins spack

[abishekg7]

launch jenkins icon

[abishekg7]

cscs-ci run

[abishekg7]

launch jenkins icon

[samkellerhals]

Looks good to me. So basically before we did not have concurrent builds and now we do as each one happens in a per build workspace? Only question I have is are the build numbers always unique, and will jenkins create these new custom workspace folders if they do not exist? Also will these folders be deleted over time, or do we need to do some sort of cleanup afterwards?

[github-actions]

Mandatory Tests

Please make sure you run these tests via comment before you merge!

• cscs-ci run
• launch jenkins spack

Optional Tests

In case your change might affect downstream icon-exclaim, please consider running

• launch jenkins icon

For more detailed information please look at CI in the EXCLAIM universe.

[abishekg7]

Looks good to me. So basically before we did not have concurrent builds and now we do as each one happens in a per build workspace? Only question I have is are the build numbers always unique, and will jenkins create these new custom workspace folders if they do not exist? Also will these folders be deleted over time, or do we need to do some sort of cleanup afterwards?

Thanks! So we did have concurrent builds before, but when we introduced spack to the build process, it started interpreting the @ in the concurrent build workspace names as a version specifier and then failed. So then we disabled concurrent builds to avoid this issue, but that slowed down our workflow. Now we are switching to underscore in the build directory, which satisfies spack at least.

And we cleanup the workspace after each build with this

post { always { archiveArtifacts artifacts: 'local_copy/spack*.txt', allowEmptyArchive: true echo 'Cleaning up workspace' deleteDir() } }

[abishekg7]

launch jenkins icon

[abishekg7]

cscs-ci run

[abishekg7]

launch jenkins spack