Hi Jasha,
On 11/02/2012 07:57 PM, Jasha Joachimsthal wrote:
Currently the person who executes the release process builds the release
artifacts on his own system. I wondered why we don't make the Maven release
from Jenkins. Jenkins has a plugin to perform Maven releases [1]. We no
longer depend on the environment settings of individual committers and our
"local" repository does not contain home brew artifacts from other
projects. Besides why would you do something manually if the machine can do
it for you ;)
[1] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin
Nice idea :)
As a start, I wouldn't technically trust Jenkins to do releases for us: its just
broken itself way too often.
More important though, I think we might have a problem with the formal and legal
trust as well. The PMC, as representative for the ASF, is responsible for a
(signed) release as provided by a release manager.
IANAL, but making Jenkins the release manager and have the artifacts 'auto
signed by a machine, probably doesn't provide the proper 'trust' from a legal POV.
Jasha
