These two files are associated to those two events respectively ( vib-verify.json to the creation of a PR, meanwhile vib-publish.json to the merging of changes to main), and define what VIB should do when they are triggered. The runtime_parameters are shared accross all actions, which guarantees that each release of the chart is based on the exact same configuration.Īs seen in the introduction, there are two different events that will trigger the execution of the tests. ![]() See the Runtime parameters section for further information. The installation of the chart can be customized via runtime_parameters, which should be encoded using base64. Consequently, the state between actions is not shared. Namely, this example includes a health-check, an instance of goss tests and another instance of cypress tests.įor each of the actions, VIB will deploy a brand new release of the chart provided by. There is a list of the actions to execute as part of the testing plan. This guide will focus in the verify phase section, in which there are some things to remark: "runtime_parameters": "amVua2luc1VzZXI6IHVzZXIKamVua2luc1Bhc3N3b3JkOiBDb21wbGljYXRlZFBhc3N3b3JkMTIzITQKY29udGFpbmVyUG9ydHM6CiAgaHR0cDogODA4MApzZXJ2aWNlOgogIHR5cGU6IExvYWRCYWxhbmNlcgogIHBvcnRzOgogICAgaHR0cDogODAK ", Let's take a look at an example and try to understand it! This is the role of the aforementioned vib-verify.json and vib-publish.json files, which every asset defines and can be found alongside its tests inside the /.vib folder. But as every application is different, VIB needs to be supplied with a definition of the set of actions and configurations that precisely describe the verification process to perform in each case. The CI/CD pipelines in the repository are configured to trigger VIB when an asset needs to be verified. VMware Image Builder (VIB) is a platform-agnostic, API-first modular service that allows large enterprises and independent software vendors to automate the packaging, verification, and publishing processes of software artifacts on any platform and cloud.įor more information about VIB, you can refer to its official page. The service that powers the verification of the thousands of monthly tests performed in the repository is VMware Image Builder. ![]() More on the latter in VIB pipeline files. This strategy ensures that a set of changes must have succeeded twice before a new version is sent out to the public.Īll the assets have an associated folder inside /.vib with their tests implementations (the subfolders cypress, goss and/or ginkgo) and files containing their test plans ( vib-verify.json and vib-publish.json). Accepted changes are merged to the main branch, prior to their release.A new contribution (regardless of its author) is made through a GitHub Pull Request.Before this happens, different checks are required to succeed. Bear in mind that every contribution to our charts is ultimately published to our Helm index, where it is made available for the rest of the community to benefit from. ![]() At Bitnami, we are committed to ensure the quality of the assets we deliver, and as such, tests play a fundamental role in the bitnami/charts repository.
0 Comments
Leave a Reply. |