| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
add_initiator() isn't necessary given lists have a remove method.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
We need to be able to send this message to a number of initiators
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
distbuild/build_controller.py
Reviewed by:
Lars Wirzenius
Daniel Silverstone
Sam Thursfield
|
| |
| |
| |
| | |
body and headers must now be specified for http-request message.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are cases where a state machine handles an event but stays in the
same state. A callback is registered which filters messages further
before possibly taking action. There have been bugs caused by this
pattern being incorrectly implemented (where the callback is expected to
filter the message, but a transition takes place anyway). Hopefully a
consistent naming convention will make the pattern clearer.
|
| |
| |
| |
| | |
Makes it easier to see what they mean at a glance.
|
|/
|
|
| |
This makes tracking multiple builds through one log file a bit easier.
|
|
|
|
|
| |
We want to be able to transfer all
source artifacts in a single transaction
|
|
|