[squeak-dev] automated checking for new versions of a package in order to trigger a build cycle
marcel.taeumel at hpi.de
Fri Nov 6 07:41:05 UTC 2020
> a) developer updates it [the update map/config] when a chunk of work affecting one or more packages is published
We do this already for bigger changes in Squeak Trunk to add checkpoints for the update process.
> c) the image being built loads the latest config
Squeak also loads the "bleeding edge" after loading the latest configs in order. Having more checkpoints, this might not be necessary. Maybe "bleeding edge" could be optional even in Trunk. Not sure whether is can be practical at all ...
Am 06.11.2020 02:32:04 schrieb tim Rowledge <tim at rowledge.org>:
Well it looks like one can do this without too much pain; always nice.
Once you have a config map saved in the repository it is possible to find the version number with sometihng like
| myRepo |
myRepo := MCHttpRepository
^(myRepo highestNumberedVersionNameForPackageNamed: configNameString) versionNumber
Keep track of the highest known value and compare to decide on whether to build.
This way you get a build if the map is updated, which actually solves the potential problem of several packages needing to be saved in a group.
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Oxymorons: Advanced BASIC
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev