> > - *Issue* - the container is left behind...is there anyway to automate > removal of the containers from within Jenkins? > > > It should be removed when the jenkins build itself is removed.
> The next issues I have are: > > - How to mount the workspace into the container. > - The issue I'm having here is that we start X slaves, so if I > mount the Jenkins master workspace onto the slave. Each slave will end > up > pointing to the same folder on the host trampling all over each other > - Another issue here is, the project uses Gradle so it would be > nice to attempt to reload/retain the gradle wrapper and dependency > caches. > - Extract build results (JUnit etc) > - By solving the issue above this could be resolved > > > Don't mount the workspace into the container, have the build check out the scm in its own isolated sandbox. JUnit reporting, just use standard jenkins plugins. If you want to optimise build times, create a docker image to use as a jenkins slave with caches pre-populated. > So I guess summed up my question is, how should the file system be managed > when using Docker containers as Jenkins Slaves? Any thoughts or how youve > implemented things would be great. > > > -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPYP83R6F%3DKcj%3D0RecRQBH-ksG0M9o%3D8enzZewGKeaPCYVs_yw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
