| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
shutil.move() does not preserve permissions, file modes, ownerships etc,
resulting in much confusion when prepopulating a non-root user during
deployment. This change to `mv` fixes that.
|
|/
|
|
|
|
|
| |
Add support to the VirtualBox write extension to notice if we are
doing a Vagrant Basebox installation and not do the clever network
setup we normally do to allow machines to talk to one another since
this confuses Vagrant quite a bit if it is left in.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Reviewed-By: Richard Ipsum <richard.ipsum@codethink.co.uk>
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| |
| |
| |
| |
| | |
Users need to be able to see logs of all builds, not just those that
failed.
|
|\ \
| | |
| | |
| | | |
Reviewed-By: Richard Ipsum <richard.ipsum@codethink.co.uk>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This is useful to build releases using distbuild. It avoids having the
SHA1 fields in the artifact metadata files pointing to commits that
exist only on temporary build branches. It also avoids file:// URLs in
the repo fields. Note that the repo URL still points to the Trove used
by the distbuild network, rather than being an upstream URL pointing to
git.baserock.org.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Reviewed by:
Lars Wirzenius
Sam Thursfield
Daniel Silverstone
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We could just set stdout to subprocess.PIPE
then read from the pipe, but then we won't get the output
till the command's finished and some commands take a long time.
Using the logfile kwarg a file will be created by tee
and the output will be written to it in 'real time'.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use tee to write the output to a file as well as to stdout.
Using Popen it should be straight forward to send the output to a pipe and
then read that pipe and write to wherever.
At the moment morph uses cliapp's runcmd rather than Popen. cliapp's runcmd
is a blocking call, so we're not able to read from the pipe until the
command has completed, which prevents real time logging to a number of files.
One solution to this problem might be to spawn a thread which opens a pipe
to the command being executed, the thread then reads from the pipe and writes
to our collection of logfiles.
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
Move the help out of the comment and into a help file,
and add a clearer example.
|
|\
| |
| |
| |
| |
| |
| | |
Reviewed by:
Richard Maw
Lars Wirzenius
Daniel Silverstone
|
| |
| |
| |
| | |
To cancel jobs cleanly we need to know when a job has failed.
|
| | |
|
| | |
|
| |
| |
| |
| | |
add_initiator() isn't necessary given lists have a remove method.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
There's no longer any need to log the exception separately,
it will be logged with the MorphologySyntaxError
|
|\ \
| |/
|/|
| |
| |
| | |
Reviewed by:
Daniel Silverstone
Richard Maw
|
| | |
|
|/
|
|
| |
Be more verbose and exit with an error not an exception.
|
|\
| |
| |
| |
| |
| |
| | |
Reviewed by:
Sam Thursfield
Richard Maw
Lars Wirzenius
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
The contents of the message has changed for several events,
event messages that need to be sent to several initiators have a list
of ids instead of a single id.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are two new messages:
WorkerBuildStepAlreadyStarted tells the initiator that the artifact
they want to build is already being built, e.g.
'eglibc-misc is already building on 172.17.1.37:3434'
WorkerBuildWaiting tells the initiator that the artifact they want
to build can't be built yet because there aren't any workers free, e.g.
'Ready to build eglibc-misc: waiting for a worker to become available'
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Put our _exec_response_msg into WorkerBuildFinished event,
it's essentially the same as _finished_msg, just a different name
Get our artifact's cache key from the job
|
| |
| |
| |
| | |
Now we just get everything from the job object
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The exec_response_msg also needs to be sent to a number of initiators,
so we give it a list of ids not just one.
The exec_response_msg will be sent to the controller once the artifacts
have been cached successfully.
There's no longer any need to use a route map to retrieve
the id of the initiator, since this is stored with the job
|
| |
| |
| |
| |
| | |
msg now contains a list of initiator ids rather than a single one,
since BuiltOutput needs to be sent to a number of initiators
|
| |
| |
| |
| |
| |
| | |
Each job is given a unique id, so we don't need to generate
an id for each exec request this means we can remove use of route map
since we can use the job's id for the exec request
|
| |
| |
| |
| | |
This method no longer works, we will replace it soon.
|
| |
| |
| |
| |
| | |
The name change from BuildFailed -> JobFailed etc
was unintentionally merged into master, undo this.
|
| |
| |
| |
| |
| |
| | |
_job is the job this worker is carrying out
_exec_response_msg will contain the response the worker sends back to us
when it finishes the build.
|