New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenkins cloudformation #1098
Jenkins cloudformation #1098
Conversation
@@ -16,7 +16,7 @@ RUN apt-get update -qy && apt-get dist-upgrade -qy && apt-get install -o Dpkg::O | |||
libtiff-dev libjpeg-dev libopenjp2-7-dev libwebp-dev zlib1g-dev \ | |||
graphviz \ | |||
locales \ | |||
nodejs && apt-get -qy -t stretch-backports install npm && apt-get -qy autoremove && apt-get -qy autoclean | |||
nodejs node-gyp && apt-get -qy -t stretch-backports install npm && apt-get -qy autoremove && apt-get -qy autoclean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The node-gyp
package might not be installable from NPM just due to upstream breakage, which is common enough that I remember it by name. Installing it from APT should be a big stability improvement.
usermod -aG docker jenkins | ||
snap install postgresql96 | ||
pip3 install awscli --upgrade |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an interesting judgement call: awscli releases frequently enough that I tend to pip install it to get access to new features but if we're not using it having that be cached should be more robust.
Had to provision a new Jenkins server and took the opportunity to check in more of the configuration in case it needs to happen again.