| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
|
|
|
| |
System branch: master
|
| |
|
|\
| |
| |
| |
| | |
Reviewed-By: Richard Ipsum <richard.ipsum@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
|/
|
|
|
|
|
|
|
|
|
| |
The recent changes to the BuildCommand.build() function caused distbuild
to break, because I didn't make the same change to the
InitiatorBuildCommand.build() function but did change how it was called.
This commit adds the ability to have optional fields in distbuild
messages. This is used to add an optional 'original_ref' field, which
will get passed to `morph serialise-artifact` by new distbuild
controllers, and will be ignored by older ones.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most usefully, this patch means that Morph no longer updates its cached
copy of definitions.git every time you run `morph build`.
Also, it prevents confusion in the following situation. Imagine I have
run:
morph checkout baserock:baserock/definitions master
I then wait a while, during which time someone pushes to 'master' in the
definitions.git repo that I cloned from. Now I run:
cd master
morph build systems/whatever.morph
Which commit does it build, the local head of 'master' or the remote
head of 'master'?
The answer, both before and after this patch, is that it builds the
local version of master. But previously, this only happened because of
the magic that we have to detect local changes. With this patch, the
local change detection could be disabled and `morph build` would still
build what the user had checked out as 'master' locally, not whatever
'master' pointed to in the remote repo.
|
|
|
|
|
|
|
|
|
| |
Rather than take a list of triplets to build, the BuildCommand.build()
function now takes a single repo/ref/morph triplet. Iterating through
multiple sets of triplets is now done in the build plugin.
There are a couple of cosmetic changes to the status output at the start
and end of a build as a result.
|
|
|
|
|
| |
Previously it was incorrect in the `morph help` output and in Morph's
man page.
|
|
|
|
| |
It was broken by the per-source building changes.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
You can bind to an ephemeral port by passing 0 as the port number.
To work out which port you actually got, you need to call getsockname().
To facilitate being able to spawn multiple copies of the daemons for
testing environments, you can pass a -file option, which will make the
daemon write which port it actually bound to.
If this path is a fifo, reading from it in the spawner process will
allow synchronisation of only spawning services that require that port to
be ready after it is.
|
|
|
|
|
|
|
| |
I've rarely needed to use it, and on those rare occasions, it would have
been easy enough to calculate it.
Let's get rid of this step, and save everyone some time in future.
|
|
|
|
| |
It's easy enough to deploy the image.
|
|\
| |
| |
| |
| |
| | |
Reviewed-by: Lars Wirzenius (+2 to misc fixups)
Reviewed-by: Sam Thursfield (+1 to per-source building)
Reviewed-by: Paul Sherwood (+1 to per-source building)
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This was used before the Artifact splitting code landed to determine
which artifacts should be produced.
|
| |
| |
| |
| |
| | |
There's other methods called get_sources in other modules, and
fetch_sources explains more about what it does in the context.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This involved rewriting the util.log_dict_diff() function. It has been
renamed to log_environment_changes() to better reflect its purpose.
It no longer logs both the old and new values in the event of an
environment variable changing. It now just logs the new value. This makes
the code simpler and seems like it should not be a big problem.
Some projects recommend passing credentials through the environment.
OpenStack does this, for example, see:
<http://docs.openstack.org/user-guide/content/cli_openrc.html>
It's unlikely that users would be happy about applications saving
these passwords in log files all over their system.
I do not recommend ever storing valuable passwords in the environment.
|