workaround: docker-compose example not using the specified labels (step 2) #177
No reviewers
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: forgejo/runner#177
Loading…
Reference in a new issue
No description provided.
Delete branch "earl-warren/runner:wip-upgrade-example"
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?
Builds on top of #175 which, among other things, implements a workaround by explicitly setting the labels in both .runner & config.yml.
depends_on
because its behavior is difficult to understand and sometime racesRefs: #174
159277af9e
to0f6be9f253
0f6be9f253
to6181438eec
6181438eec
to260e1370ca
260e1370ca
to2bb7667643
2bb7667643
toe12df8d551
e12df8d551
to0db35cd1b0
0db35cd1b0
to063838e8dd
063838e8dd
toee4a886ca8
ee4a886ca8
toe28f20bbd0
e28f20bbd0
to3da669eb90
3da669eb90
toa4dbe64e89
a4dbe64e89
toa4f129d128
a4f129d128
to868555f349
fix: the docker-compose example is racyto workaround: docker-compose example not using the specified labels@zwanto this is not yet the fix but it makes the example function in a predictable way.
868555f349
to4c05530aa3
workaround: docker-compose example not using the specified labelsto workaround: docker-compose example not using the specified labels (step 2)