Ticket #1115 (new enhancement)

Opened 9 years ago

Last modified 9 years ago

Make phase control options more powerful

Reported by: eternaleye Owned by:
Priority: Sometime Milestone:
Component: clients/cave Version: 0.58.2
Keywords: Cc:
Blocked By: Blocking:
Distribution: N/A


<eternaleye> ciaranm: Is there any chance --skip-until-phase/--abort-at-phase/--change-phases-for could be unified and made more powerful? Maybe something like --phase-modify (skip_until|abort_at|skip|...):<phase>:<spec> ? <eternaleye> ciaranm: I ask becuase I've run into several cases where I needed to resume multiple packages whose builds failed due to timeout, and the fact that --change-phases-for first on a resume changes them for index 1, not for the first non-succeeded package <eternaleye> (repeated swap-of-death is a pain in the ass)

It would need to be possible to specify it multiple times

Change History

comment:1 Changed 9 years ago by ciaranm

Maybe we could just make it ignore already-done stuff when calculating the index for first...

comment:2 Changed 9 years ago by eternaleye

Still not enough, since I'd like to be able to skip more than one phase.

comment:3 Changed 9 years ago by ciaranm

You can specify --skip-phase multiple times, can't you?

comment:4 Changed 9 years ago by eternaleye

For different packages, no.

comment:5 Changed 9 years ago by ciaranm

This is starting to sound excessively complicated... Maybe the solution here is to simplify your usage patterns.

Note: See TracTickets for help on using tickets.