You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Babak Vahdat <ba...@swissonline.ch> on 2014/11/07 11:47:29 UTC
Re: [DISCUSS] - Camel 2.12.5 and 2.13.3 releases
Hi,
IMHO if would be nice if we would NOT skip running tests while
building/preparing a given release.
As an example, by the recent 2.13.3 release we introduced a regression (a
concurreny issue inside camel-core) which we did NOT realize at all as the
tests were simply skipped while building. Currently there's a open JIRA
ticket about that.
Babak
Christian Mueller wrote
> Thanks Willem!
> I'm already using these settings, but by installing Wildfly, it changed my
> Maven settings... :-(
> By reverting these changes, the build is running without the tests...
>
> Best,
>
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
> On Sun, Oct 19, 2014 at 9:13 AM, Willem Jiang <
> willem.jiang@
> >
> wrote:
>
>> Hi Christian,
>>
>> You don’t need to run the whole tests for the release, normally we just
>> need to check the CI build result.
>>
>> Please add test property in your release profile just like this, then
>> maven skip the test when doing the release.
>>
>>
> <profile>
>>
> <id>
> apache-release
> </id>
>>
> <properties>
>>
> <gpg.useagent>
> false
> </gpg.useagent>
>>
> <gpg.passphrase>
> xxxx
> </gpg.passphrase>
>>
> <test>
> false
> </test>
>>
> </properties>
>>
> </profile>
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (English)
>> http://jnn.iteye.com (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On October 18, 2014 at 5:22:04 PM, Christian Müller (
>>
> christian.mueller@
> ) wrote:
>> > I have to postpone the Camel 2.12.5 release a bit until I have fixed
>> some
>> > unit test which are failing from time to time. With 8 tries, I couldn't
>> run
>> > successfully a mvn release:prepare...
>> >
>> > Best,
>> >
>> > Christian
>> > -----------------
>> >
>> > Software Integration Specialist
>> >
>> > Apache Member
>> > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
>> > Apache Incubator PMC Member
>> >
>> > https://www.linkedin.com/pub/christian-mueller/11/551/642
>> >
>> > On Thu, Oct 16, 2014 at 9:05 AM, Christian Müller <
>> >
> christian.mueller@
>> wrote:
>> >
>> > > Ok, I have updated Spring, CXF and fixed two failing tests in
>> > > camel-spring-ws and camel-jsch. The build looks good now. Release in
>> > > progress...
>> > >
>> > > Best,
>> > >
>> > > Christian
>> > > -----------------
>> > >
>> > > Software Integration Specialist
>> > >
>> > > Apache Member
>> > > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
>> > > Apache Incubator PMC Member
>> > >
>> > > https://www.linkedin.com/pub/christian-mueller/11/551/642
>> > >
>> > > On Wed, Oct 15, 2014 at 2:04 AM, Willem Jiang
>> > > wrote:
>> > >
>> > >> I’m +1 for upgrading the version of spring. AFAIK, camel don’t have
>> some
>> > >> hard dependency of certain version of Spring 3.2.x .
>> > >>
>> > >> --
>> > >> Willem Jiang
>> > >>
>> > >> Red Hat, Inc.
>> > >> Web: http://www.redhat.com
>> > >> Blog: http://willemjiang.blogspot.com (English)
>> > >> http://jnn.iteye.com (Chinese)
>> > >> Twitter: willemjiang
>> > >> Weibo: 姜宁willem
>> > >>
>> > >>
>> > >>
>> > >> On October 15, 2014 at 4:53:15 AM, Christian Müller (
>> > >>
> christian.mueller@
> ) wrote:
>> > >> > Ok, I will give CXF 2.7.13 a try...
>> > >> >
>> > >> > I'm also wondering why we still using Spring 3.2.5 instead of
>> 3.2.11. in
>> > >> > Camel 2.12.x. Any reason not to upgrade? The unit tests passed and
>> also
>> > >> the
>> > >> > feature validation passed...
>> > >> >
>> > >> > Best,
>> > >> >
>> > >> > Christian
>> > >> > -----------------
>> > >> >
>> > >> > Software Integration Specialist
>> > >> >
>> > >> > Apache Member
>> > >> > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel
>> committer
>> > >> > Apache Incubator PMC Member
>> > >> >
>> > >> > https://www.linkedin.com/pub/christian-mueller/11/551/642
>> > >> >
>> > >> > On Tue, Oct 14, 2014 at 10:27 PM, Daniel Kulp wrote:
>> > >> >
>> > >> > >
>> > >> > > There are new releases of CXF out that do fix some security
>> issues….
>> > >> I’m
>> > >> > > too sick to test/commit right now, but it might be good to give
>> it a
>> > >> try.
>> > >> > >
>> > >> > > Dan
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > On Oct 14, 2014, at 3:39 PM, Christian Müller
>> > >> > > wrote:
>> > >> > >
>> > >> > > > I could do the 2.12.5 release (last planned patch release of
>> the
>> > >> 2.12.x
>> > >> > > > branch).
>> > >> > > > If nobody has an important ticket which should be included, I
>> will
>> > >> start
>> > >> > > > the release in 24 hours.
>> > >> > > >
>> > >> > > > Best,
>> > >> > > > Christian
>> > >> > > >
>> > >> > > >
>> > >> > > > On Tue, Oct 14, 2014 at 3:21 AM, Willem Jiang
>> > >> > > > wrote:
>> > >> > > >
>> > >> > > >> Yeah, I totally agree with that.
>> > >> > > >> As my schedule is occupied this two weeks, the release will
>> be
>> > >> scheduled
>> > >> > > >> at the last week of this month.
>> > >> > > >> If other release managers have time before that, any help
>> will
>> be
>> > >> > > >> appreciated.
>> > >> > > >>
>> > >> > > >> --
>> > >> > > >> Willem Jiang
>> > >> > > >>
>> > >> > > >> Red Hat, Inc.
>> > >> > > >> Web: http://www.redhat.com
>> > >> > > >> Blog: http://willemjiang.blogspot.com (English)
>> > >> > > >> http://jnn.iteye.com (Chinese)
>> > >> > > >> Twitter: willemjiang
>> > >> > > >> Weibo: 姜宁willem
>> > >> > > >>
>> > >> > > >>
>> > >> > > >>
>> > >> > > >> On October 1, 2014 at 2:45:07 PM, Claus Ibsen (
>> > >>
> claus.ibsen@
> )
>> > >> > > >> wrote:
>> > >> > > >>> Hi
>> > >> > > >>>
>> > >> > > >>> Now that we have 2.14.0 out of the door, I think its time we
>> do a
>> > >> > > >>> round of patch releases.
>> > >> > > >>>
>> > >> > > >>> Camel 2.12.5 would be the last planned patch release of the
>> 2.12.x
>> > >> > > >> branch.
>> > >> > > >>> Camel 2.13.3 is a patch release.
>> > >> > > >>>
>> > >> > > >>> Its 3 months ago since we last release patch releases for
>> these
>> > >> two
>> > >> > > >> branches.
>> > >> > > >>>
>> > >> > > >>> Any thoughts?
>> > >> > > >>>
>> > >> > > >>>
>> > >> > > >>> --
>> > >> > > >>> Claus Ibsen
>> > >> > > >>> -----------------
>> > >> > > >>> Red Hat, Inc.
>> > >> > > >>> Email:
> cibsen@
>> > >> > > >>> Twitter: davsclaus
>> > >> > > >>> Blog: http://davsclaus.com
>> > >> > > >>> Author of Camel in Action: http://www.manning.com/ibsen
>> > >> > > >>> hawtio: http://hawt.io/
>> > >> > > >>> fabric8: http://fabric8.io/
>> > >> > > >>>
>> > >> > > >>
>> > >> > > >>
>> > >> > >
>> > >> > > --
>> > >> > > Daniel Kulp
>> > >> > >
> dkulp@
> - http://dankulp.com/blog
>> > >> > > Talend Community Coder - http://coders.talend.com
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >>
>> > >
>> >
>>
>>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-12-5-and-2-13-3-releases-tp5757263p5758665.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Camel 2.12.5 and 2.13.3 releases
Posted by Christian Müller <ch...@gmail.com>.
Sure, but the tests we are talking about only failing rarely. It's not so
easy to spot the issue and to make sure it's fixed.
Best,
Christian
-----------------
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Mon, Nov 10, 2014 at 8:05 AM, Babak Vahdat <ba...@swissonline.ch>
wrote:
> Hi
>
> Could we maybe then at least raise a ticket for all those failing tests we
> spot while trying to prepare the release. Then the community could look
> into
> and fix them either for the same RC or the upcoming releases, as I guess
> more people look into the JIRA tickets compared to the Jenkins build
> results
> by the day X.
>
> Babak
>
> Christian Mueller wrote
> > Hi,
> >
> > I do NOT think this is possible at present. It would be great if it's
> > possible, but it doesn't work yet...
> > For Camel 2.12.5, I tried it 7 times with the test enabled - and it
> failed
> > each time (but with different test). At present, we have to many test
> > which
> > are failing from time to time.
> >
> > Regarding the 2.13.3 release: As a PMC, we may did not the best job when
> > we
> > vote +1 for a release which is constantly failing on Jenkins at this
> time.
> > However, I will check this in the next releases...
> >
> > Best,
> > Christian
> > -----------------
> >
> > Software Integration Specialist
> >
> > Apache Member
> > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> > Apache Incubator PMC Member
> >
> > https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-12-5-and-2-13-3-releases-tp5757263p5758809.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [DISCUSS] - Camel 2.12.5 and 2.13.3 releases
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
Could we maybe then at least raise a ticket for all those failing tests we
spot while trying to prepare the release. Then the community could look into
and fix them either for the same RC or the upcoming releases, as I guess
more people look into the JIRA tickets compared to the Jenkins build results
by the day X.
Babak
Christian Mueller wrote
> Hi,
>
> I do NOT think this is possible at present. It would be great if it's
> possible, but it doesn't work yet...
> For Camel 2.12.5, I tried it 7 times with the test enabled - and it failed
> each time (but with different test). At present, we have to many test
> which
> are failing from time to time.
>
> Regarding the 2.13.3 release: As a PMC, we may did not the best job when
> we
> vote +1 for a release which is constantly failing on Jenkins at this time.
> However, I will check this in the next releases...
>
> Best,
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-12-5-and-2-13-3-releases-tp5757263p5758809.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Camel 2.12.5 and 2.13.3 releases
Posted by Christian Müller <ch...@gmail.com>.
Hi,
I do NOT think this is possible at present. It would be great if it's
possible, but it doesn't work yet...
For Camel 2.12.5, I tried it 7 times with the test enabled - and it failed
each time (but with different test). At present, we have to many test which
are failing from time to time.
Regarding the 2.13.3 release: As a PMC, we may did not the best job when we
vote +1 for a release which is constantly failing on Jenkins at this time.
However, I will check this in the next releases...
Best,
Christian
-----------------
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642