suzanne.soy/travis-api
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
985 Commits 26 Branches 329 Tags 5.8 MiB
d7c6edec18
Commit Graph

72 Commits

Author SHA1 Message Date
Piotr Sarnacki
d7c6edec18 Bring back ssh key endpoint, but make it configurable 2014-07-29 03:02:54 +02:00
Piotr Sarnacki
9ae3782975 Don't return collections along with simple settings 2014-07-16 18:20:35 +02:00
Piotr Sarnacki
696185e3cd Return repository_id for env vars 2014-07-16 18:14:52 +02:00
Piotr Sarnacki
2e8fc35e13 Properly validate settings 2014-07-15 16:26:24 +02:00
Piotr Sarnacki
fa56e4cfa0 Update code and specs for newest travis-core changes 2014-07-15 16:25:55 +02:00
Hiro Asari
6d3a65b541 Merge branch 'master' into ps-env-vars-in-settings 
Conflicts:
	Gemfile.lock
 2014-06-18 08:38:49 -04:00
Hiro Asari
dae8652279 Merge branch 'master' into ha-feature-remove_log_endpoint 2014-06-17 10:40:30 -04:00
Hiro Asari
9265ac62c9 Merge branch 'master' into ha-feature-remove_log_endpoint 
Conflicts:
	Gemfile.lock
	travis-api.gemspec
 2014-06-17 09:05:05 -04:00
Konstantin Haase
143a9cd071 Revert "removed the branches endpoint" 
This reverts commit f7450cdb6b.
 2014-06-17 14:44:13 +02:00
Hiro Asari
8d4c4488b1 Merge pull request #94 from travis-ci/jk_remove_branches_endpoint 
Remove the branches endpoint
 2014-06-16 11:36:59 -04:00
Hiro Asari
1cf298464a Add RemoveLog service endpoint to jobs/:id/log 
This replaces https://github.com/travis-ci/travis-api/pull/107.
 2014-06-11 13:39:21 -04:00
Piotr Sarnacki
3ef8fab3c6 Add settings endpoint for env_vars 2014-05-23 13:42:22 +02:00
Piotr Sarnacki
360881a888 Remove ssh_keys endpoint 
SshKeys will make sense only on Travis CI Pro
 2014-04-15 11:14:11 +02:00
Piotr Sarnacki
f107d4676e Params in POST and PATCH requests should be fetched from request body 
This also adds missing specs for ssh_keys endpoint
 2014-04-10 14:07:20 +02:00
Piotr Sarnacki
11e814055e Fix specs 2014-04-01 16:52:33 +02:00
Piotr Sarnacki
e9cdef1c9b Add /settings/ssh_keys API 2014-04-01 13:05:25 +02:00
Piotr Sarnacki
400b6ae6ee Add /requests/:id endpoint 2014-03-12 10:50:16 +01:00
Piotr Sarnacki
093831c1a2 Add requests API 
Requests API allows to get the requests from the DB and thus enable
users to have more insight into what's going on in their repositories.
 2014-03-06 19:36:55 +01:00
Hiro Asari
b43568a0f9 Fix Annoation-related specs 
Annotations are now blocked by features, so stub the service to
return true for the cases we expect to get data back from POST
requests
 2014-01-29 14:30:23 -05:00
Hiro Asari
8e1b190725 Require status for updating Annotation and bump travis-core 2014-01-22 09:34:26 -05:00
Hiro Asari
8ce826cda0 Merge branch 'master' into hh-add-metadata-endpoint 
Conflicts:
	Gemfile.lock
 2014-01-20 22:30:35 -05:00
Sven Fuchs
0c6576fec1 Merge pull request #99 from travis-ci/ha-api-gh47-aggregate-cc-xml 
Respond to /repos.xml with CC XML
 2014-01-17 12:50:26 -08:00
Hiro Asari
a622de2a9f Merge branch 'master' into hh-add-metadata-endpoint 
Update Gemfile.lock to point to the updated travis-core PR

Conflicts:
	Gemfile.lock
	lib/travis/api/app/endpoint/jobs.rb
	spec/integration/v2/jobs_spec.rb
 2014-01-17 09:16:41 -05:00
Piotr Sarnacki
e11dfa35cf Fix PATCH repos/:id/settings 2013-12-02 15:36:58 +01:00
Piotr Sarnacki
62a5e602c5 Implement simple repository settings API 2013-12-02 15:36:25 +01:00
Hiro Asari
d31a29e54d Fix grammar in spec description 2013-12-01 20:42:46 -05:00
Piotr Sarnacki
39260c3918 Fix specs after travis-core update 2013-11-28 18:08:39 +01:00
Hiro Asari
362b5d30bf Respond to /repos.xml with CC XML 
See #47
 2013-11-18 16:55:11 -05:00
Hiro Asari
3b20120c72 Accept .atom extension 
And return Atom feed for builds.
Specs look different, because it needs to explicitly handle the common
case where the client sends `Accept: */*`.
 2013-11-11 15:21:14 -05:00
Hiro Asari
8171d3915e Add integration specs for Atom feed 
These rudimentary specs do not test the correctness of
the Atom feed format.
 2013-11-11 11:40:37 -05:00
Josh Kalderimis
f7450cdb6b removed the branches endpoint 
we already have branch info accessible via the repos endpoints, having this at the root level doesn't make sense.
 2013-11-06 01:40:42 +01:00
Josh Kalderimis
342df12b14 remove old workers endpoints 2013-11-04 19:24:17 +01:00
Piotr Sarnacki
f19de9d134 Implement jobs/:id/cancel and builds/:id/cancel endpoints 2013-08-08 14:25:20 +02:00
Henrik Hodne
be2c538d9e Rename metadata => annotations 2013-07-10 16:55:03 -07:00
Henrik Hodne
16a73d9e0b Add PUT /jobs/:id/metadata endpoint 2013-07-09 18:41:47 -07:00
Henrik Hodne
b103a7ccb1 Add GET /jobs/:job_id/metadata endpoint 2013-07-09 18:15:32 -07:00
Piotr Sarnacki
b6a351c766 Convert params['ids'] to array 
Services like find_builds can accept :ids as a param, but it needs to be
an array, string will be passed to find and converted into integer.
 2013-07-09 15:18:31 +02:00
Piotr Sarnacki
29fb7292cb Fix tests 2013-06-13 15:54:19 +02:00
Piotr Sarnacki
be22ff6eda Ensure that we properly handle 404 formats 2013-04-11 14:47:00 +02:00
Andre Arko
6940532994 Ensure proper content type for cc.xml 2013-03-25 16:09:15 +01:00
Konstantin Haase
92be2a3fcd fix test for new autosync 2013-03-20 19:53:38 +01:00
Piotr Sarnacki
705927ff74 Don't error out if xml is requested with something else than repo 2013-03-12 12:08:43 +01:00
Piotr Sarnacki
c0b9a468d6 Forgot to delete one of the tests 2013-03-11 23:58:58 +01:00
Piotr Sarnacki
04bb751b02 When serving image, return proper Last-Modified header 2013-03-11 20:54:24 +01:00
Piotr Sarnacki
36783e6359 Handle chunked=true param in Accept header 2013-02-25 17:28:24 +01:00
Piotr Sarnacki
260c46181d Add hack to allow handling redirect to logs on the client properly. 
This hack is temporary and should be removed when we find better
solution.

TL;DR: we can't handle redirects to S3 using CORS, so in case we want to
get logs from S3 without additional requests to API, we need to return
status that will not be automatically redirected (in this case 204 seems
like the best answer).

Longer rationale:

Old logs are hosted on S3 now and in case log is not available in the
database, we would like to redirect to the archived log. Although S3
support CORS, our use case breaks on some browsers:

  * when request is triggered to /jobs/:id/log and log is archived, api
    returns 302 redirect, Location header points to the log on S3
  * browser transparently redirects to given url, but it sets Origin to
    null, for security reasons
  * "Origin: null" is ok, because we allow every origin by setting
    AllowedOrigin to "*"
  * S3 returns "Access-Control-Allow-Origin: null" header, which breaks
    some browsers (I confirmed it for webkit based browsers)

In order to fix this, S3 would need to return * in
Access-Control-Allow-Origin header or we would need to tell the browser
to not follow redirect. Both solutions are not achiveable.

Another option would be to return log information in job payload - we
could send log_url field which should be either log url on amazon or
null, but in such case we would need to query artifacts table in each
job request. This is something that should be avoided as archived logs
are not frequently requested - slowing down every request to get info
for it would be a waste.
 2013-01-29 03:51:22 +01:00
Piotr Sarnacki
a565522f41 Redirect to full amazon url 
Amazon can't work properly with SSL and CNAME for subdomains. For now we
can use full amazon url.
 2013-01-28 03:43:28 +01:00
Piotr Sarnacki
31371686c9 Redirect to archive logs 2013-01-28 03:04:36 +01:00
Sven Fuchs
7b4712c32c fix after rebase 2013-01-26 20:54:58 +01:00
Sven Fuchs
d441336573 expose logs on /job/:id/log.txt 2013-01-26 20:43:54 +01:00