Hi,
from what I know, it's not achievable. When a job is waiting for a downstream to complete, it keeps an executor occupied. So, the downstream job needs to run on a different executor.
But, frankly, that seems more of https://xyproblem.info/ :-)
So, what is your problem? what do you need?
Cheers,
Gianluca.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAD0fyGieWSsj%3DmAtLQEyuOkn0h5Y_q%2BGpf1oEZ%3DMKYfYS20mEw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/60c42944-94fb-b406-65d2-e5f905e81af6%40gmail.com.
Hi,
From what I know, a job will keep an executor busy till it completes.
Hence, if an upstream job needs to do something after a downstream completes, then Jenkins needs two executors.
Otherwise, if an upstream job doesn't need to anything after a downstream completes, then you trigger a downstream with wait options set to false and if there is only one executor Jenkins will queue the downstream job till the upstream completes and the executor will be free to run something else.
Is it clear?
Also, "waiting for something" even though doesn't need much CPU
still needs some processing power, hence you need an executor,
hence is not occupied unnecessarily ... it's occupied to do what
you asked for: "wait for something" ;-)
Hope that helps.
Cheers,
Gianluca.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAD0fyGiVtQ5p%3DZGdNwaFTPXE6XJxVuEUvkXiJgv%3DF4hAGvb0vA%40mail.gmail.com.