- 07 Feb, 2019 1 commit
-
-
Daniel Gerhardt authored
-
- 17 Dec, 2018 2 commits
-
-
Rémy Coutable authored
Don't allow Danger to fail in CI any more Closes gitlab-org/release/framework#21 See merge request gitlab-org/gitlab-ce!23695
-
Clement Ho authored
Disable docs lint internal_links check Closes #55038 See merge request gitlab-org/gitlab-ce!23665
-
- 12 Dec, 2018 1 commit
-
- 07 Dec, 2018 2 commits
-
-
Stan Hu authored
This check never worked once the global navigation changes were rolled out in https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/362. The global nav will ALWAYS include /ce and /ee links, and the CE and EE repos will never include documentation for both. gitlab-docs now expects the documentation to be in the following directories: * /tmp/gitlab-docs/ce (CE) * /tmp/gitlab-docs/ee (EE) * /tmp/gitlab-docs/omnibus (Omnibus) The problem is that the CE and EE repos will only include one of the first two. Let's disable this check until https://gitlab.com/gitlab-com/gitlab-docs/issues/305 is resolved. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55038
-
Stan Hu authored
This check never worked once the global navigation changes were rolled out in https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/362. The global nav will ALWAYS include /ce and /ee links, and the CE and EE repos will never include documentation for both. gitlab-docs now expects the documentation to be in the following directories: * /tmp/gitlab-docs/ce (CE) * /tmp/gitlab-docs/ee (EE) * /tmp/gitlab-docs/omnibus (Omnibus) The problem is that the CE and EE repos will only include one of the first two. Let's disable this check until https://gitlab.com/gitlab-com/gitlab-docs/issues/305 is resolved. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55038
-
- 06 Dec, 2018 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 05 Dec, 2018 2 commits
-
-
Yorick Peterse authored
Apparently disabling it by checking for a variable doesn't actually disable it. [ci skip]
-
Winnie Hellmann authored
-
- 04 Dec, 2018 5 commits
-
-
ddavison authored
-
Mek Stittri authored
-
Yorick Peterse authored
It appears that for some jobs (https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/129705025 for example) we process a range of commits far greater than necessary, which can lead to commits getting reverted that were merged a long time ago. [ci skip]
-
Yorick Peterse authored
This sets up GitLab CI to automatically push CE master changes into EE master, or revert them if the changes cause merge conflicts. The CI configuration contains a single job to do this: `merge:master`. This job is executed for every push to master, and periodically using a CI schedule. The periodic job is necessary because incremental jobs may not be able to revert commits if newly added commits depend on these commits. By re-running the job periodically (including all changes since a large enough time frame), we can ensure that such commits are also reverted (if they still conflict at that time). The job runs in its own "merge" stage, _after_ the build and prepare stages, but _before_ running the tests. This ensures that randomly failing tests won't prevent code from being merged into EE. Running the stage after the "prepare" stage reduces the chances of the job reverting CE changes just because it ran before a corresponding EE MR was merged into EE master.
-
DJ Mountney authored
For CE on dev.gitlab.org
-
- 29 Nov, 2018 1 commit
-
-
Rémy Coutable authored
Also, enable debug mode. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 26 Nov, 2018 1 commit
-
-
Rémy Coutable authored
1. Renames review to review-deploy. 2. Renames stop_review to review-stop. 3. Adds a build-qa-image job to the prepare stage and save the QA Docker image as artifact (example: https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/120967019). 4. Adds a manual review-qa job to the test stage to run QA tests against the Review App (example: https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/120967238). 5. Make the review-deploy job plays the review-qa job as soon as the Review App is deployed (example: https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/120988775). 6. Updates the Review Apps documentation accordingly. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 23 Nov, 2018 1 commit
-
-
Achilleas Pipinellis authored
-
- 22 Nov, 2018 2 commits
-
-
George Tsiolis authored
-
George Tsiolis authored
-
- 20 Nov, 2018 1 commit
-
-
Robert Speicher authored
Ordinarily it would get the `gitlab-org` tag from `dedicated-no-docs-pull-cache-job`, but adding the `docker` tag overwrites rather than inherits, so this job has been running on the underpowered hardware of the shared runners rather than our dedicated runners. We're also adding a `high-cpu` tag, which doesn't currently do anything but will be useful for targeting a runner specifically for this job.
-
- 16 Nov, 2018 2 commits
-
-
Winnie Hellmann authored
-
Robert Speicher authored
-
- 15 Nov, 2018 3 commits
-
-
Ian Baum authored
* Defaults to FALSE * Can be used to disable building/pushing the assets image in the gitlab:compile:assets job
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Lukas Eipert authored
-
- 14 Nov, 2018 5 commits
-
-
Stan Hu authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54059
-
Stan Hu authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54059
-
Lukas Eipert authored
-
Jan Provaznik authored
-
Jan Provaznik authored
CI jobs will be triggered both with rails 4 and 5 to make sure we keep backward compatibility if it turns out we have to switch back to rails 4. Rails 4 jobs are not allowed to fail for now, these jobs will be removed in a follow-up MR next cycle.
-
- 13 Nov, 2018 3 commits
-
-
Ian Baum authored
* Don't need to specify stage as it is inherited from the job template
-
Ian Baum authored
* The job depends on asset image created as part of the gitlab:assets:compile job. https://gitlab.com/charts/gitlab/issues/897
-
Stan Hu authored
Attempt to update google-protobuf for migration-paths Because the one we were using aren't compatible with Ruby 2.5.3, and it'll be troublesome to switch Ruby. Upgrading google-protobuf will be much easier. All of them will need to be updated for Ruby 2.5.3 We remove oj because we don't really need it and it doesn't compile on 2.5.3 with that version. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/41825
-
- 12 Nov, 2018 1 commit
-
-
Lukas Eipert authored
-
- 10 Nov, 2018 1 commit
-
-
Lukas Eipert authored
-
- 09 Nov, 2018 1 commit
-
-
Rémy Coutable authored
In `deploy`, if the previous deployment failed, we delete/cleanup all the objects related to the release, including secrets. The problem is that if we create the root password before that, it will be then recreated during the deploy with a random value! By creatigng the secret just before actually deplying a new release, we ensure that it won't be overriden. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 31 Oct, 2018 1 commit
-
-
Ian Baum authored
* Run as part of gitlab:assets:compile job * Will be used by omnibus-gitlab and the CNG images to avoid compiling multiple times https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22235
-
- 30 Oct, 2018 1 commit
-
-
Marcel Amirault authored
-
- 25 Oct, 2018 1 commit
-
-
Marin Jankovski authored
-
- 24 Oct, 2018 1 commit
-
-
Lin Jen-Shin authored
They're no longer used and have no effect
-