spinning up branches: phase 1

[pdurbin]

At tech hours we just talked about the idea of spinning up arbitrary branches on AWS. I was asked to make an issue we can estimate and I'm going to try to keep this small but the whiteboard notes below reflect some future thinking as well.

Definition of done:

• The https://github.com/IQSS/dataverse-ansible repo is modified to run on arbitrary pre-release (usually unmerged) branches rather than being hard coded to a specific release. See enable spinning up of arbitrary branches dataverse-ansible#22
• A script can be passed an arbitrary branch name and it spins up an EC2 instance, clones the main Dataverse git repo, clones the https://github.com/IQSS/dataverse-ansible repo, builds the artifacts, and deploys Dataverse.

[djbrooke]

Thanks @pdurbin, we'll estimate this today.

[pdurbin]

@donsizemore just fixed up dataverse-ansible so that it will deploy arbitrary branches (thanks!!). You just add branch name to tests/group_vars/vagrant.yml like this:

murphy:dataverse-ansible pdurbin$ git diff
diff --git a/tests/group_vars/vagrant.yml b/tests/group_vars/vagrant.yml
index 35fa041..f276df7 100644
--- a/tests/group_vars/vagrant.yml
+++ b/tests/group_vars/vagrant.yml
@@ -8,7 +8,7 @@ dataverse:
     blocked_endpoints: "admin,test"
     blocked_policy: "localhost-only"
     location: "http://localhost:8080/api"
-  branch:
+  branch: "4926-unlock-dataset-api"
   copyright: "© Your Institution"
   db:
     name: dvndb
murphy:dataverse-ansible pdurbin$ 

And then you run vagrant up. Heads up to @dlmurphy that this might be immediately useful to you when writing messaging. It works today.

[matthew-a-dunlap]

My first goal in picking this up is to explore scripting the creation of an EC2 instance and dropping in relevant information (e.g. branch name) for ansible to pick up and use for bringing up Dataverse