bmc-compuware/Code Pipeline Build
Run a mainframe build using Code Pipeline
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| ces_url | The URL to send requests to. | yes | — |
| ces_token | The token to use when connecting to Code Pipeline through CES | no | — |
| certificate | The certificate used when connecting to Code Pipeline through CES. | no | — |
| srid | The ID for the instance of Code Pipeline to connect to | yes | — |
| runtime_configuration | The runtime configuration used when connecting to Code Pipeline | no | — |
| assignment_id | The container for which you intend to build tasks. | no | — |
| level | The level that the tasks exist at in the assignment | no | — |
| task_id | The comma-separated list of task IDs for the tasks that need to be built | no | — |
| build_automatically | The request parameters for the generate will come from JSON passed in this input. This option is only valid when used in combination with a Git to Code Pipeline Integration step | no | — |
| change_type | S for standard, I for incidental, or E for emergency. Default value of S | yes | S |
| execution_status | I for immediate execution or at start date/time, H to create request in hold | yes | I |
Outputs
| name | description |
|---|---|
| generate_failed_count | The number of tasks that failed to build |
| generate_success_count | The number of tasks that built successfully |
| has_failures | Whether there were any build failures |
| is_timed_out | Whether the build timed out |
| task_count | The total number of tasks a build was initiated against |
| set_id | The ID of the set that was used for processing |
| url | The URL that can be used to retrieve information about the set that was used for processing |
| output_json | the JSON output from build |