Have you answered the Jenkins X survey yet?
If no, then
jx verify job
Verifies that the job(s) with the given label succeeds and tails the log as it executes Aliases: logs
jx verify job
Verifies that the job(s) with the given label succeeds and tails the log as it executes
# verify the BDD job succeeds jx verify job -l app=jx-bdd # verify the BDD job succeeds using name jx verify job --name jx-bdd
-b, --batch-mode Runs in batch mode without prompting for user input -c, --container string the name of the container in the job to log -d, --duration duration how long to wait for a Job to be active and a Pod to be ready (default 1h0m0s) -f, --field-selector string the field selector to use to query jobs -h, --help help for job --log-fail rather than failing the command lets just log that the job failed. e.g. this lets us run tests inside a Terraform Pod without the terraform operator thinking the terraform failed. --log-level string Sets the logging level. If not specified defaults to $JX_LOG_LEVEL --name string the name of the job to use -n, --namespace string the namespace where the jobs run. If not specified it will look in: jx-git-operator and jx --poll duration duration between polls for an active Job or Pod (default 1s) -l, --selector string the selector of the job pods --verbose Enables verbose output. The environment variable JX_LOG_LEVEL has precedence over this flag and allows setting the logging level to any value of: panic, fatal, error, warn, info, debug, trace --verify-result if the pod succeeds lets look for the last line starting with POD RESULT: to determine the test result
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified April 20, 2021: chore: regenerated plugin docs (412f8f1671)