Requirement: Any way we can just disable a stage, task, or job, instead of deleting it? This will keep us from having to re-create them if they are removed.
Currently it is not possible to disable a stage, task or job so you can use it later if required.
However Go versions your config with every run, this way you can reference the stage/job/task details from the version-ed config files.
Comments
7 comments
Yeah, please do this. It's also a pain for debugging a pipeline if you have to destroy stages to skip them.
I concur. This is one of my first struggle working with Go. Now that Go is Open Source, guidance on where this piece is located in the code or how you would recommend about implementing such feature is also welcomed :)
Olivier,
It's not a great solution, but you can always drop into xml (admin -> config xml -> edit) and grab the stage or task, and keep it externally somewhere.
Andrew,
Thanks - interesting workaround. I can see a lot of use cases for a "bypass" option in UI and API though...
agreed. my solution is in the "hack" category.
Can someone share their solution? I didn't manage to disable a job and this is frustrating!
I tried to hack with resources, but if you put a resource for which either there is no agent or the associated agent is disabled, then the job results unassigned indefinitely.
Thanks.
Hi Emanuele,
This conversation might help you.
Please note that this group is not available anymore. You should use this google group in future.
Thanks,
Juhi
Article is closed for comments.