From: <rya...@jb...> - 2005-05-04 21:13:42
|
> 5) Automatic cvs tagging for integration and release builds. After a > succesful product build, each builder should tag it's repository with > the integration and/or release build name. Any thoughts on > implementation details of this are very much welcome. We can get cruisecontrol to do this. Are you sure you want a tag for every build? Seems like this would muddy up you cvs histories unless we wrote scripts to delete old tags? > 6) Once we get hibernate tools and jbpm designer integrated, we need > to get some space on a jboss server somewhere and run this as a > nightly cron job for our nightly builds. SSH access will also be > needed so the release engineer (me ;) can remotely do integration and release builds. We can add cruisecontrol builds for the nightly builds. You can do release builds in the QA lab if you like, but I don't see the need do this on the cruisecontrol box. > 7) Email notification of build failures to the JBossIDE list. I'm not > sure how this is going to work yet but hopefully Ryan can give me a > hint on this. Cruisecontrol will do this. > 8) FTP upload of builds. We need some sort of insecure access (ala > sourceforge's release upload system) to a public jboss ftp server so I > don't have to store username/password combos in plain text in a file > in version control. The Right Way to do this is with ssh key authentication. This is secure and doesn't put passwords in CVS. In case you were wondering, cruisecontrol can do this, too :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876512#3876512 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876512 |