I agree. We should snapshot a known-good starting point and start from there. It's a huge waste of time to do apt update / upgrade / install git, bzr, mercurial, etc every single time we run CI. That's like 1/3rd the time it takes to run the unit test CI job.
On Wed, May 18, 2016 at 10:35 PM David Cheney <[email protected]> wrote: > This is a huge waste of wall time and bandwidth, and increases the > chance of failure significantly. This is something I would like to see > changed. > > On Thu, May 19, 2016 at 12:06 PM, John Meinel <[email protected]> > wrote: > > CI does a build from scratch in a pristine VM. There is some discussion > > about changing that in a variety of ways (in a container in a long > running > > VM, etc), but it doesn't have a local copy to work from so it has to > pull it > > from upstream each time. > > > > John > > =:-> > > > > > > On Wed, May 18, 2016 at 8:05 PM, David Cheney < > [email protected]> > > wrote: > >> > >> We already have godeps which can take a set of vcs repos and flick > >> them to the right revisions. > >> > >> Why does CI check out every single dependency from upstream every > >> single time we do a build ? That introduces wc -l dependencies.tsv > >> points of failure to every single CI run -- not to mention the several > >> minutes it spends laboriously checking out the code. > >> > >> Thanks > >> > >> Dave > >> > >> -- > >> Juju-dev mailing list > >> [email protected] > >> Modify settings or unsubscribe at: > >> https://lists.ubuntu.com/mailman/listinfo/juju-dev > > > > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
