Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Add a nightly CI provision test builds #22

Closed
karnowski opened this Issue · 0 comments

2 participants

@karnowski

Motivation

Our current understanding is that Jenkins, the CI build server, is single-threaded and will only build one project at a time. As such, we really want our builds to be faster than 10 minutes. However, provisioning EC2 instances can definitely take longer than 10 minutes. That means we can't test our EC2 provisioning on every commit.

Further, we want to test the provisioning every night even if no git commits have occurred, because so many of the things we rely on exist on the Internet outside of our control. We want daily assurance that our provisions are working.

See Also

Card #13: CI unit test build

Acceptance Criteria

CI build which provisions EC2 using Ruby 1.9.2 and Postgresql

Out of Scope

Two nightly builds (see #43):

  • one provisions EC2 using Ruby 1.9.2 and Postgresql
  • one provisions EC2 using REE 1.8.7 and MySQL
@karnowski karnowski referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: rake tasks for easy stopping/destroying of EC2 instances
provisioned via "rake provision:ec2"
643ddf8
@karnowski karnowski was assigned
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: adding better logging 4032b7a
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: implementing nightly build script 672a867
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: added ability to "force" a stop or destroy of EC2 instance via
Rake
8b7a2ed
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: bugfix, removed unused, broken code e295eda
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: added rake task to determine the EC2 instance's current DNS name fb21681
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: changed the acceptance tests to work in production environment
on an EC2 instance
b24bd94
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: getting the nightly build pieces all together 0661d8d
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: extra protection f5704f8
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: finer-grained timestamp on CI ec2 instance names b27357f
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: adding lots of RVM debug messages 6e51a7e
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: explicitly state which ruby to use (to make Jenkins happy) 3a52bde
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: always fail if command fails, even if we don't have an active
EC2 instance
8e96f09
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: fun with shell, spaces, and missing quotes 1c4865f
@relevance relevance referenced this issue from a commit
Larry Karnowski and Lake Denman GH #22: allow Selenium tests to run on Jenkins server 247775c
@mtnygard mtnygard closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.