Well, the file system triggers are nice to know, but I'm too low level
a peon in order to implement such a policy on our servers. Besides, we
use AIX and not Linux here.
So I have the following choices:
* Use a crontab entry to look for changes every five minutes or so.
* Use Hudson and use its File System CM plugin to do the same thing.
* Both Nexus and Artifactory can use plugins written in Groovy.
Unfortunately, I don't know Groovy, and the documentation is rather
light on details.
* Use Subversion the triggers do what I want, but training a vendor to
use it might be too difficult. You have to checkout the directory, do
a "svn add', and then do a "svn commit". I'm having a hard enough time
getting the developers here to understand that.
I'm leaning towards using Artifactory or Nexus as the actual release
managers for a variety of reasons, and then using Hudson's ability to
examine the file system for changes in the directory where the
downloaded patches would be stored.
I want to get away from granting direct access to vendors on our
servers, and I both Nexus and Artifactory will have an interface
that's pretty simple to use. Using Hudson allows me to monitor the
directories without asking for scheduling abilities to run a process
every five minutes. The powers that be will probably not mind Hudson
too much, but hate crontab stuff.
Seems a little too Rube Goldberg for my tastes, but it seems like the
simplest and easiest thing to document. Hudson gives us some reporting
and emailing capabilities built into the system.
--
David Weintraub
qazwart_at_gmail.com
Received on 2010-11-22 18:24:40 CET