Manually triggered pipeline stages don't allow deployment promotion?

[Nathan Zipf]

Hi all,

I just discovered stages which I have found useful for grouping up build and deploy steps of my pipeline for each environment. 

Is it a known limitation that you can't 'promote' from a deployment stage? I could not find this anywhere within the stage documentation and understand that it is in beta, so not sure if it's a bug or just an undocumented limitation. 

Example pipeline using stages as follows (no ability to 'promote' within deployments tab):

pipelines:
  default:
    - stage:
        name: Build & Deploy Test App
        deployment: Test
        trigger: manual
        steps:
          - step:
              name: Build App
              script:
                - **build**
          - step:
              name: Deploy App
              script:
                - **deploy**
    - stage:
        name: Build & Deploy Production App
        deployment: Production
        trigger: manual
        steps:
          - step:
              name: Build App
              script:
                - **build**
          - step:
              name: Deploy App
              script:
                - **deploy**

In this example without stages, this would allow 'promotion' from Test to Production deployment:

pipelines:
  default:
    - step:
        name: Build & Deploy Test App
        deployment: Test
        trigger: manual
        script:
          - **build**
          - **deploy**
    - step:
        name: Build & Deploy Production App
        deployment: Production
        trigger: manual
        script:
          - **build**
          - **deploy**

Please let me know if I'm missing something. 

Thanks in advance

[Theodora Boudale · Accepted solution]

Hi Nathan and welcome to the community!

This is a bug, we have a bug report in our issue tracker here:

• https://jira.atlassian.com/browse/BCLOUD-22402

You can add yourself as a watcher (by selecting the Start watching this issue link in the bug report) if you'd like to get notified via email of any updates. You can also select the link This affects my team to indicate you are affected by this issue.

Our development team will post an update on that bug report when this is fixed. Please note that we don't provide ETAs and bug fixing is implemented as per our policy here.

In the meantime, you can select the build number of the build that deployed to Test (from the Deployments page) to open it, and on the build's page, you should see an option to Deploy to Production.

Please feel free to reach out if you have any questions.

Kind regards,
Theodora