Skip to main content
Contact a Moderator

Question

1
Replies
324
Views
 Mohammed Burhanuddin (MohammedB9117)
incessant Technologies

incessant Technologies
IN
MohammedB9117 Member since 2018 2 posts
incessant Technologies
Posted: December 26, 2018
Last activity: January 24, 2019
Posted: 26 Dec 2018 2:50 EST
Last activity: 24 Jan 2019 3:19 EST
Closed

Deployment Pipeline stages limitation

We are planning to make use of Deployment Mgr on 7.4. By default this is having 4 stages, Dev, QA, STG and PROD. Why this limitation of only 4 environments and how to over come this. When thought of trying to extend, all of the corresponding rules are internal and final. We are having more than 4 environments, like STG1 and STG2 or Pre-PROD. Can we not make use of Deployment Mrg in our scenario.

Please suggest.

Thanks in advance.

DevOps
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 2 years ago
Posted: 24 Jan 2019 3:19 EST
Sumit Khurana (khurs)
PEGA
Sr. Product Manager- DevOps
Pegasystems Inc.
IN

Deployment Manager today cannot support more than 4 stages in the application life cycle. We have this on our roadmap though. 


However, you can create two pipelines for the same application, have one pipeline publish the artifact and on the other as you start deployment, choose the option "Deploy an existing artifact" and select the artifact generated by the first pipeline

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice