dyindude/jenkins-bootstrap

jenkins-bootstrap's Issues

make deployment less vagrant-specific

should be able to also drop this project on an Ubuntu 18.04 server and achieve the same results, plugging in user directories, etc

consistent way to pass HOST_IP to container chain

Currently generating a file, which shouldn't exist in the repo
It might be fine to set it as an env var and just make sure it gets added to each build in the build chain
Maybe write an environment file to the ansible/vagrant folder after deploy in case we need to re-deploy jenkins zero

cert expiry time definition

per https://docs.ansible.com/ansible/latest/modules/openssl_certificate_info_module.html, valid_at should support a simple +30d notation now instead of shelling out to date to compute this (which seems to now be invalid output for the module)

secrets should use docker secrets engine

helpers/check_status_code should retry

let it retry, maybe three times before failing the job?

swarm example?

not sure if we can run swarm on a single host, but this might be necessary for docker secrets

jenkins uid/gid should not be static

see jenkinsci/docker#112 (comment)

update docker-compose and other build scripts to use ${SERVICE}${ENVIRONMENT} pattern

I had already done this with other projects, but been dragging my feet on doing it with Jenkins. This will resolve the current build, and get us closer to where we need to be to share this with other people.

docker-compose doesn't work on first run of vagrant

TASK [launch nginx] ************************************************************
failed: [default] (item=/vagrant/docker/nginx) => {"ansible_loop_var": "item", "changed": true, "cmd": "docker-compose -p ${SERVICE}${ENVIRONMENT} up -d", "delta": "0:00:00.502380", "end": "2019-10-03 12:30:07.980407", "item": "/vagrant/docker/nginx", "msg": "non-zero return code", "rc": 1, "start": "2019-10-03 12:30:07.478027", "stderr": "Couldn't connect to Docker daemon at http+docker://localhost - is it running?\n\nIf it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.", "stderr_lines": ["Couldn't connect to Docker daemon at http+docker://localhost - is it running?", "", "If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable."], "stdout": "", "stdout_lines": []}
failed: [default] (item=/vagrant/docker/jenkins) => {"ansible_loop_var": "item", "changed": true, "cmd": "docker-compose -p ${SERVICE}${ENVIRONMENT} up -d", "delta": "0:00:00.453096", "end": "2019-10-03 12:30:08.549846", "item": "/vagrant/docker/jenkins", "msg": "non-zero return code", "rc": 1, "start": "2019-10-03 12:30:08.096750", "stderr": "Couldn't connect to Docker daemon at http+docker://localhost - is it running?\n\nIf it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.", "stderr_lines": ["Couldn't connect to Docker daemon at http+docker://localhost - is it running?", "", "If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable."], "stdout": "", "stdout_lines": []}

a second vagrant provision fixes it, need to find the race condition