Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-04-05 08:47:10 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/*]: chore: 🔧 Remove "Chart Test" pipeline (#9931)

Browse Source 
* [bitnami/*]: chore: 🔧 Remove "Chart Test" action

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>

* Update contributing

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
This commit is contained in:
Javier J. Salmerón-García
2022-04-26 12:33:52 +02:00
committed by GitHub
parent 74e7106184
commit 2246e0540e
3 changed files with 2 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
.github/ct-install.yaml vendored
View File

@@ -1,16 +0,0 @@
chart-dirs:
- bitnami
chart-repos:
- bitnami=https://charts.bitnami.com/bitnami
debug: true
excluded-charts:
- common
- kubeapps
- kibana
- kong
- mariadb-galera
- ejbca
- wavefront
- dataplatform-bp1
- dataplatform-bp2
remote: origin

23
.github/workflows/lint-test.yaml vendored
View File

@@ -1,23 +0,0 @@
name: Test Charts
on: pull_request
jobs:
test:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Fetch history
run: git fetch --prune --unshallow
- name: Set up chart-testing
uses: helm/chart-testing-action@v2.1.0
- name: Create kind cluster
uses: helm/kind-action@v1.2.0
- name: Run chart-testing (install)
run: ct install --config .github/ct-install.yaml

5
CONTRIBUTING.md
View File

@@ -51,15 +51,14 @@ Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will
### PR Approval and Release Process
1. Changes are automatically linted and tested using the [`ct` tool](https://github.com/helm/chart-testing) as a [GitHub action](https://github.com/helm/chart-testing-action). Those tests are based on `helm install`, `helm lint` and `helm test` commands and provide quick feedback about the changes in the PR. For those tests, the chart is installed on top of [kind](https://github.com/kubernetes-sigs/kind) and this step is not blocking (as opposed to 3rd step).
1. Changes are manually reviewed by Bitnami team members.
1. Once the changes are accepted, the PR is verified with a [Static analysis](https://github.com/bitnami/charts/blob/master/TESTING.md#Static-analysis) that includes the lint and the vulnerability checks. If that passes, the Bitnami team will review the changes and trigger the verification and functional tests.
1. Once the changes are accepted, the PR is verified with a [Static analysis](https://github.com/bitnami/charts/blob/master/TESTING.md#Static-analysis) that includes the lint and the vulnerability checks. If that passes, the Bitnami team will review the changes and trigger the verification and functional tests.
1. When the PR passes all tests, the PR is merged by the reviewer(s) in the GitHub `master` branch.
1. Then our CI/CD system is going to push the chart to the Helm registry including the recently merged changes and also the latest images and dependencies used by the chart. The changes in the images will be also committed by the CI/CD to the GitHub repository, bumping the chart version again.
***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the chart in the registry.
### Testing
### Testing
1. Read the [Test Strategy](https://github.com/bitnami/charts/blob/master/TESTING.md) guide.
2. Determine the types of tests you will need based on the chart you are testing and the information in the test strategy.