Peter Darton
Peter Darton
> rather than forcing a Jenkins admin to hard-code and then maintain a list of images, each Jenkinsfile can pick something to run Where I work, the former is preferred...
> administrator is in constant contact with project developers That's our situation - our Jenkins servers are dedicated to/owned by the developers. We're not running Jenkins as an independent service...
> I am afraid that ship has sailed. There is not anybody in charge of deciding what tools and techniques the Jenkins project should promote, so we wind up with...
> builder package Yeah, the `builder` package contains a lot of "if I were to write that today, I wouldn't do it that way" code, but doing anything to it...
My guess is that your template has an "Instance Capacity" set to 1. Try removing that setting, or increasing the number.
@erikhofer Ah, that's very useful information. Can you provide a step-by-step explanation of how to reproduce the issue? FYI Personally, I never define templates "on job level" and so I...
@erikhofer Could you do the same test, but this time make the image name different? They can both resolve to the same image, but what I want to know is...
...also, if my suspicions are confirmed, I'd be much obliged if you could grab the config.xml file from either of your jobs and paste it here. e.g. if your Jenkins...
There's insufficient information on #629 that one cannot be 100% sure. I agree it could be but, without the other half of the problem description (the cloud config) we can't...
I've just (interactively) tested the jsonUsernamePassword one and that seems to work just fine.