Joseph Schorr
039d53ea6c
- Fix initdb
...
- Add ability to specific custom fields for manual running of build triggers and add a "branch name" selector for running github builds
2014-09-30 16:29:32 -04:00
Jake Moshenko
539fc04205
Seek the file pointer to zero since we now use multipart for upload of userfiles, which does not seek automatically.
2014-09-10 17:18:49 -04:00
Joseph Schorr
46d1dc98ce
Make absolutely sure to skip requests without a valid payload
2014-06-19 17:20:43 -04:00
Joseph Schorr
62930aa9b5
Make sure we have a head_commit in the payload from Github
2014-05-16 15:45:13 -04:00
Joseph Schorr
c2ed1a9e52
Add support for skipping Dockerfile builds via the [skip build] or [build skip] message
2014-05-01 15:25:46 -04:00
jakedt
893e5136a0
Make the local userfiles 404 if the file is not there. Remove some extraneous logging from the trigger.
2014-04-16 22:43:57 -04:00
jakedt
be728ceccb
Fix the implementation of local userfiles and switch master_branch to default_branch to match the github api.
2014-04-16 22:35:47 -04:00
jakedt
0827e0fbac
Merge remote-tracking branch 'origin/master' into ncc1701
...
Conflicts:
endpoints/web.py
static/directives/signup-form.html
static/js/app.js
static/js/controllers.js
static/partials/landing.html
static/partials/view-repo.html
test/data/test.db
2014-04-14 19:37:22 -04:00
jakedt
e87ffa20cf
First attempt at making config loadable through string config overrides in an env variable.
2014-04-03 17:31:46 -04:00
Joseph Schorr
7c466dab7d
- Add an analyze method on triggers that, when given trigger config, will attempt to analyze the trigger's Dockerfile and determine what pull credentials, if any, are needed and available
...
- Move the build trigger setup UI into its own directive (makes things cleaner)
- Fix a bug in the entitySearch directive around setting the current entity
- Change the build trigger setup UI to use the new analyze method and flow better
2014-04-02 23:33:58 -04:00
jakedt
e7c20e1052
Add tarball support to the builder and pull github code as a tarball.
2014-03-31 15:40:24 -04:00
Joseph Schorr
6fd2440294
Handle empty GitHub repositories and do not 500 if the repository cannot be read
2014-03-28 15:32:56 -04:00
Joseph Schorr
368a8da7db
- Add data classes for notifications
...
- Add basic API for notifications
- Change the password required to be a notification
2014-03-12 00:49:03 -04:00
jakedt
011490d36d
Refactor a lot of the build create code out into a common method. Add an endpoint for manually starting triggers.
2014-02-25 19:39:43 -05:00
jakedt
b23a7ed130
Extract the top level zipball subdir from the zip file.
2014-02-24 22:57:58 -05:00
jakedt
b094480164
Add code that will allow build triggers to be deactivated or deleted from their services.
2014-02-24 16:36:49 -05:00
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
