delta/gitlab/gitlab-ce.git/scripts, branch refactor-trigger-build-script

Move the trigger-build script into one location to serve both omnibus and cloud-native triggers.

2018-06-14T14:31:32+00:00

Add CI job to check Gemfile.rails5.lock

2018-06-12T11:23:58+00:00

Follow Rubocop for scripts/prune-old-flaky-specs

2018-06-01T06:30:10+00:00

Eliminate constants warnings by:

2018-06-01T05:46:46+00:00

* Replace `require` or `require_relative` with `require_dependency`
* Remove unneeded `autoload`

Merge branch 'dz-no-ee-check' into 'master'

2018-05-22T16:26:30+00:00

Add check for top-level ee directory in CE repo

Closes #46239

See merge request gitlab-org/gitlab-ce!19062

Update no-ee-check with rubocop recommendation.

2018-05-22T15:35:51+00:00

Signed-off-by: Dmitriy Zaporozhets

Add check for top-level ee directory in CE repo

2018-05-21T11:52:45+00:00

Signed-off-by: Dmitriy Zaporozhets

Merge branch 'rc/improve-single-script-jobs-ci-config' into 'master'

2018-05-21T11:03:17+00:00

Improve the single-script jobs CI config

See merge request gitlab-org/gitlab-ce!19040

Improve the single-script jobs CI config

2018-05-21T09:30:44+00:00

Signed-off-by: Rémy Coutable

Build cloud native images on tags

2018-05-17T22:17:53+00:00

When on a tag, trigger a multi-project pipeline in the CNG repostiory.

Opting for a trigger rather than an addition to our release-tools
project for a few reasons:

- The Dockerfiles in the CNG image repo change infrequently, and as a result
I don't feel the need/overhead for stable branches in that repo at this time
- My intent with the CNG repo, is that once stable, the Dockerfiles
would actualy move to their component projects, to be versioned with the
code they are building
- It is likely that we will want to followup with a manually triggered package
for branches for devs, and possibly review apps, so it made sense to
build the CNG ci jobs to accept this sort of pipeline.