Skip to content

Commit e12459b

Browse files
authored
Merge pull request apache#473 from theopenlab/update-job-naming
Update jobs naming notations
2 parents 448165a + d04207c commit e12459b

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

README.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,24 @@ Jobs naming notations
1212
---------------------
1313
To unify the jobs name format, we have the following naming notations:
1414

15-
{project}-{test type}-{backend}-{service}
15+
{project}-{test type}-{backend}-{service}-{version}
1616

1717
- The *project* usually is the name of the git repo which contains tests to run.
18-
- The *test type* is the type of tests to run, e.g. acceptance tests, unit test.
19-
- The *backend* is the test environment provider, default is `Devstack`, optionally.
20-
- The *service* is the specific OpenStack service which this job will run against,
21-
optionally.
18+
- The *test type* is the type of tests to run, e.g. acceptance test, integration test, funcational test, unit test.
19+
- The *backend* is the test environment provider, include: deploying tools, public cloud, private cloud,
20+
e.g. devstack, kubeadm, minikube, opentelekoncloud, optionally, default is `devstack`.
21+
- The *service* is the specific *backend* service which this job will run against, optionally, default is `core services`.
22+
- The *version* is the specific *backend* version which this job will run against, optionally, default is `master`.
2223

2324
For an example, the job definition about running the specific Trove related
2425
acceptance tests of terraform-provider-openstack repo can be named as:
2526

2627
terraform-provider-openstack-acceptance-test-trove
2728

29+
And running spark integration test against kubernetes 1.13.0 that is deployed by minikube:
30+
31+
spark-integration-test-minikube-k8s-1.13.0
32+
2833
More information
2934
----------------
3035
Web page about OpenLab:

0 commit comments

Comments
 (0)