jujubox and charmbox

[Matt Bruzek]

With the release of Juju 2.0 we have spent some time updating jujubox and
charmbox with the latest install steps and tools.

We use these containers for some of our internal tooling. If you are using
these containers please note the changes and let us know if you have any
feedback.

*jujubox* - an isolated container with just the Juju tools.

   - Created a "juju-1" branch that installs Juju 1.x the master branch now
   tracks Juju 2.x.
   - Added the ability to build with a user other than ubuntu.
   - Using ENV directives for JUJU_DATA and JUJU_REPOSITORY environment
   variables.
   - Using the ENTRYPOINT, WORKDIR and USER directives removed the need for
   run.sh.
   - Changed the ADD directives to COPY very minimal change but enough to
   warrant review comments.
   - Using FROM ubuntu:16.04 as the common base.
   - Removed the extra packages that are not used by Juju.


These changes resulted in a significant reduction in the jujubox image size.

*charmbox* - an isolated container with amulet, charm-tools, bundletester
and git. We use this container for some CI tools on our team, and some
people use it for charm reviews.

   - The master branch now installs Juju 2.x.
   - Removed the devel branch as we will only be tracking jujubox branches.
   - Updated charmbox to be in sync with the changes from jujubox.
   - Added the packages that were removed from jujubox
   - Using ENV directives for LAYER_PATH and INTERFACE_PATH.
   - Charm-tools is installed from source as this gives us all access to
   fixes that are not yet released.

We also re-enabled the build triggers to build charmbox when jujubox is
updated. This should provide a better experience using these containers.
Please let us know if you find any problems with these containers.

   - Matt Bruzek <matthew.bruzek at canonical.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161128/157822b7/attachment.html>