You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2010/04/05 22:55:26 UTC
Re: [Informal Vote] please express your opinion on using Nexus and
Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Here's my vision of automation (achieved over time :-) ), and why CI
could be important - it is building the potential releases from source
checkout.
We have CI going on Hudson; we decide at some point that things merit a
release; so we push some button on the CI or Nexus interface and get a
particular snapshot release tagged, checked out and built as a candidate.
We do some additional integration testing, and then vote on the thing in
the nexus repo, where it look like a release but is in some "held"
state. After the vote succeeds, we log onto the Nexus web interface and
push another button, and the release happens.
-Marshall
On 3/28/2010 12:36 PM, Jörn Kottmann wrote:
> Marshall Schor wrote:
>> I'm +1 for doing this, and offer to do some/most of the legwork to get
>> this to happen.
>>
>> Other opinions?
>>
> From a development point of view Hudson can help us
> to make sure that our build is never broken, and if so notice us,
> but usually our build always works. Not sure if it is worth the effort
> to get one build broken notification per year.
>
> The only other advantage I see is that it can automatically publish
> snapshot builds, but when this is the motivation to get CI on Hudson
> we maybe should start to release more frequently.
>
> Jörn
>
>
Re: [Informal Vote] please express your opinion on using Nexus and
Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Posted by Tommaso Teofili <to...@gmail.com>.
Yes, it really sounds nice to me too (so +1 again).
Tommaso
2010/4/6 Jörn Kottmann <ko...@gmail.com>
> Marshall Schor wrote:
>
>> Here's my vision of automation (achieved over time :-) ), and why CI
>> could be important - it is building the potential releases from source
>> checkout.
>>
>> We have CI going on Hudson; we decide at some point that things merit a
>> release; so we push some button on the CI or Nexus interface and get a
>> particular snapshot release tagged, checked out and built as a candidate.
>>
>> We do some additional integration testing, and then vote on the thing in
>> the nexus repo, where it look like a release but is in some "held"
>> state. After the vote succeeds, we log onto the Nexus web interface and
>> push another button, and the release happens.
>>
>>
>
> +1 sounds nice
>
> Jörn
>
Re: [Informal Vote] please express your opinion on using Nexus and
Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Posted by Jörn Kottmann <ko...@gmail.com>.
Marshall Schor wrote:
> Here's my vision of automation (achieved over time :-) ), and why CI
> could be important - it is building the potential releases from source
> checkout.
>
> We have CI going on Hudson; we decide at some point that things merit a
> release; so we push some button on the CI or Nexus interface and get a
> particular snapshot release tagged, checked out and built as a candidate.
>
> We do some additional integration testing, and then vote on the thing in
> the nexus repo, where it look like a release but is in some "held"
> state. After the vote succeeds, we log onto the Nexus web interface and
> push another button, and the release happens.
>
+1 sounds nice
Jörn
Re: [Informal Vote] please express your opinion on using Nexus and
Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Posted by Marshall Schor <ms...@schor.com>.
+1 Good idea, I think.
I've noticed that maven plugins have an additional folder, called "it"
under source, where it appears they have "integration tests". Maybe
there's some support for this (I haven't investigated further... )
-Marshall
On 4/16/2010 4:10 AM, Jörn Kottmann wrote:
> It would also be nice if Hudson could run the
> extended UIMA-AS test suite for us once in a while.
> These tests are not executed when UIMA-AS is build
> because they take too long.
>
> Jörn
>
> Marshall Schor wrote:
>> Here's my vision of automation (achieved over time :-) ), and why CI
>> could be important - it is building the potential releases from source
>> checkout.
>>
>> We have CI going on Hudson; we decide at some point that things merit a
>> release; so we push some button on the CI or Nexus interface and get a
>> particular snapshot release tagged, checked out and built as a
>> candidate.
>>
>> We do some additional integration testing, and then vote on the thing in
>> the nexus repo, where it look like a release but is in some "held"
>> state. After the vote succeeds, we log onto the Nexus web interface and
>> push another button, and the release happens.
>>
>> -Marshall
>>
>
>
>
Re: [Informal Vote] please express your opinion on using Nexus and
Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Posted by Jörn Kottmann <ko...@gmail.com>.
It would also be nice if Hudson could run the
extended UIMA-AS test suite for us once in a while.
These tests are not executed when UIMA-AS is build
because they take too long.
Jörn
Marshall Schor wrote:
> Here's my vision of automation (achieved over time :-) ), and why CI
> could be important - it is building the potential releases from source
> checkout.
>
> We have CI going on Hudson; we decide at some point that things merit a
> release; so we push some button on the CI or Nexus interface and get a
> particular snapshot release tagged, checked out and built as a candidate.
>
> We do some additional integration testing, and then vote on the thing in
> the nexus repo, where it look like a release but is in some "held"
> state. After the vote succeeds, we log onto the Nexus web interface and
> push another button, and the release happens.
>
> -Marshall
>