jdev - 2023-09-09

  1. agh

    Zash: wonderful, thank you.

  2. Guus

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

  3. Guus

    Openfire uses both Atlassian Bamboo and Github workflows

  4. Guus

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

  5. Guus

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

  6. Guus

    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. :)

  7. Guus

    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?)

  8. Guus

    Mongoose seems to have CircleCI and Github workflows

  9. Guus

    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.

  10. lovetox

    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

  11. lovetox

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

  12. lovetox

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

  13. lovetox

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

  14. lovetox

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

  15. lovetox

    both think are very dependent on the language and ecosystem in use

  16. lovetox

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

  17. Guus

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

  18. MattJ

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

  19. MattJ

    Written in and configured in

  20. Guus

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

  21. moparisthebest

    Guus: Jenkins!

  22. moparisthebest

    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

  23. singpolyma

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

  24. Zash

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

  25. Guus

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

  26. moparisthebest

    > 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

  27. moparisthebest

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

  28. Zash

    Jackal seems to have some Github CI stuff

  29. Guus

    moparisthebest: fair enough ☺️