Piotr Sarnacki 7317d6b265 Rename current_build sort to current_build_id ... This a quick workaround for sorting by current_build. When the field that we use to sort is the same as one of the associations name API V3 will try to join the association. So in this case it will try to join :current_build, which fails. This needs a better solution, but I want to get this working for now.		2016-06-06 16:40:41 +02:00
..
app	fix the error - it's reporting to Sentry - Yay	2016-05-30 18:07:54 +02:00
enqueue/services	Add permission methods to enqueue_build	2016-05-23 15:07:33 -05:00
v2	try another spot to throw and error	2016-05-30 18:05:25 +02:00
v3	Rename current_build sort to current_build_id	2016-06-06 16:40:41 +02:00
workers	Add an equeue service	2016-05-23 15:07:33 -05:00
app.rb	forgot this and it's not tested	2016-05-30 17:57:48 +02:00
attack.rb	update rakefile to allow heroku deployment, update create.rb with api builds rate limit	2016-03-31 16:54:12 +02:00
instruments.rb	only run Skylight for 20% of the dynos (rounding up if there are less than five)	2015-01-19 14:00:00 +01:00
serializer.rb	Allow to handle settings collections	2014-04-01 12:00:06 +02:00
v2.rb	Move API v2 payload definitions to travis-api from travis-core	2014-03-24 20:25:06 +01:00
v3.rb	add specs, update error names	2016-04-20 14:31:08 +02:00