- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan 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.
-
- 14 Nov, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 17 Oct, 2016 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 06 Oct, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 19 Sep, 2016 8 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
Environments that can have a URL with predefined CI variables.
-
- 29 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 10 Jul, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-