Skip to content

Testing your Package Branch against Bigbang before Package Merge📜

These instructions right now are written for istio changes, but the same is probably true for kyverno and possibly for others. CODEOWNERS reviewing Merge Requests (MRs) should enforce this.

Run Bigbang Tests Against your Branch📜

As part of your MR that modifies istio you will need to run bigbang tests against your branch. To do this, at a minimum, you will need to complete the following:

  1. Create a new branch on bigbang off of master git checkout master && git pull && git checkout -b my-bigbang-branch-for-testing.

  2. Modify the test values. Yours will be different for your package, you may need more than this.

    nexusRepositoryManager:
  git:
    tag: null
    branch: my-package-branch-that-needs-testing
  values:
    istio:
      hardened:
        enabled: true

  3. Stage your changes git add -A.

  4. Commit your changes git commit -m "prepping for test."
  5. Push your changes git push -u origin my-bigbang-branch-for-testing.
  6. Create the bigbang MR as a draft with TEST ONLY DO NOT MERGE in the title, and add the label of the package to test (e.g., monitoring).
  7. Wait for tests to finish, and do fixes on your package branch as needed until they pass.
  8. Close the bigbang MR by deleting the bigbang branch git push -d origin my-bigbang-branch-for-testing.
  9. Link the bigbang MR on your package MR as evidence of your package working in bigbang.
Last update: 2024-08-16 by Alfredo Diaz