The Google Cloud Dataflow runner has now been recovered. Special thanks goes to Luke Cwik for working through several issues to get us here.
Jenkins project "beam_PostCommit_RunnableOnService_GoogleCloudDataflow" now verifies this integration. It runs a test pass for every code push to the repository, with failure emails being sent to the commits@ mailing list. >From this point onward, let's make sure we address any breakage to this test as soon as possible. ( Hopefully, we'll get this running in a pre-commit way too. That is, unfortunately, blocked on INFRA-11610 [2]. ) [1] https://builds.apache.org/view/Beam/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/ [2] https://issues.apache.org/jira/browse/INFRA-11610 On Wed, Apr 13, 2016 at 10:55 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Great work guys ! > > A big step forward. > > Thanks > Regards > JB > > > On 04/14/2016 07:43 AM, Davor Bonaci wrote: > >> I've just merged a pull request that includes this project-wide renaming >> of >> Java packages. (Long live Beam!) >> >> At this point, pending pull requests may need to be rebased. We'll try to >> fix the Cloud Dataflow runner as soon as possible, but it might take a >> little bit to complete that. >> >> There's still a lot left to re-organize in Beam, but I'd expect future >> changes not to be this far-reaching. >> >> A special thanks goes to Ben Chambers for pulling off several tricks to >> get >> this done quickly and effectively. >> >> On Tue, Apr 12, 2016 at 9:38 PM, Jean-Baptiste Onofré <[email protected]> >> wrote: >> >> Hi Davor, >>> >>> +1 ! >>> >>> I already updated the PullRequest for annotations package. >>> >>> Thanks ! >>> Regards >>> JB >>> >>> >>> On 04/13/2016 03:23 AM, Davor Bonaci wrote: >>> >>> We are preparing to do a massive, project-wide package rename from >>>> "com.google.cloud.dataflow" to "org.apache.beam". At the earliest, this >>>> could occur sometime tomorrow afternoon (Pacific time). >>>> >>>> Unfortunately, there's no way to do this without affecting ongoing work. >>>> We'll try to do it as quickly as possible to minimize such impact. >>>> >>>> We'll ensure that existing automated testing passes before merging the >>>> change, with the exception of integration coverage with the Google Cloud >>>> Dataflow service. We expect that the code in Beam's master will not work >>>> against Cloud Dataflow for a little bit -- we'll accept this breakage >>>> on a >>>> one-time basis, and try to recover it as soon as possible thereafter. >>>> >>>> If anybody sees any issues with this plan, I'd love to hear it. >>>> >>>> This is one of those mandatory things we've been delaying for a while >>>> now. >>>> Of course, there are more such things to come, but hopefully none that >>>> are >>>> this wide. >>>> >>>> Thanks! >>>> >>>> >>>> -- >>> Jean-Baptiste Onofré >>> [email protected] >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >>> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
