deis/jenkins-node

Tooling for bringing up a Jenkins Worker Node for Deis CI.

jenkins-node's Issues

slim down docker image

sittin' at 1.634 GB at time of writing...

migrate existing nodes to k8s

This ticket is to help track progress on migrating the existing CI nodes over from an Ansible-style deployment to k8s containers.

So far the following jobs are being used for testing:

• jenkins-node-1 is deployed to champagne.deis.com
• test-job-for-node-test-k8s is set up to run on the k8s worker

At this point, the job is succeeding. Further testing is required to ensure e2e works on this node as well, but once that's completed then we can start slowly migrating the nodes to k8s.

make this app scalable

Because we require a single NODE_NAME and NODE_SECRET envvar in the container which relates to a single worker node in jenkins, this application is unable to scale higher than 1. Instead of creating single applications for each jenkins node, it'd be more "12 factorish" to allow this app to scale proportionately to the number of nodes we want in Jenkins.

Refactor: Reduce custom logic

#9 updates the jenkins-node image to act more like a default Jenkins jnlp-slave. However, due to how e2e is setup to run (see deis/e2e-runner), we still have some custom logic in the Dockerfile and jenkins-slave script.

Therefore, this ticket is to make updates (most likely necessary both in this and the aforementioned e2e-runner repo) to switch up the Dockerfile to pull from jenkinsci/jnlp-slave as well as removing our version of the script (delete the rootfs dir).