Sometimes, Jenkins builds simply get stuck, and aborting them from the job page does not help.
If this is your case, then, you can do something with it:
- read your build job’s full name and, the build number that you wan to terminate
Jenkins.instance.getItemByFullName("<job_full_name>").getBuildByNumber(<build_number>).finish(hudson.model.Result.ABORTED, new java.io.IOException("Stopping this build without being polite."));
You have two options:
- Set up a web-based browser – this will require you more work to set up and maintain, but will give you much easier way to browse the repo
- Browse manually the repository – requires no setup, you will find what you look for in a minute, but it’s not greatly user friendly
If you go for solution 1, there are a few implementations, that can be even downloaded as docker containers (like docker-registry-web ).
If you go for solution 2 (which is what this post is about), you only need to perform two steps with your browser:
- list what are the repositories
This will give you a JSON list of repositories… just find one of your interest
- list the tags for a it
(source: Stack overflow – snth’s answer)
While configuring distributed builds with Jenkins with slaves on Amazon EC2, your first setup could make use of on-demand instances.
Meaning that Amazon manages some machines that you could start (boot) and stop (shutdown) whenever you want. Amazon bills you for the time these machines are running.
So if you want to save some money, you want these machines to be running only when you use them: in the case of Jenkins slaves, only when Jenkins has something to do on them.
Amazon helps you, by providing you a console interface that can be scripted, and plugged to other logic in Jenkins, but what could be this logic?
The Slave setup plugin lets you configure slaves as “on-demand”, by providing a hook (1) that allows you to specify – right in the configuration of the slave node – a script to be executed before connecting (2) and another one to be executed after disconnecting (3).
You can find more details in its documentation (section “on-demand slave setup”).
System: long-running container that creates/delete files. Host is a RHEL7.2 (kernel 3.10.0-327.el7.x86_64) machine, with Docer v1.8.2 backed by a “loop-lvm” devicemapper pool.
Symptom: despite the container also deletes files, the available space in the devicemapper pool only shrinks and never increases.
Possible solution: run “fstrim /” from inside the container. Note that this requires you to run it in ‘privileged’ mode.
If you are using docker on Red-Hat based distributions, then devicemapper is your default filesystem for backing docker.
In case you want to change some of its default settings (i.e. if pool size of 100Gb is not enough), have a look at the “real docs” for RH7 or at this page for other distributions.
If you want to dig deeper, in this other page you will find a pretty detailed comparison of the different filesystems options available for RH.
In case you have a docker container on which you need a shell, and you don’t have it (e.g. it runs in the background, no sshd runs on it, …), you can have a shell on it by executing:
docker exec -it <container_name> /bin/bash
If you have a fancy jenkins configuration, and your jobs don’t behave as you expect, you might use this nice feature of Jenkins for obtaining the thread dump of the Jenkins threads.
Just go to the URL: