š
Improving the ergonomics of an environment is a very worthwhile investment across all levels of a company. Ergonomics help lead to less fatigue and burnout for the personnel in charge of BAU operations. Reduced burnout helps ease turnover and saves the company money by not needing to spend as much hiring and onboarding newcomers to replace lost numbers.
### Enhancement #01: Basic Scripts
To begin, let's create basic scripts for our main actions:
* Create <-- Creates the container
* Remove <-- Remove the container
* Start <-- Starts the container
* Stop <-- Stops the container
* Log <-- Helps us to quickly get the log output of a container
* Bash <-- Helps us explore the container's file directory
```bash
# $ vi ./jenkins_config.sh
#!/bin/bash
CONTAINER_NAME="jenkins_McAws" # Rename this to anything you want
VOLUME_NAME="jenkins_McAws_data" # Rename this to anything you want
```
```bash
# $ vi ./create_DockerJenkins.sh
#!/bin/bash
echo "Creating Jenkins Container"
. ./jenkins_config.sh
docker create --name ${CONTAINER_NAME} \
--restart=on-failure \
-p 8080:8080 -p 50000:50000 \
-v ${VOLUME_NAME}:/var/jenkins_home \
jenkins/jenkins:lts-jdk11
```
```bash
# $ ./remove_DockerJenkins.sh
#!/bin/bash
echo "Removing Jenkins Container"
. ./jenkins_config.sh
docker stop ${CONTAINER_NAME}
docker rm ${CONTAINER_NAME}
```
```bash
# $ vi ./start_DockerJenkins.sh
#!/bin/bash
echo "Start Jenkins Container"
. ./jenkins_config.sh
docker start ${CONTAINER_NAME}
```
```bash
# $ vi ./stop_DockerJenkins.sh
#!/bin/bash
echo "Stopping Jenkins Container"
. ./jenkins_config.sh
docker stop ${CONTAINER_NAME}
```
```bash
# $ vi ./log_DockerJenkins.sh
#!/bin/bash
echo "Opening Logs of Jenkins Container"
. ./jenkins_config.sh
docker logs ${CONTAINER_NAME}
```
```bash
# $ vi ./bash_DockerJenkins.sh
#!/bin/bash
echo "Starting Bash of Jenkins Container"
. ./jenkins_config.sh
docker exec -it ${CONTAINER_NAME} /bin/bash
```
These scripts will help us to execute operations without needing to put in the container name (which can get real annoying, real fast). These scripts can also allow opportunities to bundle multiple commands at once (e.g. `remove_DockerJenkins.sh`)
### Enhancement #02: Dockerfile (i.e. Custom Image)
Let's enhance this further by creating a Dockerfile for Jenkins.
š”
The Dockerfile is a recipe to create a docker image for containers. Think of it like ordering a pizza, you typically start from a base (i.e. FROM <any_image_from_docker> ), and then you add whatever toppings you want until you're satisfied (i.e. COPY, RUN, ADD, etc)
We create this simple Dockerfile that is a copy of the `jenkins/jenkins:lts-jdk11` image without any modifications. (Don't worry, we'll add more to this soon)
```dockerfile
# $ vi Dockerfile
# We base our image off the Jenkins image we used on previous commands
FROM jenkins/jenkins:lts-jdk11
```
We must update the `jenkins_config.sh` and `create_DockerJenkins.sh` to accommodate this enhancement.
```bash
# $ vi ./jenkins_config.sh
#!/bin/bash
IMAGE_NAME="jenkins_image" # Specify our custom IMAGE_NAME
CONTAINER_NAME="jenkins_McAws"
VOLUME_NAME="jenkins_McAws_data"
```
```bash
# $ ./create_DockerJenkins.sh
#!/bin/bash
echo "Creating Jenkins Container"
. ./jenkins_config.sh
# Builds docker image using the Dockerfile and naming it as ${IMAGE_NAME}
docker build -t ${IMAGE_NAME} . # <- Don't forget the '.'!
docker create --name ${CONTAINER_NAME} \
--restart=on-failure \
-p 8080:8080 -p 50000:50000 \
-v ${VOLUME_NAME}:/var/jenkins_home \
${IMAGE_NAME} # Replace the base jenkins image with our custom image
```
### Enhancement #03: Upping our Security
Although upping security doesn't make our lives 'easier' per se, it's still good to secure your hosts so that we have peace of mind that malicious attackers will have a harder time getting access to Jenkins' functionality.
Go to `http://