jakedt
|
13dea98499
|
Prepare the build worker to support multiple tags and subdirectories. Change the build database config to accept a job config object instead of breaking out the parameters into independent blocks.
|
2014-02-24 16:11:23 -05:00 |
|
jakedt
|
4b0f4c0a7b
|
Handle the case of empty repositories in the trigger.
|
2014-02-24 14:12:54 -05:00 |
|
jakedt
|
d861f9b646
|
Add some code for finding Dockerfiles in the repository.
|
2014-02-24 13:56:21 -05:00 |
|
jakedt
|
86e93a2c0f
|
Write triggers are successfully installing on GitHub, noice!
|
2014-02-21 17:09:56 -05:00 |
|
jakedt
|
a6400171b3
|
First stab at implementing token.activate.
|
2014-02-21 16:02:31 -05:00 |
|
Joseph Schorr
|
5519d93a64
|
Get UI for activating github build triggers in place and working. Note that the actual server-side activation is still not done (but the proper method is invoked)
|
2014-02-20 18:57:49 -05:00 |
|
jakedt
|
9e426816a5
|
Pass trigger information on build status. Set up a trigger for the sample building repository. Allow to list the builds started from a trigger. Protect the callback with the proper auth for creating a trigger on a repo.
|
2014-02-19 16:08:33 -05:00 |
|
jakedt
|
f60f9eb62a
|
Properly connect the github push webhook with the build worker. Still need to resolve the archive format.
|
2014-02-18 18:09:14 -05:00 |
|
jakedt
|
b5d4919364
|
Split out callbacks into their own blueprint. Add build trigger DB information and connect it with some APIs. Stub out the UI to allow for generation of triggers. Split out the triggers into a plugin-ish architecture for easily adding new triggers.
|
2014-02-18 15:50:15 -05:00 |
|