Gregory's ServerWe want to have (potential) #user #feedback :)
If you use Github-/Gitea-/Forgejo- #actions , why have you not switched or what would make you potentialy do so?
If you are not in position to decide, just try to asume why :)
For "other" feedback, just comment "below" ;)
Please #retweet so we get more coverage :)
Anonymous poll
Poll
I'm used to actions syntax
1
50%
I don't want to selvhost
0
0%
Woodpecker confix/syntax is hard
1
50%
Because of all the predefined existing actions
2 people voted. 2
100%
Voting ended 16 November at 12:35.
@WoodpeckerCI Maybe not useful, but I went the other direction. I don’t like the complexity of GitHub actions so never wanted to use Forgejo actions and instead picked Woodpecker due to previous familiarity with drone
@WoodpeckerCI
For me it's basically backwards. I don't like Actions, more Gitlab-like syntax is what I like.
I still didn't migrate from Drone to WoodpeckerCI, but it's planned:
https://git.skobk.in/skobkin/docker-stacks/issues/88
And the only thing is stopping me right now is a lot of already existing CI pipelines which I need to check first.
// Sorry if the first part wasn't about what you were asking, but the second is.
@WoodpeckerCI
For me it's basically backwards. I don't like Actions, more Gitlab-like syntax is what I like.
I still didn't migrate from Drone to WoodpeckerCI, but it's planned:
https://git.skobk.in/skobkin/docker-stacks/issues/88
And the only thing is stopping me right now is a lot of already existing CI pipelines which I need to check first.
@WoodpeckerCI the biggest point of friction for me is that you cannot simply run docker itself in the standard docker based runner setup, making it awkward to embrace something like testcontainers or other ad-hoc scripts that run docker: all such workflows need to be translated and duplicated into equivalent woodpecker plugins/steps. That wouldn't be so bad if woodpecker offered a standalone runner that could run on a dev machine and execute flows locally as part of the developer iteration loop.