Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-02-05Add cache to the 'compile-assets' and 'gitlab:assets:compile' jobsRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-02-01Only use 2 replicas for nginx-ingress.controllerRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-02-01Don't install Prometheus in Review AppsRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-02-01Fine-tune Review Apps pod resource requestsRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-01-30Pass $CI_COMMIT_TAG as GITLAB_TAG to the CNG triggered pipelinesRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-01-24Introduce echoinfo for informationLin Jen-Shin
2019-01-24Use $CI_COMMIT_REF_NAME for tags in trigger-buildRémy Coutable
Also, pass GITLAB_VERSION and GITLAB_ASSETS_TAG to CNG triggered pipelines. Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-01-24Use $CI_COMMIT_REF_SLUG in review-apps.shRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-01-17[Review Apps] Don't exit when dependable job failsRémy Coutable
The function that retrieves the dependable job is pretty basic and retrieves the first job found with the matching name, but this job can be failed but then successfully retried. In that case, we would exit the depending job even though the dependable job actually succeeded (the second time). Let's simplify things, be optimistic and continue with the depending job even if the dependable job fails. That reverts to the original behavior. Signed-off-by: Rémy Coutable <remy@rymai.me>
2019-01-10Merge branch ↵Rémy Coutable
'55323-review-apps-use-2-replicas-for-the-tiller-deploy-deployment' into 'master' [Review Apps] Use 2 replicas for the `tiller-deploy` Deployment Closes #55323 See merge request gitlab-org/gitlab-ce!23806
2019-01-07Merge branch 'exit-error-if-job-waited-fails' into 'master'Rémy Coutable
Exit `wait_for_job_to_be_done` as error if the job fails See merge request gitlab-org/gitlab-ce!23997
2018-12-31Stop using deprecated argument to `gem`Sean McGivern
`--no-rdoc` and `--no-ri` have been deprecated since RubyGems 2.0: https://github.com/rubygems/rubygems/blob/v2.0.0/History.txt#L43 They were finally removed in a recent release: https://github.com/rubygems/rubygems/pull/2354
2018-12-21Exit as error if job failsMark Lapierre
If a script is waiting for a job to be done and that job fails, exit with an error status so that the script doesn't continue with a prerequisite in an invalid state.
2018-12-19Use 2 replicas for the DeploymentRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-12-18Specify the 'sync' policy for the external-dns deploymentsRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-12-17Run gitlab:assets:compile on qa jobsMark Lapierre
Optionally compiling assets when needed for qa jobs proved unworkable so instead we fall back on compiling them for all qa jobs.
2018-12-17Merge branch 'rs-prepare-build-parity' into 'master'Rémy Coutable
CE-EE parity for prepare_build script See merge request gitlab-org/gitlab-ce!23819
2018-12-14Remove rails 4 support in CI, Gemfiles, bin/ and config/Jasper Maes
2018-12-13CE-EE parity for prepare_build scriptRobert Speicher
This removes EE-only directives in favor of file existence checks.
2018-12-13Remove CREATE_DB_USER variable in prepare_buildRobert Speicher
The last usage of this variable was removed in 0ab6469187285368d9f64f9ec67dbbcfa3e5a901.
2018-12-06[QA] Better retrieve job ID for a retried jobRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-12-05Removed the merge-train scriptYorick Peterse
We're moving the automatic merging logic to a separate repository, so there's no need in keeping this file around. [ci skip]
2018-12-04Automatically merge CE master into EE masterYorick Peterse
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.
2018-11-29Pass GITLAB_REF_SLUG to CNG triggered pipelinesRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-11-28Merge branch '49570-add-review_qa-job' into 'master'Sean McGivern
Add an automatic job to run QA smoke tests against Review Apps Closes #49570 See merge request gitlab-org/gitlab-ce!22853
2018-11-26Override CI_COMMIT_REF_SLUG for QA branchesRémy Coutable
The `gitlab:assets:compile` job isn't run for the QA branches, thus there's no Docker image correspinding these branches in the registry. By overriding `CI_COMMIT_REF_SLUG` to `master` for QA branches, the `fetch-assets` job in the `omnibus-gitlab` pipeline will pull the `master` assets Docker image. Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-11-26Add a manual job to run QA against a Review AppRémy Coutable
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>
2018-11-22Merge branch 'fix-typos-occured' into 'master'Kushal Pandya
Fix typos occured to occurred See merge request gitlab-org/gitlab-ce!23105
2018-11-22Pass GITLAB_REF_SLUG to the Omnibus triggersRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-11-21Merge remote-tracking branch 'origin/master' into fix-typos-occuredHiroyuki Sato
Conflicts: - app/assets/javascripts/ide/stores/modules/pipelines/actions.js - spec/javascripts/ide/stores/modules/pipelines/actions_spec.js
2018-11-15Add BUILD_ASSETS_IMAGE CI variableIan Baum
* Defaults to FALSE * Can be used to disable building/pushing the assets image in the gitlab:compile:assets job
2018-11-15Fix typos occured to occurredHiroyuki Sato
2018-11-14Switch rails 4 to 5 in gitlab-ciJan Provaznik
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.
2018-11-13Ensure we abort the cleanup if release is emptyRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-11-11Disable usage pings in review appsBalasankar "Balu" C
2018-11-09Ensure we create the secrets at the right timeRémy Coutable
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>
2018-11-06Allow to override the gitlab-qa ref for the downstream triggerRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-11-01Use CI_COMMIT_REF_SLUG when building assets imageIan Baum
* Using CI_COMMIT_REF_NAME fails when the branch or tag contains special characters
2018-11-01Merge branch 'gt-update-typos-in-comments-and-specs' into 'master'Achilleas Pipinellis
Fix typos in comments and specs See merge request gitlab-org/gitlab-ce!22683
2018-11-01Fix typos in comments and specsGeorge Tsiolis
2018-11-01Merge branch 'prettify-all-remaining-things' into 'master'Filipa Lacerda
Prettify remaining files with differences in CE and EE See merge request gitlab-org/gitlab-ce!22702
2018-10-31Add prettier to static-analysis jobMike Greiling
2018-10-31Build a docker container storing only the frontent assetsIan Baum
* 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
2018-10-23Add omitted indentation fixIan Baum
2018-10-23Add review app to gitlab-ceIan Baum
* Uses the same supporting code as used in EE * Includes automated cleanup * Install external-dns helm chart to review apps cluster if it isn't already * Adds variables REVIEW_APPS_AWS_SECRET_KEY and REVIEW_APPS_AWS_ACCESS_key * review-apps-ce uses a different cipher
2018-10-22Fix/update prettier scriptMike Greiling
2018-10-22Improve automated Review Apps cleanupRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-10-10Improve the variables passed in trigger-buildRémy Coutable
Make the variable names consistent by following the `TOP_UPSTREAM_SOURCE_*` pattern. Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-10-10Pass 'TOP_UPSTREAM_SOURCE_SHA' in trigger-buildRémy Coutable
This is needed because `GITLAB_VERSION` has a special meaning in `omnibus-gitlab` triggers: this is the GitLab version to build. The problem is that `omnibus-gitlab` also has triggers to run QA for an `omnibus-gitlab` commit, and if we use `GITLAB_VERSION` in that case, the comment would be posted on the GitLab CE/EE commit (stored in `GITLAB_VERSION`), whci hwouldn't make any sense. Thus we need `TOP_UPSTREAM_SOURCE_SHA` to represent the commit on which we want to leave a comment. Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-10-08Improve downstream pipeine trigger classRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>