Skip to content

Latest commit

 

History

History

.openshift-ci

This folder supports OpenShift CI for this repo config.

stackrox/stackrox jobs in openshift/release typically execute the following steps:

  • begin.sh
  • An automation-flavors create() depending on cluster type. [optional: e.g. with GKE create() is handled in dispatch.sh]
  • dispatch.sh is the entrypoint for tests. Depending on the job, this will run one of the scripts in scripts/ci/jobs.
  • An automation-flavors destroy() depending on cluster type.
  • end.sh

The *.py in this folder provides some semantics useful to e2e and system tests e.g.:

  • create a cluster
  • run test
  • gather and examine state
  • teardown

Python Style & Lint

Python code is expected to be PEP8 and checked with pycodestyle. Linting is via pylint.

For dev workflow there are make targets:

make style
make fix-style
make lint

Debugging

Links

Job Definition: https://github.com/openshift/release/tree/master/ci-operator/jobs/stackrox/stackrox Config Definition: https://github.com/openshift/release/tree/master/ci-operator/config/stackrox/stackrox

Access Job Cluster and Real Time Logs

  • To access the OpenShift UI to view the pod logs directly in OpenShift UI search for something like Using namespace https://console.build01.ci.openshift.org/k8s/cluster/projects/ci-op-yz5q9nlt.
  • Access OpenShift UI, open Administrator overview on the top left.
  • View the Environment, copy the KUBECONFIG path, open the Pod's Terminal view in the UI and run cat <KUBECONFIG_PATH>
  • Copy KUBECONFIG content and create the KUBECONFIG locally
  • Run export KUBECONFIG=/local/path/to/kubeconfig

Check StackRox logs and build logs

Path in artifacts:

download build logs: artifacts/gke-qa-e2e-tests/stackrox-stackrox-e2e-test/artifacts/howto-locate-other-artifacts-summary.html