| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This yarn was failing 'cause of a missing
chunk morph rather than a failure to push
Change-Id: I70d79b1b9ec972cebde825d90c039666867bb1fa
|
|
|
|
| |
Change-Id: I8e5726cd1c16b7ef3c614e647f3ccfe50bf80ffe
|
|
|
|
| |
Change-Id: I7c993aee22f8438c28566acce01c524d9b315951
|
|
|
|
| |
Change-Id: Iee611887c54f8b8b67504ae2ba0cd78be703e455
|
|
|
|
| |
Change-Id: I54d1a03ba37f7589783f41c02482c0ac1821508d
|
|
|
|
| |
Change-Id: If3f6abdaab6518e77da911bfe1952c8ffe4bda34
|
|
|
|
| |
Change-Id: Ia644ddfaa5138f0ad459099cf26f51b545a9f9ca
|
|
|
|
| |
Change-Id: I60e808d7f42890dac2e1470a994e1a31a92401e7
|
|
|
|
| |
Change-Id: I77a8a3aab887f5d14a372690502df3fdeba6db10
|
|
|
|
| |
Change-Id: I1df58c33987597d4aa5a8eb241b4de4ac72fe250
|
|
|
|
|
|
|
| |
"the user gets the repo" does not set exit-morph, so it is not valid to
check whether it exited successfully.
Change-Id: I05e2d5c1919eee6b714269642eb9c39bcf578bbc
|
|
|
|
| |
Change-Id: I5dec13df6c28eeb4e8c83ec41fb4bd119e2eebb1
|
|
|
|
| |
Change-Id: Iaab620f3d9ebc037fe024db933b03e8f40ca40a4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a `morph generate-manifest-csv` command which creates
a CSV manifest for a system containing license information,
upstream URL and a guess at the version of each component in a
system.
The existing `morph generate-manifest` is also renamed to
`morph generate-manifest-genivi` to improve the distinction
between the two commands which generate a manifest.
The basis of this commit was done by
Michael Drake <michael.drake@codethink.co.uk>.
Change-Id: I712de11eaa6e1564c5bae5f5f396e5e77484972f
|
|
|
|
| |
Change-Id: Ie0ac708946c3b1d65d2022638c02d6a2d288ad9d
|
|
|
|
|
|
|
|
|
|
|
| |
Its going to be more likely that a baserock user is more interesed
in the build log than actually the debug output from morph.
And also the intuitive option would be to use -v for this.
--verbose/-v: show build output
--debug/-d: show morph debug output
Change-Id: I1fb99034dc8680a5f168f6306724663aea33ebc5
|
|
|
|
| |
Change-Id: Ibc95fe1d78c8d68dd20a4d2187f93f363369dfec
|
|
|
|
| |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
|
|
|
|
|
|
|
|
|
| |
This test fails with latest Busybox. Since we plan on removing
workspaces anyway, I don't see a reason to fix it. The `morph foreach`
command does actually still work as expected.
Morph's ./check test suite now passes again in a 'build' reference
system built from commit 88eface4c72dab689bc409c77e209833a0acd038 or
newer.
|
|
|
|
|
|
|
| |
We will use MorphologyLoader.load_from_file() to load morphologies
from a temporary file, so the output will be unpredictable. That
will break this test, so we may as well convert it into a yarn
to fix it.
|
|
|
|
|
|
| |
This commit fixes an issue where running morph's yarn tests would
leave behind a number of scripts/git-daemon-wrap processes due to
some tests not stopping their git server properly.
|
|
|
|
|
|
|
| |
Fix "attempting to build a system morphology which has never been committed"
use WHEN ... THEN morph succeeded
The old yarn worked just as well, this change is just for consistency.
|
|
|
|
|
| |
Simplify 'deploying a cluster morphology as a tarfile'
and 'attempting to upgrade a tarfile deployment'
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Existing tests generally request something like
morph build systems/foo-system.morph, now that the system arg is treated
relative to the working directory we must change into the directory that
contains the morphs to run morph build systems/foo-system.morph
|
| |
|
|
|
|
|
| |
These were previously completely untested, so their unsafe mounting
wasn't noticed, but now both are fixed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
You need both bottle and flup for this to work, and it would wait
forever for a cache-server that is never going to start unless you have
bottle and flup.
So we now check whether the cache server is functional before attempting
distbuild tests.
|
| |
|
|
|
|
| |
Deploying after distbuild currently broken
|
| |
|
| |
|
|
|
|
|
| |
When all the tests that use build-mode: test are gone, the build mode
can be removed.
|
|
|
|
|
|
| |
The arguments to `morph deploy` can get quite long, any way we can make it
shorter and clearer is useful. We can also avoid having the strange
--no-upgrade flag in future.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we would use file: URIs to point to the git repositories.
This was fast and simple, but had the drawback that it bypassed all the
git cache logic, so changes to the git cache weren't adequately covered
by the test suite.
Now we spool up a simulated git server per scenario, and shut it down at
the end.
|
|
|
|
| |
This replaces an old cmdtest.
|
|
|
|
| |
We're using the wrong morph if we don't use run_morph
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a check in it to see whether it needed to do the git branch
and git checkout based on whether the name of the branch matched that in
the morphology.
This had a couple of problems:
1. Now that we aren't always building from HEAD, we need to be able to
roll its commit back, so using the existing branch isn't always the
best idea.
2. It only checks the "ref" field, not "unpetrify-ref", so even though
we clone the right ref in there, it's checking the commit id against
the system branch name, so would always try to re-create the branch,
and fail when it already exists.
So now, we remove the original ref and re-create it with our preferred
HEAD.
A better solution might be to change the clone logic to not
automatically checkout HEAD, and instead require an explicit branch then
checkout, but the initial clone logic is shared with build, and I didn't
feel like tracking down all the different places that it was used.
|
|
|
|
|
|
|
|
|
| |
The help for the show-branch-root command said it returns a path, but
the command and the yarns just showed the aliased url it was cloned
from.
Given I found myself needing the path in some scripts, not the repo url,
I think it's more useful to reconcile the difference this way.
|
|
|
|
|
|
|
|
|
| |
This is closer to our current workflow, where we are always petrified
and update the ref field when we need to update a component.
This required rearranging the operations to create the chunk repository
before the definitions repository, and remove a check that assumes we
weren't already petrified.
|
|
|
|
|
|
|
| |
We don't use this any more, and instead prefer to always keep
definitions.git petrified, and update the refs ourselves.
branch-from-image still uses some of the remaining petrify code.
|
|\
| |
| |
| |
| |
| | |
'origin/baserock/richardmaw/S11416/no-unnecessary-temp-branches'
Reviewed-by: Daniel Silverstone
|
| | |
|
| | |
|
| | |
|
|/ |
|