| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[ci skip]
|
| |
|
|
|
|
| |
Docs also added.
|
| |
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Add docs for assigning labels/milestone when moving issue
Extends https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3934
See merge request !4069
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Artifacts expire date
What do you think @grzesiek?
The syntax will be simple:
```
job:
artifacts:
expire_in: 7d
```
- [x] Implement `expire_in`
- [x] Check current design of expiry information with @jschatz1 and @markpundsack
- [x] Add tests in GitLab application for a `ExpireBuildArtifactsWorker` and for `ArtifactsController::keep`
- [x] Add user documentation how to use `artifacts:expire_in`
- [x] Prepare GitLab Runner changes to pass `expire_in`: gitlab-org/gitlab-ci-multi-runner!191
- [x] Fix `timeago` with help of @jschatz1
- [x] Merge latest master after builds view changes @iamphill
- [ ] Add Omnibus support for `expire_build_artifacts_worker` cron job
- [ ] Add documentation how to configure `expire_build_artifacts_worker`
This is based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4201.
See merge request !4200
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
- Move ci/api under api/ci
- Clean up builds.md and runners.md
- Replace old links with new ones
- Add CI API links in ci/README.md
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | | |
Closes #18484
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | | |
* Resolves #18015
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `sha` parameter is optional, and when present, must match the
current HEAD SHA of the source branch. Otherwise, the API call fails
with a 409 Conflict and a message containing the current HEAD for the
source branch.
Also tidy up some doc wording.
|
|\ \ \
| |/ / |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Amend jira service api docs [ci skip]
## What does this MR do?
Amends the API documentation for jira service integration
## Are there points in the code the reviewer needs to double check?
No
## Why was this MR needed?
The current documentation omits the username and password parameters
## What are the relevant issue numbers?
## Screenshots (if relevant)
See merge request !4382
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
(default 5min)
|
| | | | |
|
| |/ / |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
fix example urls for (dis)associating runners to projects
See merge request !2993
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Added authentication service for docker registry
This adds a simple authentication service for docker which uses current user credentials to authenticate pulls and pushes.
I have only one concern. Since the `.docker/config` is unencrypted, thus the password for user stored there is unencrypted, maybe we should from the start implement function to generate/provide a separate password just for the purposes of accessing docker registry?
What do you think @jacobvosmaer @sytses @marin?
cc @marin
See merge request !3787
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
# Conflicts:
# config/initializers/1_settings.rb
|
| | | | | | |
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
[ci skip]
|
| | | | |
| | | | |
| | | | |
| | | | | |
Closes #15638
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3749#note_11626427
- Personal access tokens are still a separate entity as far as the
codebase is concerned - they just happen to use the same entry point
as private tokens.
- Update tests and documentation to reflect this change
|
|\ \ \ \ \
| |/ / / / |
|
| | | | |
| | | | |
| | | | | |
This reverts merge request !4030
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
list
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | | | |
|
| |\ \ \ \
| | |/ / / |
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
The user API documentation and the actual implementation were out of sync, missing certain newly introduced fields and beeing inconsistent between certain API definitions. The documentation was changed according the actual latest implementation.
Signed-off-by: Fabio Huser <fabio@fh1.ch>
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Update build triggers API documentation
[ci skip]
* Ensure updated/deleted timestamps are consistent
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
# Conflicts:
# Gemfile.lock
|
| | | |
| | | |
| | | | |
- Parameter validation as ISO8601 format
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
endpoint
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
API: Subscribe and unsubscribe from issues and merge requests
* Closes #6024
This MR is based on !3611, which must be merged first.
See merge request !3615
|
| | | |
|
| | | |
|