Jenkins build is back to normal : beam_SeedJob_Standalone #21

[Apache Jenkins Server]

See 

Re: Update on 2.2.0 release

[Jean-Baptiste Onofré]

Hi guys,

can we move forward on 2.2.0 release ?

Only two Jira are still open for 2.2.0:

BEAM-3011 - Pin Runner harness container image in Python SDK
BEAM-2271 - Release guide or pom.xml needs update to avoid releasing Python 
binary artifacts


Both are related to Python SDK.
Can we have an update about this ?
Are they blocker for the 2.2.0 release ?

@Reuven: I think we are good to do a 2.2.0.RC1. Thoughts ?

Thanks !
Regards
JB

On 10/10/2017 12:53 AM, Reuven Lax wrote:

I've now cut a release branch for 2.2.0.

On Mon, Oct 9, 2017 at 2:01 AM, Jean-Baptiste Onofré 
wrote:


It sounds good to me.

Regards
JB


On 10/09/2017 12:38 AM, Reuven Lax wrote:


At this point it's taken over three weeks to resolve release-blocking
issues, and there are still some remaining. Monday morning I will go ahead
and cut an initial release candidate, so we get a snapshot to base on. The
remaining blocking issues will either be cherry picked into an additional
release candidate or punted to 2.3.0, depending on severity.

Reuven

On Wed, Sep 20, 2017 at 5:34 AM, Jean-Baptiste Onofré 
wrote:

Hi Reuven,


thanks for the update. I will pick up some Jira in my bucket (to
verify/double check or implement).

Regards
JB


On 09/20/2017 04:23 AM, Reuven Lax wrote:

There are 7 issues left on

https://issues.apache.org/jira/projects/BEAM/versions/12341044 after I
moved some items to 2.3.0 if they appeared to not need to be in 2.2.0
(some
were originally slated for 2.1.0, and there was no apparent progress on
them). Please object if you feel that it's important that any of these
be
in 2.2.0

Of the remaining issues, three (BEAM-2956, BEAM-2298, BEAM-2271) appear
to
already be fixed; please verify this and close the issue if you are the
reporter. The remaining issues (BEAM-2834, BEAM-2858, BEAM-2870,
BEAM-29540) all have outstanding pull requests. As soon as all of these
pull requests are merged, I will start the release cut.

Reuven


--

Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Vilhelm von Ehrenheim]

+1 for sharing the Stockholm meetup closer to the event.

The Meetup filled up really fast which is great! There seem to be a growing
interest for Beam here.

Btw, Gris is also already sending us swag for that event as proposed.

Vilhelm

On 23 Oct 2017 22:35, "Griselda Cuevas"  wrote:

> @Ahmet - thanks for sharing part 1 of Neville's post and the one about the
> SF Cloud Mafia Meetup. We can tweet about part 2 maybe tomorrow or Weds and
> about the Stockholm meetup closer to the date.
>
> @Ismael - re:Swag, I'm thinking of creating a swag store for Apache Beam -
> I'll send a separate thread with the proposal. The idea is that we create
> an online store for people to order swag for their events, they could pick
> from a wide selection offered by a vendor. I got us an initial budget of
> USD$2k and I was planning to give codes to Meetup founders and folks
> speaking at conferences this year, once we run out of this budget people
> can get their own swag or we can collaborate on a joint fund to get the
> store going. I'll submit a new thread with details and the vendor proposal.
>
> G
>
> On 23 October 2017 at 07:56, Etienne Chauchot  wrote:
>
> > Hi,
> >
> > +1 to share Neville's blogpost.
> >
> > Etienne
> >
> >
> >
> > Le 20/10/2017 à 22:08, Griselda Cuevas a écrit :
> >
> >> Hi everyone - What do you think about sharing Neville's blogpost[1]
> about
> >> the road to Scio on the Apache Beam Twitter account?, I think it'd be
> good
> >> to share some content since the last time we were active as 9/27.
> >>
> >> Also - could you help promote some of the upcoming Meetups? I made the
> >> following tweets:
> >>
> >> 11/1 - San Francisco Cloud Mafia
> >> Tweet:
> >> Come join the SF Cloud Mafia to learn about stream & batch processing
> with
> >> #ApacheBeam on Nov. 1st. https://www.meetup.com/San-
> >> Francisco-Cloud-Mafia/events/244180581/
> >>
> >> 11/22 - StockholmApache Beam Meetup
> >> Tweet:
> >> Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join
> if
> >> you're around! https://www.meetup.com/Apache-Beam-Stockholm/
> >>
> >> [1] https://labs.spotify.com/2017/10/16/big-data-processing-at-
> >> spotify-the-road-to-scio-part-1/
> >>
> >> Thanks!
> >> G
> >>
> >>
> >
>

Re: Java pre/post commit test suite breakage

[Kenneth Knowles]

I want to wait and get some green from Jenkins running against the HEAD
groovy scripts to confirm. I haven't sat at my desk long enough to see a
full `mvn -P release clean verify` yet.

On Mon, Oct 23, 2017 at 3:27 PM, Kenneth Knowles  wrote:

> I was easily able to reproduce all the sorts of failures (and some more!)
>
> Here are some things that now work that didn't work, or didn't work
> correctly, before
>
>  - mvn apache-rat:check
>  - mvn -P release apache-rat:check
>  - mvn -P release -f somewhere/else/pom.xml apache-rat:check
>
> It turns out we had these issues:
>
>  - items in .gitignore that our RAT config did not ignore
>  - sub-modules actually *did* inherit the RAT config, depending on the
> command you run
>  - paths in the RAT exclude were relative to current dir
>  - paths in our RAT exclude that aren't even part of our codebase or
> generated targets, but just things that Jenkins dropped in the workspace,
> and we were cloning directly into the workspace
>
> I think with the new Jenkins config and the new pom.xml things should work
> well.
>
> Incidentally, Valentyn, changes to Jenkins job DSL groovy scripts do not
> take effect from being merged but only when the seed job next runs. (TODO:
> fix this). I am still trying to get the relevant Jenkins UI pages to load
> to get your change incorporated into the live scripts, which were regressed
> by being run from an old PR (TODO: fix the fact that this can happen).
>
> Kenn
>
> On Mon, Oct 23, 2017 at 2:21 PM, Valentyn Tymofieiev <
> valen...@google.com.invalid> wrote:
>
>> Thanks a lot!
>>
>> Kenn, Were you able to reproduce RAT failures and test the fix locally? I
>> think "mvn clean verify -Prelease" still passes for me.
>>
>> Timeout for the test suite has been increased in
>> https://github.com/apache/
>> beam/pull/4028 .
>>
>> On Mon, Oct 23, 2017 at 2:10 PM, Kenneth Knowles 
>> wrote:
>>
>> > Wrong link - https://github.com/apache/beam/pull/4027
>> >
>> > On Mon, Oct 23, 2017 at 2:10 PM, Kenneth Knowles 
>> wrote:
>> >
>> > > Yea, root cause is the config bug I described. Proposed fix at
>> > > https://github.com/apache/beam/pull/4019/files. I'm working with
>> infra
>> > to
>> > > sort out other build issues that are probably not related.
>> > >
>> > > On Mon, Oct 23, 2017 at 1:53 PM, Lukasz Cwik > >
>> > > wrote:
>> > >
>> > >> The build breakage I outlined is being tracked in
>> > >> https://issues.apache.org/jira/browse/BEAM-3092
>> > >>
>> > >> On Mon, Oct 23, 2017 at 11:54 AM, Lukasz Cwik 
>> wrote:
>> > >>
>> > >> > Another breaking change was caused by https://github.com/apache/
>> > >> > beam/commit/241d3cedd5a8fd3f360b8ec2f3a8ef5001cbca98 because it
>> > changed
>> > >> > the build layout on the Jenkins server and our RAT rules expected
>> to
>> > >> apply
>> > >> > from a root directory. I pinged Kenneth Knowles about it and he
>> said
>> > he
>> > >> was
>> > >> > taking a look.
>> > >> >
>> > >> > On Mon, Oct 23, 2017 at 11:53 AM, Raghu Angadi
>> > >> > > >> > > wrote:
>> > >> >
>> > >> >> Regd (1) :
>> > >> >>
>> > >> >> [4] did have have a file without Apache Licence. It was fixed the
>> > next
>> > >> >> day (
>> > >> >> commit
>> > >> >> > > >> >> c7b83032ad38c3dcac0#diff-26b77e086ff8292ef54f12b22b7b767a>),
>> > >> >> thanks to Ken Knowles who pinged me about it.
>> > >> >>
>> > >> >> On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev <
>> > >> >> valen...@google.com>
>> > >> >> wrote:
>> > >> >>
>> > >> >> > Hi Beam-Dev,
>> > >> >> >
>> > >> >> > It's been >5 days since the last successful run of a
>> > >> >> > beam_PreCommit_Java_MavenInstall build[1]  and >4 days since
>> last
>> > >> >> > successful run of beam_PreCommit_Java_MavenInstall[2].
>> > >> >> >
>> > >> >> > Looking at build logs I see following problems.
>> > >> >> >
>> > >> >> > 1. After October 17, postcommit builds started to fail with
>> > >> >> >
>> > >> >> > Failed to execute goal org.apache.rat:apache-rat-plug
>> in:0.12:check
>> > >> >> > (default) on project beam-parent: Too many files with unapproved
>> > >> >> license: 1
>> > >> >> > See RAT report in: /home/jenkins/jenkins-slave/wo
>> > >> >> > rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
>> > >> >> > t-2.3.0-SNAPSHOT.rat
>> > >> >> >
>> > >> >> > The earliest build that I see this error is Postcommit #5052
>> [3].
>> > >> >> >
>> > >> >> > This makes me suspect [4] or [5] as a breaking change, since
>> they
>> > >> change
>> > >> >> > pom files.
>> > >> >> >
>> > >> >> > Questions:
>> > >> >> > - Is there a way we can reproduce this failure locally? mvn
>> clean
>> > >> verify
>> > >> >> > passes locally for me.
>> > >> >> > - Is there a way we can see the See RAT report mentioned in the
>> > error
>> > >> >> > log?
>> > >> >> >
>> > >> 

Re: Java pre/post commit test suite breakage

[Kenneth Knowles]

I was easily able to reproduce all the sorts of failures (and some more!)

Here are some things that now work that didn't work, or didn't work
correctly, before

 - mvn apache-rat:check
 - mvn -P release apache-rat:check
 - mvn -P release -f somewhere/else/pom.xml apache-rat:check

It turns out we had these issues:

 - items in .gitignore that our RAT config did not ignore
 - sub-modules actually *did* inherit the RAT config, depending on the
command you run
 - paths in the RAT exclude were relative to current dir
 - paths in our RAT exclude that aren't even part of our codebase or
generated targets, but just things that Jenkins dropped in the workspace,
and we were cloning directly into the workspace

I think with the new Jenkins config and the new pom.xml things should work
well.

Incidentally, Valentyn, changes to Jenkins job DSL groovy scripts do not
take effect from being merged but only when the seed job next runs. (TODO:
fix this). I am still trying to get the relevant Jenkins UI pages to load
to get your change incorporated into the live scripts, which were regressed
by being run from an old PR (TODO: fix the fact that this can happen).

Kenn

On Mon, Oct 23, 2017 at 2:21 PM, Valentyn Tymofieiev <
valen...@google.com.invalid> wrote:

> Thanks a lot!
>
> Kenn, Were you able to reproduce RAT failures and test the fix locally? I
> think "mvn clean verify -Prelease" still passes for me.
>
> Timeout for the test suite has been increased in
> https://github.com/apache/
> beam/pull/4028.
>
> On Mon, Oct 23, 2017 at 2:10 PM, Kenneth Knowles 
> wrote:
>
> > Wrong link - https://github.com/apache/beam/pull/4027
> >
> > On Mon, Oct 23, 2017 at 2:10 PM, Kenneth Knowles  wrote:
> >
> > > Yea, root cause is the config bug I described. Proposed fix at
> > > https://github.com/apache/beam/pull/4019/files. I'm working with infra
> > to
> > > sort out other build issues that are probably not related.
> > >
> > > On Mon, Oct 23, 2017 at 1:53 PM, Lukasz Cwik  >
> > > wrote:
> > >
> > >> The build breakage I outlined is being tracked in
> > >> https://issues.apache.org/jira/browse/BEAM-3092
> > >>
> > >> On Mon, Oct 23, 2017 at 11:54 AM, Lukasz Cwik 
> wrote:
> > >>
> > >> > Another breaking change was caused by https://github.com/apache/
> > >> > beam/commit/241d3cedd5a8fd3f360b8ec2f3a8ef5001cbca98 because it
> > changed
> > >> > the build layout on the Jenkins server and our RAT rules expected to
> > >> apply
> > >> > from a root directory. I pinged Kenneth Knowles about it and he said
> > he
> > >> was
> > >> > taking a look.
> > >> >
> > >> > On Mon, Oct 23, 2017 at 11:53 AM, Raghu Angadi
> > >>  > >> > > wrote:
> > >> >
> > >> >> Regd (1) :
> > >> >>
> > >> >> [4] did have have a file without Apache Licence. It was fixed the
> > next
> > >> >> day (
> > >> >> commit
> > >> >>  > >> >> c7b83032ad38c3dcac0#diff-26b77e086ff8292ef54f12b22b7b767a>),
> > >> >> thanks to Ken Knowles who pinged me about it.
> > >> >>
> > >> >> On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev <
> > >> >> valen...@google.com>
> > >> >> wrote:
> > >> >>
> > >> >> > Hi Beam-Dev,
> > >> >> >
> > >> >> > It's been >5 days since the last successful run of a
> > >> >> > beam_PreCommit_Java_MavenInstall build[1]  and >4 days since
> last
> > >> >> > successful run of beam_PreCommit_Java_MavenInstall[2].
> > >> >> >
> > >> >> > Looking at build logs I see following problems.
> > >> >> >
> > >> >> > 1. After October 17, postcommit builds started to fail with
> > >> >> >
> > >> >> > Failed to execute goal org.apache.rat:apache-rat-
> plugin:0.12:check
> > >> >> > (default) on project beam-parent: Too many files with unapproved
> > >> >> license: 1
> > >> >> > See RAT report in: /home/jenkins/jenkins-slave/wo
> > >> >> > rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
> > >> >> > t-2.3.0-SNAPSHOT.rat
> > >> >> >
> > >> >> > The earliest build that I see this error is Postcommit #5052 [3].
> > >> >> >
> > >> >> > This makes me suspect [4] or [5] as a breaking change, since they
> > >> change
> > >> >> > pom files.
> > >> >> >
> > >> >> > Questions:
> > >> >> > - Is there a way we can reproduce this failure locally? mvn clean
> > >> verify
> > >> >> > passes locally for me.
> > >> >> > - Is there a way we can see the See RAT report mentioned in the
> > error
> > >> >> > log?
> > >> >> >
> > >> >> > 2. Prior to onset of #1 Java Precommit builds no longer complete
> > >> within
> > >> >> > allotted 150 min time. Looking at [6-8] it seems the build makes
> > >> >> consistent
> > >> >> > progress, but just does not finish on time. We can also see
> several
> > >> >> recent
> > >> >> > successful builds with execution time very close to time out
> > [9-11].
> > >> >> >
> > >> >> > I'd like to propose to increase time limit for Java precommit
> test
> > >> suite
> > 

Re: Java pre/post commit test suite breakage

[Kenneth Knowles]

Yea, root cause is the config bug I described. Proposed fix at
https://github.com/apache/beam/pull/4019/files. I'm working with infra to
sort out other build issues that are probably not related.

On Mon, Oct 23, 2017 at 1:53 PM, Lukasz Cwik 
wrote:

> The build breakage I outlined is being tracked in
> https://issues.apache.org/jira/browse/BEAM-3092
>
> On Mon, Oct 23, 2017 at 11:54 AM, Lukasz Cwik  wrote:
>
> > Another breaking change was caused by https://github.com/apache/
> > beam/commit/241d3cedd5a8fd3f360b8ec2f3a8ef5001cbca98 because it changed
> > the build layout on the Jenkins server and our RAT rules expected to
> apply
> > from a root directory. I pinged Kenneth Knowles about it and he said he
> was
> > taking a look.
> >
> > On Mon, Oct 23, 2017 at 11:53 AM, Raghu Angadi
>  > > wrote:
> >
> >> Regd (1) :
> >>
> >> [4] did have have a file without Apache Licence. It was fixed the next
> >> day (
> >> commit
> >>  >> c7b83032ad38c3dcac0#diff-26b77e086ff8292ef54f12b22b7b767a>),
> >> thanks to Ken Knowles who pinged me about it.
> >>
> >> On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev <
> >> valen...@google.com>
> >> wrote:
> >>
> >> > Hi Beam-Dev,
> >> >
> >> > It's been >5 days since the last successful run of a
> >> > beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
> >> > successful run of beam_PreCommit_Java_MavenInstall[2].
> >> >
> >> > Looking at build logs I see following problems.
> >> >
> >> > 1. After October 17, postcommit builds started to fail with
> >> >
> >> > Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
> >> > (default) on project beam-parent: Too many files with unapproved
> >> license: 1
> >> > See RAT report in: /home/jenkins/jenkins-slave/wo
> >> > rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
> >> > t-2.3.0-SNAPSHOT.rat
> >> >
> >> > The earliest build that I see this error is Postcommit #5052 [3].
> >> >
> >> > This makes me suspect [4] or [5] as a breaking change, since they
> change
> >> > pom files.
> >> >
> >> > Questions:
> >> > - Is there a way we can reproduce this failure locally? mvn clean
> verify
> >> > passes locally for me.
> >> > - Is there a way we can see the See RAT report mentioned in the error
> >> > log?
> >> >
> >> > 2. Prior to onset of #1 Java Precommit builds no longer complete
> within
> >> > allotted 150 min time. Looking at [6-8] it seems the build makes
> >> consistent
> >> > progress, but just does not finish on time. We can also see several
> >> recent
> >> > successful builds with execution time very close to time out [9-11].
> >> >
> >> > I'd like to propose to increase time limit for Java precommit test
> suite
> >> > from 2.5 to 4 hours. 4 hours is long time. I agree that we should
> >> > definitely try to reduce the test execution time, and reduce
> flakiness.
> >> > However we need the tests at least pass for now. If we write off
> failed
> >> > test suites as 'flakes' and merge PRs without having a green test
> >> signal,
> >> > we will have to spend more time tracing breakages such as #1.
> >> >
> >> > Thoughts?
> >> >
> >> > Thanks,
> >> > Valentyn
> >> >
> >> > [1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
> >> > [2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
> >> > [3] https://builds.apache.org/job/beam_PostCommit_Java_MavenInst
> >> > all/5052/changes
> >> >
> >> > [4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3b
> >> > c3c67ba3e2617cb7f11a8c
> >> > [5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b
> >> > 3e9a26b6c9d0bb6dc3
> >> >
> >> > [6] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
> >> ll/15222/
> >> > [7] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
> >> ll/15195/
> >> > [8] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
> >> ll/15220/
> >> >
> >> > [9] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
> >> ll/15009/
> >> > [10] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
> >> ll/15068/
> >> > [11] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
> >> ll/15016/
> >> >
> >> >
> >>
> >
> >
>

Re: Java pre/post commit test suite breakage

[Lukasz Cwik]

The build breakage I outlined is being tracked in
https://issues.apache.org/jira/browse/BEAM-3092

On Mon, Oct 23, 2017 at 11:54 AM, Lukasz Cwik  wrote:

> Another breaking change was caused by https://github.com/apache/
> beam/commit/241d3cedd5a8fd3f360b8ec2f3a8ef5001cbca98 because it changed
> the build layout on the Jenkins server and our RAT rules expected to apply
> from a root directory. I pinged Kenneth Knowles about it and he said he was
> taking a look.
>
> On Mon, Oct 23, 2017 at 11:53 AM, Raghu Angadi  > wrote:
>
>> Regd (1) :
>>
>> [4] did have have a file without Apache Licence. It was fixed the next
>> day (
>> commit
>> > c7b83032ad38c3dcac0#diff-26b77e086ff8292ef54f12b22b7b767a>),
>> thanks to Ken Knowles who pinged me about it.
>>
>> On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev <
>> valen...@google.com>
>> wrote:
>>
>> > Hi Beam-Dev,
>> >
>> > It's been >5 days since the last successful run of a
>> > beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
>> > successful run of beam_PreCommit_Java_MavenInstall[2].
>> >
>> > Looking at build logs I see following problems.
>> >
>> > 1. After October 17, postcommit builds started to fail with
>> >
>> > Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
>> > (default) on project beam-parent: Too many files with unapproved
>> license: 1
>> > See RAT report in: /home/jenkins/jenkins-slave/wo
>> > rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
>> > t-2.3.0-SNAPSHOT.rat
>> >
>> > The earliest build that I see this error is Postcommit #5052 [3].
>> >
>> > This makes me suspect [4] or [5] as a breaking change, since they change
>> > pom files.
>> >
>> > Questions:
>> > - Is there a way we can reproduce this failure locally? mvn clean verify
>> > passes locally for me.
>> > - Is there a way we can see the See RAT report mentioned in the error
>> > log?
>> >
>> > 2. Prior to onset of #1 Java Precommit builds no longer complete within
>> > allotted 150 min time. Looking at [6-8] it seems the build makes
>> consistent
>> > progress, but just does not finish on time. We can also see several
>> recent
>> > successful builds with execution time very close to time out [9-11].
>> >
>> > I'd like to propose to increase time limit for Java precommit test suite
>> > from 2.5 to 4 hours. 4 hours is long time. I agree that we should
>> > definitely try to reduce the test execution time, and reduce flakiness.
>> > However we need the tests at least pass for now. If we write off failed
>> > test suites as 'flakes' and merge PRs without having a green test
>> signal,
>> > we will have to spend more time tracing breakages such as #1.
>> >
>> > Thoughts?
>> >
>> > Thanks,
>> > Valentyn
>> >
>> > [1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
>> > [2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
>> > [3] https://builds.apache.org/job/beam_PostCommit_Java_MavenInst
>> > all/5052/changes
>> >
>> > [4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3b
>> > c3c67ba3e2617cb7f11a8c
>> > [5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b
>> > 3e9a26b6c9d0bb6dc3
>> >
>> > [6] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
>> ll/15222/
>> > [7] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
>> ll/15195/
>> > [8] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
>> ll/15220/
>> >
>> > [9] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
>> ll/15009/
>> > [10] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
>> ll/15068/
>> > [11] https://builds.apache.org/job/beam_PreCommit_Java_MavenInsta
>> ll/15016/
>> >
>> >
>>
>
>

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Griselda Cuevas]

@Ahmet - thanks for sharing part 1 of Neville's post and the one about the
SF Cloud Mafia Meetup. We can tweet about part 2 maybe tomorrow or Weds and
about the Stockholm meetup closer to the date.

@Ismael - re:Swag, I'm thinking of creating a swag store for Apache Beam -
I'll send a separate thread with the proposal. The idea is that we create
an online store for people to order swag for their events, they could pick
from a wide selection offered by a vendor. I got us an initial budget of
USD$2k and I was planning to give codes to Meetup founders and folks
speaking at conferences this year, once we run out of this budget people
can get their own swag or we can collaborate on a joint fund to get the
store going. I'll submit a new thread with details and the vendor proposal.

G

On 23 October 2017 at 07:56, Etienne Chauchot  wrote:

> Hi,
>
> +1 to share Neville's blogpost.
>
> Etienne
>
>
>
> Le 20/10/2017 à 22:08, Griselda Cuevas a écrit :
>
>> Hi everyone - What do you think about sharing Neville's blogpost[1] about
>> the road to Scio on the Apache Beam Twitter account?, I think it'd be good
>> to share some content since the last time we were active as 9/27.
>>
>> Also - could you help promote some of the upcoming Meetups? I made the
>> following tweets:
>>
>> 11/1 - San Francisco Cloud Mafia
>> Tweet:
>> Come join the SF Cloud Mafia to learn about stream & batch processing with
>> #ApacheBeam on Nov. 1st. https://www.meetup.com/San-
>> Francisco-Cloud-Mafia/events/244180581/
>>
>> 11/22 - StockholmApache Beam Meetup
>> Tweet:
>> Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join if
>> you're around! https://www.meetup.com/Apache-Beam-Stockholm/
>>
>> [1] https://labs.spotify.com/2017/10/16/big-data-processing-at-
>> spotify-the-road-to-scio-part-1/
>>
>> Thanks!
>> G
>>
>>
>

Re: Java pre/post commit test suite breakage

[Lukasz Cwik]

Another breaking change was caused by
https://github.com/apache/beam/commit/241d3cedd5a8fd3f360b8ec2f3a8ef5001cbca98
because it changed the build layout on the Jenkins server and our RAT rules
expected to apply from a root directory. I pinged Kenneth Knowles about it
and he said he was taking a look.

On Mon, Oct 23, 2017 at 11:53 AM, Raghu Angadi 
wrote:

> Regd (1) :
>
> [4] did have have a file without Apache Licence. It was fixed the next day
> (
> commit
>  d38c3dcac0#diff-26b77e086ff8292ef54f12b22b7b767a>),
> thanks to Ken Knowles who pinged me about it.
>
> On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev  >
> wrote:
>
> > Hi Beam-Dev,
> >
> > It's been >5 days since the last successful run of a
> > beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
> > successful run of beam_PreCommit_Java_MavenInstall[2].
> >
> > Looking at build logs I see following problems.
> >
> > 1. After October 17, postcommit builds started to fail with
> >
> > Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
> > (default) on project beam-parent: Too many files with unapproved
> license: 1
> > See RAT report in: /home/jenkins/jenkins-slave/wo
> > rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
> > t-2.3.0-SNAPSHOT.rat
> >
> > The earliest build that I see this error is Postcommit #5052 [3].
> >
> > This makes me suspect [4] or [5] as a breaking change, since they change
> > pom files.
> >
> > Questions:
> > - Is there a way we can reproduce this failure locally? mvn clean verify
> > passes locally for me.
> > - Is there a way we can see the See RAT report mentioned in the error
> > log?
> >
> > 2. Prior to onset of #1 Java Precommit builds no longer complete within
> > allotted 150 min time. Looking at [6-8] it seems the build makes
> consistent
> > progress, but just does not finish on time. We can also see several
> recent
> > successful builds with execution time very close to time out [9-11].
> >
> > I'd like to propose to increase time limit for Java precommit test suite
> > from 2.5 to 4 hours. 4 hours is long time. I agree that we should
> > definitely try to reduce the test execution time, and reduce flakiness.
> > However we need the tests at least pass for now. If we write off failed
> > test suites as 'flakes' and merge PRs without having a green test signal,
> > we will have to spend more time tracing breakages such as #1.
> >
> > Thoughts?
> >
> > Thanks,
> > Valentyn
> >
> > [1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
> > [2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
> > [3] https://builds.apache.org/job/beam_PostCommit_Java_MavenInst
> > all/5052/changes
> >
> > [4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3b
> > c3c67ba3e2617cb7f11a8c
> > [5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b
> > 3e9a26b6c9d0bb6dc3
> >
> > [6] https://builds.apache.org/job/beam_PreCommit_Java_
> MavenInstall/15222/
> > [7] https://builds.apache.org/job/beam_PreCommit_Java_
> MavenInstall/15195/
> > [8] https://builds.apache.org/job/beam_PreCommit_Java_
> MavenInstall/15220/
> >
> > [9] https://builds.apache.org/job/beam_PreCommit_Java_
> MavenInstall/15009/
> > [10] https://builds.apache.org/job/beam_PreCommit_Java_
> MavenInstall/15068/
> > [11] https://builds.apache.org/job/beam_PreCommit_Java_
> MavenInstall/15016/
> >
> >
>

Re: Java pre/post commit test suite breakage

[Raghu Angadi]

Regd (1) :

[4] did have have a file without Apache Licence. It was fixed the next day (
commit
),
thanks to Ken Knowles who pinged me about it.

On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev 
wrote:

> Hi Beam-Dev,
>
> It's been >5 days since the last successful run of a
> beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
> successful run of beam_PreCommit_Java_MavenInstall[2].
>
> Looking at build logs I see following problems.
>
> 1. After October 17, postcommit builds started to fail with
>
> Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
> (default) on project beam-parent: Too many files with unapproved license: 1
> See RAT report in: /home/jenkins/jenkins-slave/wo
> rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
> t-2.3.0-SNAPSHOT.rat
>
> The earliest build that I see this error is Postcommit #5052 [3].
>
> This makes me suspect [4] or [5] as a breaking change, since they change
> pom files.
>
> Questions:
> - Is there a way we can reproduce this failure locally? mvn clean verify
> passes locally for me.
> - Is there a way we can see the See RAT report mentioned in the error
> log?
>
> 2. Prior to onset of #1 Java Precommit builds no longer complete within
> allotted 150 min time. Looking at [6-8] it seems the build makes consistent
> progress, but just does not finish on time. We can also see several recent
> successful builds with execution time very close to time out [9-11].
>
> I'd like to propose to increase time limit for Java precommit test suite
> from 2.5 to 4 hours. 4 hours is long time. I agree that we should
> definitely try to reduce the test execution time, and reduce flakiness.
> However we need the tests at least pass for now. If we write off failed
> test suites as 'flakes' and merge PRs without having a green test signal,
> we will have to spend more time tracing breakages such as #1.
>
> Thoughts?
>
> Thanks,
> Valentyn
>
> [1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
> [2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
> [3] https://builds.apache.org/job/beam_PostCommit_Java_MavenInst
> all/5052/changes
>
> [4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3b
> c3c67ba3e2617cb7f11a8c
> [5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b
> 3e9a26b6c9d0bb6dc3
>
> [6] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15222/
> [7] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15195/
> [8] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15220/
>
> [9] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15009/
> [10] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15068/
> [11] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15016/
>
>

Re: Java pre/post commit test suite breakage

[Ben Chambers]

I believe license errors are detected by Apache RAT, which are part of the
release profile. I believe you need to run "mvn clean verify -Prelease" to
enable anything associated with that profile.

On Mon, Oct 23, 2017 at 11:46 AM Valentyn Tymofieiev
 wrote:

> Hi Beam-Dev,
>
> It's been >5 days since the last successful run of a
> beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
> successful run of beam_PreCommit_Java_MavenInstall[2].
>
> Looking at build logs I see following problems.
>
> 1. After October 17, postcommit builds started to fail with
>
> Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
> (default) on project beam-parent: Too many files with unapproved license: 1
> See RAT report in: /home/jenkins/jenkins-slave/workspace/beam_PostCommit_
> Java_MavenInstall/target/beam-parent-2.3.0-SNAPSHOT.rat
>
> The earliest build that I see this error is Postcommit #5052 [3].
>
> This makes me suspect [4] or [5] as a breaking change, since they change
> pom files.
>
> Questions:
> - Is there a way we can reproduce this failure locally? mvn clean verify
> passes locally for me.
> - Is there a way we can see the See RAT report mentioned in the error log?
>
>
> 2. Prior to onset of #1 Java Precommit builds no longer complete within
> allotted 150 min time. Looking at [6-8] it seems the build makes consistent
> progress, but just does not finish on time. We can also see several recent
> successful builds with execution time very close to time out [9-11].
>
> I'd like to propose to increase time limit for Java precommit test suite
> from 2.5 to 4 hours. 4 hours is long time. I agree that we should
> definitely try to reduce the test execution time, and reduce flakiness.
> However we need the tests at least pass for now. If we write off failed
> test suites as 'flakes' and merge PRs without having a green test signal,
> we will have to spend more time tracing breakages such as #1.
>
> Thoughts?
>
> Thanks,
> Valentyn
>
> [1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
> [2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
> [3] https://builds.apache.org/job/beam_PostCommit_Java_
> MavenInstall/5052/changes
>
> [4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3bc3c67ba3e261
> 7cb7f11a8c
> 
> [5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b3e9a26b6
> c9d0bb6dc3
> 
>
> [6] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15222/
> [7] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15195/
> [8] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15220/
>
> [9] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15009/
> [10] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15068/
> [11] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15016/
>

Re: Java pre/post commit test suite breakage

[Kenneth Knowles]

Agreed. We have to have green to make progress. The timeout should be there
only to halt a build that is a true failure.

It looks like the RAT check is rooted in the current working directory
rather than relative to the pom.xml. That's either our bug or RAT's, since
it makes no sense as a default behavior, but I'll find a way to fix it
either way.

On Mon, Oct 23, 2017 at 11:45 AM, Valentyn Tymofieiev 
wrote:

> Hi Beam-Dev,
>
> It's been >5 days since the last successful run of a
> beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
> successful run of beam_PreCommit_Java_MavenInstall[2].
>
> Looking at build logs I see following problems.
>
> 1. After October 17, postcommit builds started to fail with
>
> Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
> (default) on project beam-parent: Too many files with unapproved license: 1
> See RAT report in: /home/jenkins/jenkins-slave/wo
> rkspace/beam_PostCommit_Java_MavenInstall/target/beam-paren
> t-2.3.0-SNAPSHOT.rat
>
> The earliest build that I see this error is Postcommit #5052 [3].
>
> This makes me suspect [4] or [5] as a breaking change, since they change
> pom files.
>
> Questions:
> - Is there a way we can reproduce this failure locally? mvn clean verify
> passes locally for me.
> - Is there a way we can see the See RAT report mentioned in the error
> log?
>
> 2. Prior to onset of #1 Java Precommit builds no longer complete within
> allotted 150 min time. Looking at [6-8] it seems the build makes consistent
> progress, but just does not finish on time. We can also see several recent
> successful builds with execution time very close to time out [9-11].
>
> I'd like to propose to increase time limit for Java precommit test suite
> from 2.5 to 4 hours. 4 hours is long time. I agree that we should
> definitely try to reduce the test execution time, and reduce flakiness.
> However we need the tests at least pass for now. If we write off failed
> test suites as 'flakes' and merge PRs without having a green test signal,
> we will have to spend more time tracing breakages such as #1.
>
> Thoughts?
>
> Thanks,
> Valentyn
>
> [1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
> [2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
> [3] https://builds.apache.org/job/beam_PostCommit_Java_MavenInst
> all/5052/changes
>
> [4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3b
> c3c67ba3e2617cb7f11a8c
> [5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b
> 3e9a26b6c9d0bb6dc3
>
> [6] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15222/
> [7] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15195/
> [8] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15220/
>
> [9] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15009/
> [10] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15068/
> [11] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15016/
>
>

Java pre/post commit test suite breakage

[Valentyn Tymofieiev]

Hi Beam-Dev,

It's been >5 days since the last successful run of a
beam_PreCommit_Java_MavenInstall build[1]  and >4 days since last
successful run of beam_PreCommit_Java_MavenInstall[2].

Looking at build logs I see following problems.

1. After October 17, postcommit builds started to fail with

Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
(default) on project beam-parent: Too many files with unapproved license: 1
See RAT report in: /home/jenkins/jenkins-slave/workspace/beam_PostCommit_
Java_MavenInstall/target/beam-parent-2.3.0-SNAPSHOT.rat

The earliest build that I see this error is Postcommit #5052 [3].

This makes me suspect [4] or [5] as a breaking change, since they change
pom files.

Questions:
- Is there a way we can reproduce this failure locally? mvn clean verify
passes locally for me.
- Is there a way we can see the See RAT report mentioned in the error log?


2. Prior to onset of #1 Java Precommit builds no longer complete within
allotted 150 min time. Looking at [6-8] it seems the build makes consistent
progress, but just does not finish on time. We can also see several recent
successful builds with execution time very close to time out [9-11].

I'd like to propose to increase time limit for Java precommit test suite
from 2.5 to 4 hours. 4 hours is long time. I agree that we should
definitely try to reduce the test execution time, and reduce flakiness.
However we need the tests at least pass for now. If we write off failed
test suites as 'flakes' and merge PRs without having a green test signal,
we will have to spend more time tracing breakages such as #1.

Thoughts?

Thanks,
Valentyn

[1] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/
[2] https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/
[3] https://builds.apache.org/job/beam_PostCommit_Java_
MavenInstall/5052/changes

[4] https://github.com/apache/beam/commit/d745cc9d8cc1735d3bc3c67ba3e261
7cb7f11a8c
[5] https://github.com/apache/beam/commit/0d8ab6cbbc762dd9f9be1b3e9a26b6
c9d0bb6dc3

[6] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15222/
[7] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15195/
[8] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15220/

[9] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15009/
[10] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15068/
[11] https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15016/

Build failed in Jenkins: beam_SeedJob_Standalone #18

[Apache Jenkins Server]

See 

--
GitHub pull request #3668 of commit 4edd021cb041d60298e3c39677bdc7cffa8d8004, 
no merge conflicts.
Setting status of 4edd021cb041d60298e3c39677bdc7cffa8d8004 to PENDING with url 
https://builds.apache.org/job/beam_SeedJob_Standalone/18/ and message: 'Build 
started sha1 is merged.'
Using context: Jenkins: Standalone Seed Job
[EnvInject] - Loading node environment variables.
Building remotely on beam6 (beam) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/beam.git 
 > +refs/head/*:refs/remotes/origin/* 
 > +refs/pull/${ghprPullId}/*:refs/remotes/origin/pr/${ghprPullId}/*
 > git rev-parse refs/remotes/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse origin/pr/3668/merge^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch 
configuration for this job.
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/beam.git 
 > +refs/head/*:refs/remotes/origin/* 
 > +refs/pull/${ghprPullId}/*:refs/remotes/origin/pr/${ghprPullId}/*
 > git rev-parse refs/remotes/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse origin/pr/3668/merge^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch 
configuration for this job.
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/beam.git 
 > +refs/head/*:refs/remotes/origin/* 
 > +refs/pull/${ghprPullId}/*:refs/remotes/origin/pr/${ghprPullId}/*
 > git rev-parse refs/remotes/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse origin/pr/3668/merge^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch 
configuration for this job.
Not sending mail to unregistered user valen...@google.com
Not sending mail to unregistered user ekirpic...@gmail.com

Build failed in Jenkins: beam_SeedJob #498

[Apache Jenkins Server]

See 

--
GitHub pull request #3668 of commit 4edd021cb041d60298e3c39677bdc7cffa8d8004, 
no merge conflicts.
Setting status of 4edd021cb041d60298e3c39677bdc7cffa8d8004 to PENDING with url 
https://builds.apache.org/job/beam_SeedJob/498/ and message: 'Build started 
sha1 is merged.'
Using context: Jenkins: Seed Job
[EnvInject] - Loading node environment variables.
Building remotely on beam4 (beam) in workspace 

Cloning the remote Git repository
Cloning repository https://github.com/apache/beam.git
 > git init  # timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/beam.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git fetch --tags --progress https://github.com/apache/beam.git 
 > +refs/heads/*:refs/remotes/origin/* 
 > +refs/pull/3668/*:refs/remotes/origin/pr/3668/*
 > git rev-parse refs/remotes/origin/pr/3668/merge^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/pr/3668/merge^{commit} # timeout=10
Checking out Revision 0871ca05d575d85c136ea4b7809d41580af7af15 
(refs/remotes/origin/pr/3668/merge)
Commit message: "Merge 4edd021cb041d60298e3c39677bdc7cffa8d8004 into 
77c77add12fb9b118f4ff1418d7fe5dec5154895"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0871ca05d575d85c136ea4b7809d41580af7af15
First time build. Skipping changelog.
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
SPARK_LOCAL_IP=127.0.0.1

[EnvInject] - Variables injected successfully.
Processing DSL script job_beam_Java_Build.groovy
Processing DSL script job_beam_Java_CodeHealth.groovy
Processing DSL script job_beam_Java_IntegrationTest.groovy
Processing DSL script job_beam_Java_UnitTest.groovy
Processing DSL script job_beam_PerformanceTests_Dataflow.groovy
Processing DSL script job_beam_PerformanceTests_JDBC.groovy
Processing DSL script job_beam_PerformanceTests_Python.groovy
Processing DSL script job_beam_PerformanceTests_Spark.groovy
Processing DSL script job_beam_PostCommit_Java_JDKVersionsTest.groovy
Processing DSL script job_beam_PostCommit_Java_MavenInstall.groovy
Processing DSL script job_beam_PostCommit_Java_MavenInstall_Windows.groovy
Processing DSL script job_beam_PostCommit_Java_ValidatesRunner_Apex.groovy
Processing DSL script job_beam_PostCommit_Java_ValidatesRunner_Dataflow.groovy
Processing DSL script job_beam_PostCommit_Java_ValidatesRunner_Flink.groovy
Processing DSL script job_beam_PostCommit_Java_ValidatesRunner_Gearpump.groovy
Processing DSL script job_beam_PostCommit_Java_ValidatesRunner_Spark.groovy
Processing DSL script job_beam_PostCommit_Python_ValidatesRunner_Dataflow.groovy
Processing DSL script job_beam_PostCommit_Python_Verify.groovy
Processing DSL script job_beam_PreCommit_Go_MavenInstall.groovy
Processing DSL script job_beam_PreCommit_Java_MavenInstall.groovy
Processing DSL script job_beam_PreCommit_Pipeline.groovy
Processing DSL script job_beam_PreCommit_Python_MavenInstall.groovy
Processing DSL script job_beam_PreCommit_Website_Merge.groovy
Processing DSL script job_beam_PreCommit_Website_Stage.groovy
Processing DSL script job_beam_PreCommit_Website_Test.groovy
Processing DSL script job_beam_Python_UnitTest.groovy
Processing DSL script job_beam_Release_NightlySnapshot.groovy
Processing DSL script job_seed.groovy
Processing DSL script job_seed_standalone.groovy
ERROR: (job_seed_standalone.groovy, line 58) No such property: defaultBranch 
for class: javaposse.jobdsl.dsl.helpers.BuildParametersContext

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Neville Li]

Hi all,

Part 2 is out:
https://labs.spotify.com/2017/10/23/big-data-processing-at-spotify-the-road-to-scio-part-2/

We also have a meetup in Stockholm later today:
https://www.meetup.com/stockholm-hug/events/244112281/

On Mon, Oct 23, 2017 at 3:03 PM Ismaël Mejía  wrote:

> Has anybody thought about getting some Beam 'swag' for these events
> (the meetups + conference talks) ? So far I have seen some Beam
> stickers around but it would be really nice to have some other items:
> t-shirts, mugs, socks, corkscrews, webcam covers, whatever.
> People seem to love these things and is a simple way to promote the
> project.
>
> Ismaël
>
>
> On Sat, Oct 21, 2017 at 7:40 AM, Jean-Baptiste Onofré 
> wrote:
> > +1 for Neville's post.
> >
> > And no problem to promote the coming meetups.
> >
> > Regards
> > JB
> >
> >
> > On 10/20/2017 10:08 PM, Griselda Cuevas wrote:
> >>
> >> Hi everyone - What do you think about sharing Neville's blogpost[1]
> about
> >> the road to Scio on the Apache Beam Twitter account?, I think it'd be
> good
> >> to share some content since the last time we were active as 9/27.
> >>
> >> Also - could you help promote some of the upcoming Meetups? I made the
> >> following tweets:
> >>
> >> 11/1 - San Francisco Cloud Mafia
> >> Tweet:
> >> Come join the SF Cloud Mafia to learn about stream & batch processing
> with
> >> #ApacheBeam on Nov. 1st. https://www.meetup.com/San-
> >> Francisco-Cloud-Mafia/events/244180581/
> >>
> >> 11/22 - StockholmApache Beam Meetup
> >> Tweet:
> >> Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join
> if
> >> you're around! https://www.meetup.com/Apache-Beam-Stockholm/
> >>
> >> [1] https://labs.spotify.com/2017/10/16/big-data-processing-at-
> >> spotify-the-road-to-scio-part-1/
> >>
> >> Thanks!
> >> G
> >>
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Ismaël Mejía]

Has anybody thought about getting some Beam 'swag' for these events
(the meetups + conference talks) ? So far I have seen some Beam
stickers around but it would be really nice to have some other items:
t-shirts, mugs, socks, corkscrews, webcam covers, whatever.
People seem to love these things and is a simple way to promote the project.

Ismaël


On Sat, Oct 21, 2017 at 7:40 AM, Jean-Baptiste Onofré  wrote:
> +1 for Neville's post.
>
> And no problem to promote the coming meetups.
>
> Regards
> JB
>
>
> On 10/20/2017 10:08 PM, Griselda Cuevas wrote:
>>
>> Hi everyone - What do you think about sharing Neville's blogpost[1] about
>> the road to Scio on the Apache Beam Twitter account?, I think it'd be good
>> to share some content since the last time we were active as 9/27.
>>
>> Also - could you help promote some of the upcoming Meetups? I made the
>> following tweets:
>>
>> 11/1 - San Francisco Cloud Mafia
>> Tweet:
>> Come join the SF Cloud Mafia to learn about stream & batch processing with
>> #ApacheBeam on Nov. 1st. https://www.meetup.com/San-
>> Francisco-Cloud-Mafia/events/244180581/
>>
>> 11/22 - StockholmApache Beam Meetup
>> Tweet:
>> Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join if
>> you're around! https://www.meetup.com/Apache-Beam-Stockholm/
>>
>> [1] https://labs.spotify.com/2017/10/16/big-data-processing-at-
>> spotify-the-road-to-scio-part-1/
>>
>> Thanks!
>> G
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com