Skip to content

Uninterruptible Tasks #319

@DT-one

Description

@DT-one

I would like to suggest this again.

I have resources being pulled off tasks to complete other shorter tasks when it should be person, with a material resource (both persistent and mandatory) that completes the task without temporarily being allocated to something else. Without something like an uninterruptable constraint I cannot find a way to suppress this behaviour

The original solution, setting priority to 1000 to prevent prevent resource stealing, doesn't work.

Of course I am ignorant, but I don't see why it would be hard to implement, just mark the resource as hard unavailable once the task has started. If you can't fulfil another task because of this, throw an error

#40

I would like to suggest new feature: Uninterruptible Tasks.

Some tasks involve setup times that would have to be duplicated after every break. So one thing would be to model those explicitly, but as a workaround, it would be nice to be able to tell taskjuggler that no breaks are allowed. Example below.

Hand in hand with this goes another idea: Persistent allocations for nested tasks.

Maybe I'm doing it wrong, but the persistent flag for allocations for nested tasks is not respected and subtasks are executed by different resources.

Example:

task "A"
{
uninterruptible
allocate joe { alternative jack persistent }
task "B"
task "C"
}

Should be executed without breaks, by either joe or jack.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions