https://github.com/crc-org/ci-definitions
This project holds a set of specs used within different ci systems to build and test Openshift Local
https://github.com/crc-org/ci-definitions
ci k8s oci openshift openshift-local tekton
Last synced: 2 months ago
JSON representation
This project holds a set of specs used within different ci systems to build and test Openshift Local
- Host: GitHub
- URL: https://github.com/crc-org/ci-definitions
- Owner: crc-org
- License: apache-2.0
- Created: 2024-07-29T16:54:58.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2025-01-31T13:40:23.000Z (5 months ago)
- Last Synced: 2025-02-25T06:43:26.700Z (4 months ago)
- Topics: ci, k8s, oci, openshift, openshift-local, tekton
- Language: Shell
- Homepage:
- Size: 83 KB
- Stars: 2
- Watchers: 1
- Forks: 3
- Open Issues: 11
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ci-definitions
This repository contains several specs to define ci actions used within the building process of Openshift Local. The logic on each action is encapsulated as a container which improve their portability.
## release
The ci-definitions is a group of actions, as so the release / versioning is tied to each action on the project. Each action contains a file named `release-info` which holds the inforamtion for the release of the specific action.
The following snippet shows how to release new version for a specific ci action (i.e crc-builder v1.0.0):
```bash
# Create a branch, branch will NOT be pushed
git checkout -b b-crc-builder-v1.0.0
# Change the version on the release-info file for the ci action
sed ... (TBC)
# Generate the tasks with the new version
make crc-builder-tkn-create
# Commit the cut for the ci action
git commit -s -m "chore: cut crc-builder v1.0.0"
# Create the tag
git tag crc-builder-v1.0.0
# Here the gh builder flow for the ci action will create oci image and bundle with tekton tasks
git push upstream crc-builder-v1.0.0
# Change version on release-info to next version
```
## testing PRs
Manually run make XXX-tkn-create, then;
Typically PRs will be composed of images, tasks and pipelines:
* Pipelines and tasks can use git resolver using the forked repo source for the PR
* Task which needs the image need to be updated with the ghcr image
A testing commit can be done at very last part of the PR to test this customizations which then can be used
from a pipelinerun with a pipelineref to the forked repo source for the pr.
If everything works just revert and dismiss latest commit and create a tag