====== Buildbot and the test farm ======

===== Brief introduction =====

How to maintain code integrity despite numerous modifications (including bug insertion) ?
This is addressed by maintaining a test suite, combining reference input files and corresponding output files,
against which all modifications of ABINIT are confronted, especially when a merge request in the trunk is issued.
For ABINIT, a test farm with about twenty "builders" spread on a dozen of different computers, is available
for running such test suite on different architecture and operating systems.

Buildbot is the software used to launch and analyze the automatic tests of ABINIT on the ETSF test farm. 

===== External links =====
  *  https://buildbot.net/ (the buildbot site)
 
===== Internal links =====

  * **Configurations**   
    *  [[bb:slaves|Slave matrix]]
    *  [[bb:builder|Builder matrix]]
    *  [[bb:addnotes|Additional notes]]

  * **Operations**
     *   [[https://buildbot.abinit.org/#/waterfall?reload=100|The ABINIT waterfall on the ETSF test farm]].
     *   [[https://bbportal.abinit.org/#/status|Nightly builds Status]] ( <color #ed1c24>restricted access</color> )
 
===== Particulars =====


  *  [[bb:misc|Particulars of the use of buildbot]] in the ABINIT environment (e.g. how to trigger the tests, how to handle failures, how to access directly the test farm)
  * [[https://docs.abinit.org/developers/developers_howto/#how-to-add-a-new-test-in-the-test-suite|How to add a new test]].

/*  [[developers:addnewtest|How to add a new test in the test suite]].*/