Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Merge requests
  • !2142

Add more explicit documentation around Repeatable Job configurations

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Administrator requested to merge github/fork/cincodenada/patch-3 into develop Aug 25, 2021
  • Overview 4
  • Commits 3
  • Pipelines 0
  • Changes 1

Created by: cincodenada

I've done my fair share of puzzling over repeatable jobs and have been reading through related issues, and gave a swing at more explicitly explaining the expected behavior of these jobs, and pointing folks in the right direction from various methods that could be construed as operation on Repeatable Job configurations but don't.

I noticed these docs had started to refer to Repeatable Job configurations to distinguish them from the delayed jobs created by those configurations, and I think that is good language, and expanded usage of that as well.

This was spurred by my running into unexpected behavior around job ID's being unique, which is part of what I've made explicit in the new description.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/cincodenada/patch-3