Configuration on JayeX - Cloud Native CI/CD Built On Kubernetes

Git

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

JayeX supports a number of different Git providers. You can specify the Git provider you wish to use and the organisation to use for the Git providers for each environment in your jx-requirements.yml

GitHub

This is the default Git provider if you don’t specify one.

cluster:
  environmentGitOwner: myorg
  provider: gke
environments:
- key: dev
- key: staging
- key: production

GitHub Enterprise

The configuration is similar to the above but you need to specify the URL of the gitServer (if it differs from https://github.com) and gitKind: github

Repository

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

JayeX lets you configure different artifact repositories. We use artifact repositories to:

store artifacts from some kinds of build (e.g. Java builds tend to deploy jars, pom.xml files and tarballs)
act as a Maven proxy to cache maven dependencies when using java/maven builds
implement a chart repository for releasing helm charts

Nexus

By default if you don’t make any explicit configuration then JayeX uses:

Nexus as an artifact repository to store artifacts (e.g. Java jars, pom.xml files, tarballs or npm modules etc)
ChartMuseum as a repository of charts

You can explicitly configure nexus via the following jx-requirements.yml file:

Storage

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

By storage we mean cloud storage (e.g. bucket storage for logs). Any chart you add via helmfile which uses Persistent Volumes instead of cloud storage will be up to you to backup and manage.

If you are using a cloud platform and terraform then your storage will be configured OOTB.

If you are on-premises and have installed something like minio on your cluster then you can configure the storage section of your jx-requirements.yml file to map to minio bucket URLs