Skip to content

Design Artifact: Improve discoverability of Auto DevOps

If Repo is blank, we show a line of text starting in 10.6:

You can automatically build and test your application if you enable Auto DevOps (Beta) for this project. You can automatically deploy it as well, if you add a Kubernetes cluster. Learn more about Auto DevOps (Beta)

This line is buried in a large wall of text when creating new project

Screen_Shot_2018-02-21_at_9.29.53_AM

If repo is not blank, we show the Auto DevOps banner, but only if the following criteria are met:

  • User must have the right permissions (be at least a master) &&
  • Project does not have .gitlab-ci.yml &&
  • Project has Auto DevOps disabled &&
  • Instance has disabled Auto DevOps &&
  • project doesn't have a deployment service configured

Screen_Shot_2018-02-21_at_9.30.16_AM

Proposal

Auto DevOps is the new workflow we are promoting. It should be a first class feature that users know exist. Redesign the project overview page to highlight Auto DevOps as a feature. Keep copy to a minimum to avoid a large wall of text that users glance over. Copy should briefly describe what Auto DevOps is, highlighting why users should take advantage of it.

The criteria used to determine whether or not we show this information should be reevaluated.

Reevaluate other CTAs on this page, like adding a new file when the repo is blank. Determine what should be first class and what should not be.

Edited by Daniel Gruesso