You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by Stanton Sievers <ss...@apache.org> on 2014/02/24 14:24:31 UTC
Build failures
Hi everyone,
I'm seeing compile errors in the latest from trunk. It looks like the
STREAMS-26 branch may have bled into trunk in some way based on the commit
history.
I'd like to propose that this project setup builds on builds.apache.org and
report build failures to this list. If there are no objections, I can get
this setup today or tomorrow.
Thanks,
-Stanton
Re: Build failures
Posted by Stanton Sievers <ss...@apache.org>.
I agree it's a good discussion to get started.
Any branch management is likely to be easier to discuss in the context of
Git, which seems like the way things are heading per the other discussion
thread. And if there are other projects on builds.a.o that are managing
their builds in a similar way, we should look at what they are doing as a
template.
Thanks,
-Stanton
On Tue, Feb 25, 2014 at 12:11 PM, Steve Blackmon <sb...@apache.org>wrote:
> A lead integrator knowing and asserting state of the code is
> essential, but having easily accessible objective stats at the ready
> can help with effective communication and decision making. Scanning
> builds.apache.org it's apparent that many projects have multiple
> stable, unstable, and release candidate branches under CI
> concurrently.
>
> I was thinking some other developers might pitch in on refactoring the
> 17 remaining modules in streams-contrib to work with
> StreamsLocalBuilder, and that comparing the jenkins build reports of
> trunk and branch could indicate when it was ready to merge. The code
> base is reasonably simple and small today, but growing rapidly, and
> will become more complex as additional runtimes such as storm and
> hadoop with external version and dependency issues are supported.
> Since we are setting up CI, we might as well discuss and pilot some of
> these scenarios.
>
> Thanks,
> Steve
>
> On Tue, Feb 25, 2014 at 6:33 AM, Stanton Sievers <ss...@apache.org>
> wrote:
> > IMHO, knowing which modules and tests are active/passing should be the
> > responsibility of the individual developer. You can build the whole
> > project in a reasonable amount of time.
> >
> > I would agree that such a process would be good to introduce into the CI
> > system but only if there were functional or integration-level tests that
> > required resources unavailable to an individual developer.
> >
> >
> > On Mon, Feb 24, 2014 at 12:37 PM, Steve Blackmon <sblackmon@apache.org
> >wrote:
> >
> >> It would be nice to have a way to place feature branches we are
> >> planning to merge under automated build as well, not to publish any
> >> artifacts necessarily, just to identify any breaking changes and track
> >> how many and which modules and tests are active/passing.
> >>
> >> STREAMS-26 is a good example we could use to test this process out.
> >>
> >> Steve
> >>
> >> On Mon, Feb 24, 2014 at 11:03 AM, Stanton Sievers <ss...@apache.org>
> >> wrote:
> >> > Can you help set that up? I've never setup snapshots in the
> builds.a.o
> >> > environment before. Certainly willing to learn. :)
> >> >
> >> >
> >> > On Mon, Feb 24, 2014 at 11:49 AM, Matt Franklin <
> >> m.ben.franklin@gmail.com>wrote:
> >> >
> >> >> On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers <
> ssievers@apache.org
> >> >> >wrote:
> >> >>
> >> >> > A new job [1] has been created on builds.a.o for Streams trunk. It
> >> will
> >> >> > build using JDK 1.7 and the latest maven (currently 3.0.5). Once
> I've
> >> >> > verified it builds successfully, I'll set the job to e-mail this
> list
> >> >> when
> >> >> > builds fail.
> >> >> >
> >> >> > We can setup snapshot deploys and other CI functionality as we see
> >> fit.
> >> >> >
> >> >>
> >> >> Let's setup snapshots now.
> >> >>
> >> >>
> >> >> >
> >> >> > [1] https://builds.apache.org/job/Streams%20Trunk/
> >> >> >
> >> >> >
> >> >> > On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <
> >> >> m.ben.franklin@gmail.com
> >> >> > >wrote:
> >> >> >
> >> >> > > >
> >> >> > > > If we can revert trunk to revision 1569602, it should build
> again
> >> >> with
> >> >> > > >> all modules in the build plan.
> >> >> > > >>
> >> >> > > >
> >> >> > > > I will revert the code.
> >> >> > > >
> >> >> > >
> >> >> > > This is done.
> >> >> > >
> >> >> >
> >> >>
> >>
>
Re: Build failures
Posted by Steve Blackmon <sb...@apache.org>.
A lead integrator knowing and asserting state of the code is
essential, but having easily accessible objective stats at the ready
can help with effective communication and decision making. Scanning
builds.apache.org it's apparent that many projects have multiple
stable, unstable, and release candidate branches under CI
concurrently.
I was thinking some other developers might pitch in on refactoring the
17 remaining modules in streams-contrib to work with
StreamsLocalBuilder, and that comparing the jenkins build reports of
trunk and branch could indicate when it was ready to merge. The code
base is reasonably simple and small today, but growing rapidly, and
will become more complex as additional runtimes such as storm and
hadoop with external version and dependency issues are supported.
Since we are setting up CI, we might as well discuss and pilot some of
these scenarios.
Thanks,
Steve
On Tue, Feb 25, 2014 at 6:33 AM, Stanton Sievers <ss...@apache.org> wrote:
> IMHO, knowing which modules and tests are active/passing should be the
> responsibility of the individual developer. You can build the whole
> project in a reasonable amount of time.
>
> I would agree that such a process would be good to introduce into the CI
> system but only if there were functional or integration-level tests that
> required resources unavailable to an individual developer.
>
>
> On Mon, Feb 24, 2014 at 12:37 PM, Steve Blackmon <sb...@apache.org>wrote:
>
>> It would be nice to have a way to place feature branches we are
>> planning to merge under automated build as well, not to publish any
>> artifacts necessarily, just to identify any breaking changes and track
>> how many and which modules and tests are active/passing.
>>
>> STREAMS-26 is a good example we could use to test this process out.
>>
>> Steve
>>
>> On Mon, Feb 24, 2014 at 11:03 AM, Stanton Sievers <ss...@apache.org>
>> wrote:
>> > Can you help set that up? I've never setup snapshots in the builds.a.o
>> > environment before. Certainly willing to learn. :)
>> >
>> >
>> > On Mon, Feb 24, 2014 at 11:49 AM, Matt Franklin <
>> m.ben.franklin@gmail.com>wrote:
>> >
>> >> On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers <ssievers@apache.org
>> >> >wrote:
>> >>
>> >> > A new job [1] has been created on builds.a.o for Streams trunk. It
>> will
>> >> > build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've
>> >> > verified it builds successfully, I'll set the job to e-mail this list
>> >> when
>> >> > builds fail.
>> >> >
>> >> > We can setup snapshot deploys and other CI functionality as we see
>> fit.
>> >> >
>> >>
>> >> Let's setup snapshots now.
>> >>
>> >>
>> >> >
>> >> > [1] https://builds.apache.org/job/Streams%20Trunk/
>> >> >
>> >> >
>> >> > On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <
>> >> m.ben.franklin@gmail.com
>> >> > >wrote:
>> >> >
>> >> > > >
>> >> > > > If we can revert trunk to revision 1569602, it should build again
>> >> with
>> >> > > >> all modules in the build plan.
>> >> > > >>
>> >> > > >
>> >> > > > I will revert the code.
>> >> > > >
>> >> > >
>> >> > > This is done.
>> >> > >
>> >> >
>> >>
>>
Re: Build failures
Posted by Stanton Sievers <ss...@apache.org>.
IMHO, knowing which modules and tests are active/passing should be the
responsibility of the individual developer. You can build the whole
project in a reasonable amount of time.
I would agree that such a process would be good to introduce into the CI
system but only if there were functional or integration-level tests that
required resources unavailable to an individual developer.
On Mon, Feb 24, 2014 at 12:37 PM, Steve Blackmon <sb...@apache.org>wrote:
> It would be nice to have a way to place feature branches we are
> planning to merge under automated build as well, not to publish any
> artifacts necessarily, just to identify any breaking changes and track
> how many and which modules and tests are active/passing.
>
> STREAMS-26 is a good example we could use to test this process out.
>
> Steve
>
> On Mon, Feb 24, 2014 at 11:03 AM, Stanton Sievers <ss...@apache.org>
> wrote:
> > Can you help set that up? I've never setup snapshots in the builds.a.o
> > environment before. Certainly willing to learn. :)
> >
> >
> > On Mon, Feb 24, 2014 at 11:49 AM, Matt Franklin <
> m.ben.franklin@gmail.com>wrote:
> >
> >> On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers <ssievers@apache.org
> >> >wrote:
> >>
> >> > A new job [1] has been created on builds.a.o for Streams trunk. It
> will
> >> > build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've
> >> > verified it builds successfully, I'll set the job to e-mail this list
> >> when
> >> > builds fail.
> >> >
> >> > We can setup snapshot deploys and other CI functionality as we see
> fit.
> >> >
> >>
> >> Let's setup snapshots now.
> >>
> >>
> >> >
> >> > [1] https://builds.apache.org/job/Streams%20Trunk/
> >> >
> >> >
> >> > On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <
> >> m.ben.franklin@gmail.com
> >> > >wrote:
> >> >
> >> > > >
> >> > > > If we can revert trunk to revision 1569602, it should build again
> >> with
> >> > > >> all modules in the build plan.
> >> > > >>
> >> > > >
> >> > > > I will revert the code.
> >> > > >
> >> > >
> >> > > This is done.
> >> > >
> >> >
> >>
>
Re: Build failures
Posted by Steve Blackmon <sb...@apache.org>.
It would be nice to have a way to place feature branches we are
planning to merge under automated build as well, not to publish any
artifacts necessarily, just to identify any breaking changes and track
how many and which modules and tests are active/passing.
STREAMS-26 is a good example we could use to test this process out.
Steve
On Mon, Feb 24, 2014 at 11:03 AM, Stanton Sievers <ss...@apache.org> wrote:
> Can you help set that up? I've never setup snapshots in the builds.a.o
> environment before. Certainly willing to learn. :)
>
>
> On Mon, Feb 24, 2014 at 11:49 AM, Matt Franklin <m....@gmail.com>wrote:
>
>> On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers <ssievers@apache.org
>> >wrote:
>>
>> > A new job [1] has been created on builds.a.o for Streams trunk. It will
>> > build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've
>> > verified it builds successfully, I'll set the job to e-mail this list
>> when
>> > builds fail.
>> >
>> > We can setup snapshot deploys and other CI functionality as we see fit.
>> >
>>
>> Let's setup snapshots now.
>>
>>
>> >
>> > [1] https://builds.apache.org/job/Streams%20Trunk/
>> >
>> >
>> > On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <
>> m.ben.franklin@gmail.com
>> > >wrote:
>> >
>> > > >
>> > > > If we can revert trunk to revision 1569602, it should build again
>> with
>> > > >> all modules in the build plan.
>> > > >>
>> > > >
>> > > > I will revert the code.
>> > > >
>> > >
>> > > This is done.
>> > >
>> >
>>
Re: Build failures
Posted by Stanton Sievers <ss...@apache.org>.
Can you help set that up? I've never setup snapshots in the builds.a.o
environment before. Certainly willing to learn. :)
On Mon, Feb 24, 2014 at 11:49 AM, Matt Franklin <m....@gmail.com>wrote:
> On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers <ssievers@apache.org
> >wrote:
>
> > A new job [1] has been created on builds.a.o for Streams trunk. It will
> > build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've
> > verified it builds successfully, I'll set the job to e-mail this list
> when
> > builds fail.
> >
> > We can setup snapshot deploys and other CI functionality as we see fit.
> >
>
> Let's setup snapshots now.
>
>
> >
> > [1] https://builds.apache.org/job/Streams%20Trunk/
> >
> >
> > On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <
> m.ben.franklin@gmail.com
> > >wrote:
> >
> > > >
> > > > If we can revert trunk to revision 1569602, it should build again
> with
> > > >> all modules in the build plan.
> > > >>
> > > >
> > > > I will revert the code.
> > > >
> > >
> > > This is done.
> > >
> >
>
Re: Build failures
Posted by Matt Franklin <m....@gmail.com>.
On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers <ss...@apache.org>wrote:
> A new job [1] has been created on builds.a.o for Streams trunk. It will
> build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've
> verified it builds successfully, I'll set the job to e-mail this list when
> builds fail.
>
> We can setup snapshot deploys and other CI functionality as we see fit.
>
Let's setup snapshots now.
>
> [1] https://builds.apache.org/job/Streams%20Trunk/
>
>
> On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <m.ben.franklin@gmail.com
> >wrote:
>
> > >
> > > If we can revert trunk to revision 1569602, it should build again with
> > >> all modules in the build plan.
> > >>
> > >
> > > I will revert the code.
> > >
> >
> > This is done.
> >
>
Re: Build failures
Posted by Stanton Sievers <ss...@apache.org>.
A new job [1] has been created on builds.a.o for Streams trunk. It will
build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've
verified it builds successfully, I'll set the job to e-mail this list when
builds fail.
We can setup snapshot deploys and other CI functionality as we see fit.
[1] https://builds.apache.org/job/Streams%20Trunk/
On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin <m....@gmail.com>wrote:
> >
> > If we can revert trunk to revision 1569602, it should build again with
> >> all modules in the build plan.
> >>
> >
> > I will revert the code.
> >
>
> This is done.
>
Re: Build failures
Posted by Matt Franklin <m....@gmail.com>.
>
> If we can revert trunk to revision 1569602, it should build again with
>> all modules in the build plan.
>>
>
> I will revert the code.
>
This is done.
Re: Build failures
Posted by Matt Franklin <m....@gmail.com>.
On Mon, Feb 24, 2014 at 10:30 AM, Steve Blackmon <sb...@apache.org>wrote:
> Stanton,
>
> I believe I committed some of the patch code into trunk mistakenly.
> +1 on setting up continuous integration.
>
> If we can revert trunk to revision 1569602, it should build again with
> all modules in the build plan.
>
I will revert the code.
Since it looks like you are trying to branch by feature, we might want to
think about moving to Git. I will send a separate proposal for that.
>
> Thanks,
> Steve
>
> On Mon, Feb 24, 2014 at 7:24 AM, Stanton Sievers <ss...@apache.org>
> wrote:
> > Hi everyone,
> >
> > I'm seeing compile errors in the latest from trunk. It looks like the
> > STREAMS-26 branch may have bled into trunk in some way based on the
> commit
> > history.
> >
> > I'd like to propose that this project setup builds on builds.apache.organd
> > report build failures to this list. If there are no objections, I can
> get
> > this setup today or tomorrow.
> >
> > Thanks,
> > -Stanton
>
Re: Build failures
Posted by Steve Blackmon <sb...@apache.org>.
Stanton,
I believe I committed some of the patch code into trunk mistakenly.
+1 on setting up continuous integration.
If we can revert trunk to revision 1569602, it should build again with
all modules in the build plan.
Thanks,
Steve
On Mon, Feb 24, 2014 at 7:24 AM, Stanton Sievers <ss...@apache.org> wrote:
> Hi everyone,
>
> I'm seeing compile errors in the latest from trunk. It looks like the
> STREAMS-26 branch may have bled into trunk in some way based on the commit
> history.
>
> I'd like to propose that this project setup builds on builds.apache.org and
> report build failures to this list. If there are no objections, I can get
> this setup today or tomorrow.
>
> Thanks,
> -Stanton
Re: Build failures
Posted by Matt Franklin <m....@gmail.com>.
On Mon, Feb 24, 2014 at 7:24 AM, Stanton Sievers <ss...@apache.org>wrote:
> Hi everyone,
>
> I'm seeing compile errors in the latest from trunk. It looks like the
> STREAMS-26 branch may have bled into trunk in some way based on the commit
> history.
>
> I'd like to propose that this project setup builds on builds.apache.organd
> report build failures to this list. If there are no objections, I can get
> this setup today or tomorrow.
>
+1
>
> Thanks,
> -Stanton
>