actions-marketplace-validations/Code Pipeline Generate
Run a mainframe generate using Code Pipeline.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Nov 17, 2025
- License
- None
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/bmc-compuware_ispw-generate@980feb1aff8eff605d56010b7be35e4e5bb676dc # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
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 generate 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 generated | no | — |
| generate_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 | no | S |
| execution_status | I for immediate execution or at start date/time, H to create request in hold | no | I |
| auto_deploy | Generates can be set up to automatically Deploy as well by an option set up by the Code Pipeline. The default is to not use Auto Deploy. If the Auto Deploy option is set-up through Code Pipeline, then you may use this option to automatically deploy instead of using the deployAutomatically option within the DeployTask/DeployAssignment/DeployRelease actions | yes | false |
Outputs
| name | description |
|---|---|
| generate_failed_count | The number of tasks that failed to generate |
| generate_success_count | The number of tasks that generated successfully |
| has_failures | Whether there were any generate failures |
| is_timed_out | Whether the generate timed out |
| task_count | The total number of tasks a generate 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 |