Monitoring product status and repository health

CloudBees platform for SDM is a preview, with early access for select preview members. Product features and documentation are frequently updated. If you find an issue or have a suggestion, please contact support@cloudbees.com.

Once you have created products and associated repositories, then you can use CloudBees platform for SDM to:

  • Visit the product Overview regularly (daily) to identify any repositories that need your attention and take actions required to keep the product and its repositories healthy.

  • Visit the product Pull requests screen regularly to identify pull requests that are blocking delivery of product features and fixes.

Checking overall repository health

Pull request issues provide an indicator of repository health. Using the product Overview, you can identify repositories that require attention.

To check the overall repository health:

  1. From the Product hub, select a product.

  2. Select a repository name to view a filtered list of the pull requests for that repository.

Status labels

Status labels provide an immediate indicator of issues that need attention. These labels are used on Overview and Pull requests screens.

Any repository or pull request that needs attention has a status label. These labels range from severe, such as builds failing, to minor, such as ready to merge. Each label indicates that some action is required.

Status labels on Overview show the number of active issues for each label; labels used on Pull requests do not.

Status labels are color-coded according to the severity of the issue. These colors correspond to the status label sorter, the color-matched circles in the upper right of the screen. The colors are explained in tooltips visible when hovering over each of the circles:

  • Red: Needs immediate attention. Work is blocked.

  • Yellow. Needs attention soon. Work might be blocked.

  • Green: Requires action. Work is not blocked.

Label Label color Screen Why it appears What it means

Build failing

Red

Overview and Pull requests

A test or build for the pull request is failing.

Notify an engineer to address the issues.

Reviewer needed

Red

Overview and Pull requests

A pull request needs to be reviewed.

Assign a reviewer.

Failure on master branch

Red

Overview

A test or build is failing on the master branch. This label applies only at the repository level and not to pull requests.

Notify an engineer to address the issues.

Merge conflict

Red

Overview and Pull requests

A pull request has a merge conflict and can not be merged.

Investigate the activity and notify the owner of the PR.

Open for more than 24 hours

Yellow

Overview and Pull requests

A pull request has been open for more than 24 hours.

Investigate the activity.

Open for more than 10 days

Yellow

Overview and Pull requests

A pull request has been open for more than 10 days.

Investigate the activity.

Stalled activity

Yellow

Overview and Pull requests

A pull request has not been updated or has not had activity for 24 hours.

Investigate the pull request.

Ready to merge

Green

Overview and Pull requests

A pull request is approved but has not been merged.

Merge the pull request.

Monitoring pull requests

You can use the product Pull requests to view a list of open pull requests, the associated repository, time last updated, time created, who created the pull request, and any status labels.

Each column of the table can be sorted by clicking on the column heading. Refer to the getting started section for additional suggestions.

To monitor pull requests:

  1. From the Product hub, select a product.

  2. In the left menu, select Pull requests.

  3. Select a color icon to filter the list based upon status label color.

  4. Select the same color again to remove the filter.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.