Rename "Builds" to "Pipelines", "CI/CD Pipelines", or "Jobs" everywhere
Summary
We use the word Builds in a few places where it's not clear to the reader what is really meant. We should use the term "CI/CD Pipelines" whenever we are discussing the entire pipeline, or the shorter version "Pipelines" when we don't have enough room (such as the main menu. When referring to the individual builds, we should use "jobs" instead. Yes, that is conflating the job definition and the instance of an individual job run, but that distinction isn't important and the simplicity gained is valuable.
For backstory: CI matches our current product name and is partially accurate, but Pipelines is becoming a common term for next generation CI/CD. Until Pipelines become completely common, we'll use "CI/CD Pipelines" to help people with the transition. Lastly, the product itself should be called "GitLab CI/CD" since it is no longer just about CI. "GitLab CI/CD Pipelines" just doesn't feel right though.
| Where | Current | Change to | Image |
|---|---|---|---|
| Settings > CI/CD Pipelines | "Build Status" | Pipeline status | link |
| Settings > Runners | "Runner is active and can process any builds" | Runner is active and can process any jobs | link |
| Settings > Runners | "Runner is paused and can process any builds" | Runner is active and can process any jobs | link |
| Settings > Runners | "To start serving your builds you can either add specific Runners you your project or use shared Runners" | To start serving your jobs you can either add specific Runners you your project or use shared Runners | link |
| Settings > Integrations | "Build Events" | To be removed by @godfat | link |
| Settings > Integrations | "This URL will be triggered when the build status changes" | This URL will be triggered when the job status changes | link |
| Settings > Integrations > Project Services | Description of external services | link | |
| Settings > Edit Project > Export Project | "Build traces and artifact" | Job traces and artifact | link |
| Settings > Edit Project > Sharing & Permissions | "Builds" | CI/CD or Pipelines | link |
| Settings > Edit Project > Merge Requests | "Only allow merge requests to be merged if the build succeeds Builds need to be configured to enable this feature. " | Only allow merge requests to be merged if the pipelines succeeds (CI/CD or Pipelines) need to be configured to enable this feature | link |
| Settings > Triggers | "Pass build variables" | Pass job variables | link |
| GitLab EE Settings > Mirror Repository | "Trigger builds for mirror updates" | Trigger pipelines for mirror updates | link |
| Pipelines > Pipeline Submenu | "Builds"" | Jobs | link |
| Pipelines > Get started with pipelines | Get started with pipelines help page | stays the same | link |
| Pipelines show view | "Builds" tab | "Jobs" | link |
| Builds List | "Get started with Builds" | "Get started with CI/CD Pipelines" | link |
| Builds List | "No builds to show" | "No jobs to show" | link |
| Builds List > Build column | "Builds" | "Jobs" | |
| Builds show view > header and sidebar | "Build" | "Job" | link |
| Graphs > Continuos Integration | Pipelines | link |