Support Actions concurrency syntax#32751
Conversation
3551677 to
fcf4517
Compare
52833e7 to
130f2a2
Compare
461c7c1 to
d5168a2
Compare
e038ed2 to
f77f266
Compare
concurrency for Actionsconcurrency syntax
ad71599 to
8f5948b
Compare
This comment was marked as resolved.
This comment was marked as resolved.
) Move the main logic of `generateTaskContext` and `findTaskNeeds` to the `services` layer. This is a part of #32751, since we need the git context and `needs` to parse the concurrency expressions. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
I have no more questions. If the new changes look good, feel free to merge. Thank you all. |
|
@lunny Are there any considerations to backport this PR to 1.25 ? Thanks. |
|
IMO This is too large for backporting and changes the database structure |
Thanks for the response. Did 1.25.1 or earlier versions introduce any other setting or feature that would enable new workarounds to avoid ongoing pipelines being cancelled by new pushes? Ideally the jobs would queue, the concurrency syntax feature is secondary to me. |
|
1.25 won't get large changes. I think you can use the main-nightly, it should be stable enough for daily usage. And any bug will be fixed in first time. |
|
When can we expect this to be released? As mentioned, 1.2X release isn't going to happen due to the changes needed. However, as it is merged, where can I see for which release it's planned? |
|
It's in the linked milestone |
No guarantees but, 1.26 should happen rather soonish, maybe a few more weeks. |
| if _, err := x.SyncWithOptions(xorm.SyncOptions{ | ||
| IgnoreDropIndices: true, | ||
| }, new(ActionRun)); err != nil { | ||
| return err | ||
| } | ||
|
|
||
| if err := x.Sync(new(ActionRun)); err != nil { | ||
| return err | ||
| } |
There was a problem hiding this comment.
Why SyncWithOptions then Sync? Bug?
Fix #24769
Fix #32662
Fix #33260
Depends on https://gitea.com/gitea/act/pulls/124
This PR removes the auto-cancellation feature added by #25716. Users need to manually add
concurrencyto workflows to control concurrent workflows or jobs.