Skip to content

Run CI/CD pipelines on a schedule Improving UI FE and UX

Resources

UX @dimitrieh FE @brycepj BE @zj

Issue Origin

Issue idea came from: https://gitlab.com/gitlab-org/gitlab-ce/issues/2989

This is basically the %9.2 iteration of CI/CD pipelines on a schedule

Design

  • Moves pipelines scheduling away from triggers in settings to its own subtab in Pipelines => Scheduling
  • Triggers in settings changes back to its old form (before it had schedules)
  • Variables support
  • Hides cron field when other radio option preset is selected
  • Current time zone detection (via location?) (if too hard leave it out, but its very nice and saves time)
  • Timezone format can be found here http://stackoverflow.com/questions/1727077/generating-a-drop-down-list-of-timezones-with-php
  • clicking Cron syntax will open up a new tab linking to the Wikipedia page https://en.wikipedia.org/wiki/Cron
  • take ownership must be in there (same as with triggers.. as it uses triggers in the background?) (They need to own it because pipelines trigged on the schedule need to run as somebody to inherit project authorizations for submodules, registry images, etc.)

New_pipeline_menu_Copy_4

New_pipeline_menu_Copy_9

image

Target search works like: Artboard

Illustration: illustration_scheduled_pipelines.svg illustration_scheduled_pipelines.svg

Jobs / pipeline list tags should but updated as well:

img

  • Api triggers: Triggered
  • Scheduled triggers: Scheduled

extra notes:

  • "last triggered" column should not be displayed
  • On the edit page at the bottom we should provide a active/nonactive checkbox like:

image

What do you mean exactly with GitLab cron? I don't think we need to re-event the wheel :) Can we link to an external link? We have a couple of "official" options:

@axil Sounds good to me! (Can you add the link you choose to the issue description?) also see https://gitlab.com/gitlab-org/gitlab-ce/issues/30882#note_28093611

updating issue description

Next iterations could include

Related issues

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

CC/Call to actions