[CI] help needed: integration of Fuel changes with new version number
Hi guys Clément asked us a while ago to update Fuel for Spur support and we did (https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-seriali... <https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-seriali...>). The problem now: Fuel is an integral part of the integration process and the change to the Fuel version number means that the automatic integration will not work. Hereâs why: This slice can't be automatically integrated because I changed the Fuel version number. Now, when the image worker reads the result from the validation, Fuel raises an exception because of the different version numbers in the parent and child image. We should probably add a mechanism that ensures that the original Fuel version is reloaded after the validation, such that the Fuel file is written by the same version that then reads it in the parent. Can someone please manually integrate or (which would be way cooler) adapt the integration process such that future updates to Fuel can be automatically integrated? Cheers, Max
On 05 Feb 2015, at 11:35, Max Leske <maxleske@gmail.com> wrote:
Hi guys
Clément asked us a while ago to update Fuel for Spur support and we did (https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-seriali... <https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-seriali...>). The problem now: Fuel is an integral part of the integration process and the change to the Fuel version number means that the automatic integration will not work. Hereâs why:
This slice can't be automatically integrated because I changed the Fuel version number. Now, when the image worker reads the result from the validation, Fuel raises an exception because of the different version numbers in the parent and child image.
We should probably add a mechanism that ensures that the original Fuel version is reloaded after the validation, such that the Fuel file is written by the same version that then reads it in the parent.
Can someone please manually integrate or (which would be way cooler) adapt the integration process such that future updates to Fuel can be automatically integrated?
Ok, I have put it on Fix To Include (after checking that it merges well) and will include it with the next update. Marcus
On 05 Feb 2015, at 15:19, Marcus Denker <marcus.denker@inria.fr> wrote:
On 05 Feb 2015, at 11:35, Max Leske <maxleske@gmail.com <mailto:maxleske@gmail.com>> wrote:
Hi guys
Clément asked us a while ago to update Fuel for Spur support and we did (https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-seriali... <https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-seriali...>). The problem now: Fuel is an integral part of the integration process and the change to the Fuel version number means that the automatic integration will not work. Hereâs why:
This slice can't be automatically integrated because I changed the Fuel version number. Now, when the image worker reads the result from the validation, Fuel raises an exception because of the different version numbers in the parent and child image.
We should probably add a mechanism that ensures that the original Fuel version is reloaded after the validation, such that the Fuel file is written by the same version that then reads it in the parent.
Can someone please manually integrate or (which would be way cooler) adapt the integration process such that future updates to Fuel can be automatically integrated?
Ok, I have put it on Fix To Include (after checking that it merges well) and will include it with the next update.
Marcus
Great, thanks.
participants (2)
-
Marcus Denker -
Max Leske