Page History

...

Several project templates are defined for each gerrit repository. When creating the templates, the usual convention is to group all CI materials like templates and scripts in a directory named for that repository. Each directory should have at a minimum one YAML file. For example, "ci-management/jjb/com-log/com-log.yaml". Every repository should have at least Most repositories have the following items defined in its a yaml file:

• Project view.  This causes a tab to appear on the Jenkins server that groups all jobs for the repository together.
• Info file verifier.   This checks changes to the repository's INFO.yaml file.
• Verify and merge jobs appropriate for . These check submitted changes, and depend on the implementation language of the code in that repository.
• Sonar job to analyze static code and gather unit-test coverage statistics.
• Release job to promote an artifact from a staging repository to a release repository.

After creating or modifying a YAML file, submit it the change to Gerrit where the change set it will be verified and can be reviewed. Only the LF Release Engineering team can merge changes to the ci-management repository.

...