8.11 CI Plan

"Show environments to which a Merge Request is deployed ", which I think is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/19992, could be moved to 8.12.

https://gitlab.com/gitlab-org/gitlab-ce/issues/19991 has moved to 8.12.

@ayufan I think there's a lot of good stuff in this plan, but I can't help but feel like we're not making any progress towards the CI/CD vision. There's a lot of frontend polish of existing features, which is great. But can we also tackle something from the overall direction or towards CI deploys of GitLab.com?

The next step in the Deploy Pipelines section of the vision is:

Link and display cross-commit pipeline (e.g. before and after a merge)

We don't have an issue yet for that specific part, but have the larger issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/17013

An alternative path could be to go towards Multi-project pipelines by tackling first-class triggers. This would help the overall vision as well as help deploys of GitLab.com. In fact, the linking and displaying is mostly about the visuals of the pipeline, whereas triggers is about expanding the use-cases we can handle with pipelines, so could be considered higher priority.

An alternative path could be to go towards Multi-project pipelines by tackling first-class triggers. This would help the overall vision as well as help deploys of GitLab.com. In fact, the linking and displaying is mostly about the visuals of the pipeline, whereas triggers is about expanding the use-cases we can handle with pipelines, so could be considered higher priority.

This seems to too big as for 8.11. We need to spend more time discussing how we want to progress on this.

Link and display cross-commit pipeline (e.g. before and after a merge)

Let's try to follow this path and expose that on backend first and work on frontend then.

mentioned in merge request !5327 (closed)

I was trying to think of some way of moving forward with multi-project pipelines. If we can agree on a simple permission system, like using your existing creds, but creating a new scope that is limited to reads and triggers, then develop a simple first-class trigger system that makes use of that new permission system. It should help with CE/EE/Omnibus pipeline and be the precursor to a full multi-project pipeline.

The problem is that we don't yet have a good proposal, so it's hard to see it as being small enough to get done this release. But maybe we'll get lucky. :)

Or we could move up #19992 (closed) ([Epic] Show deployment activity and current status for merge requests), currently slated for 8.12. It's needed for the idea-to-production vision. It could be manageable if we don't worry about tracking deploys before and after the merge commit.

@ayufan The more I think about it, the more I like focusing on #19992 (closed) for this release. It'll have a nice visual impact, and bring home the value of what we've shipped lately (environments, deployments, and manual actions). It might also help guide thinking about "linking cross-commit pipelines" if we first think about how to know when a PR has been deployed to production after a merge.

If we have to cut some of the things on the list to make room for #19992 (closed), I can live with that. Global pipelines and the API changes don't need to get done this release, for example. I'd suggest cutting the coverage stuff too, but customers have been asking for it, and there's already some WIP, so it would be good to close that out.

I'd really like to keep #18141 (closed) in though.

After conversation with @ayufan:

Pick up #19992 (closed) (with focus on high priority parts, and best efforts for some)
Drop #18054 (moved)
Drop the API changes
Add an issue to think about permissions, but not shipping this release

Add an issue to think about permissions, but not shipping this release

I would love to ship something as part of this issue. We will define steps and maybe we manage to ship a step 1.

Updated description with changes above.

mentioned in issue #14549 (closed)

Marked the task Show user in pipeline view https://gitlab.com/gitlab-org/gitlab-ce/issues/20002 (already implemented) as completed

Marked the task Generate coverage report for whole test suite: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5018 (@ayufan @grzesiek) as completed

@tmaczukin Can you add Runner improvements for mounting repository code within services to the plan?

@grzesiek Added :)

Is there any plan to implement the proper handling of submodules by gitlab-runner? I've seen it mentioned off and on on the planning pages for GitLab CI for the last 6-7 releases or so, but it keeps getting deferred silently. Until then any project that needs submodules requires some boilerplate code in the CI config and deploy key setup for the dependencies.

@jasonroehm Thanks for your interest. There are a few meta challenges we need to resolve first, particularly around permissions. We currently have "Think about permissions and ship some (small) iteration" slated for this release to move this forward. We know this is important, but we haven't yet come to an agreement on how to solve it cleanly.

mentioned in merge request !5595 (merged)

Marked the task Add an URL as a configuration of Environment and show this as part of current deploy status: https://gitlab.com/gitlab-org/gitlab-ce/issues/19527 as completed

Marked the task "CI configuration" button when .gitlab-ci.yml is present: #20101 (closed): !5558 (merged) as completed

mentioned in merge request !5742 (merged)

Marked the task Use badge template instead of using separate images https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5520 as completed

Marked the task Pre-create all builds when processing the pipeline (@ayufan): this is to solved https://gitlab.com/gitlab-org/gitlab-ce/issues/18644 and https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/289: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5295 as completed

Marked the task Format Environments page https://gitlab.com/gitlab-org/gitlab-ce/issues/20059: !5687 (merged) as completed

Marked the task Improve Pipeline processing by using State Machine: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5782 as completed

Marked the task Show current deploy status - Is this SHA currently deployed? https://gitlab.com/gitlab-org/gitlab-ce/issues/19571#note_13246122 (gitlab-org/gitlab-ce!5622) as completed

Marked the task Show deployment activity and current status for merge requests #19992 (closed) as completed

Marked the task Implement test coverage badge using badge templates https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5708 as completed

Marked the task Implement code coverage badge and some other improvements regarding code coverage: #3714 (closed) (@grzesiek) as completed

Marked the task Create pipeline_hooks: https://gitlab.com/gitlab-org/gitlab-ce/issues/20115 (!5620 (merged)) as completed

@ayufan #19992 (closed) isn't fully done. One of the pieces is now slated for 8.12. This issue's description should be updated.

Marked the task Show deployment activity and current status for merge requests #19992 (closed) as incomplete

Thanks @markpundsack I'm updating descrition.

mentioned in commit 30091edf

Marked the task Collapse build tabs: #18516 (closed): !5595 (merged) as completed

Marked the task Show pipelines for merge requests: #18681 (closed): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5485 as completed

mentioned in commit 59fa031e

Marked the task Improve build view to show pipelines: #18141 (closed):!5742 (merged) as completed

mentioned in commit 26730316

mentioned in commit c236ee4d

Marked the task Retry all docker operations in GitLab Runner to increase stability of builds: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/122 as completed

Marked the task Report wall-clock elapsed time rather than cumulative job time (@godfat): #17007 (closed), !5734 (merged) as completed

@ayufan There are 18 issues with the 8.11 milestone (other than this issue) that are still open. 4 are bugs, but what are the rest? Are some in the wrong milestone?

e.g. Looks like we broke out https://gitlab.com/gitlab-org/gitlab-ce/issues/18937, but then didn't put it in this list.

@markpundsack We assumed that we would have time to do #18937 (closed), but we missed a merge window.

We should include that for 8.12, and start getting rid of Builds tab where possible and instead focus on showing a list of Pipelines and maybe a latest pipeline graph.

Marked the task Report wall-clock elapsed time rather than cumulative job time (@godfat): #17007 (closed), !5734 (merged) as completed

Marked the task Fix issue with leaking sockets when using docker executor: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/196: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/185: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/260 as completed

Marked the task Mounting used volumes to all services containers (docker executor): https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/241 as completed

Marked the task Support shared builds volume (docker executor): https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/193 as completed

Milestone changed to %8.12

Milestone changed to %8.11

Status changed to closed

Mentioned in commit nick.thomas/gitlab-ee@c236ee4d

8.11 CI Plan

The key features (includes a Frontend and Backend):

The planned Frontend improvements (@annabeldunstone @hazelyang):

The planned Backend improvements (@ayufan @godfat @grzesiek @tmaczukin):

The planned GitLab Runner improvements (@ayufan @tmaczukin):

The planned documentation/blog posts:

Slipped

Stretch; likely not to happen:

Designs

Child items ...

Activity

Admin message

Admin message

8.11 CI Plan

The key features (includes a Frontend and Backend):

The planned Frontend improvements (@annabeldunstone @hazelyang):

The planned Backend improvements (@ayufan @godfat @grzesiek @tmaczukin):

The planned GitLab Runner improvements (@ayufan @tmaczukin):

The planned documentation/blog posts:

Slipped

Stretch; likely not to happen:

Activity