[Epic] Remove usage of "build"
Description
Meta issue to outline how we can (slowly) kill our (mis)usage of the term "Build".
Background
We use the term inconsistently with other vendors, and this causes unnecessary confusion. Travis and CircleCI, for example, call an entire pipeline run a single "build" whereas we call each job in the pipeline a "build". Furthermore, "builds" is an old term from back when CI was mainly for compiled code where the build was the most important part. With scripted languages and TDD, "tests" are a much more important part of CI. Lastly, we're moving beyond CI and into CD, where the trend seems to be called "Pipelines" (see Atlassian's Bitbucket and Jenkins 2.0 pipelines).
Proposal
- Add Pipeline views anywhere we have Build views
- In Pipeline context, use the term Jobs to refer to each individual run (#25232 (closed))
- Update documentation to refer only to Pipelines and Jobs (https://gitlab.com/gitlab-org/gitlab-ce/issues/27805)
- Add APIs for pipelines
- Add APIs for Jobs (while leaving Builds intact)
- Deprecate Builds APIs
- Rename Builds to Jobs controller (https://gitlab.com/gitlab-org/gitlab-ce/issues/30699)
Additionally, the Builds APIs will be removed when API v3 is removed, but won't be tracked here.
Activity
We were discussing the "build" term in #14133 (closed). I'd also really like to see the renaming happening in the MR widget (see my comment https://gitlab.com/gitlab-org/gitlab-ce/issues/14133#note_4186521).
Milestone changed to %9.0
mentioned in issue #19609 (closed)
mentioned in issue #21677 (moved)
Just for the record, I'm repasting my suggestion from a different ticket, Mark's response, and my comment.
"Builds" because, well, everyone knows what a build is. Developers say "Has the package built?", "Have you triggered the build?", "Damn, you broke the build!", not the pipeline. Then "Jobs" because it's exactly how we call these things in gitlab-ci.yml...
<@markpundsack> I plan on killing usage of the term "build" and focusing on "pipelines" and "jobs".
I love the fact projects are projects in GitLab. That's how devs call it so it's great. Yet the "build" term isn't going anywhere, and developers will use this term even in 20 years as much as they do today. I fail to see anyone saying "damn, you broke the pipeline", "has the package... pipelined?", but I do hear the reasoning. Hopefully people will like the name and pick it up. Thanks.
Mentioned in issue #23205 (closed)
@Nowaker they aren't trying to change the way developers talk...
FWW, I'm no longer thinking we need to wait until 9.0 for any of these tasks, except #7 (closed), removing the builds API. At this point, I think #1 (closed) is complete.
Mentioned in issue #25232 (closed)
mentioned in issue #26259 (closed)
mentioned in issue #26843 (closed)
@markpundsack is it correct that this on is on the plan for 8.17? and should have the milestone be set accordingly?
@dimitrieh The epic be completed until 9.0, but most of the work should be done by 8.17.
@joshlambert @ayufan Can you review the proposal and make sure there are issues for any steps needed in 8.17 (1 through 6 currently)?
mentioned in issue #27135 (closed)
mentioned in issue #25177 (closed)
marked the task In Pipeline context, use the term Jobs to refer to each individual run (#25232 (closed)) as completed
@ayufan Can you confirm the state of the proposal checklist in the description? Specifically that new APIs have been created, old ones deprecated, and the only thing remaining is some final documentation things?
changed milestone to %9.3
@markpundsack I updated a list and added one extra item. Both of them are scheduled for %9.3.
marked the checklist item Update documentation to refer only to Pipelines and Jobs (https://gitlab.com/gitlab-org/gitlab-ce/issues/27805) as completed
added Deliverable label
marked the checklist item Rename Builds to Jobs controller (https://gitlab.com/gitlab-org/gitlab-ce/issues/30699) as completed
