I think it is the CI groups private bucket. It was a link I followed from Vincent, and I didn't pay attention to our internal URLs. I wish I had noticed, since then I could have pointed him at the official location. I guess I was just thrown off that streams.canonical.com wasn't updated.
Thanks for clarifying the process. It does still seem strange that we copy to mirrors before the official location, but I understand the build process. I'm not sure if we want to slow down dev releases to wait a day to get streams updated or not. I like the layout, but if we are doing more than one release per week, that slows velocity a lot. So *definitely* stable releases should always wait for streams.canonical.com. And maybe dev releases should move to that (but maybe not this week). John =:-> On Mar 17, 2014 11:47 PM, "Curtis Hovey-Canonical" <[email protected]> wrote: > On Mon, Mar 17, 2014 at 12:14 PM, Curtis Hovey-Canonical > <[email protected]> wrote: > > On Mon, Mar 17, 2014 at 5:01 AM, John Meinel <[email protected]> > wrote: > > > >> nor are they in HP: > >> > https://region-a.geo-1.objects.hpcloudsvc.com/v1/11289530460295/tools/streams/v1/com.ubuntu.juju:released:tools.json > > > > I don't know what 11289530460295 is (The scripts publish to > > 60502529753910 and since the mirror file hasn't changed since November > > 2013, I think they have always published to the container in the > > mirrors file. > > Google knows a lot about my container id, but very little about the > one you cite John. I think it is the container that images are > published too, I am surprised to see juju tools there. I think they > got there by accident, and they only go there when os images are > released. This is not my monkey, not my circus. > > -- > Curtis Hovey > Canonical Cloud Development and Operations > http://launchpad.net/~sinzui >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
