|Christophe van de Kerchove 2e41e6ac34||7 maanden geleden|
|hooks||3 jaren geleden|
|resources||10 maanden geleden|
|.pre-commit-config.yaml||7 maanden geleden|
|AUTHORS||10 maanden geleden|
|CHANGELOG.md||7 maanden geleden|
|Dockerfile||7 maanden geleden|
|Jenkinsfile||1 jaar geleden|
|README.md||7 maanden geleden|
This is a dind image... I know it's bad but has some great advantages, really.
We do publish a
latest tag on this image. Since this is basically a build image, we can use a the latest tag. If you prefer running a specific tag. Just pin a version in you jenkins config or Jenkinsfile.
We do not follow the jnlp release tags in the docker image tags. You can always find the jnlp version in the Dockerfile that was used to create the image or you can use the labels.
This was made to run on k8s, and let's face it, I don't mind having to clean up the used images after a build, but I'm not the only guy using the jenkins and other won't clean up... Because it's easier to mount a volume this way. I don't have to do nasty stuff to it for it to mount a couple of text file. I'm don't have to manually launch a container on a host while having k8s launching containers as well. k8s should be the only one launching container on it's cluster. So I decided to change my mind and go for a dind image. This also means I don't have to install every tool on the slave image. Meaning that when some guy who doesn't know what he's doing is adding his tool on the slave container, he won't be able to brake the slave image for everybody !!! This way he'll only break his build container and limit the breaking to his job only, leaving the rest of us with a working jenkins.
Final word on this, dind is bad but it does have some nice perks.
Usage is restricted in a k8s environment... do not use outside of it... go for an official container.
If you are in a k8s environment, just google “jenkins+kubernetes”, you'll have plenty of examples. If we don't exactly explain how to use it here, it's because we have our own deployment procedures of jenkins, this procedure is detailed on our internal wiki, but it does contains some sensible information and there is a lot of documentation for this setup on line (even form google itself)
We set labels on our images with additional information on the image. we follow the guidelines defined at http://label-schema.org/. Visit their website for more information about those labels.
If you have comments or detect an issue, please be adviced we don't check the docker hub comments. You can always contact us through the repository.
These file are generate using the
git changelog and
git authors commands made available using the
git-extras package. Please refer to your OS's package documentation to install these tools.
This repository uses a pre-commit config file. Our CI will automatically run pre-commit. For more information about pre-commit: https://pre-commit.com/