add documentation relative to CI tests

phylo42 / PEWO

Phylogenetic Placement Evaluation Workflows : Benchmark placement software and different reference trees

MIT License

12 stars 9 forks source link

add documentation relative to CI tests #6

Closed blinard-BIOINFO closed 3 years ago

blinard-BIOINFO commented 3 years ago

@nromashchenko commented in #4 :

Our Travis CI runs two pipelines travis/tests/1..., travis/tests/2... on every push, making sure it's possible to build and run those toy examples in the isolated environment. If a developer does not change config files of those, his new app is not tested with CI.

What needs to be done:

add a section relative to CI in developer documentation
add a concrete example, this example could be directly based on AppSPAM example, e.g. commit 8a4af9d discussed in #4

blinard-BIOINFO commented 3 years ago

Done, there is a new section "Merging to PEWO rapository" in developers instructions describing how to add their tool in circle CI config.

Also, I described how to modify R script for building plots for new tools.