Ok, I will merge the code changes. Our package actually was already renamed JenkinsBuildTools [1] :)
[1] https://github.com/jbrichau/JenkinsBuildTools <https://github.com/jbrichau/JenkinsBuildTools> > On 28 May 2015, at 13:02, Esteban Lorenzano <esteba...@gmail.com> wrote: > > ahhhhh :) > that’s integrated in image (not that I’m happy with that, but… ) so it has to > be handled (for now) with SLICEs. > I would be super happy if you create a configuration of it and extract it to > a subproject (like sthub Pharo/HudsonBuildTools… or even better > Pharo/JenkinsBuildTools). > then we can manage it through configurations, a much much better approach :) > > Esteban > >> On 28 May 2015, at 12:55, Johan Brichau <jo...@inceptive.be >> <mailto:jo...@inceptive.be>> wrote: >> >> Esteban, >> >> I mean the HudsonBuildTools Smalltalk package containing classes such as >> HDTestReport >> >> it’s still in your Pharo4 image btw :) >> >> Johan >> >>> On 28 May 2015, at 11:43, Esteban Lorenzano <esteba...@gmail.com >>> <mailto:esteba...@gmail.com>> wrote: >>> >>> HI, >>> >>> Hudson tools are obsolete since… well, since before hudson was renamed as >>> jenkins :) >>> I don’t know why you maintain them or what changes you did, but is not >>> needed and we are not using them since years (I don’t even remember last >>> time I checked at them). >>> Instead, we use zeroconf and command line (check at our configurations in >>> ci.pharo.org <http://ci.pharo.org/> and pharo-contribution to have an idea… >>> >>> Now, what we still use is the scripts to build distributions (formerly >>> one-click, now platform dependent). You can check them at: >>> https://github.com/pharo-project/pharo-ci >>> <https://github.com/pharo-project/pharo-ci> >>> >>> Esteban >>> >>>> On 28 May 2015, at 10:49, Johan Brichau <jo...@inceptive.be >>>> <mailto:jo...@inceptive.be>> wrote: >>>> >>>> Hi all, >>>> >>>> Over the past few years we have maintained our own fork of Lukas’ >>>> HudsonBuildTools package, but I noticed there are updates flowing in with >>>> newer version of Pharo. >>>> >>>> So, I would like to merge our version with Pharo’s (and vice-versa) but I >>>> am unable to find where the main repository for this package is. >>>> >>>> Can anyone point me to that? >>>> >>>> thanks >>>> Johan >>> >> >