20 Dec
2012
20 Dec
'12
8:30 a.m.
Hi Edy,
On Dec 19, 2012, at 6:29 PM, Eduard Moraru <enygma2002(a)gmail.com> wrote:
Hi devs,
Well, the subject pretty much sums it up. I am proposing to skip any
testing while building a release, since that is the job of the CI
infrastructure and, it happened more than once for the build of the release
to fail because of a flickering test. This is really annoying for a release
manager that has to start over the entire build (since right now it's a
real pain to alter the scripts to continue the build).
Besides this, tests (specially the functional ones added into platform)
uselessly delay the build, thus, the release.
Note: We are already skipping tests for enterprise and manager. This vote
is actually about skipping tests for commons, rendering and platform as
well.
The build that is released should always have had all tests passed on it so Im' not a
bit fan of this option. A better way is to do build promotion, i.e. release from jenkins.
There are various jenkins plugin for this.
The way I view it is like this:
* once a day we run the release job (starting after RC is released usually), which will
build the whole stack (from commons to functional tests) using the target version and we
push it to a staging repo on nexus
* this release job can also be triggered manually
* we start to only release like this and we thus always release with a perfectly passing
build
* as soon as there is a promoted build during sorin and manuel could do some smoke testing
on it and we can advertise the build on our lists and give it 2-3 days before we move from
staging to target repo.
I don't think this is hard to set up and I could work on this after I finish with
false positives emails.
Thanks
-Vincent