Jenkins build is back to normal : beam_SeedJob_Standalone #21

2017-10-23 Thread Apache Jenkins Server
See

Re: Update on 2.2.0 release

2017-10-23 Thread 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

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

2017-10-23 Thread 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"

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

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

2017-10-23 Thread 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

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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,

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

Re: Java pre/post commit test suite breakage

2017-10-23 Thread 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

Java pre/post commit test suite breakage

2017-10-23 Thread 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

Build failed in Jenkins: beam_SeedJob_Standalone #18

2017-10-23 Thread Apache Jenkins Server
See -- GitHub pull request #3668 of commit 4edd021cb041d60298e3c39677bdc7cffa8d8004, no merge conflicts. Setting status of 4edd021cb041d60298e3c39677bdc7cffa8d8004 to PENDING with

Build failed in Jenkins: beam_SeedJob #498

2017-10-23 Thread Apache Jenkins Server
See -- GitHub pull request #3668 of commit 4edd021cb041d60298e3c39677bdc7cffa8d8004, no merge conflicts. Setting status of 4edd021cb041d60298e3c39677bdc7cffa8d8004 to PENDING with url

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

2017-10-23 Thread 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: >

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

2017-10-23 Thread 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