Jenkins clean-after-build support

[jkloetzke]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.05%. Comparing base (6d75dfb) to head (9bc1e2a).
⚠️ Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #664      +/-   ##
==========================================
+ Coverage   89.03%   89.05%   +0.02%     
==========================================
  Files          50       50              
  Lines       16137    16157      +20     
==========================================
+ Hits        14367    14389      +22     
+ Misses       1770     1768       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rhubert]

Can this be added for the local build backend as well? ;)

[jkloetzke]

Can this be added for the local build backend as well? ;)

Interesting idea. I'm not sure if this really works. On Jenkins, the result is either uploaded or stored directly in the Jenkins job. For local builds, that's instead everything below dev/dist. So it pretty much boils down to rm -rf dev/{src,build} after the build. Not sure if this is worth a new option... 🤔

[rhubert]

So it pretty much boils down to rm -rf dev/{src,build} after the build. Not sure if this is worth a new option... 🤔

In our environment we have the local build backend running in a gitlab-ci pipeline...on a cluster based system with pre allocated resources... Since we do not know and can not request enough resources for all possible build scenarios the build sometimes fails due to exceeded resource limits - mostly filesystem usage. Such an option could help us there I guess.

[jkloetzke]

I see. That makes sense. I'm afraid this will be tricky compared to the Jenkins backend. There is no internal tracking yet of which workspaces are still required during the build.

I guess in your case you only need the final package(s) and want to discard all dependencies? Or keep all dist workspaces?

[rhubert]

In the end I only need the final packages. But keeping the dist packages would also be sufficient.

This is not a very important feature - using the cache and a couple of retries is a viable workaround. It just came to my mind reading this PR 😉