Sam Gleske

Results 397 comments of Sam Gleske

@goffinf here's the new build -> https://github.com/samrocketman/yet-another-docker-plugin/releases/tag/0.1.0-rc38-samrocketman-rc1 You can enable a logger for `com.github.kostyasha.yad.DockerProvisioningStrategy` to see additional debug output for the strategy being used.

I've experienced this with 20+ configured slaves as well. Each image is tracked separately if it's in a different DockerCloud.

![image](https://user-images.githubusercontent.com/875669/39234440-1b131cd8-4828-11e8-9562-20a9f36e943c.png) Using Linux containers... This works for me by configuring the `Different jenkins master URL` under the Launch method of yet another docker plugin cloud settings in the Jenkins global...

Need more system information. - Linux distro and version. - Docker daemon version.

https://vmware.github.io/vic-product/assets/files/html/1.1/vic_app_dev/container_operations.html vsphere does not appear to be a full implementation of the remote docker API. If you manually delete a single offline agent does the container get removed on the...

@saibalak80 as a temporary workaround you can create a regularly scheduled freestyle job which cleans up dead agents. You would need the groovy plugin installed and run the following system...

I don't experience this when using Docker daemon so it might be a difference with how vsphere containers work compared to Docker.

Except: https://github.com/KostyaSha/yet-another-docker-plugin/blob/80c991f821c3a68354e8c744c9fd876810f88e28/yet-another-docker-plugin/src/main/resources/com/github/kostyasha/yad/launcher/DockerComputerJNLPLauncher/init.sh#L103 Running `su - ...` will create a clean environment discarding any customization Jenkins would make from the environment or path side.

Correct, I mean before executing slave.jar. A desired scenario is to run the same version of Jenkins as the master across different platforms.

https://github.com/KostyaSha/yet-another-docker-plugin/blob/98ecf0a17ccbab6ba6913bdb82f97f6de54fb0bb/yet-another-docker-plugin/src/main/java/com/github/kostyasha/yad/launcher/DockerComputerSingleJNLPLauncher.java#L247-L257 We could take advantage of [`${parameter:-word}` bash parameter expansion][1]. For example, in `DockerComputerSingleJNLPLauncher.java` you could add to `config.sh` the following where `getJavaPath()` is a hypothetical user defined Java executable:...