Forum Discussion

Henchway's avatar
Henchway
Contributor
5 years ago

Settings a HTTP response code for triggered tasks

Hi everyone, we’re offering a triggered task as a sort of simplified API for a more complex REST API (specifically Jira). What we want to achieve is to influence the HTTP return code, status and ...
bojanvelevski's avatar
bojanvelevski
Valued Contributor
3 years ago
Copy LinkReport

Hi @Chandan,

You can rename the pipeline you’re importing, to be similar but yet distinctive from the prod one. Maybe add a suffix -1 ?

Ex.
Prod: pipeline
Import: pipeline-1

Now when you have the new pipeline in the required project, you can easily point the executor to that pipeline, and revert to the old one if needed. By Executor I mean, triggered task, scheduled, Pipeline Execute.

Or you can even export the prod pipeline, and keep it locally in case a rollback is needed.

Is this acceptable to you?

Chandan's avatar
Chandan
New Contributor III
3 years ago
Copy LinkReport

I can use this approach along with the solution provided by @dmiller. This will enable me have a copy of existing pipeline ( with different name in different canvas) and edit the original versioned pipeline in its own canvas.