-
Notifications
You must be signed in to change notification settings - Fork 573
Added cartridge collection load test to travis. #199
base: master
Are you sure you want to change the base?
Added cartridge collection load test to travis. #199
Conversation
"description": "This is the skeleton cartridge" | ||
}, | ||
"cartridge": { | ||
"url": "https://github.com/RobertNorthard/adop-cartridge-skeleton.git", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use cartridge, which's under Accenture namespace on Github i.e. not personal account?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @anton-kasperovich updated to use skeleton cartridge under the Accenture namespace 👍
Dependency was merged already, I suppose you can continue work on this PR, right? |
Signed-off-by: Northard, Robert A <[email protected]>
@@ -24,10 +24,11 @@ script: | |||
- sleep 30 | |||
- ./adop workspace -w Travis create | |||
- ./adop project -p TestProject -w Travis create | |||
- ./adop project -p TestProject -w Travis load_collection -c https://raw.githubusercontent.com/Accenture/adop-docker-compose/master/test/resources/cartridge_collection.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anton-kasperovich I think I'll need to split this PR into two, unless I reference another cartridge collection (e.g. DOA) but I don't like this idea as the test should be decoupled. Therefore two PRs;
- adding the test cartridge collection JSON
- Updating travis file to test collection
I'm not really keen on two PRs really as it means we can't update the test data and tests at the same time and adds additional overhead.
Whats your opinion?
Added cartridge collection load test to travis as it is important to confirm that we can actually load a cartridge using the CLI. A number of delivery patterns may depend on the CLI for automating provisioning.
Notes: I'll update the cartridge collection URL to this repo once the travis checks have run (travis will fail until the dependent PRs are merged)
Dependent on:
Signed-off-by: Northard, Robert A [email protected]