Hi Aaron,
wrt the Dockerfile situation. What you are saying is right, but my proposal
is the following:
Instead of having a fat Dockerfile like
---
FROM ubuntu:16
RUN apt update
...
---
You instead run that fat Dockerfile locally on your laptop and push it to
"aaronmarkham:elephantmaster9000"
For stash vs archive, maybe we need to look into attached storage
options and combine some deployments, so that artifacts get stored in
an accessible way. I notice sometimes the web portal for Jenkins
becomes unresponsive. If disk space is causing this, we need to
address it.
For the Dockerfile
Hi,
thanks a lot for these great notes! I'm happy to give my comments about
them :)
* Archiving is *very VERY* bad for the CI master performance. It floods the
disk with data since archiving persists the data. We are now at the point
where we technically can't extend the volume any further (we
I'll start a different thread about the website. Sure, there's a lot
of overlap with CI. I learned a lot in the last few weeks having to
iterate on 7 different docs packages and trying to streamline the
build process in CI.
Here are my notes:
* Stash operations vs. archiving - recommendations in
