Table of Contents

Modifying an application pipeline


Only available versions of this content are shown in the dropdown

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

    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.

  • Configuring Jenkins server information

    If you are using a Jenkins step, specify details about the Jenkins server such as its URL.

  • Modifying merge options for branches

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

  • 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.

Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

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