Re: improving WorkspaceCleanupThread in a multi-branch world

> On 11.05.2016, at 13:38, Michael Neale wrote: > > Is it worth exploring smarter heuristics, or is the real solution to have an > alternative workspace cleaner that multibranch plugins include, that cleanup > any workspaces on the event of a branch (job) removal? (not

Re: improving WorkspaceCleanupThread in a multi-branch world

On Wednesday, May 11, 2016 at 10:05:28 PM UTC+10, Daniel Beck wrote: > > > > WorkspaceCleanupThread should be moved into a plugin, and from there it > can be grown, be made configurable and/or get siblings. There are probably > already issues in Jira related to all that. > > For things like

improving WorkspaceCleanupThread in a multi-branch world

One thing I have come across with using multibranch pipeline (with github, BTW) is that it generates a LOT of noise in a agent's workspace. The WorkspaceCleanupThread runs periodically to cleanup things, but will only remove workspaces on an agent (slave) machine that haven't been used in a

Re: improving WorkspaceCleanupThread in a multi-branch world

On 05/11/2016 02:05 PM, Daniel Beck wrote: On 11.05.2016, at 13:38, Michael Neale wrote: Is it worth exploring smarter heuristics, or is the real solution to have an alternative workspace cleaner that multibranch plugins include, that cleanup any workspaces on the

About a Jenkins Plugin for my java project(Framework)

Hello, I've just finished the development a framework of IHM automation testing(i used java like programming language and selenuim webdriver,cucumber), so i would that users can use this framework through jenkins. so i would know how can i make my own plugin for this framework. Best

Re: [GSOC 2016] Support core plugin improvements

Hi, Could you please let me know a way to find an actual UI component which is referring to the jelly file [1] and the Java class[2]. Then I can study and understand the implementation well through remote debugging. [1]

Re: [GSOC 2016] Support core plugin improvements

You can find usages of it in Jenkins core with https://github.com/jenkinsci/jenkins/search?utf8=✓=DirectoryBrowserSupport Thus if we take the usecase of displaying the job workspace the main code is here

Re: [GSOC 2016] Support core plugin improvements

Thanks a lot Steve. I am OK with anytime on Saturday and Sunday. -- 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 an email to

Re: [GSOC 2016] Support core plugin improvements

I will try to be available but it is often less easy for me the WE with my kids If it's not between midnight and 9AM my time I could try to join On Wed, May 11, 2016 at 10:18 PM, Minudika Malshan wrote: > Thanks a lot Steve. I am OK with anytime on Saturday and Sunday. >

About Jenkins Plugin for my own java project(Framework)

Hello, I've just finished the development a framework of IHM automation testing(i used java like programming language and selenuim webdriver,cucumber), so i would that users can use this framework through jenkins. so i would know how can i make my -- You received this message because you

Re: improving WorkspaceCleanupThread in a multi-branch world

On Wed, May 11, 2016 at 8:30 AM, Oliver Gondža wrote: > There is no easy way to map workspace directory to Job(s) that used that No, but you can easily map `Job` to a workspace on a given `Node`. So when a job is deleted, it should be possible to immediately scan all currently

Re: Forcing Pipeline "node" blocks to run on the same agent/in the same workspace?

Hello, As part of the Google Summer of Code 2016, I will be working on a plugin called External Workspace Manager. The basic idea of this plugin is to be able to provide the same workspace for multiple jobs. For example you would have an upstream job that will run a job on a defined workspace,

Re: Forcing Pipeline "node" blocks to run on the same agent/in the same workspace?

Yes, in my case I have the same groovy script used in different jobs, and each job specifies a specific BUILD_NODE via the Node label parameter plugin. -- Craig On Monday, May 9, 2016, Michael Neale wrote: > Craig, does that mean that you have a label specific for each