integration-test job from dingo-postgresql/0.10.2
Github source:
b05d1c17
or
master branch
Properties¶
cf
¶
api_url
¶URI for Cloud Foundry API to allow lookup of user-provided service names after provisioning
integration_test
¶
organization
¶Organization to use for Cloud Foundry integration test
- Default
system
service_name
¶Service name to use for Cloud Foundry integration test
- Default
dingo-postgresql
space
¶Organization to use for Cloud Foundry integration test
- Default
dingo-postgresql-integration-test
password
¶Username for Cloud Foundry API access allow lookup of user-provided service names after provisioning
skip_ssl_validation
¶Set to true if Cloud Foundry API is using self-signed SSL certificate
- Default
false
username
¶Username for Cloud Foundry API access allow lookup of user-provided service names after provisioning
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/integration-test/
directory
(learn more).
bin/cf-create-service
(frombin/cf-create-service
)bin/run
(frombin/run
)bin/test-clone-from-latest-by-name
(frombin/test-clone-from-latest-by-name
)bin/test-storage
(frombin/test-storage
)helpers/ctl_setup.sh
(fromhelpers/ctl_setup.sh
)helpers/ctl_utils.sh
(fromhelpers/ctl_utils.sh
)helpers/test_helpers.sh
(fromhelpers/test_helpers.sh
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.