Re: One-Shot Executors

we want to distinguish error due to job misconfiguration (bad docker image ID for sample) and infrastructure issue (no available resources) 2016-03-10 19:58 GMT+01:00 Suckow, Thomas J : > > > On 3/9/16, 12:40 PM, "jenkinsci-dev@googlegroups.com on behalf of Jesse > Glick"

OT - was Re: One-Shot Executors

> 20-30 jobs all trying to get a cut of the pie. > > From: <jenkin...@googlegroups.com > on behalf of nicolas de > loof <nicolas...@gmail.com > > Reply-To: "jenkin...@googlegroups.com " < > jenkin...@googlegroups.com > > Date: Thursday, March 10, 2

Re: One-Shot Executors

v@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" <jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>> Date: Thursday, March 10, 2016 at 1:46 AM To: "jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" <jenkinsci-d

Re: One-Shot Executors

On 3/9/16, 12:40 PM, "jenkinsci-dev@googlegroups.com on behalf of Jesse Glick" wrote: > >Or just fail the build and the next one should work. I just don't want to have to kick builds when a normal slave would "just wait". Our

Re: One-Shot Executors

please see https://github.com/jenkinsci/one-shot-executor-plugin/commit/86c632091391e3204432a8c7d1a18bb48b3a66e3 basically, this on let the provisionner keep a task in the Queue when it can determine it hasn't enough resources to run extra slaves. this can be used to prevent overload, or allocate

Re: One-Shot Executors

" I do agree that certain issues should fail immediately (image not found). Certain other issues should perform exponential backoff (Cloud infrastructure down). Provisioning limits could be annoying though, would be interesting if they could be left in the queue until Jenkins side provisioning

Re: One-Shot Executors

On Wed, Mar 9, 2016 at 11:52 AM, Suckow, Thomas J wrote: > Certain other issues should perform exponential backoff (Cloud > infrastructure down). Or just fail the build and the next one should work. > It could also handle the logic of some users wanting to configure

Re: One-Shot Executors

;mailto:jenkinsci-dev@googlegroups.com>> > Date: Friday, March 4, 2016 at 3:08 AM > To: "jenkinsci-dev@googlegroups.com <mailto:jenkinsci-dev@googlegroups.com>" > <jenkinsci-dev@googlegroups.com <mailto:jenkinsci-dev@googlegroups.com>> > Subject: One-Shot Executors &

Re: One-Shot Executors

> Date: Friday, March 4, 2016 at 3:08 AM To: "jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" <jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>> Subject: One-Shot Executors Hi folks, Yoann and I have extracted from ou

Re: One-Shot Executors

Yes, was me. I never will get used with your "style". You claim you don't work on a plugin, you even create another one, and now complain you've been removed from the plugin admin team ? Feel free to report this "abuse" to board if this is such a disturbance for you, I'm sure someone will find the

Re: One-Shot Executors

Ok, offtopic should die, i sent email to board, i will get explanations and description from board. For cloud faster provisioning stephenc replied that will look at possible ways on Monday. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: One-Shot Executors

Was it you? I still answering in PRs and issues. @magnayan is also not actively maintaining it, would you also remove it? If it was you (the person that never worked on this plugin) then i would be glad to see the list of plugins what you maintain and ensure that you also removed from all

Re: One-Shot Executors

*you* just said you aren't working anymore on this plugin. So why complain ? 2016-03-05 16:31 GMT+01:00 Kanstantsin Shautsou : > `You've been removed from the Jenkins team docker-plugin Developers` > Thanks to anonymous person, removing person from team would be a

Re: One-Shot Executors

`You've been removed from the Jenkins team docker-plugin Developers` Thanks to anonymous person, removing person from team would be a great benefit to this plugin! ;) That a bit offtop, please continue with the initial topic. On Saturday, March 5, 2016 at 11:47:09 AM UTC+3, Kanstantsin Shautsou

Re: One-Shot Executors

> On Mar 5, 2016, at 11:15, nicolas de loof wrote: > > > > 2016-03-05 7:36 GMT+01:00 Kanstantsin Shautsou >: > I made my plugin after @stephenc comments and seems that his work somebody > finally tried

Re: One-Shot Executors

2016-03-05 7:36 GMT+01:00 Kanstantsin Shautsou : > I made my plugin after @stephenc comments and seems that his work somebody > finally tried to expose > https://github.com/jenkinsci/mansion-cloud-plugin/pull/9 According to > stephenc comments such logic should be

Re: One-Shot Executors

I made my plugin after @stephenc comments and seems that his work somebody finally tried to expose https://github.com/jenkinsci/mansion-cloud-plugin/pull/9 According to stephenc comments such logic should be generic and would make

Re: One-Shot Executors

2016-03-04 21:14 GMT+01:00 Kanstantsin Shautsou : > Cloud delays in theory should be possible to avoid by: > 1) kicking suggestReview. I wrote plugin but had no ability to test on > huge installations > https://github.com/KostyaSha/faster-node-provision-plugin > 2)

Re: One-Shot Executors

Cloud delays in theory should be possible to avoid by: 1) kicking suggestReview. I wrote plugin but had no ability to test on huge installations https://github.com/KostyaSha/faster-node-provision-plugin 2) increasing one of coefficients for provisioner(or statistics collector, forgot classname)

Re: One-Shot Executors

There was actually an extra + sign on URL that broke the link 2016-03-04 17:25 GMT+01:00 Kanstantsin Shautsou : > This is called cached. Everybody who uses jenkins jira hits this issue > always. > > On Friday, March 4, 2016 at 3:41:47 PM UTC+3, nicolas de loof wrote:

Re: One-Shot Executors

This is called cached. Everybody who uses jenkins jira hits this issue always. On Friday, March 4, 2016 at 3:41:47 PM UTC+3, nicolas de loof wrote: > > Dominik edited the wiki page to fix a typo and now it is not available as > https://wiki.jenkins-ci.org/display/JENKINS/One-Shot+Executor

Re: One-Shot Executors

Dominik edited the wiki page to fix a typo and now it is not available as https://wiki.jenkins-ci.org/display/JENKINS/One-Shot+Executor anymore, but still there https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=96075993 Can a Confluence expert can explain this ? 2016-03-04 12:08 GMT+01:00

One-Shot Executors

Hi folks, Yoann and I have extracted from our docker-slaves hack-ish pet project a stable sub-component so a plugin can manage slaves that are dedicated to a Build, not relying on Cloud API, and get them tied to a Build. i.e Slave and Build share a common lifecycle. If Slave fails to start, Build