An error occurred fetching the project authors.
- 23 Feb, 2017 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 10 Feb, 2017 1 commit
-
-
Lin Jen-Shin authored
This could prevent errors described in: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8970 Everything we're using right now, should be valid of course.
-
- 06 Feb, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 04 Feb, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 25 Jan, 2017 6 commits
-
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
- 05 Jan, 2017 1 commit
-
-
Z.J. van de Weg authored
Until this commit, GitLab would check if the URL in your .gitlab-ci.yml would be valid and adressable. However, this approach is rather limited. To begin, the URL couldn't be http://example:$PORT/my-project, as the PORT value would be interpolated after checking if the URL was valid, which its not. Also this gem will limit the amount of protocols allowed. This commit doesn't check, at all, if the URL is valid. This is now the responsablilty of the user. In my opion this is right, as the user ultimately benefits from a correct URL, but also, its impossible to cover all cases.
-
- 15 Dec, 2016 1 commit
-
-
Lin Jen-Shin authored
So that this would be more consistent with the other variables, which all of them are string based. Closes #25554
-
- 18 Nov, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 18 Oct, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 17 Oct, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 30 Sep, 2016 2 commits
-
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
- 19 Sep, 2016 3 commits
-
-
Kamil Trzcinski authored
Squashed commits: [f9a9315] Use : to test invalid environment name
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
- 07 Sep, 2016 7 commits
-
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
-
- 11 Aug, 2016 1 commit
-
-
Kamil Trzcinski authored
This change simplifies a Pipeline processing by introducing a special new status: created. This status is used for all builds that are created for a pipeline. We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped). This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled. This also allows us to visualise a full pipeline (with created builds). This also removes an after_touch used for updating a pipeline state parameters. Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
-
- 05 Aug, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 03 Aug, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 20 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 19 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 18 Jul, 2016 6 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-