> On Jun 1, 2016, at 6:21 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > > : I’m not sure we want Jenkins to do this stuff. > > FWIW: some of the reasons i've argued in the past that having (ASF) > jenkins execute as much as possible as a script, rather then just > requiring the RM to run the exact same scripts locally, was to help reduce > the amount of data the RM had to transfer over the wire between their > local machine and the internet. > > For example... > > If there was a parameterized jenkins job to "build an RC" give na branch + > sha, that automatically committed the artifacts to the dist repo w/o any > *.asc files, then the RM would have to download the artifacts from each RC > (just like any other tester) but the only thing the RM would have to > "upload" is the *.asc files they generated once they artifacts have been > vetted.
This ASF release policy says that remote release building is problematic - read the full text for nuance though: <http://www.apache.org/dev/release.html#owned-controlled-hardware> -- Steve www.lucidworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
