Introduction
|
Always develop software according to CESSDA’s Technical Architecture.
Adhering to the Technical Architecture recommendations will greatly increase the chances that your software is accepted by CESSDA.
Use the CESSDA Software Maturity Levels questionnaire to assess the readiness of your software for CESSDA.
|
Developing an application for CESSDA
|
Contribute code to an existing repository through a repository fork.
Use the Feature Branch Workflow for developing a contribution.
Always test your contribution before submitting it.
Use pull requests to submit repository contributions.
Resynchronise your forked repository to ensure you have any latest repository changes.
|
Using automation to build, test and deploy our code
|
Automation benefits developers, CESSDA, and anyone that uses or develops your code.
Use CESSDA’s Jenkins CI infrastructure when developing for CESSDA.
Write unit tests for your code contributions where possible.
|