This is the CSCS Production Repository on the GitHub, with the list of CSCS production builds and EasyBuild configuration files. Please check the CSCS User Portal for details on how to use the EasyBuild framework at CSCS.

1. Add the EasyBuild configuration files to a new branch, including all the required dependencies
2. Create and assign yourself a pull request following this policy for the title:
   • the title must match a supported system in the list daint dom fulen kesch leone monch, otherwise the build will fail immediately. The system names have to be enclosed in square brackets to be distinguished from the actual pull request title and be parsed by the corresponding Jenkins project.
   • if the title matches WIP ("Work In Progress"), then the test build will be aborted immediately, as work in progress is not supposed to be tested.
   • Dom and Piz Daint can test both software stacks -gpuand -mc at once:
     1. if the title matches only ${system}-gpu or ${system}-mc, only that software stack will be used:
        • [dom-gpu] NAMD will build using -gpu, [dom-mc] NAMD will use -mc.
     2. if the title matches both or none, then both will be used, one after another in a loop:
        • [dom] NAMD will build using both -gpu and -mc in a loop.
        • [dom-gpu,dom-mc] NAMD will do the same.
3. The CSCS Jenkins project TestingEB will test the build of new EasyBuild recipes with respect to the master. The corresponding pipeline of TestingEB is contained in the jenkins/JenkinsfileTestingEB script.
4. If the build is successful, you should ask for a review: the pull request will only be merged when approved.
5. In order to re-trigger the testing of the pull request without committing a change, add the comment retest this please which will notify the TestingEB Jenkins project.
6. (CSCS only) for production builds, please update the appropriate production build list here.