Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Modifying an application pipeline

Updated on July 14, 2022

You can modify the details of your pipeline, such as configuring tasks, updating the repositories that the pipeline uses, and modifying the URLs of the systems in your environment. You cannot modify information if your pipeline is running.

  • Modifying application details

    You can modify application details, such as the product rule that defines the content of the application that moves through the pipeline.

  • Modifying URLs and authentication profiles in 5.5.x

    You can modify the URLs of your development and candidate systems and the authentication profiles that are used to communicate between those systems and the orchestration server.

  • Modifying repositories

    You can modify the development and production repositories through which the product rule that contains application contents moves through the pipeline. All the generated artifacts are archived in the development repository, and all the production-ready artifacts are archived in the production repository.

  • Modifying stages and tasks in the pipeline

    You can modify the stages and the tasks that are performed in each stage of the pipeline. For example, you can skip a stage or add tasks such as Pega unit testing to be done on the QA stage.

  • Modifying merge options for branches in 5.5.x

    If you are using branches in your application, specify options for merging branches into the base application.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us