On 2020-01-23 4:50, Chesnay Schepler wrote:
On 23/01/2020 10:19, Thomas Bouron wrote:
On Thu, 23 Jan 2020 at 08:56, Robert Munteanu <romb...@apache.org> wrote:
On Wed, 2020-01-22 at 17:53 -0800, Chris Lambertus wrote:
Additionally, orphaned docker jobs are causing major resource
contention. I will be adding a weekly job to docker system prune —all
&& service docker restart.
+1, it's easy to get this wrong. It would be great if you could also
document some best practices when using containers for CI on the ASF
Jenkins instance.
docker system prune -af works, but is probably a big hammer, when each
job should instead clean up after itself.
+1 on this.
For Brooklyn, we are using docker container for CI and I think we do it
right (you can see the Dockerfile and Jenkinsfile in the repo for more
context). But guidelines would be great. For instance, it took a long
time
to arrive to the particular setup we are currently running.
Back to the question of timeouts, the main Brooklyn build pipeline takes
around 1h30.
Best.
The Flink snapshot deployments take about 1h15m.
CouchDB is busy moving off the shared Jenkins workers, but our runs take
20-30 minutes on pull requests (unless there's a problem) and about
30-45 minutes on release branches after that. There are plans to extend
the release branch builds with other tasks that take longer, such as
preparing our Docker images -- these run rarely but do take upwards of
90-120 minutes each, and cannot be split into multiple steps.
-Joan
