Hey Guys,
Ok... I've been feeling a little uneasy about relying on HackyInstaller for
all updating of our Build sensors (ie. LOCC, JUnit, etc). Here is why.
Currently, we store these sensors in the hackyBuild module under version
control. Now that we are probably going to move these sensors out of
version control and just use HackyInstaller to manage these sensors we
might run into problems.
A significant change in an Ant based sensor also could mean that the tool
(ie, LOCC, JBlanket) has been significantly changed. Therefore, users that
just update the JBlanket sensor without updating JBlanket will be totally
confused when their sensor no longer works. Not to mention, that all of a
sudden their build.xml code could be invalid.
In my CLEW build process (which is very similar the Hackystat build
process), I was responsible for ensuring that everyone had the right Ant
based sensors, Ant tools (ie LOCC, JBlanket), and the right build.xml
code. However, if I change CLEW's build process to use HackyInstaller,
then that control is now out of my hands. Again, here is an example. A
while back when the Ant Build Sensor was in development the necessary
build.xml code was changing quite frequently. Luckily, since we had a
"working" version of the build sensor in CVS we didn't need to worry about
the changes till we decided to uniformly upgrade to the new Build
sensor. Now, imagine if we were using HackyInstaller. Once a couple of my
developers upgraded the build sensor causing a broken build, I'd probably
have to change the build.xml on the spot (which is debatable on whether
that is a good or bad thing).
Anyway, I'm just saying that as a Manager of a project using Hackystat
sensors it seems easier to manage the sensors while they are under version
control than under HackyInstaller control. When these sensors are under
CVS, I can be fairly certain that everyone is using the same sensors, which
might not be the most current ones, but at least I know we should have the
same ones. On the other hand, if we rely on the HackyInstaller GUI
interface to update these sensors we probably would have a large range of
different versions amongst our developers.
Then again, this might not be a problem if sensors our sensors don't change
very much.
thanks, aaron
- [HACKYSTAT-DEV-L] More thoughts about HackyInstaller Aaron Kagawa
-
