Introduction
Architecture
Onboard
Introduction
Teams
Users
Introduction
IntroductionPromote an image in Amazon ECRDownload a file from JFrog ArtifactoryMove or copy an image from JFrog ArtifactoryUpload a file to JFrog ArtifactoryStore an object on Amazon S3Retrieve an object from Amazon S3
IntroductionCreate or update a functionInvoke a function
IntroductionRun an AWS CodePipelineRun a Bamboo projectRun a Bitbucket pipelineRun a CloudBees CI jobRun a CircleCI workflowRun a GitHub Actions workflowRun a GitLab pipelineRun a Harness pipelineRun a Jenkins® jobRun a JFrog pipelineRun a TeamCity project
Check out a Git repository
IntroductionAWS credentialsECR credentialsEKS credentialsGit global credentialsOCI credentials
IntroductionRun Argo WorkflowsCopy a remote image with CraneDeploy a binary with EC2Deploy to ECSRender an ECS task definitionBuild a container image with KanikoDeploy with OctopusDeploy with SpinnakerRun Ansible PlaybookDeploy with HerokuDeploy with AWS CodeDeployDeploy with AWS Elastic Beanstalk
Publish evidence items
IntroductionHelm chart installHelm chart packageHelm chart publishHelm chart uninstall
IntroductionCreate a Kubernetes namespaceCreate/update a Kubernetes resourceDeploy to a Kubernetes cluster
IntroductionVerify with NewRelic
Execute remote commands via SSH
IntroductionAnchoreAquasecJFrog XraySnyk ContainerSonatype (Nexus) ContainerTrivy
IntroductionStackhawkZAP
IntroductionCheckmarxFind Security BugsGitHub Security ScannerGosecMendNexus IQSnykSonarQube bundledSonarQube
IntroductionMendSnyk
IntroductionTruffleHog ContainerTruffleHog CodeTruffleHog S3
Publish test results
CI insights for Jenkins

Manual approval

2 minute read

Use this job to request a workflow approval from users and teams. Refer to Manage workflows for more information.

All CloudBees custom job repositories are listed at CloudBees, Inc. on GitHub.

Inputs

Table 1. Input details
Input name Data type Required? Description

approvers

String

No

A list of users whose participation in the workflow approval process is requested. The approvers field supports both user IDs and email addresses.

delegates

String

Yes

The value must be the path to the Manual approval custom job yaml file: cloudbees-io/manual-approval/custom-job.yml@v1

disallowLaunchByUser

String

No

When set to true, it prevents the user who started the workflow from participating in the approval. Default value is false.

instructions

String

Yes

Use to add instructions for approvers. This text will appear:

  • In the approval response request email notification.

  • On workflow run details screen.

notifyAllEligibleUsers

String

No

Use to notify all users who have the execute approval permission on the workflow when no approvers are listed by selecting Notify all eligible users. Default value is false.

Notifications will be sent as follows:

  • If users are listed in Approvers and Notify all eligible users is true or false, then

    • Only listed approvers will receive notification.

    • Only listed approvers can participate in approval process.

  • If Approvers is blank and Notify all eligible users is false, then

    • No notifications will be sent.

    • All eligible users can participate in approval process.

  • If Approvers is blank and Notify all eligible users is true, then

    • The CloudBees platform will select and notify up to 10 eligible users.

    • All eligible users can participate in approval process.

timeout-minutes

Integer

No

The amount of time approvers have to respond to the approval request. The default value is 4320 minutes (three days).

Usage example

In your YAML file, add:

 workflow-approval-name:
    timeout-minutes: 4320
    delegates: cloudbees-io/manual-approval/custom-job.yml@v1
    with:
      approvers:
      notifyAllEligibleUsers: false
      instructions: "Enter instructive text for approvers here. "
▼
Introduction