Contribute code on JayeX - Cloud Native CI/CD Built On Kubernetes

Pull Request Reviews

Mon, 01 Jan 0001 00:00:00 +0000

The pull request is the main place we gate changes in JayeX. It’s here we:

run the tests (make test-slow-integration)
execute end to end tests against static jenkins and Tekton
check the change for linting issues
check the code for formatting issues
validate that all generated code (mocks, kubernetes clients, kubernetes openapi structs) are up to date
validate that we can generate the apidoc
validate that your commits are conventional

Our philosophy is to automate the checks as much as possible - there are some that must still be done by a human but we plan to reduce those as far as possible.

Continuous Integration of JX itself

Mon, 01 Jan 0001 00:00:00 +0000

You may be wondering how JayeX introduce changes to JayeX. Of course, JayeX is built using JayeX itself! That means that new changes to the project go through a CI process, and are built and tested using pipelines that run on a JayeX Kubernetes cluster.

Pipelines

A Pull Request in the jx repository will automatically trigger some jobs to do CI. The jobs are triggered by Lighthouse, and we can configure which jobs to execute. The jobs with always_run configured to be true, will be run when the PR is opened. All jobs (independently of having always_run set to true or false) can be manually triggered writing a comment in the PR. The comment needed to trigger the job is also in the configuration, in the trigger key. For example, to trigger the pr tests manually, you may write a new comment in the PR containing “/test pr”, and the pr job will be triggered.

Triaging issues

Mon, 01 Jan 0001 00:00:00 +0000

The main issue tracker for the JayeX project is https://github.com/jenkins-x/jx/issues. This aims to capture issues, ideas and development work. If in doubt please raise an issue and a JayeX team member will look to triage it as soon as possible.

As JayeX is using prow from the Kubernetes ecosystem we figured we’d take their lead in triaging a large number of issues to aid and encourage contributions. We are reusing the style of labels including colours in an attempt to create familiarity across open source projects and reduce the barrier to contributing.