tmms/jenkins
Name | From | Base OS | Annotations |
---|---|---|---|
tmms/jenkins:2.452.1 | jenkins/jenkins:2.452.1-alpine | Linux Alpine | |
tmms/jenkins:2.452.2 | jenkins/jenkins:2.452.2-alpine | Linux Alpine | |
tmms/jenkins:2.462.3 | jenkins/jenkins:2.462.3-alpine | Linux Alpine | |
tmms/jenkins:2.479.1 | jenkins/jenkins:2.479.1-alpine | Linux Alpine | |
tmms/jenkins:2.479.2 | jenkins/jenkins:2.479.2-alpine | Linux Alpine | youngest |
tmms/jenkins:2.479.3 | jenkins/jenkins:2.479.3-alpine | Linux Alpine |
This image is built from the official jenkins/jenkins
repository and contains different plugins and tools for our projects.
This image installs the following Jenkins plugins, which are the minimally required extensions for our projects:
def pluginList = new ArrayList(Jenkins.instance.pluginManager.plugins)
pluginList.sort { it.getShortName() }.each{
plugin ->
println ("${plugin.getDisplayName()} (${plugin.getShortName()}): ${plugin.getVersion()}")
}
The jenkins build by this image are able to handle docker containers inside. Also docker-compose projects could be executed inside jenkins. To use this feature make sure you add the docker socket file to the volumes of jenkins container:
Bitbucket
Bitbucket supports creation of personal access tokens and project tokens.
To use a personal access tokens within jenkins credentials just use a username-password credential and fill in the password input field your token.
Using a project token it is necessary to use bitbucket api token
credentials. Though the plugins asks for tokens with project admin rights yiu could easily use a token with only project read rights for login purposes.
docker pull tmms/jenkins