hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Apache jenkins job to build release artifacts (WAS: Issue with my username on my company provided dev box?)
Date Fri, 31 Jan 2014 11:09:51 GMT
FWIW I've used a (local) VM for releases in the past, a VM with read-only
access to the repository, that was never used for development

-lets you lock down the box more
-guarantees src is untainted by edits
-lets you run a release build/test run within the VM while you are still
coding, without any interference
-lets you do an rm -rf ~/.m2 ~/.ivy before the build
-lets people with windows desktops cut a release

-Slower IO
-All changes to things like release notes need to be done local &
propagated via SVN
-if you do want auto-publish via scp, VM needs your private key without a
password. We created a special user @sourceforge for this
-usual brittleness of a VM that is only used once every month to changes
-after the yum update things may break, the wrong version of java creep in,
etc. That has to be included in the schedule.
-once you share the VMs by copying disk images the maintenance cost is
-automated releases can get you complacent about shipping things without
doing the full install tests (on other (clean) VMs)
-when you did run the fully distributed test harness, it would certainly
pick up on things like concurrency and network problems, but it did nothing
to help you actually track down the issue (

that release process in full:


NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message