| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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

+ 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
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
Rename type to stage
However, make the `type` and `types` as alias for `stage` and `stages`.
/cc @vsizov @sytses
See merge request !222
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix truncate_first_line if message is nil
Fixes https://gitlab.com/gitlab-org/gitlab-ci/issues/255
/cc @jacobvosmaer
See merge request !217
|
| |/ |
|
| | |
|
|/
|
|
| |
Rewrite Gravatar URLs if needed in order to have images in different size
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added Application Settings
This moves some of the settings from application.yml to Admin page.

/cc @sytses @vsizov
See merge request !215
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Do not use image's file name as alternative text
`image_tag` by default uses the image's file name for the img tag's alt
attribute. This is not preferable in many cases. E.g. it clutters the UI
with a long hash string if a gravatar could not be loaded.
To fix this, the `alt` option is set for `image_tag` calls.

See merge request !214
|
| |
| |
| |
| |
| |
| |
| |
| | |
`image_tag` by default uses the image's file name for the img tag's alt
attribute. This is not preferable in many cases. E.g. it clutters the UI
with a long hash string if a gravatar could not be loaded.
To fix this, the `alt` option is set for `image_tag` calls.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Truncate commit messages after subject line in table
Commit messages are now additionally truncated after the first line.
Before, a commit message's body was attached behind the subject which
made messages hardly readable in some cases.

See merge request !213
|
| |/
| |
| |
| |
| |
| | |
Commit messages are now additionally truncated after the first line.
Before, a commit message's body was attached behind the subject which
made messages hardly readable in some cases.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
Fix inline edit runner-description
Fixes: #217
Replaced .show and .hide with .removeClass('hide') and .addClass('hide') (Like done for #192 in MR 177)
See merge request !206
|
| |
| |
| |
| | |
Replaced .show and .hide with .removeClass('hide') and .addClass('hide') (Like done for #192 in MR 177)
|
| | |
|
| | |
|
|/
|
|
|
|
| |
- 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
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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):


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.
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
Use config/secrets.yml to store session secret and database encryption secret
I took the approach that config/secrets.yml is generated when key is not found.
/cc @vsizov @jacobvosmaer
See merge request !195
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use builds_without_retry to calculate average coverage
/cc @vsizov
See merge request !197
|
| |/ |
|
|/
|
|
| |
when clicking on available runner from project's page
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|