Henrik Hodne
63155e65b6
Fix link to travis-web
...
Fix #55
2013-03-03 18:27:29 -06:00
Sven Fuchs
7e005aad1b
use travis-core/sf-log-models
2013-02-10 21:30:50 +01:00
Sven Fuchs
b8dfb1cd00
auth PUT to /artifacts/:id
2013-01-30 08:50:27 +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
489a33cbf6
Try 307 redirect on /logs.txt
2013-01-28 19:05:07 +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
b81644acba
comment out put to /artifacts/:id for now
2013-01-26 20:44:04 +01:00
Sven Fuchs
4ea95494de
allow put to /artifacts/:id
2013-01-26 20:44:04 +01:00
Sven Fuchs
d441336573
expose logs on /job/:id/log.txt
2013-01-26 20:43:54 +01:00
Piotr Sarnacki
f2d768080f
Return last builds on each branch for /builds?branches=true
...
This is a hack to fix travis-ci/travis-web#123 easier. A proper solution
would be to refactor how /branches work.
2013-01-26 01:12:47 +01:00
Sven Fuchs
ee11e571b7
pass the api payload type for workers because we now do not return AR scopes any more
2013-01-23 02:44:30 +01:00
Konstantin Haase
1dd3324350
add /users/:id
2013-01-21 12:16:51 +01:00
Sven Fuchs
92a3d17ebf
use travis-core/sf-restart-event
2013-01-17 19:06:34 +01:00
Konstantin Haase
cc2a1cd50e
do not require user scope for /auth/github
2013-01-11 17:48:30 +01:00
Konstantin Haase
3d6defe3b1
do not store token from /auth/github
2013-01-11 16:49:08 +01:00
Konstantin Haase
ada6ee0f2c
fix scope check
2013-01-11 16:20:53 +01:00
Konstantin Haase
e7be49dcb1
fix the payload
2012-12-17 20:22:51 +01:00
Konstantin Haase
f878eee987
fix logging
2012-12-17 20:06:45 +01:00
Konstantin Haase
b3b5476076
first think, then commit
2012-12-17 19:26:58 +01:00
Konstantin Haase
9a1988d586
fix template
2012-12-17 19:22:33 +01:00
Konstantin Haase
f5fdcc41c6
fix token logic
2012-12-17 15:35:35 +01:00
Konstantin Haase
8c8f031259
have travis token added to user payload on the server
2012-12-17 15:13:38 +01:00
Sven Fuchs
c44445d8e2
use the api serializer to serialize a user record
2012-12-17 01:40:16 +01:00
Konstantin Haase
b005047d95
rename token parameter to github_token for /auth/github
2012-12-12 18:30:55 +01:00
Konstantin Haase
44d6c02591
actually check if github sent a token
2012-12-10 15:49:37 +01:00
Konstantin Haase
3d8c9ed914
use localStorage after handshake
2012-12-10 14:03:31 +01:00
Piotr Sarnacki
88363423f4
Fix whitelist auth check for localhost
2012-12-09 23:46:18 +01:00
Konstantin Haase
83e42adc65
that did not work
2012-12-06 16:55:58 +01:00
Konstantin Haase
2250d1ba5c
only send user payload
2012-12-06 16:51:33 +01:00
Konstantin Haase
981a32f877
fix setTimeout
2012-12-06 16:24:37 +01:00
Konstantin Haase
24ea1ca7c0
cheap escape
2012-12-06 16:05:36 +01:00
Konstantin Haase
7b4fe5dab3
no inspect
2012-12-06 15:52:49 +01:00
Konstantin Haase
af1aeb8147
set action and method
2012-12-06 15:40:29 +01:00
Konstantin Haase
afad81f927
Addressable::URI.parse might return nil
2012-12-06 15:34:13 +01:00
Konstantin Haase
ee1f9d899d
set content type
2012-12-06 15:24:46 +01:00
Konstantin Haase
cd9d84783d
fix regex
2012-12-06 15:20:23 +01:00
Konstantin Haase
3b84b83699
post data for targets we know
2012-12-06 15:08:27 +01:00
Konstantin Haase
ac318df762
Merge branch 'master' into rkh-better-login
2012-12-06 14:47:15 +01:00
Konstantin Haase
497eebab94
simplify popup check
2012-12-05 15:10:28 +01:00
Konstantin Haase
811aa47098
rewrite post message login
2012-12-05 14:09:56 +01:00
Konstantin Haase
d3ed96f165
trigger redirect
2012-12-04 14:39:50 +01:00
Piotr Sarnacki
440dacece3
Add endpoints for key regeneration
...
Enpoints are:
POST /repos/:id/key
and
POST /repos/:owner/:name/key
Both versions will replace current ssl key for given repo with the new
one.
2012-12-03 02:54:01 +01:00
Konstantin Haase
a62948b047
make /key public again
2012-12-02 20:39:54 +01:00
Konstantin Haase
5d515f3b8a
enforce v2 for /key
2012-12-02 20:21:19 +01:00
Konstantin Haase
0d7db43c7a
set scope
2012-12-02 19:47:24 +01:00
Henrik Hodne
6f534d388e
Note endpoints that are not yet implemented
2012-11-28 18:10:55 -06:00
Piotr Sarnacki
65637c5731
Add endpoint for getting repo public key
2012-11-26 02:26:34 +01:00
Sven Fuchs
e383193323
renamed service to requeue_request
2012-11-24 14:43:21 +01:00
Sven Fuchs
fcf8768294
it's request_requeue, not requeue_request
2012-11-23 21:23:13 +01:00