AccelerateHS/accelerate

Continuous integration

Open

#385 opened on May 15, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Haskell (830 stars) (112 forks)batch import
help wanted

Description

Now that travis has proper build stages, we should use this for the accelerate-travis-buildbot so that it is only updated when all builds pass.

https://blog.travis-ci.com/2017-05-11-introducing-build-stages

Contributor guide

Tech stack
shell
Domain
ci cd
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.
half day
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
Travis CI configurationshell scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the current Travis CI configuration in the repository (likely .travis.yml in the .travis directory or root). Understand the build stages concept from the provided blog link (https://blog.travis ci.com/2017-05-11 introducing build stages). Then modify the configuration to use build stages so that the accelerate travis buildbot is only updated when all builds pass. The issue has no linked pull requests or recent comments, so no ongoing work is apparent.