actions-marketplace-validations/Code Pipeline Deploy

Run a mainframe deploy using Code Pipeline

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/bmc-compuware_ispw-deploy@5941c6ac4c55c0c6ad225e50b1b1d37c1e5cb8eb # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

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 deploy 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 deployed	no	—
deploy_automatically	The request parameters for the deploy 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	no	I
deploy_environments	Define specific environments to deploy. If you wish to deploy to only certain environments, you can list them here, separated by a space. The length of the field is limited to 255.	no	false
system	Define a specific system to deploy	no	false

name	description
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