https://github.com/devwithkrishna/jenkins-docker-slave-images
These are docker images created to use as a jenkins slave
https://github.com/devwithkrishna/jenkins-docker-slave-images
docker dockerfile jenkins runners
Last synced: 2 months ago
JSON representation
These are docker images created to use as a jenkins slave
- Host: GitHub
- URL: https://github.com/devwithkrishna/jenkins-docker-slave-images
- Owner: devwithkrishna
- License: mit
- Created: 2024-07-15T17:42:49.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2025-07-01T18:12:58.000Z (12 months ago)
- Last Synced: 2025-12-30T11:42:58.884Z (6 months ago)
- Topics: docker, dockerfile, jenkins, runners
- Language: Dockerfile
- Homepage: https://github.com/devwithkrishna/jenkins-docker-slave-images
- Size: 32.2 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://shields.io/)
[](https://shields.io/)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk11-dind-image.yaml)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk11-tf-depoy-image.yaml)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk17-dind-image.yaml)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk17-tf-depoy-image.yaml)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk21-dind-image.yaml)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk21-tf-depoy-image.yaml)
[](https://github.com/devwithkrishna/jenkins-docker-slave-images/actions/workflows/build-publish-jdk21-python-image.yaml)




# jenkins-docker-slave-images
These are docker images created to use as a jenkins slave
# How the Build flow works
```shell
├───.github
│ └───workflows
│ ├───build-publish-jdk11-dind-image.yaml
│ ├───build-publish-jdk11-tf-deploy-image.yaml
│ ├───build-publish-jdk17-dind-image.yaml
│ ├───build-publish-jdk17-tf-deploy-image.yaml
│ ├───build-publish-jdk21-dind-image.yaml
│ └───build-publish-jdk21-tf-deploy-image.yaml
├───jdk-11
│ ├───dind
│ └───tf-deploy
├───jdk-17
│ ├───dind
│ └───tf-deploy
└───jdk-21
├───dind
└───tf-deploy
```
* Build and push to Dockerhub will be taken care by ``docker/build-push-action``
* Authentication to Dockerhub will be taken care by ``docker/login-action``
* Image scanning is carried by using [trivy](https://github.com/aquasecurity/trivy)
* The builds are scheduled which means they will be triggered at the configured time.
* Each time the build is triggered, 2 versions of image are pushed (also multi arch images)
* One image version will be latest as usual and other will be in a format `___>`
* Eg: dockerofkrishnadhas/jenkins-slave-tf-deploy-jdk17-image:tf_v1.9.1_az_2.61.0
* This means `dockerofkrishnadhas/jenkins-slave-tf-deploy-jdk17-image` has `terraform 1.9.1` version and `azure cli 2.61.0` version
* These are set as cron to be executed monthly once on 17th of every month
* get_software_versions.sh ➡️ This script executes and get the live software versions available in image and passes them as an environment variable in github workflow.