Woodpecker CI

49 readers

2 users here now

Welcome to the Woodpecker CI Community.

🌳 This is a place for users, developers, and enthusiasts of Woodpecker CI to share, discuss, and learn about all things related to this open-source continuous integration tool. Whether you're troubleshooting, sharing pipelines, or discussing best practices, you're in the right place!

Rules

Respect Everyone: Treat all members with respect. No harassment, discrimination, or belittling of any kind.
Stay On Topic: Posts should be related to Woodpecker CI. Off-topic discussions will be redirected or removed.
Search Before Posting: Avoid duplicate questions. Use the search function to see if your topic has already been covered.
No Spam or Over Self-Promotion: Spamming and self-promotion are not allowed. Relevant content and contributions are welcome, but should not be overdone.
Use Descriptive Titles: When creating a new post, use a clear and descriptive title to help others understand what it's about.
Be Constructive: Criticism is welcome when it's constructive and intended to improve the conversation.

Resources

founded 11 months ago

MODERATORS

alx

Here is Woodpecker 2.5.0 (woodpecker-ci.org)

submitted 5 months ago by alx to c/woodpecker_ci

3 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 5 months ago

OK, so, the project looks cool, and I'm grateful for any OSS. Let me put that up front.

However. I'm going to bitch a little about standards. Every single CI tool re-invents their own build syntax. It's always some .XYZ.yaml file in your project; they all look almost exactly alike and have essentially the same structure and operations, but they each feel the need to make things slightly differently, making them non-portable between systems.

Compare Woodpecker's .woodpecker.yaml to Github's .github/workflow.yaml, to Sourcehut's .build.yaml... they're almost, but not quite, all the same.

Please, for the love of dog, pick a fucking standard so I don't have to remember each and all of your special snowflake terminology for the same god-damned functions. There is no standard; not even in ForgeFed. So if you're developing a new CI system, please please just pick one of the existing ones - I don't care which, because they all do the same god-damned things - and use it. It'll be one less syntax I'll have to learn if I want to try your project.

Please. I'm literally begging you. Stop re-inventing this wheel: it's going to look exactly like all the other wheels, only be incompatible.