ManageIQ/miq_bot

Travis stalled build detector should restart a stalled build at most 3 times on the same pull request

Open

#82 opened on Jun 25, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Ruby (38 forks)auto 404
bughelp wantedpinned

Repository metrics

Stars
 (16 stars)
PR merge metrics
 (PR metrics pending)

Description

From: https://github.com/ManageIQ/manageiq/pull/3258

screen shot 2015-06-25 at 9 27 38 am

Since we don't delete old comments on the pull request (by design), we could check to see how many comments on the PR begin with the tag: <stalled_finished_job /> and skip the PR entirely if there are already 3 comments.

It's easy to test this by creating a PR with a test that does sleep 60 * 15, it should stall after ten minutes, get restarted, etc. 3 times.

Contributor guide

Research direction
Examine the stalled build detection code and modify it to count existing comments with the tag '<stalled finished job />' on the PR and skip if count >= 3.
Tech stack
ruby
Domain
devopsci cdtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75