On Mon, Feb 18, 2019 at 4:08 AM Oliver Gondža <[email protected]> wrote: > Can you be more specific on the use-case here? As I understand, you > suggest to use container as a per-test fixture (ala docker-fixtures) and > running Jenkins _inside_ of the container.
Yes. I think there are potentially a lot of use cases here, but to take one example from my personal experience with the `mercurial` plugin: while I can and do use `docker-fixtures` to run tests in which an _agent_ runs in a specific image (where particular versions of Python and Mercurial are installed), the situation is currently hopeless when the test is exercising code whereby the _master_ needs to run `hg` commands (for example: form validation or branch indexing). These tests are currently written to just use whatever copy of Mercurial happens to be installed on the computer running `mvn test`, or to mark the test skipped if there is none (very likely in CI). Besides making external tools / commands available to the Jenkins process, a harness like this could be used to reproduce bugs affecting a particular JVM, servlet container, filesystem layout, or other details of the (Linux) platform. -- 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/CANfRfr17zaZS_ma_OG4XtWbe0TZOeL-9E20595n1JxAbfWaSpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
