- 07 Sep, 2017 4 commits
- 23 May, 2017 1 commit
-
-
Mathieu Giraud authored
See #1847.
-
- 10 May, 2017 1 commit
-
-
Ryan Herbert authored
This reverts commit 25c2c31a. See #2403
-
- 02 May, 2017 1 commit
-
-
Ryan Herbert authored
-
- 28 Apr, 2017 2 commits
-
-
Ryan Herbert authored
-
Ryan Herbert authored
-
- 10 Apr, 2017 1 commit
-
-
Mikaël Salson authored
With duplicate job names only one of the duplicate will be run. This prevented the review environments to be deployed.
-
- 03 Apr, 2017 1 commit
-
-
Mikaël Salson authored
Deploy to $PROD_CLIENT_SERVER where the SSH config is as is: Host app.vidjil.org StrictHostKeyChecking no UserKnownHostsFile=/dev/null User = bonsai-ci IdentityFile = ~/.ssh/bonsai-ci
-
- 30 Mar, 2017 2 commits
-
-
Mikaël Salson authored
-
Mikaël Salson authored
For web application features that target both ther client and the server
-
- 24 Mar, 2017 1 commit
-
-
Mathieu Giraud authored
-
- 23 Mar, 2017 14 commits
-
-
I'm not sure that's necessary, but I prefer having consistent restrictions for the two environment-related jobs.
-
This is not really documented but it seems that removing the prefix prevents Gitlab from realising that an environment has actually been deployed. See vdj#370
-
-
-
Taken from the Jenkins Vidjil-browser-functional job
-
-
-
-
-
-
As server configuration may change depending on server, the SSH client was configured directly on the server rather than on the .gitlab-ci.yml file. Example: Host vda.vidjil.org StrictHostKeyChecking no UserKnownHostsFile=/dev/null IdentityFile = ~/.ssh/bonsai-ci
-
According to the documentation <https://docs.gitlab.com/ce/ci/yaml/#stages>: “Jobs of the same stage are run in parallel”. Therefore a stage test_unit seems to make sense where all unit tests would be launched in parallel.
-
Mathieu Giraud authored
-
Mathieu Giraud authored
-