Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Community Edition
GitLab Community Edition
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 13,992
    • Issues 13,992
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 803
    • Merge Requests 803
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Community EditionGitLab Community Edition
  • Merge Requests
  • !10533

Merged
Opened Apr 07, 2017 by Kamil Trzciński@ayufan0 of 9 tasks completed0/9 tasks
  • Report abuse
Report abuse

Add "engineering" UI for Pipeline Schedule

What does this MR do?

We merged this awesome MR, but it was only backend change. This MR brings very simple engineering UI.

It does expose scheduled triggers only when editing page. It is hidden, because we give us a right to break that in %9.2 when we start working on better UI.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Screenshots (if relevant)

Screen_Shot_2017-04-07_at_14.55.33 Screen_Shot_2017-04-07_at_14.55.12

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Branch has no merge conflicts with master (if it does - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

  • Discussion 66
  • Commits 19
  • Pipelines 7
  • Changes 16
Sean McGivern
Assignee
Sean McGivern @smcgivern
Assign to
9.1
Milestone
9.1
Assign milestone
Time tracking
2
Labels
CI/CD [DEPRECATED] Stretch
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ce!10533

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.