8.15 CI Plan

Few ideas:

Be able to have docker images in the projects (no need for gitlab-build-images )
Be able to create a docker image in one stage, test in it the next stage, deploy it the last stage -- IIRC this is not yet possible because it would consume a lot of storage (GC docker can only be done offline?)
Slash commands: /trigger status <ref>

I would finally love to run builds if they are head: https://gitlab.com/gitlab-org/gitlab-ce/issues/8998

Implement pipelines for merge requests with all needed around things (ex. runner improvements): https://gitlab.com/gitlab-org/gitlab-ce/issues/23902

Start enforcing CI limits (one idea for 8.15): https://gitlab.com/gitlab-org/gitlab-ce/issues/23366

Solve technical debt by:

Finalising renames of classes,
Improving Ci::Build#status implementation,
Adding PipelineStage as database object,
Remove Build emails,
Migrate existing build_events to pipeline_events,
Introduce DeploymentsController and allow to show information about deployment (will be needed as part of Terminal support).

https://gitlab.com/gitlab-org/gitlab-ce/issues/23712: Improve duration calculation for pipelines.

I propose to have #24644 (moved) because people are talking about it now #24635 (closed)

All things that didn't go in last release..

Apart from that:

ux wise:

https://gitlab.com/gitlab-org/gitlab-ce/issues/24339

See how we can go and prioritize the following:

https://gitlab.com/gitlab-org/gitlab-ce/issues/24429

If you have some big future planned CI related ux issue, bring it on ;)

perhaps this: https://gitlab.com/gitlab-org/gitlab-ce/issues/18054 (but we should wait perhaps for the new filtering/search functionality.. or just bring the feature with the old filtering or without filtering)

https://gitlab.com/gitlab-org/gitlab-ce/issues/17739 wouldn't be a bad choice

This is one of the most up voted issues in GitLab Runner https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1421

Also the problem I've encountered and was difficult to workaround.

Now since we're sending pipeline emails, a lot of things start popping up...

While I suggest #24644 (moved), it's also important to consider #24846 (closed) and #24896 (closed) (basically the same thing) because it's indeed very confusing to get a pipeline email in those cases. I don't feel not sending an email in those cases would be a good idea, so we need to think about not creating a pipeline in the first place. /cc @adamniedzielski

@ayufan, following your comments, your links (only run on head, enforce limits) both include an element of concurrency management - which has at least 2 tickets #18224 (moved), #20481 (moved). Managing concurrency/limits also helps alleviate the problems described in https://about.gitlab.com/2016/11/22/introducing-review-apps/#comment-3015266832. Because it can ensure one deploy doesn't get splattered half way through by another commit occurring. Would really really love to see concurrency handling added.

On another note, https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5744 was discussed during 8.13, was dropped and appears to have fallen off the radar. linkable line numbers against a completed build output would be a nice touch.

Thanks for all your hard work guys!

In addition to gitlab-org/gitlab-ci-multi-runner#1421, adding tmpfs handling to gitlab-runner would be another nice (hopefully low hanging fruit) option - https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1454.

@halberom I understand, maybe we can solve line numbers in more clever way by building on top of existing solution.

Any chance #24256 (closed) can be looked at for 8.15? It's causing a lot of duplication in my CI jobs because non-predefined variables don't work in environment definitions in CI jobs.

marked the task Add pprof HTTP endpoints to metrics server gitlab-org/gitlab-ci-multi-runner!398 as completed

marked the task gitlab-monitor!27 (merged) as completed

marked the task gitlab-monitor!29 (merged) as completed

marked the task gitlab-org/gitlab-ci-multi-runner!401 as completed

marked the task Create pipeline along with builds in the transation !7742 (merged) as completed

marked the task Rename MergeRequest#pipeline to head_pipeline!7783 (merged) as completed

marked the task Expose some new fields in build entity !7785 (closed), !7818 (merged) as completed

marked the task technical debt Improve handling of statuses (Refine CI statuses): https://gitlab.com/gitlab-org/gitlab-ce/issues/24273 as completed

marked the task Introduce the performance statistics for runners: as completed

changed milestone to %8.16

marked the task Make Mattermost easier to configure: https://gitlab.com/gitlab-org/gitlab-ce/issues/24769 as completed

marked the task Slack Slash commands: https://gitlab.com/gitlab-org/gitlab-ce/issues/22182 as completed

marked the task Enforce CI limits: https://gitlab.com/gitlab-org/gitlab-ce/issues/23366 as completed

marked the task Add CI_BUILD_REF_SLUG: https://gitlab.com/gitlab-org/gitlab-ce/issues/22849 as completed

marked the task Terminal support: #22864 (closed): https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/72 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6770 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7690 as completed

changed milestone to %8.15

Closing this issue as 8.15 is finished.

closed

8.15 CI Plan

Deliverables:

Stretch:

The planned GitLab Runner improvements:

Future proposals

Links

Designs

Child items ...

Activity

Admin message

Admin message

8.15 CI Plan

Deliverables:

Stretch:

The planned GitLab Runner improvements:

Future proposals

Links

Activity