forge
/
build
1
0
Fork 0
Code Issues 13 Pull Requests Releases Wiki Activity

Task dependencies #7

New Issue
Open
opened 2020-09-22 14:06:58 +00:00 by southerntofu · 0 comments
southerntofu commented 2020-09-22 14:06:58 +00:00
Owner
Copy Link

There should be a way for tasks to specify dependencies. That is a tough one because there's a lot of nuance here:

  • tasks that run after another one, whether it succeeded or not
  • tasks that run after another one succeded
  • etc..

This will pave the way for sanely running tasks in parallel without unexpectedly breaking things

There should be a way for tasks to specify dependencies. That is a tough one because there's a lot of nuance here: - tasks that run after another one, whether it succeeded or not - tasks that run after another one succeded - etc.. This will pave the way for sanely running tasks in parallel without unexpectedly breaking things
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: forge/build#7
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?