jcsda-internal/CI Job Launcher
Launch a JEDI-CI job
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| container_version | Container version (latest, next) | yes | latest |
| target_project_name | Name build bundle project for this repository (if different from the repo name). | no | "" |
| jedi_ci_token | GitHub token associated with the JEDI CI GitHub app | no | "" |
| test_script | Test script to run (must be in //jedi-ci/shell/) | no | run_tests.sh |
| target_repo_dir | Deprecated option, we no longer pre-clone the target repository. | no | target_repository |
| bundle_repository | Repository to use when cloning the bundle. | no | https://github.com/JCSDA-internal/jedi-bundle.git |
| bundle_branch | Default branch to use when cloning the bundle. | no | develop |
| unittest_tag | CMake tag used to execute unit tests. | no | "" |
| unittest_dependencies | (Deprecated) use test_dependencies+test_strategy instead. This option forces test strategy to be ALL. | no | "" |
| test_dependencies | Build bundle dependencies used for tests. | no | "" |
| test_strategy | The strategy used for building and running tests. May be ALL, INTEGRATION, or UNIT. - INTEGRATION: The bundle is trimmed to only include the test_dependencies all tests are run. - UNIT: The bundle is trimmed to only include the test_dependencies and unit tests are run. - ALL: A 2-stage build is performed with the first step using the test_dependencies to build the unit tests and the second step building the full bundle for integration tests. | no | ALL |
| self_test | Whether to run a self-test of the JEDI CI action. | no | false |
Outputs
no outputs