Hi, TestReviver that is a part of HudsonBuildTools20 and it is a tool that can process Fuel files generated by CI server. It is an UI tool dependent on Spec so it adds some mess to headless images without GUI that need to use HudsonBuildTools for SUnit reports. I propose to remove it from the standard image and move it to a separate SmalltalkHub project. It is not used directly in Pharo and will be easy to load it from the Catalog by people who need such functionality. Cheers, -- Pavel
On 26 Feb 2016, at 16:50, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
TestReviver that is a part of HudsonBuildTools20 and it is a tool that can process Fuel files generated by CI server. It is an UI tool dependent on Spec so it adds some mess to headless images without GUI that need to use HudsonBuildTools for SUnit reports. I propose to remove it from the standard image and move it to a separate SmalltalkHub project. It is not used directly in Pharo and will be easy to load it from the Catalog by people who need such functionality.
Yes, tools should be separate from the base. We should rename HudsonBuildTools in JenkinsBuildTools, too⦠Marcus
Go go go :) Le 26/2/16 16:50, Pavel Krivanek a écrit :
Hi,
TestReviver that is a part of HudsonBuildTools20 and it is a tool that can process Fuel files generated by CI server. It is an UI tool dependent on Spec so it adds some mess to headless images without GUI that need to use HudsonBuildTools for SUnit reports. I propose to remove it from the standard image and move it to a separate SmalltalkHub project. It is not used directly in Pharo and will be easy to load it from the Catalog by people who need such functionality.
Cheers, -- Pavel
participants (3)
-
Marcus Denker -
Pavel Krivanek -
stepharo