2009/12/18 [email protected] <[email protected]> > Carl, > what are you using to do your rpm and ami builds? I'd be interested > to know what you come up with for the Hudson+Human. That's the > direction I am headed, too. I am thinking automated nightly release > to dev servers and manual/manually scheduled releases elsewhere. Maybe > a plugin for hudson will work. More than likely, I'll end up with a > shell script though. :)
Maven2 can help cover this space as well :) rpm, deb, msi, javadoc, source, etc... can all be released as "secondary" artefacts to a maven repository. Once you're using maven at this level, you really need to be looking at an installation of nexus or artifactory. The other route, if you're using OSGi, is to consider releasing to a bundle repository such as eclipse's P2 (Nexus pro can also help with this) Either way, the same logic applies. The ONLY binary artefacts that get deployed to dev/stage/prod/etc are those produced from CI builds. I'd even go so far as to recommend continuous deployment to an environment for your Hudson builds That way, everything can easily be kept in sync to avoid any nasty surprises > -- > > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > > -- Kevin Wright mail/google talk: [email protected] wave: [email protected] skype: kev.lee.wright twitter: @thecoda -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
