| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
If you deploy the chef system now and then 'gem install erubis' you
seem to end up with a working Chef. Suksess!
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| | |
Conflicts:
strata/core.morph
strata/ruby.morph
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Using chef-12.0.0.alpha.0 results in the following error:
# chef-client
/usr/lib/ruby/2.0.0/rubygems/dependency.rb:296:in `to_specs': Could not
find 'ohai' (~> 7.2) - did find: [ohai-7.2.0.rc.1] (Gem::LoadError)
|
| | |
| |
| |
| |
| | |
This increases the size to around 250MB, but it's required for
libffi to work, and much other stuff no doubt.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Taking advantage of the new work in Morph 'master' allowing chunk morphs
to go in definitions, we can now treat each Gem as a chunk, and with a
bit of hackery, make fetching and compiling+installing the Gem from
http://rubygems.org/ look like a normal Morph build. To avoid the
hackery we need to introduce a separate build-mode, probably, but this
is a start!
|
| | |
| |
| |
| |
| | |
Nasty hack, but saves 200MB or about 50% of the total size of the
system.
|
| | |
| |
| |
| | |
It's about 70MB, and not needed in a container.
|
| | |
| |
| |
| |
| | |
The chef system is about 667MB with core-runtime included which seems
excessive for a container!
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This uses a local repo with all the required Gems committed in advance
and a script that runs 'gem install' as the build tool.
|
| | |
| |
| |
| | |
Installs chef by running 'gem' at deploy time. Sorry.
|
| |\ \
| | |
| | |
| | |
| | | |
Reviewed-by: Sam Thursfield
Reviewed-by: Michael Drake
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
We don't need to store gits on there, so we don't need it to be quite so
large.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The per-mason trove only needs to worry about being an artifact cache,
so we can prevent it populating itself from the upstream trove by making
it use the SSH protocol for fetching sources, and not registering its
ssh key with the upstream trove.
The MASON_UPSTREAM_TROVE_ADDRESS option has been removed, as this is now
the TROVE_HOST.
The distbuild network is now configured to use the upstream trove for
sources, and the local trove for artifacts, with the
ARTIFACT_CACHE_SERVER option.
mason.configure now uses ARTIFACT_CACHE_SERVER to tell deploy commands
which server to fetch artifacts from.
|
| |/ / |
|
| |\ \
| | |
| | |
| | | |
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Add a note showing how to copy the mason controller's id_rsa.key.pub
to the upstream trove. This is needed or else artifact upload will
now work, resuling in a FAIL.
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| | |
| |
| |
| |
| |
| | |
This includes `git replace` mitigation code and raising an exception
if morph can't talk to the remote git cache, rather than assuming the
morphology didn't exist, and building the wrong thing.
|
| |\ \
| | |
| | |
| | | |
Reviewed-by: Richard Maw
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Failing to do this means that the deployment uses the wrong morphology,
because build will end up using the repo without the .git suffix, so it
will never update the cached version of the repo without it.
The version with the .git suffix is only updated on the initial
checkout, but is used by deploy, so it would pick up obsolete
morphologies and not include new changes.
Rubber-stamped-by: Richard Maw
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rubber-stamped-by: Richard Maw
The majority of the patches were approved, but for the rest there is
nobody else familiar enough with the code to comment.
This code has been through a Mason pipeline a couple of times though,
so it is less likely to break anything.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This requires the script be run in the top of the definitions repository,
but will actually try to upload the changes that were tested, rather
than the current HEAD.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The rest of the ssh commands are to the VM host, which we can't change
all of, since some are run as part of the deployment extension.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This name requires less context to understand its use.
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| | |
It was a sucky placeholder name that wasn't replaced by anything better.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Also update morph with fix to GitDirectory config caching.
Cpython change reviewed by Richard Maw and Paul Sherwood, each
giving +1.
Morph change reviewed by Richard Maw, +2
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Reviewed by: Richard Maw <richard.maw@codethink.co.uk>
Merged by: James Thomas <james.thomas@codethink.co.uk>
|
