aehlke · August 29, 2015 14:13
diff --git a/gistfile1.txt b/gistfile1.txt
 Temporary Jenkins instructions for QA

 Until we roll Jenkins out to everyone, this is the process that should work for you. This is only because CircleCI
 integration is broken until my circle.yml changes are merged ( https://github.com/tophatmonocle/THM/pull/823 which
 I need to update shortly), which blocks the nicer workflow I've built in Jenkins.

 One requirement is that the branch you are launching is on the upstream tophatmonocle/THM repo, not someone's fork.
 We should already be moving over to this now anyway.

 To launch a test server:
 1. Jenkins must have already triggered and finished an assets build for the branch. It does this automatically when
 branches are pushed and takes about 7 minutes. If the branch isn't recent, Jenkins may not know about it, or if the
 code was pushed before Jan 15th, I may have canceled the build (due to a build backlog issue). To make absolutely 
 sure a build has happened, you can just trigger one yourself here: https://jenkins.tophat.com/job/pipeline-step-build/build?delay=0sec
 - fill in the branch name and sha1 of the latest commit, hit Build, and wait for it to finish in ~7 minutes.
 2. Visit https://jenkins.tophat.com/job/pipeline-step-launch-US-test/build?delay=0sec and input the branch name, the 
 same sha1 you used in step 1, and optionally the ami_name_search if you don't want the latest production AMI. Hit Build,
 and Giskard should send a message in IRC with a link once the server is ready. The build may fail though if there aren't
 any free ELBs available - you'll see the build status in the "Build History" after submitting that form. This step takes
 about 1.5 minutes to run, whether or not there's an ELB it can use.
	Temporary Jenkins instructions for QA

	Until we roll Jenkins out to everyone, this is the process that should work for you. This is only because CircleCI
	integration is broken until my circle.yml changes are merged ( https://github.com/tophatmonocle/THM/pull/823 which
	I need to update shortly), which blocks the nicer workflow I've built in Jenkins.

	One requirement is that the branch you are launching is on the upstream tophatmonocle/THM repo, not someone's fork.
	We should already be moving over to this now anyway.

	To launch a test server:
	1. Jenkins must have already triggered and finished an assets build for the branch. It does this automatically when
	branches are pushed and takes about 7 minutes. If the branch isn't recent, Jenkins may not know about it, or if the
	code was pushed before Jan 15th, I may have canceled the build (due to a build backlog issue). To make absolutely
	sure a build has happened, you can just trigger one yourself here: https://jenkins.tophat.com/job/pipeline-step-build/build?delay=0sec
	- fill in the branch name and sha1 of the latest commit, hit Build, and wait for it to finish in ~7 minutes.
	2. Visit https://jenkins.tophat.com/job/pipeline-step-launch-US-test/build?delay=0sec and input the branch name, the
	same sha1 you used in step 1, and optionally the ami_name_search if you don't want the latest production AMI. Hit Build,
	and Giskard should send a message in IRC with a link once the server is ready. The build may fail though if there aren't
	any free ELBs available - you'll see the build status in the "Build History" after submitting that form. This step takes
	about 1.5 minutes to run, whether or not there's an ELB it can use.