1.8 KiB
CI workflow
The Fuel developers team recommends that you follow this CI workflow:
Prepare labs and start or update the lab:
Download the ISO from Fuel CI. Depending on the Fuel version specified in plugin’s requirements, Jenkins downloads the released ISO and/or the currently developed and passed BVT test on core CI.
Deploy the downloaded ISO and prepare the required labs for testing using the
fuel-dev
andfuel-qa
repositories:$ fuel-main/utils/jenkins/system_tests -t test -j \ dis_fuelweb_test -i (path to downloaded Fuel-ISO) \ -o --group=setup -V ${VIRTUAL_ENV} -k
Create or restore the required empty VMs from snapshots.
A Gerrit review job starts building your plugin. See Gerrit workflow.
- Use a preconfigured Gerrit Trigger to start your job after a new Gerrit patch arrives.
- Run a code syntax checker and unit tests according to the instructions from Testing.
- Run a Puppet linter. See Puppet OpenStack.
- Build the plugin.
- Trigger the plugin testing.
Vote on the Gerrit patch page and add review the result in the comment using Gerrit Trigger.
Test the plugin:
- Install the plugin.
- Configure the environment.
- Deploy the environment with the inactive plugin.
- Run the OSTF tests.
Run plugin-specific functional tests to check that the current plugin version provides expected functionality.
Publish the resulting aggregated logs to the log storage.
You can do this by archiving logs.