| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Implement build trigger API
This commit implements Build Triggers.
There are changes to API request:
- Due to security advised method to pass trigger token is to use form data
- Advised method to pass variables is to use form data
TODO:
- [x] Implement API
- [x] Implement UI
- [x] Dimitriy and Valery review
- [x] Write specs
- [x] Write documentation
- [x] Job documentation review
See merge request !229
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
- deny all globals that are not hases and doesn't contain script, the script is required now
- verify that script is either string or array of an strings
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Support yaml variables
This MR introduces ability to define variables from YAML.
```yaml
variables:
DB_NAME: postgres
test:
script: echo $DB_NAME
```
The variables are passed using the same API as Secure Variables. The API introduces additional parameter: public. All variables defined in YAML are marked as public. The GitLab Runner when detects public variables will pass them to the services. This makes it easy to fine tune linked services to for example define database name.
```yaml
services:
- postgres
variables:
POSTGRES_DB: gitlab
```
The above example will run [postgres](https://registry.hub.docker.com/u/library/postgres/) and pass POSTGRES_DB to postgres container making it to create `gitlab` database instead of default `postges`.
**Note:** All variables will passed to all service containers. It's not designed to distinguish which variable should go where.
/cc @sytses @vsizov @dzaporozhets
See merge request !227
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Fix service testing
Fixes:
- https://gitlab.com/gitlab-org/gitlab-ci/issues/248
- https://gitlab.com/gitlab-org/gitlab-ci/issues/208
/cc @vsizov
See merge request !221
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commits with [ci skip] have special skipped status
![Screen_Shot_2015-07-30_at_14.02.50](https://gitlab.com/gitlab-org/gitlab-ci/uploads/f200af385679b564cd15d730bd4ccd20/Screen_Shot_2015-07-30_at_14.02.50.png)
+ Commits with [ci skip] are marked as skipped
+ Commits without builds are marked as skipped
Resolution for:
+ https://dev.gitlab.org/gitlab/gitlab-ci/issues/264
+ https://dev.gitlab.org/gitlab/gitlab-ci/issues/266
This requires CE update:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1073
/cc @vsizov @sytses
See merge request !216
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| | |
Rewrite Gravatar URLs if needed in order to have images in different size
|
|/ |
|
|
|
|
|
|
| |
- check if user has manage access to project
- don't cache result of authorized_projects, because it's serialised with User object
- clear user sessions
|
|
|
|
|
|
|
| |
- fixes upgrader script not working with v7.1x versions
- rspec test cases from gitlab for upgrader lib
- rename gitlab to gitlabci
- use real data for gitlabci3 version check
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow to specify flexible list of types in yaml
First part of flexible pipeline build in GitLab CI
Having following `.gitlab-ci.yml`:
```
types:
- test
- deploy
- notify
rspec:
script: "rspec"
rubocop:
script: "rubocop"
staging:
type: deploy
script: "echo deploy"
only:
- master
production:
type: deploy
script: "echo production"
only:
- tags
dockerhub:
type: notify
script: "curl http://docker/hub/web/hook"
downstream:
type: notify
script: "curl http://build/downstream/jobs"
```
GitLab CI will trigger two test jobs in parallel, when finished it will trigged either staging or production, when finished it will trigger dockerhub and downstream in parallel.
The UI (screenshots are not for above YAML):
![Screen_Shot_2015-07-10_at_15.56.26](https://gitlab.com/gitlab-org/gitlab-ci/uploads/1f714b73772cf0d44168fb8e20e35561/Screen_Shot_2015-07-10_at_15.56.26.png)
![Screen_Shot_2015-07-10_at_15.57.19](https://gitlab.com/gitlab-org/gitlab-ci/uploads/fc9f458f2ca517d923a4382466fa99eb/Screen_Shot_2015-07-10_at_15.57.19.png)
TODO:
- [x] Implement in CI
- [x] Specs
- [x] Changelog
- [x] CI tests
- [ ] Documentation
/cc @vsizov @sytses @dzaporozhets
See merge request !198
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
```
types:
- test
- deploy
- notify
rspec:
script: "rspec"
rubocop:
script: "rubocop"
staging:
type: deploy
script: "echo deploy"
only:
- master
production:
type: deploy
script: "echo production"
only:
- tags
dockerhub:
type: notify
script: "curl http://docker/hub/web/hook"
downstream:
type: notify
script: "curl http://build/downstream/jobs"
```
This will trigger two test jobs in parallel, when finished it will trigged either staging or production, when finished it will trigger dockerhub and downstream in parallel.
|
| | |
|
|/ |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make configurable builds_path in application.yml
We have a new option in `application.yml`:
```
gitlab_ci:
builds_path: builds/
```
/cc @marin @vsizov
See merge request !193
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added random salt and hashing to oauth state parameter
This ensures signs state parameter. The generated state is built like this:
```
salt = random_hex(16bytes)
secret = sha256_hex(gitlab_ci_secret + salt + return_to)
state = "salt:secret:return_to"
```
This prevents from faking the state and forcing redirect to provided URL. However this doesn't prevent replay attacks if you know the valid `state` parameter for specific `return_to`. Should we be concerned about it?
/cc @vsizov @jacobvosmaer
See merge request !192
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This ensures that content of state is generated by CI, but doesn't prevent replay attacks on state parameter.
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allow to define per-job allow_failure parameter
It allows to ignore status of specific build when computing status for commit
YAML syntax:
```yaml
rspec:
script: aa
allow_failure: true
```
![Screen_Shot_2015-07-08_at_11.28.53](https://gitlab.com/gitlab-org/gitlab-ci/uploads/0af264f026cac18921aef339bcf41fe2/Screen_Shot_2015-07-08_at_11.28.53.png)
/cc @vsizov @sytses
See merge request !191
|
| |/
| |
| |
| | |
It allows to ignore status of specific job when computed for commit
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
Build trace in file
https://dev.gitlab.org/gitlab/gitlab-ci/issues/272
See merge request !167
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|