Re: Clearing external workspaces during build discard using Fingerprints and Workspace Cleanup plugin

Great, thank you. I was rethinking an implementation for this and I think the following may be most sensible: Scan all artifact fingerprints after a regular time interval. If an artifact has no build usage history, it is deleted. If the working directory of the artifact is left empty after this,

Re: Clearing external workspaces during build discard using Fingerprints and Workspace Cleanup plugin

There is a recent thread about this purge job history plugin: https://groups.google.com/forum/#!msg/jenkinsci-dev/OxSNmlyP1dY/PkKPxkvwDgAJ Martin On Monday, August 12, 2019 at 10:53:14 AM UTC-7, martinda wrote: > > Hi Ben, > > It is indeed expensive to run a scan of fingerprints at the end of ev

Re: Clearing external workspaces during build discard using Fingerprints and Workspace Cleanup plugin

Hi Ben, It is indeed expensive to run a scan of fingerprints at the end of every run or a project, esp. when, in the end, no workspace meets the criteria for discard. I recently found about a plugin called purge job history plugin . It loo

Re: How to get current running job name without build number?

On Mon, Aug 12, 2019 at 10:27 AM Robert Sandell wrote: > If your code is running in an http request thread, which it normally is when > a user is visiting a config page you can ask Stapler for the current ancestor > path; > > Stapler.getCurrentRequest().findAncestorObject(Job.class) Or if you a

Re: Should MessageExclusion be moved up to scm-api-plugin?

Note that for multibranch projects this is done via the `BranchBuildStrategy` API, as in `scm-trait-commit-skip-plugin`. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send

Re: How to get current running job name without build number?

If your code is running in an http request thread, which it normally is when a user is visiting a config page you can ask Stapler for the current ancestor path; Stapler.getCurrentRequest().findAncestorObject(Job.class) /B Den sön 11 aug. 2019 kl 09:57 skrev Navnath Kumbhar : > Thank you Gavin.