After looking into Jenkins' slave system a bit more, I think this would need to have access to the Docker container to run slave.jar. That would mean that any Docker images people want to execute on would have to have a JVM in a reasonably well-defined location. Adding slave.jar in the pipeline code with docker cp could work with that, so there wouldn't be too many restrictions on image selection. Nicolas, do you think some of the one-shot executor logic could be reused for this, or is it more targeted at a standard build?
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e40f7513-1c72-4850-8026-dae073b2f978%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
