Trivial SEE COMMENTS (Looking for a CauseOfBlockage that will cause Jenkins to automatically ask the cloud for a new machine or another slave to accept a job because the currently assigned slave will not be available for that job.)
I am enhancing the vsphere-cloud-plugin to work with slave templates so that the vSphereCloud can provision new slaves.
In my first release I am going to have a newly provisioned slave run the jobs until the limited run limit is reached (right now 1 job execution) then it will be unprovisioned.
When only working with 1 job this works perfectly. When I introduce a 2nd job then the newly provisioned slave is created, job 1 of 2 is executed, the slave is unprovisioned, another slave is provisioned, job 2 of 2 is executed, and the slave is unprovisioned.
What I am expecting to see here is when (and yes I would have to implement a method that would control this which I can't find or doesn't exist) job 2 comes in and 1) the computer (or slave) tells jenkins it cannot handle the job (I tried canTake and reported all types of CauseOfBlockage) and 2) the cloud tells jenkins it can provision.
I am wondering what I can do here. I would like the availability to notify jenkins that a slave/computer can handle a newly launched job request (even amongst the jobs already waiting to be ran)
[JENKINS-30203] When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution
| Component/s | New: vsphere-cloud-plugin [ 16104 ] | |
| Component/s | Original: ci [ 18920 ] | |
| Key |
Original:
|
New:
|
| Workflow | Original: classic default workflow [ 165294 ] | New: JNJira [ 165294 ] |
| Project | Original: Infrastructure [ 10301 ] | New: Jenkins [ 10172 ] |
| Assignee | Original: R. Tyler Croy [ rtyler ] |
| Summary | Original: Jobs assigned to a cloud slave (once provisioned) but the cloud will only be able to handle a sub-set of those job. The cloud should be able to provision a new slave to handle the remaining jobs needing execution | New: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution |
| Description |
Original:
I am enhancing the vsphere-cloud-plugin to work with slave templates so that the vSphereCloud can provision new slaves. In my first release I am going to have a newly provisioned slave run the jobs until the limited run limit is reached (right now 1 job execution) then it will be unprovisioned. When only working with 1 job this works perfectly. When I introduce a 2nd job then the newly provisioned slave is created, job 1 of 2 is executed, the slave is unprovisioned, another slave is provisioned, job 2 of 2 is executed, and the slave is unprovisioned. What I am expecting to see here is when (and yes I would have to implement a method that would control this which I can't find or doesn't exist) job 2 comes in and 1) the computer (or slave) tells jenkins it cannot handle the job (I tried canTake and reported all types of CauseOfBlockage) and 2) the cloud tells jenkins it can provision. I am wondering what I can do here. I would like the availability to notify jenkins that a slave/computer can handle a newly launched job request (even amongst the jobs already waiting to be ran) |
New:
SEE COMMENTS (Looking for a CauseOfBlockage that will cause Jenkins to automatically ask the cloud for a new machine or another slave to accept a job because the currently assigned slave will not be available for that job.) I am enhancing the vsphere-cloud-plugin to work with slave templates so that the vSphereCloud can provision new slaves. In my first release I am going to have a newly provisioned slave run the jobs until the limited run limit is reached (right now 1 job execution) then it will be unprovisioned. When only working with 1 job this works perfectly. When I introduce a 2nd job then the newly provisioned slave is created, job 1 of 2 is executed, the slave is unprovisioned, another slave is provisioned, job 2 of 2 is executed, and the slave is unprovisioned. What I am expecting to see here is when (and yes I would have to implement a method that would control this which I can't find or doesn't exist) job 2 comes in and 1) the computer (or slave) tells jenkins it cannot handle the job (I tried canTake and reported all types of CauseOfBlockage) and 2) the cloud tells jenkins it can provision. I am wondering what I can do here. I would like the availability to notify jenkins that a slave/computer can handle a newly launched job request (even amongst the jobs already waiting to be ran) |
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
| Priority | Original: Major [ 3 ] | New: Trivial [ 5 ] |
| Workflow | Original: JNJira [ 165295 ] | New: JNJira + In-Review [ 181917 ] |
pjdarton
made changes -
| Assignee | New: pjdarton [ pjdarton ] |
pjdarton
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
