| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|\
| |
| | |
Removed deprecated API behaviour
|
| |
| |
| |
| | |
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Only update trace when trace is given
|
| |
| |
| |
| |
| |
| | |
Fixes #295
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
|\ \ |
|
| |/
| |
| |
| | |
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Implemented api for project jobs with working tests and updated doc
The rest API allows you to manipulate a project on gitlab-ci but there is no way to manipulate build jobs through the api.
I tested it, implemented truly working tests & updated documentation
http://feedback.gitlab.com/forums/176466-general/suggestions/7068630-expose-the-job-api-to-the-rest-api
See merge request !39
|
| |
| |
| |
| | |
Implemented tests and updated documentation
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
| | |
|
| | |
|
| |
| |
| |
| | |
This reverts commit 0d39bfa32967c5f2794bdf30d088b74a78fd54c2.
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Migrate E-mail notification to Services menu
As discussed earlier e-mail notifications lives now under Services menu.
Let me know if this is right direction.
I think now that maybe I shouldn't migrate email_add_committer and email_recipients to MailService and instead use parameters from Project. What guys do you think?
Tests results are here:
https://semaphoreapp.com/ayufan/gitlab-ci/branches/topic-settings-email
See merge request !30
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
This silences another cron error with duck tape.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
As an administrator, it is not interesting for me to get emails from
GitLab CI that look like:
```
.
.
.
.
```
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
API for webhooks registering
Simple API method for creating new WebHooks for specified Project.
P.S. Sorry for not squasing commits, they were already pushed.
See merge request !11
|
| | | |
|
| | | |
|
|\ \ \ |
|
| |\ \ \
| | |/ /
| |/| | |
Changed sudo by su -c
|
| | | |
| | | |
| | | | |
See PR #5935 in gitlabhq/gitlabhq for more details
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | | |
Last_build fix
See merge request !99
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | | |
You can provide project token durinng runner regstration and runner will
be created specifically for this project
|
| | |
| | |
| | |
| | |
| | | |
A cron job should be quiet if all goes well. Getting an email that says
'Done' every hour is annoying for administrators.
|
| |/
|/| |
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://gitlab.com/kestred/gitlab-ci into kestred/gitlab-ci-enhancement/separate-commits-from-builds
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
CHANGELOG
app/models/build.rb
app/services/create_build_service.rb
db/schema.rb
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is an entirely non-user facing change which prepares GitLab CI for future support of Parallel Builds.
See https://about.gitlab.com/2013/12/19/gitlab-ci-with-parallel-builds-and-deployments/.
These changes specifically avoid changing the supported API or changing any of the website views.
Changes to the website views will come in tandem with future features like "Multiple build scripts".
The supported API won't change as part of any future changes on this vein, to maintain support for the unofficial GitLab CI runners.
This closes the following implementation step:
1. A commit has many builds
Signed-off-by: Kestred <kestred@riotcave.com>
|