toelt / argo-continuous-integration

Continuous integration with Argo that supports bitbucket private webhooks.

Argo Continuous Integration

Continuous integration with Argo that supports bitbucket private webhooks.

Installation

Change your host in the ingress.yml file first. This file resides in the kubernetes folder.

kubectl apply -f kubernetes/

Usage

Once deployed, add a webhook to your bitbucket repositories https://<your-argo-domain>/webhook.

ingress

Change the url in the ingress before deploying. This Ingress will route traffic from your Argo domain to the Argo CI implementation, Bitbucket will use this domain as a webhook.

starter workflow

The webhook is going to be called and it will start up a 'starter' Workflow, which in turn will pull the repository and start the argo.yml Workflow which has to reside in the root of the repository. The argo.yml file in this repository consists of a sshPrivateKeySecret named 'bitbucket-creds', this has to be a secret in the namespace you will deploy this in. Feel free to rename this and adjust this in the argo.yml file. This Secret is needed to be able to pull your repository from Bitbucket and start the actual Workflow.

example workflow

An example Workflow that has to reside in the root of the project you want to apply CI/CD to and will be triggered by the starter workflow, can be found in the example-workflow folder. This Workflow will build a docker image, run Cypress frontend tests and deploy it via Ansible to Kubernetes.