Jallib build frequency

[Matthew Schinkel]

Hi everyone, as you can see there is a jallib-dev build (maybe I should name it differently).

Anyways, I run a build every hour if any changes have been committed. Some days there are multiple changes throughout the day, and multiple posts to the group.

It is handy that when you commit, a build is run and you know if there are issues with the committed files. I'm just not sure how often we need this.

Would you prefer one build per day or is it good as is?

Matt.

[Rob CJ]

Hi Matt,

I think once a day is enough. Sometimes - not often - I commit something more than once a day and for me it is not needed to have a buil on each commit (or in an hour), once a day is good enough for me. It prevents that you get more than one e-mail per day.

When I make a mistake I am already warned since GitHub runs a Python script after each commit that I do which validates all jal files and compiles all samples. If something goes wrong I get an e-mail and I can fix it. And if your server checks once a day, it - hopefully - only sends the message that the build succeeded. 

Kind regards,

Rob

---

Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Matthew Schinkel <mattsc...@hotmail.com>
Verzonden: donderdag 5 februari 2026 22:20
Aan: jallib <jal...@googlegroups.com>
Onderwerp: [jallib] Jallib build frequency

 

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jallib+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jallib/4f974a1c-80f0-4531-be33-f205590e60fdn%40googlegroups.com.