jdev - 2023-09-09

Zash: wonderful, thank you.

Server developers: what automation do you use in your project, with regards to continuous integration / running tests?

Openfire uses both Atlassian Bamboo and Github workflows

EJabberd seems to use Github workflows too: https://github.com/processone/ejabberd/blob/master/.github/workflows/ci.yml - anything else?

I'm not seeing any obvious CI integration in Tigase's Github repo

Prosody is using Mercurial and is Lua - I tried poking it with a stick from a distance, but I can't make head or tails from that. :)

I'm not sure if M-Link's source / build is public in the first place (probably not, given that it's a commercial package, right?)

Mongoose seems to have CircleCI and Github workflows

I'm probably missing a lot of things. Anyone care to correct/complete me? I'm trying to find common denominators, to build tooling that would benefit most projects.

what i find pretty cool is that ejabberd can execute a build on any branch, and user can then download and install that, makes it easy for the developers to tell the users to test a specific fix or feature for example without merging it into main branch

probably i lack imagination but what would be tooling that is useful for many server projects ?

specifically tooling that would work, independent of how the project is setup (git provider, programming language)

i could only imagine maybe some kind of standardized test suite where projects can test against

other than that, i think CI is mostly used for building packages and linting your code

both things are very dependent on the language and ecosystem in use ✏

I'm only asking what CI/CD frameworks are in use by the projects, if any :)

Guus: for Prosody we use buildbot (written in Python)

Written in and configured in

I didn't know that one. Reading up on it.

Guus: Jenkins!

I no longer have time for proprietary crap that: 1. I can't test locally 2. Can change out from under me at any time That rules out GitHub actions, circle ci, remember Travis CI ? Etc etc

Travis was open soruce, I'm still running a self hosted version on one of my servers

moparisthebest, https://github.com/nektos/act

moparisthebest: I'm not asking what you prefer, I was asking what's in use by the existing server projects. ☺️

> moparisthebest, https://github.com/nektos/act Yes I saw this, it's interesting, but still only trying to copy some features from GitHub actions, your mileage may vary Meanwhile I'm using these scripts https://github.com/moparisthebest/self-ci (0 documentation lol) to build all my stuff on my own Jenkins on push, or locally the same ↺

Guus: xmpp-proxy is a server project if you squint :P https://github.com/moparisthebest/xmpp-proxy/tree/master/.ci

Jackal seems to have some Github CI stuff

moparisthebest: fair enough ☺️