Changes between Version 1 and Version 2 of 2020WP/VALID-12_clevy_Trusting_Continuous Integration


Ignore:
Timestamp:
2020-04-07T10:11:19+02:00 (7 months ago)
Author:
clevy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 2020WP/VALID-12_clevy_Trusting_Continuous Integration

    v1 v2  
    2727}}} 
    2828 
    29 ''...'' 
     29IMMERSE is expected to improve NEMO development process beyond state-of-the art through the extension of NEMO testing suite with a continuous integration service. Following most recent best practices in software development, this tasks aims at deploying a continuous integration service that will be triggered as often as needed, allowing a functional and scientific verification of code results. The service will allow to perform tests routinely on various selected configurations (code branch, testing scope, compiler, compilation options, HPC centers, …). [[br]] 
     30This action is a contribution to IMMERSE delivrable D2.1: Continuous integration service NEMO deployed on NEMO repository.[[br]] [[br]] 
     31The so-called trusting tool has been developped by Nicolas Martin in 2015. As an insight on the functionalities of this tool, it was producding the following web pages (with two different options below): 
     32* New interface on https://pagesperso.locean-ipsl.upmc.fr/ntmlod/trusting_dev 
     33* Older interface on  https://pagesperso.locean-ipsl.upmc.fr/ntmlod/trusting 
    3034 
     35This action will re-install the trusting tool to make it fonctionnal for the most recent NEMO releases.[[br]] 
     36Once this done, hopefully on a few centers/target computers to check partability, this action should also allow to easily add new configurations or test cases to the trusting process.[[br]] 
     37 
     38Starting point for the development https://forge.ipsl.jussieu.fr/nemo/browser/utils/CI/trust 
    3139=== Implementation 
    3240