Skip to content

smoke-tests job from cf-mysql/36.7.0

Github source: 653ae52 or master branch

Properties

cf

admin_password

Password of the admin user

Default
""

admin_username

Username of the admin user

Default
""

api_url

Full URL of Cloud Foundry API

Default
""
Example
https://api.your-domain.example.com

app_domains

List of shared domains for pushed apps (tests will use the first domain)

skip_ssl_validation

Whether to add –skip-ssl-validation for cf cli

Default
false

smoke_tests

org

The name of the Org to run acceptance tests against

Default
""
use_existing_org

Runs smoke test errand as an existing org. Creates a new org if false

Default
false

cf_mysql

broker

services

Array of Services the broker provides

external_host

Hostname given for dashboard URLs (e.g. p-mysql.example.com)

Default
""

host

Hostname given to apps by the broker, usually a Load Balancer address or the IP of the first proxy. Used only by the standalone tests, and is optional. If omitted, and standalone_tests_only is true, either cluster_ips must be provided, or mysql links must be provided.

mysql

port

Port used to access MySQL

Default
3306

proxy

api_force_https

Expect proxy to force redirect to HTTPS

Default
true
api_password

Proxy API password

api_username

Proxy API username

Default
proxy

smoke_tests

db_password

Password for generated database user

password

Password for generated user to comply with CF password policy, if exists.

Default
""
standalone_tests_only

Instead of running the full smoke test suite, only run a minimal set of tests that do not require a running CF deployment

Default
false
timeout_scale

scaling multiplier used to determine command timeouts

Default
1

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/smoke-tests/ directory (learn more).

  • bin/run (from errand.sh.erb)
  • config/config.yml (from config.yml.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.