Hi Tim.

We do a cron job for squeak-app to create the updated bundles for files.squeak.org. Daily for Trunk, monthly for releases. In-image changes are not propagated to GitHub or TravisCI.

You could avoid a cron setup by -- after any change in your selected packages -- writing stuff to some related repository which can then be tracked through GitHub/TravisCI.

Hmm.. you can also set up Squot and track/commit/push the packages you are interested in to some personal repo. Maybe fork github.com/squeak-smalltalk/squeak-app and push changes to there into some folder. From there you can integrate TravisCI, too. From within your working image, you could automatically trigger Squot to do that pushing from time to time.

Maybe this helps. :-)

Best,
Marcel
Am 05.11.2020 03:34:41 schrieb tim Rowledge <tim at rowledge.org>:
I'd rather like to monitor a number of packages and trigger a build cycle when something new has been spotted; sort of a CI server setup for internal use.

There's bits of what look like partial solutions to this scattered around the image but I'm not spotting quite what I want so far. There's methods to query repositories about latest versions, but they seem to be not quite what I need. I could imagine using MCConfigurations somehow but it's still a bit vague.

Has anyone already done something of this sort? I'm keen to avoid wasting time if this is a solved thing.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Never do card tricks for the group you play poker with.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20201105/f4866b81/attachment-0001.html>