projectatomic / adb-tests

placeholder for tests for the adb while its long term place to live is sorted out
GNU General Public License v2.0
7 stars 19 forks source link

Tests for Mesos provider to run before releasing new version of ADB #31

Closed dharmit closed 2 years ago

dharmit commented 8 years ago

This job can be accessed on CentOS CI UI.

This is a parameterized build which asks for a URL before starting the build. The URL needs to be a valid URL to the Vagrant box. Once you provide a valid URL, flow of the job is like below:

  1. New Vagrant box is pulled for libvirt provider.
  2. Atomic Developer Bundle repo is cloned to ~/adb.
  3. My fork of ADB Tests repo is cloned to ~/adb-tests.
  4. Vagrantfile for Mesos provider under ~/adb/components/centos/centos-mesos-marathon-singlenode-setup/ is modified to refer to the newly built box instead of default projectatomic/adb.
  5. New Vagrant box is boot up.
  6. We clone atomicapp inside the box, start an atomicapp projectatomic/helloapache with the provider Mesos and hit Marathon API to check if the app started up properly.
  7. Vagrant box is destroyed before exiting the tests.

@navidshaikh ping, once again we need to remove references to my fork before the final merge.

dharmit commented 8 years ago

Add info that only libvirt is support ATM.

dharmit commented 8 years ago

@navidshaikh I've incorporated the changes suggested or replied back where I haven't made changes. Before the merge, just like last time, we'll need to remove references to my forked repo

navidshaikh commented 8 years ago

@dharmit : Looks good. Lets remove the references to forked repo and we merge it?

dharmit commented 8 years ago

Sorry, the reference changing and few other things that got added to adb-ci-ansible repo broke this stuff. I'll try to look at this over weekend.