Platform Processes
Terminology
See Naming Conventions.
Update CI Tools
See Updating CI Tools.
Create repositories
- application code.
- See ‘Create a GitHub Repository’ for details.
- Deployment, via Helm.
- See the CDC Deployment (
cessda/cessda.cdc.deploy
- private) repository for a working example.
- See the CDC Deployment (
- Reverse Proxy.
- See the CDC Reverse (
cessda/cessda.cdc.reverse
- private) repository for a working example.
- See the CDC Reverse (
- Test.
- See the CDC Test (
cessda/cessda.cdc.test
- private) repository for a working example.
- See the CDC Test (
- User Guide - generates documentation from Markdown files.
- See the CDC User Guide (https://github.com/cessda/cessda.cdc.userguide/) repository for a working example.
Create Jenkins jobs
A Jenkins jobs is needed to run the build, test and deployment pipeline. If there is a database component, then jobs are needed to backup and restore the database contents as well as deploying a specified version of the database schema. See Create a New Jenkins Job.
Create DNS records
Needed for development, staging and production instances (see CESSDA naming conventions). Then update the Product Endpoint Details file.
Create/edit Jenkinsfile for each repository
Provide a basic pipeline to build, test and deploy the component. See Building Maven Projects With Jenkins for details.
See also TemplateJenkinsfileForJDK11MavenProjects and Adding the Deployment Jenkinsfile.
Work with developers to create test suites to be used by the pipeline.
- Development. Work with developers to create staging builds for user group testing. If relevant, ensure the job for deploying a specified version of the database schema runs successfully.
- Staging. Work with users and developers to approve production builds. See the Software Releases procedure for details.
- Production. If relevant, ensure the database backup and restore jobs run successfully.