forge
/
build.sh
3
2
Fork 1
Code Issues 6 Pull Requests Releases Wiki Activity

Rework lockfile mechanism #13

New Issue
Open
opened 2020-04-27 09:50:04 +00:00 by southerntofu · 1 comment
southerntofu commented 2020-04-27 09:50:04 +00:00
Owner
Copy Link

Rework git-build.sh lockfile so we can have multiple git-build running in parallel. This will be useful for forgehook

Rework git-build.sh lockfile so we can have multiple git-build running in parallel. This will be useful for forgehook
southerntofu commented 2020-04-27 09:57:46 +00:00
Author
Owner
Copy Link

For example, git-build when running for a set of tasks could hash the arguments and setup a .git-build.HASH.LOCK so that calling different tasks has different lockfiles?

For example, git-build when running for a set of tasks could hash the arguments and setup a .git-build.HASH.LOCK so that calling different tasks has different lockfiles?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
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.sh#13
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?