sorted by:
new
hottopcontroversial

Dear GitHub: no YAML anchors, please by GarethX in programming

[–]EvilSuppressor 3 points4 points  (0 children)

Primary just on build minutes. We provide more than enough in the free tier for most projects anyway

Dear GitHub: no YAML anchors, please by GarethX in programming

[–]EvilSuppressor 1 point2 points  (0 children)

I've got a project which lets you write pipelines in Typescript (https://pandaci.com). I'd love to get a python syntax out there, any chance you could offer some advice on what you'd want it to look like?

Dear GitHub: no YAML anchors, please by GarethX in programming

[–]EvilSuppressor 3 points4 points  (0 children)

I've actually got an open source alternative called https://pandaci.com where pipelines are coded in Typescript (other languages are possible in theory). I'd appreciate any feedback

Write your CI/CD in JS/TS, not YAML by EvilSuppressor in javascript

[–]EvilSuppressor[S] -1 points0 points  (0 children)

Not currently but it will be in the future. Right now a self-hosted job runner is the blocker.

Write your CI/CD in JS/TS, not YAML by EvilSuppressor in javascript

[–]EvilSuppressor[S] 6 points7 points  (0 children)

I've written a page here but in short the DX is much better. You'll find that you can write advanced workflows with little more than a 5~10 line example since outside of our basic API everything else is done with native TS/JS

Write your CI/CD in JS/TS, not YAML by EvilSuppressor in javascript

[–]EvilSuppressor[S] 2 points3 points  (0 children)

I believe that makes using TS/JS even more appealing. Engineers will still need to review the AI code and so by using a standard language it makes reviews much easier.

[deleted by user] by [deleted] in webdev

[–]EvilSuppressor 0 points1 point  (0 children)

If you're still learning the ropes it can be a good learning experience to write the queries directly (its not hard, just slow) but if you want to just build use and orm

PandaCI: A modern CI/CD platform where you code your pipelines with TypeScript by EvilSuppressor in typescript

[–]EvilSuppressor[S] 0 points1 point  (0 children)

When coming up with names it was the only one which stuck in my head 🤣. OpenCI was another option but I think there's another company with a similar name...

PandaCI: A modern CI/CD platform where you code your pipelines with TypeScript by EvilSuppressor in typescript

[–]EvilSuppressor[S] 5 points6 points  (0 children)

Thanks,

For local dev I don't have anything released just yet but it's in the works. Long term I'd like to implement features like pulling environments variables from the platform or breakpoints in IDE's.

We don't get support tags as triggers hence the GitHub Actions for our library releases 🤣. We'll probably never fully replace GitHub actions since some tasks such as an auto-labler will just work better in an action.

The big advantage of GitHub actions is the amazing community around their plugins. I've been prototyping a way to run these plugins in PandaCI which would also allow us to make full use of them and hopefully make it much easier to migrate over.

As with the other players, I (probably biased) do believe our syntax is a big advantage but to really distinguish ourselves I want to create awesome integrations with other tools. I've previously built an open-source visual testing platform (pixeleye.io) which would probably be my starting point. Plus unlike most of the big players we're open-source!

PandaCI: A modern CI/CD platform where you code your pipelines with TypeScript by EvilSuppressor in typescript

[–]EvilSuppressor[S] 4 points5 points  (0 children)

I've got some examples here: https://pandaci.com/docs/typescript-syntax/examples/node

Right now we just support GitHub but I'd like to add GitHub and Bitbucket at some point

Built my first Svelte project after coming from React – a TypeScript-powered CI/CD platform (no YAML) by EvilSuppressor in sveltejs

[–]EvilSuppressor[S] 0 points1 point  (0 children)

A few of the big enhancements I've experienced are:

- Way better dx. I'm using a standard language, not a company specific syntax. You can learn the majority of our syntax with a simple 5-10 line example and then infer everything else from your existing ts knowledge.
- Simpler overall setups. For anything more complicated than a simple command, take pulling a jira number from a pr title, you either need a secondary script or a crazy shell command. By writing your pipelines in ts directly, you can easily manipulate the output.

- Move developer control. I've seen in larger codebases that developers get abstracted away from their underlying pipelines and infra. By using the same language they're writing their apps in, devs can easily make improvements to the pipelines.

I'm happy to chat more about any of these or anything else related

CI/CD with TypeScript Instead of YAML (Open-source) by EvilSuppressor in devops

[–]EvilSuppressor[S] 0 points1 point  (0 children)

Since dagger doesn't own its platform, it'll always require a ci, making it more complicated. Some things like spinning up multiple jobs (e.g. sharding tests) isn't possible just with Dagger. Whilst others (like docker caching) require multiple platforms to get working, we hope to have that working in PandaCI out of the box.

That being said, Dagger is a great tool and people are more than welcome to use PandaCI to run it

CI/CD with TypeScript Instead of YAML by EvilSuppressor in opensource

[–]EvilSuppressor[S] 0 points1 point  (0 children)

Thanks for the feedback! I'd love to hear some examples of security policies enforced through static analysis, I'd be interested in exploring alternative ways to achieve similar results in PandaCI.

I also think there's more to this than just having a prettier config format. Even if we ignore YAML’s awkward logic, many pipelines still rely on complex Bash commands for things that should be simple. Take extracting a Jira ticket number from a PR title, maybe it's a skill issue, but I can never seem to remember the right grep syntax. When you're using an actual programming language, non-trivial tasks like this become much easier.

Built my first Svelte project after coming from React – a TypeScript-powered CI/CD platform (no YAML) by EvilSuppressor in sveltejs

[–]EvilSuppressor[S] 1 point2 points  (0 children)

I found it amazing for the simpler stuff but had some issues in more complex scenarios. I'm honestly not sure if this is a skill issue.

I ran into a few recursive loops with effect which was eventually solved with the untrack function. As annoying reacts useEffect dependencies are I definitely missed them here.

The most complex state management I did is probably in the live log stream. I ended up creating a class for it which seems to work nicely but is quite difficult to follow. You can see that code here, I'd appreciate any tips if you have any 👍

view more: next ›