search

galatea-associates / fuse-test-data-gen

Repository for the Galatea internal data generator tool, used for generating domain data for POCs
0 stars 0 forks source link

Set up CI build #24

Open j-barber opened 5 years ago

j-barber commented 5 years ago

Set up a jenkins build to run automatically on commits, and ensure all tests are run and failing tests break the build.

j-barber commented 5 years ago

Can you add some evidence showing that this works, and update the readme to explain how the CI pipeline is set up?

GalaJoe commented 5 years ago

Screenshots evidencing functionality and configuration can be found at: https://drive.google.com/drive/u/0/folders/1u639JFAPE_Qt35q92WjjLHDnnwhHjZj1

The current configuration uses a branch discovery strategy both when pull requests are created as well as when pull requests are merged. Branches are discoverable by having a Jenkinsfile within them.

The current Jenkins pipeline includes 2 stages: 1) Installation of requirements which hinges on the requirements.txt file. 2) Execution of the Unit Tests. Those included in this branch are minimal for the purpose of validating correctness of the Jenkins configuration, Issue Branch 23 is the implementation of the actual tests.

When testing additional to Unit is implemented, the Jenkins Pipeline will be updated to accommodate this.

GalaJoe commented 5 years ago

Prior CL build via Jenkins was operational. Since then our Jenkins server has been rebuilt, meaning this project is no longer there. To resolve this:

1) Add the FUSE-Test-Data-Gen job back into Jenkins 2) Update the Jenkinsfile to now include all new tests as of PR:Primary_Refactor and add documentation stages on code coverage/linting