Metadata
- Source
- FLUID-6236
- Type
- Improvement
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Tony Atkins [RtF]
- Reporter
- Tony Atkins [RtF]
- Created
2018-01-12T05:24:00.377-0500 - Updated
2024-07-22T10:35:27.052-0400 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Testing Infrastructure
Description
Currently, Infusion is tested on our CI servers using the linux Vagrant vm, and its one one-off Vagrantfile and provisioning.
This ticket covers replacing that with a comparable configuration for the Vagrant CI Plugin developed by @@Alfredo Matas, and defining multiple environments, so that we can easily test in both linux and windows (even if we choose to primarily test one or the other).
Comments
-
Tony Atkins [RtF] commented
2018-01-12T05:25:54.672-0500 To quote @@Alfredo Matas when discussing this earlier:
https://github.com/fluid-project/infusion/Vagrantfile , seems very similar to the universal one to me 11:01
I think that using the same definition of the used at universal repo, and changing the lasts steps to this: https://github.com/fluid-project/infusion/blob/master/package.json#L22-L25
*to use these lines -
Alfredo Matas commented
2018-01-12T05:41:56.395-0500 In fact, with the plugin we can run the tests inside a Windows VM as well as we do in the Fedora.
This can be also a good recent example:
https://github.com/colinbdclark/Flocking/blob/master/.vagrant.yml
-
Tony Atkins [RtF] commented
2020-12-16T08:11:47.596-0500 IMO this is no longer needed. CI testing of Infusion is now handled using GitHub actions.