ami stack is built on Jenkins (continuous integration) in the chemistry dept at Cambridge. Every time any part of the stack is pushed to its repository it, and all its downstream dependencies, are rebuilt. This includes running the tests in a very strict clean environment, which often throws up more errors than IDEs or local
The site at https://jenkins.ch.cam.ac.uk/view/AMI2/ is a subset of the PMR group software selected for
norma. Currently all components (except
jumbo-converters ) should build and test (green button). Failing compilation gives red buttons, successful compilation but failed tests give yellow buttons.
A failed build or test alerts me by email.
The chemistry Jenkins builers take their input from both
The complete dependency graph can be seen in https://jenkins.ch.cam.ac.uk/view/AMI2/depgraph-view/ . This shows the considerable number of upstream dependencies for
ami. (Ignore anything with 'chem' or 'jumbo' in the label unless you are seriously interested in chemistry).