Disabling stages, jobs or tasks

Follow

Comments

7 comments

  • Avatar
    Andrew C Slocum

    Yeah, please do this. It's also a pain for debugging a pipeline if you have to destroy stages to skip them.

  • Avatar
    Olivier Jacques

    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 :)

  • Avatar
    Andrew C Slocum

    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.

  • Avatar
    Olivier Jacques

    Andrew,

    Thanks - interesting workaround. I can see a lot of use cases for a "bypass" option in UI and API though...

  • Avatar
    Andrew C Slocum

    agreed. my solution is in the "hack" category.

  • Avatar
    Emanuele Cantalini

    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.

  • Avatar
    Juhi Bharatbhai Jariwala

    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.