From e759b5a2eb09f526f7758fd6bfdbb86c2c576d9e Mon Sep 17 00:00:00 2001 From: Jim Van Fleet Date: Wed, 27 Jul 2016 14:33:59 -0400 Subject: [PATCH] Getting started with Docker construction --- .gitignore | 7 +++++++ BINSCRIPTS.md | 41 +++++++++++++++++++++++++++++++++++++++++ Jenkinsfile | 26 ++++++++++++++++++++++++++ common.bash | 2 ++ 4 files changed, 76 insertions(+) create mode 100644 .gitignore create mode 100644 BINSCRIPTS.md create mode 100644 Jenkinsfile create mode 100644 common.bash diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..7323a01 --- /dev/null +++ b/.gitignore @@ -0,0 +1,7 @@ +bin/build.sh +bin/destroy.sh +bin/install.sh +bin/rebuild.sh +bin/rerun.sh +bin/run.sh +bin/test.sh diff --git a/BINSCRIPTS.md b/BINSCRIPTS.md new file mode 100644 index 0000000..8569b7d --- /dev/null +++ b/BINSCRIPTS.md @@ -0,0 +1,41 @@ +# util + +This repository is intended to be downloaded into a container repository during development for convenience purposes. Since the major mechanisms of developing to the Docker container construction lifecycle are identical across container images, this repository allows for consistency and additional ease of use across all container images. + +## Install + +If you are reading this file in BINSCRIPTS.md, your container project is likely to be util-enabled. + +To use these scripts yourself, issue this command: + +``` +curl "https://github.internet2.edu/raw/docker/util/master/bin/install.sh?token=AAAAEddkrL9MeeA6VWcNn_PgV30r4lD1ks5XogeiwA%3D%3D" | bash +``` + +### common.bash + +The installation process will create a common.bash file. This file should be the central, canonical authority for management of environment variables. While a subprocess may override them, the files in common.bash should be treated as authoritative defaults. Processes (e.g. `docker build`, `bats`, inside `Jenkinsfile`) can read this file and process the results therein. + +You should edit this file to change the image name, and add any other helpful environment variables. + +### Jenkinsfile + +This will also install a Jenkinsfile to your repository, if it doesn't have one. This will ensure that your Jenkins pipeline can leverage these scripts in the way intended. Ensuring the commands that you issue on your laptop match the commands issued by the build pipeline is critical to ensure predictable, reliable results. + +## Use + + +### Building + +#### build.sh +`bin/build.sh ` +#### destroy.sh +#### rebuild.sh + +### Running +### rerun.sh +### run.sh + + +### Testing +#### test.sh \ No newline at end of file diff --git a/Jenkinsfile b/Jenkinsfile new file mode 100644 index 0000000..aead388 --- /dev/null +++ b/Jenkinsfile @@ -0,0 +1,26 @@ +node { + + stage 'Checkout' + + checkout scm + + stage 'Acquire util' + + sh 'mkdir -p bin' + dir('bin'){ + git([ url: "https://github.internet2.edu/docker/util.git", + credentialsId: "jenkins-github-access-token" ]) + sh 'ls' + sh 'mv bin/* .' + } + + stage 'Base' + + sh 'bin/build.sh' + + stage 'Tests' + + sh 'bin/test.sh' + + +} \ No newline at end of file diff --git a/common.bash b/common.bash new file mode 100644 index 0000000..96e0143 --- /dev/null +++ b/common.bash @@ -0,0 +1,2 @@ +maintainer="tier" +imagename="imagename-replaceme-in-common-bash" \ No newline at end of file