Three CI builds in the last 48 hours have failed because launchpad had a lie down
John Meinel
john at arbash-meinel.com
Thu May 19 02:06:31 UTC 2016
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 <david.cheney at canonical.com>
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
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160518/e640d412/attachment.html>
More information about the Juju-dev
mailing list