> > A part of the release process is to update the web site. I wonder if > > this could be simplified with a Jenkins job watching for the release > > tags and building/uploading the new site automatically. That would > > make one less thing to think about when releasing new versions. I > > suspect the most difficult issue to solve is to let Jenkins publish > > the content without compromising the security.
If you are willing to start the Jenkins job manually, you could use build parameters for asking for the security infos. You could also use several jobs - automatic job1 checks for thinks to do. If then send an email "manual things have to be done". Otherwise be quite. - manual job2 does the secured actions Jan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
