| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add order option to projects API call
https://dev.gitlab.org/gitlab/gitlab-ci/issues/222
See merge request !101
|
| | | |
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Doc: Migrating to packaged CI
https://dev.gitlab.org/gitlab/gitlab-ci/issues/116
See merge request !100
|
| | | |
|
| | | |
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Storing runner info
https://dev.gitlab.org/gitlab/gitlab-ci/issues/223

See merge request !98
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| |\ \
| | | |
| | | | |
Updated copyright to 2015
|
| |/ / |
|
|\ \ \ |
|
| |\ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Backup/Restore && Documentation
https://dev.gitlab.org/gitlab/gitlab-ci/issues/116
I created MR here because it looks like Gitlab.com sidekiq does not work there.
See merge request !154
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | | |
Remove project ID from dashboard for public projects
See merge request !99
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added Sidekiq config...
I added a config file for Sidekiq for regulating the amount of threads.
See merge request !70
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
changelog
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
More explicit permission error for developers
https://dev.gitlab.org/gitlab/gitlab-ci/issues/226
See merge request !97
|
|/ / |
|
| |
| |
| |
| | |
necessary.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Improved email templates
Fixes https://dev.gitlab.org/gitlab/gitlab-ci/issues/215
See merge request !95
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add user permissions matrix
https://dev.gitlab.org/gitlab/gitlab-ci/issues/127
# Users Permissions
GitLab CI relies on user's role on the GitLab. There are three permissions levels on GitLab CI: admin, master, developer, other.
Admin user can perform any actions on GitLab CI in scope of instance and project. Also user with admin permission can use admin interface.
| Action | Guest, Reporter | Developer | Master | Admin |
|---------------------------------------|-----------------|-------------|----------|--------|
| See commits and builds | ✓ | ✓ | ✓ | ✓ |
| Retry or cancel build | | ✓ | ✓ | ✓ |
| Remove project | | | ✓ | ✓ |
| Create project | | | ✓ | ✓ |
| Change project configuration | | | ✓ | ✓ |
| Add specific runners | | | ✓ | ✓ |
| Add shared runners | | | | ✓ |
| See events in the system | | | | ✓ |
| Admin interface | | | | ✓ |
See merge request !93
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove redundant header
https://dev.gitlab.org/gitlab/gitlab-ci/issues/193
See merge request !94
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update the build script example used by GitLab B.V. to support both docker and shell executors.
Updated build examples for GitLab CE to be able to used with either Docker or regular shell executors.
See merge request !92
|
| | | |
| | | |
| | | |
| | | | |
and shell executors.
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove project IDs from dashboard
https://dev.gitlab.org/gitlab/gitlab-ci/issues/225
See merge request !91
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Clean up project advanced settings. Migrate from gitlab_url to path
https://dev.gitlab.org/gitlab/gitlab-ci/issues/218
See merge request !90
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Update guide from 7.9 -> 7.10
See merge request !89
|
|/ / / |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add HipChat Notification Service
My company is looking for a secure, private, stable and hopefully less-expensive alternative to our existing GitHub & Jenkins setup, and is currently focused on GitLab and GitLab CI after trying a number of other solutions. The biggest hurdle is integrations.
I saw that GitLab CI was lacking a service to notify HipChat of builds, and in my search to see if there was a workaround I saw [someone ask about it](http://feedback.gitlab.com/forums/176466-general/suggestions/5350117-gitlab-ci-should-push-notifications-to-configured), and figured it just hadn't been done yet. So, I did it.
* Move existing Slack service spec into a subdir, mirroring /app
* Wire up HipChat service to the project and services controller.
* Split the message building into own class.
* 'namespace' room and token variables.
* Enforce v2 client (bug in HipChat gem v1.5.0. fixed in 1.5.1). Note
that I'm using the same version string as GitLab-CE, for shared
installations. This does prevent 'old' room tokens from being reused.
'v1' is more compatible, but there is rumblings about finally deprecating
it and moving to v2 only on their GitHub issue tracker for this gem.
* Defer execution to a notifier worker, like the Slack service.
* Ensure passing specs (basically a Slack service spec copy, fwiw)
* Added change to the CHANGELOG
I'm not sure exactly how your feedback's "Accepting Merge Requests" tag is supposed to work, but I'm happy to learn and change my contribution procedure if anything is wrong here. Thanks!

See merge request !83
|