Skip to end of banner
Go to start of banner

addEnvironmentTrigger

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 65 Next »

See also: Actions

Description

Add a trigger to a deployment project. Pre-defined types are: scheduled, afterSuccessfulStage, afterSuccessfulPlan, afterSuccessfulDeployment. One or more repositories can be specified for pre-defined type triggers based on repositories. Custom types can be specified with the appropriate trigger key (or alias) and all required parameters using the various field parameters.

Required Parameters

deploymentProject, name, type

Optional Parameters

repository, branch, schedule, ipRestriction, triggeringEnvironment, disable, field, field1, value1, field2, value2

Type

Create

Category

Deployments

Output Formats

Replacement Variables

Since Version

Examples

addEnvironmentTrigger

Related How To's

  • No labels

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.