You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Ismaël Mejía <ie...@gmail.com> on 2019/04/18 16:37:42 UTC
Re: SNAPSHOTS have not been updated since february
Any progress on this?
On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <da...@google.com> wrote:
>
> I made a bug for this specific issue (artifacts not publishing to the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
>
> While I was gathering info for the bug report I also noticed +Yifan Zou has an experimental PR testing a fix: https://github.com/apache/beam/pull/8148
>
> On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com> wrote:
>>
>> +Daniel Oliveira
>>
>> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com> wrote:
>>>
>>> Sorry for the typo. Ideally, the snapshot publish is independent from postrelease_snapshot.
>>>
>>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com> wrote:
>>>>
>>>> Hey,
>>>>
>>>> I'm trying to publish the artifacts by commenting "Run Gradle Publish" in my PR, but there are several errors saying "cannot write artifacts into dir", anyone has idea on it? Ideally, the snapshot publish is dependent from postrelease_snapshot. The publish task is to build and publish artifacts and the postrelease_snapshot is to verify whether the snapshot works.
>>>>
>>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>> I believe this is related to https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a fix in progress https://github.com/apache/beam/pull/8132
>>>>>
>>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com> wrote:
>>>>>>
>>>>>> I was trying to validate a fix on the Spark runner and realized that
>>>>>> Beam SNAPSHOTS have not been updated since February 24 !
>>>>>>
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
>>>>>>
>>>>>> Can somebody please take a look at why this is not been updated?
>>>>>>
>>>>>> Thanks,
>>>>>> Ismaël
Re: SNAPSHOTS have not been updated since february
Posted by Yifan Zou <yi...@google.com>.
We could send an email alert once the snapshots publishing fails.
Alternatively, we have a job_PostRelease_NightlySnapshot
<https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_PostRelease_NightlySnapshot.groovy>
to
validate the healthy of the snapshots. It pulls the latest snapshots and
run java examples against multiple runners. We may also be able to check
the publishing date of the recent snapshot and notify devs if it has not
been updated for a long time.
On Tue, Apr 23, 2019 at 3:25 AM Ismaël Mejía <ie...@gmail.com> wrote:
> Thanks a lot Yifan, just pulled them and everything working as expected +1
>
> I wonder still if we may need some extra verification task to detect
> when those have not been updated (which can happen for both INFRA or
> other reasons).
>
> On Tue, Apr 23, 2019 at 4:44 AM Yifan Zou <yi...@google.com> wrote:
> >
> > The Infra is reviewing the security on our new Jenkins agents. In the
> meanwhile, I assigned the publishing job to the 'ubuntu' labelled nodes as
> a workaround. The snapshots were successfully published in
> beam_Release_NightlySnapshot#421. I'll move the job assignment back once
> our nodes are fully setup.
> >
> > Thanks
> >
> > Yifan
> >
> >
> > On Fri, Apr 19, 2019 at 2:05 AM Ismaël Mejía <ie...@gmail.com> wrote:
> >>
> >> Thanks everyone for the quick answer and thanks Yifan for taking care.
> >>
> >> On Thu, Apr 18, 2019 at 7:15 PM Yifan Zou <yi...@google.com> wrote:
> >> >
> >> > The origin build nodes were updated in Jan 24 and the nexus
> credentials were removed from the filesystem because they are not supposed
> to be on external build nodes (nodes Infra does not own). We now need to
> set up the role account on the new Beam JNLP nodes. I am still contacting
> Infra to bring the snapshot back.
> >> >
> >> > Yifan
> >> >
> >> > On Thu, Apr 18, 2019 at 10:09 AM Lukasz Cwik <lc...@google.com>
> wrote:
> >> >>
> >> >> The permissions issue is that the credentials needed to publish to
> the maven repository are only deployed on machines managed by Apache Infra.
> Now that the machines have been given back to each project to manage Yifan
> was investigating some other way to get the permissions on to the machine.
> >> >>
> >> >> On Thu, Apr 18, 2019 at 10:06 AM Boyuan Zhang <bo...@google.com>
> wrote:
> >> >>>
> >> >>> There is a test target
> https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam,
> which builds and pushes snapshot to maven every day. Current failure is
> like, the jenkin machine cannot publish artifacts into maven owing to some
> weird permission issue. I think +Yifan Zou is working on it actively.
> >> >>>
> >> >>> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com>
> wrote:
> >> >>>>
> >> >>>> And is there a way we can detect SNAPSHOTS not been published
> daily in
> >> >>>> the future?
> >> >>>>
> >> >>>> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com>
> wrote:
> >> >>>> >
> >> >>>> > Any progress on this?
> >> >>>> >
> >> >>>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <
> danoliveira@google.com> wrote:
> >> >>>> > >
> >> >>>> > > I made a bug for this specific issue (artifacts not publishing
> to the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
> >> >>>> > >
> >> >>>> > > While I was gathering info for the bug report I also noticed
> +Yifan Zou has an experimental PR testing a fix:
> https://github.com/apache/beam/pull/8148
> >> >>>> > >
> >> >>>> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <
> boyuanz@google.com> wrote:
> >> >>>> > >>
> >> >>>> > >> +Daniel Oliveira
> >> >>>> > >>
> >> >>>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <
> boyuanz@google.com> wrote:
> >> >>>> > >>>
> >> >>>> > >>> Sorry for the typo. Ideally, the snapshot publish is
> independent from postrelease_snapshot.
> >> >>>> > >>>
> >> >>>> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <
> boyuanz@google.com> wrote:
> >> >>>> > >>>>
> >> >>>> > >>>> Hey,
> >> >>>> > >>>>
> >> >>>> > >>>> I'm trying to publish the artifacts by commenting "Run
> Gradle Publish" in my PR, but there are several errors saying "cannot write
> artifacts into dir", anyone has idea on it? Ideally, the snapshot publish
> is dependent from postrelease_snapshot. The publish task is to build and
> publish artifacts and the postrelease_snapshot is to verify whether the
> snapshot works.
> >> >>>> > >>>>
> >> >>>> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <
> altay@google.com> wrote:
> >> >>>> > >>>>>
> >> >>>> > >>>>> I believe this is related to
> https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a
> fix in progress https://github.com/apache/beam/pull/8132
> >> >>>> > >>>>>
> >> >>>> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <
> iemejia@gmail.com> wrote:
> >> >>>> > >>>>>>
> >> >>>> > >>>>>> I was trying to validate a fix on the Spark runner and
> realized that
> >> >>>> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
> >> >>>> > >>>>>>
> >> >>>> > >>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
> >> >>>> > >>>>>>
> >> >>>> > >>>>>> Can somebody please take a look at why this is not been
> updated?
> >> >>>> > >>>>>>
> >> >>>> > >>>>>> Thanks,
> >> >>>> > >>>>>> Ismaël
>
Re: SNAPSHOTS have not been updated since february
Posted by Ismaël Mejía <ie...@gmail.com>.
Thanks a lot Yifan, just pulled them and everything working as expected +1
I wonder still if we may need some extra verification task to detect
when those have not been updated (which can happen for both INFRA or
other reasons).
On Tue, Apr 23, 2019 at 4:44 AM Yifan Zou <yi...@google.com> wrote:
>
> The Infra is reviewing the security on our new Jenkins agents. In the meanwhile, I assigned the publishing job to the 'ubuntu' labelled nodes as a workaround. The snapshots were successfully published in beam_Release_NightlySnapshot#421. I'll move the job assignment back once our nodes are fully setup.
>
> Thanks
>
> Yifan
>
>
> On Fri, Apr 19, 2019 at 2:05 AM Ismaël Mejía <ie...@gmail.com> wrote:
>>
>> Thanks everyone for the quick answer and thanks Yifan for taking care.
>>
>> On Thu, Apr 18, 2019 at 7:15 PM Yifan Zou <yi...@google.com> wrote:
>> >
>> > The origin build nodes were updated in Jan 24 and the nexus credentials were removed from the filesystem because they are not supposed to be on external build nodes (nodes Infra does not own). We now need to set up the role account on the new Beam JNLP nodes. I am still contacting Infra to bring the snapshot back.
>> >
>> > Yifan
>> >
>> > On Thu, Apr 18, 2019 at 10:09 AM Lukasz Cwik <lc...@google.com> wrote:
>> >>
>> >> The permissions issue is that the credentials needed to publish to the maven repository are only deployed on machines managed by Apache Infra. Now that the machines have been given back to each project to manage Yifan was investigating some other way to get the permissions on to the machine.
>> >>
>> >> On Thu, Apr 18, 2019 at 10:06 AM Boyuan Zhang <bo...@google.com> wrote:
>> >>>
>> >>> There is a test target https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam, which builds and pushes snapshot to maven every day. Current failure is like, the jenkin machine cannot publish artifacts into maven owing to some weird permission issue. I think +Yifan Zou is working on it actively.
>> >>>
>> >>> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com> wrote:
>> >>>>
>> >>>> And is there a way we can detect SNAPSHOTS not been published daily in
>> >>>> the future?
>> >>>>
>> >>>> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com> wrote:
>> >>>> >
>> >>>> > Any progress on this?
>> >>>> >
>> >>>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <da...@google.com> wrote:
>> >>>> > >
>> >>>> > > I made a bug for this specific issue (artifacts not publishing to the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
>> >>>> > >
>> >>>> > > While I was gathering info for the bug report I also noticed +Yifan Zou has an experimental PR testing a fix: https://github.com/apache/beam/pull/8148
>> >>>> > >
>> >>>> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com> wrote:
>> >>>> > >>
>> >>>> > >> +Daniel Oliveira
>> >>>> > >>
>> >>>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com> wrote:
>> >>>> > >>>
>> >>>> > >>> Sorry for the typo. Ideally, the snapshot publish is independent from postrelease_snapshot.
>> >>>> > >>>
>> >>>> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com> wrote:
>> >>>> > >>>>
>> >>>> > >>>> Hey,
>> >>>> > >>>>
>> >>>> > >>>> I'm trying to publish the artifacts by commenting "Run Gradle Publish" in my PR, but there are several errors saying "cannot write artifacts into dir", anyone has idea on it? Ideally, the snapshot publish is dependent from postrelease_snapshot. The publish task is to build and publish artifacts and the postrelease_snapshot is to verify whether the snapshot works.
>> >>>> > >>>>
>> >>>> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com> wrote:
>> >>>> > >>>>>
>> >>>> > >>>>> I believe this is related to https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a fix in progress https://github.com/apache/beam/pull/8132
>> >>>> > >>>>>
>> >>>> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com> wrote:
>> >>>> > >>>>>>
>> >>>> > >>>>>> I was trying to validate a fix on the Spark runner and realized that
>> >>>> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
>> >>>> > >>>>>>
>> >>>> > >>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
>> >>>> > >>>>>>
>> >>>> > >>>>>> Can somebody please take a look at why this is not been updated?
>> >>>> > >>>>>>
>> >>>> > >>>>>> Thanks,
>> >>>> > >>>>>> Ismaël
Re: SNAPSHOTS have not been updated since february
Posted by Yifan Zou <yi...@google.com>.
The Infra is reviewing the security on our new Jenkins agents. In the
meanwhile, I assigned the publishing job to the 'ubuntu' labelled nodes as
a workaround. The snapshots were successfully published in
beam_Release_NightlySnapshot#421
<https://builds.apache.org/job/beam_Release_NightlySnapshot/421/>. I'll
move the job assignment back once our nodes are fully setup.
Thanks
Yifan
On Fri, Apr 19, 2019 at 2:05 AM Ismaël Mejía <ie...@gmail.com> wrote:
> Thanks everyone for the quick answer and thanks Yifan for taking care.
>
> On Thu, Apr 18, 2019 at 7:15 PM Yifan Zou <yi...@google.com> wrote:
> >
> > The origin build nodes were updated in Jan 24 and the nexus credentials
> were removed from the filesystem because they are not supposed to be on
> external build nodes (nodes Infra does not own). We now need to set up the
> role account on the new Beam JNLP nodes. I am still contacting Infra to
> bring the snapshot back.
> >
> > Yifan
> >
> > On Thu, Apr 18, 2019 at 10:09 AM Lukasz Cwik <lc...@google.com> wrote:
> >>
> >> The permissions issue is that the credentials needed to publish to the
> maven repository are only deployed on machines managed by Apache Infra. Now
> that the machines have been given back to each project to manage Yifan was
> investigating some other way to get the permissions on to the machine.
> >>
> >> On Thu, Apr 18, 2019 at 10:06 AM Boyuan Zhang <bo...@google.com>
> wrote:
> >>>
> >>> There is a test target
> https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam,
> which builds and pushes snapshot to maven every day. Current failure is
> like, the jenkin machine cannot publish artifacts into maven owing to some
> weird permission issue. I think +Yifan Zou is working on it actively.
> >>>
> >>> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com>
> wrote:
> >>>>
> >>>> And is there a way we can detect SNAPSHOTS not been published daily in
> >>>> the future?
> >>>>
> >>>> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com>
> wrote:
> >>>> >
> >>>> > Any progress on this?
> >>>> >
> >>>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <
> danoliveira@google.com> wrote:
> >>>> > >
> >>>> > > I made a bug for this specific issue (artifacts not publishing to
> the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
> >>>> > >
> >>>> > > While I was gathering info for the bug report I also noticed
> +Yifan Zou has an experimental PR testing a fix:
> https://github.com/apache/beam/pull/8148
> >>>> > >
> >>>> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com>
> wrote:
> >>>> > >>
> >>>> > >> +Daniel Oliveira
> >>>> > >>
> >>>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com>
> wrote:
> >>>> > >>>
> >>>> > >>> Sorry for the typo. Ideally, the snapshot publish is
> independent from postrelease_snapshot.
> >>>> > >>>
> >>>> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <
> boyuanz@google.com> wrote:
> >>>> > >>>>
> >>>> > >>>> Hey,
> >>>> > >>>>
> >>>> > >>>> I'm trying to publish the artifacts by commenting "Run Gradle
> Publish" in my PR, but there are several errors saying "cannot write
> artifacts into dir", anyone has idea on it? Ideally, the snapshot publish
> is dependent from postrelease_snapshot. The publish task is to build and
> publish artifacts and the postrelease_snapshot is to verify whether the
> snapshot works.
> >>>> > >>>>
> >>>> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com>
> wrote:
> >>>> > >>>>>
> >>>> > >>>>> I believe this is related to
> https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a
> fix in progress https://github.com/apache/beam/pull/8132
> >>>> > >>>>>
> >>>> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <
> iemejia@gmail.com> wrote:
> >>>> > >>>>>>
> >>>> > >>>>>> I was trying to validate a fix on the Spark runner and
> realized that
> >>>> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
> >>>> > >>>>>>
> >>>> > >>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
> >>>> > >>>>>>
> >>>> > >>>>>> Can somebody please take a look at why this is not been
> updated?
> >>>> > >>>>>>
> >>>> > >>>>>> Thanks,
> >>>> > >>>>>> Ismaël
>
Re: SNAPSHOTS have not been updated since february
Posted by Ismaël Mejía <ie...@gmail.com>.
Thanks everyone for the quick answer and thanks Yifan for taking care.
On Thu, Apr 18, 2019 at 7:15 PM Yifan Zou <yi...@google.com> wrote:
>
> The origin build nodes were updated in Jan 24 and the nexus credentials were removed from the filesystem because they are not supposed to be on external build nodes (nodes Infra does not own). We now need to set up the role account on the new Beam JNLP nodes. I am still contacting Infra to bring the snapshot back.
>
> Yifan
>
> On Thu, Apr 18, 2019 at 10:09 AM Lukasz Cwik <lc...@google.com> wrote:
>>
>> The permissions issue is that the credentials needed to publish to the maven repository are only deployed on machines managed by Apache Infra. Now that the machines have been given back to each project to manage Yifan was investigating some other way to get the permissions on to the machine.
>>
>> On Thu, Apr 18, 2019 at 10:06 AM Boyuan Zhang <bo...@google.com> wrote:
>>>
>>> There is a test target https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam, which builds and pushes snapshot to maven every day. Current failure is like, the jenkin machine cannot publish artifacts into maven owing to some weird permission issue. I think +Yifan Zou is working on it actively.
>>>
>>> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com> wrote:
>>>>
>>>> And is there a way we can detect SNAPSHOTS not been published daily in
>>>> the future?
>>>>
>>>> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com> wrote:
>>>> >
>>>> > Any progress on this?
>>>> >
>>>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <da...@google.com> wrote:
>>>> > >
>>>> > > I made a bug for this specific issue (artifacts not publishing to the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
>>>> > >
>>>> > > While I was gathering info for the bug report I also noticed +Yifan Zou has an experimental PR testing a fix: https://github.com/apache/beam/pull/8148
>>>> > >
>>>> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com> wrote:
>>>> > >>
>>>> > >> +Daniel Oliveira
>>>> > >>
>>>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com> wrote:
>>>> > >>>
>>>> > >>> Sorry for the typo. Ideally, the snapshot publish is independent from postrelease_snapshot.
>>>> > >>>
>>>> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com> wrote:
>>>> > >>>>
>>>> > >>>> Hey,
>>>> > >>>>
>>>> > >>>> I'm trying to publish the artifacts by commenting "Run Gradle Publish" in my PR, but there are several errors saying "cannot write artifacts into dir", anyone has idea on it? Ideally, the snapshot publish is dependent from postrelease_snapshot. The publish task is to build and publish artifacts and the postrelease_snapshot is to verify whether the snapshot works.
>>>> > >>>>
>>>> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com> wrote:
>>>> > >>>>>
>>>> > >>>>> I believe this is related to https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a fix in progress https://github.com/apache/beam/pull/8132
>>>> > >>>>>
>>>> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com> wrote:
>>>> > >>>>>>
>>>> > >>>>>> I was trying to validate a fix on the Spark runner and realized that
>>>> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
>>>> > >>>>>>
>>>> > >>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
>>>> > >>>>>>
>>>> > >>>>>> Can somebody please take a look at why this is not been updated?
>>>> > >>>>>>
>>>> > >>>>>> Thanks,
>>>> > >>>>>> Ismaël
Re: SNAPSHOTS have not been updated since february
Posted by Yifan Zou <yi...@google.com>.
The origin build nodes were updated in Jan 24 and the nexus credentials
were removed from the filesystem because they are not supposed to be on
external build nodes (nodes Infra does not own). We now need to set up the
role account on the new Beam JNLP nodes. I am still contacting Infra to
bring the snapshot back.
Yifan
On Thu, Apr 18, 2019 at 10:09 AM Lukasz Cwik <lc...@google.com> wrote:
> The permissions issue is that the credentials needed to publish to the
> maven repository are only deployed on machines managed by Apache Infra. Now
> that the machines have been given back to each project to manage Yifan was
> investigating some other way to get the permissions on to the machine.
>
> On Thu, Apr 18, 2019 at 10:06 AM Boyuan Zhang <bo...@google.com> wrote:
>
>> There is a test target
>> https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam,
>> which builds and pushes snapshot to maven every day. Current failure is
>> like, the jenkin machine cannot publish artifacts into maven owing to some
>> weird permission issue. I think +Yifan Zou <yi...@google.com> is
>> working on it actively.
>>
>> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com> wrote:
>>
>>> And is there a way we can detect SNAPSHOTS not been published daily in
>>> the future?
>>>
>>> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com> wrote:
>>> >
>>> > Any progress on this?
>>> >
>>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <
>>> danoliveira@google.com> wrote:
>>> > >
>>> > > I made a bug for this specific issue (artifacts not publishing to
>>> the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
>>> > >
>>> > > While I was gathering info for the bug report I also noticed +Yifan
>>> Zou has an experimental PR testing a fix:
>>> https://github.com/apache/beam/pull/8148
>>> > >
>>> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com>
>>> wrote:
>>> > >>
>>> > >> +Daniel Oliveira
>>> > >>
>>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com>
>>> wrote:
>>> > >>>
>>> > >>> Sorry for the typo. Ideally, the snapshot publish is independent
>>> from postrelease_snapshot.
>>> > >>>
>>> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com>
>>> wrote:
>>> > >>>>
>>> > >>>> Hey,
>>> > >>>>
>>> > >>>> I'm trying to publish the artifacts by commenting "Run Gradle
>>> Publish" in my PR, but there are several errors saying "cannot write
>>> artifacts into dir", anyone has idea on it? Ideally, the snapshot publish
>>> is dependent from postrelease_snapshot. The publish task is to build and
>>> publish artifacts and the postrelease_snapshot is to verify whether the
>>> snapshot works.
>>> > >>>>
>>> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com>
>>> wrote:
>>> > >>>>>
>>> > >>>>> I believe this is related to
>>> https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a
>>> fix in progress https://github.com/apache/beam/pull/8132
>>> > >>>>>
>>> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com>
>>> wrote:
>>> > >>>>>>
>>> > >>>>>> I was trying to validate a fix on the Spark runner and realized
>>> that
>>> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
>>> > >>>>>>
>>> > >>>>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
>>> > >>>>>>
>>> > >>>>>> Can somebody please take a look at why this is not been updated?
>>> > >>>>>>
>>> > >>>>>> Thanks,
>>> > >>>>>> Ismaël
>>>
>>
Re: SNAPSHOTS have not been updated since february
Posted by Lukasz Cwik <lc...@google.com>.
The permissions issue is that the credentials needed to publish to the
maven repository are only deployed on machines managed by Apache Infra. Now
that the machines have been given back to each project to manage Yifan was
investigating some other way to get the permissions on to the machine.
On Thu, Apr 18, 2019 at 10:06 AM Boyuan Zhang <bo...@google.com> wrote:
> There is a test target
> https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam,
> which builds and pushes snapshot to maven every day. Current failure is
> like, the jenkin machine cannot publish artifacts into maven owing to some
> weird permission issue. I think +Yifan Zou <yi...@google.com> is
> working on it actively.
>
> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com> wrote:
>
>> And is there a way we can detect SNAPSHOTS not been published daily in
>> the future?
>>
>> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com> wrote:
>> >
>> > Any progress on this?
>> >
>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <da...@google.com>
>> wrote:
>> > >
>> > > I made a bug for this specific issue (artifacts not publishing to the
>> Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
>> > >
>> > > While I was gathering info for the bug report I also noticed +Yifan
>> Zou has an experimental PR testing a fix:
>> https://github.com/apache/beam/pull/8148
>> > >
>> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com>
>> wrote:
>> > >>
>> > >> +Daniel Oliveira
>> > >>
>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com>
>> wrote:
>> > >>>
>> > >>> Sorry for the typo. Ideally, the snapshot publish is independent
>> from postrelease_snapshot.
>> > >>>
>> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com>
>> wrote:
>> > >>>>
>> > >>>> Hey,
>> > >>>>
>> > >>>> I'm trying to publish the artifacts by commenting "Run Gradle
>> Publish" in my PR, but there are several errors saying "cannot write
>> artifacts into dir", anyone has idea on it? Ideally, the snapshot publish
>> is dependent from postrelease_snapshot. The publish task is to build and
>> publish artifacts and the postrelease_snapshot is to verify whether the
>> snapshot works.
>> > >>>>
>> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com>
>> wrote:
>> > >>>>>
>> > >>>>> I believe this is related to
>> https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a
>> fix in progress https://github.com/apache/beam/pull/8132
>> > >>>>>
>> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com>
>> wrote:
>> > >>>>>>
>> > >>>>>> I was trying to validate a fix on the Spark runner and realized
>> that
>> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
>> > >>>>>>
>> > >>>>>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
>> > >>>>>>
>> > >>>>>> Can somebody please take a look at why this is not been updated?
>> > >>>>>>
>> > >>>>>> Thanks,
>> > >>>>>> Ismaël
>>
>
Re: SNAPSHOTS have not been updated since february
Posted by Boyuan Zhang <bo...@google.com>.
There is a test target
https://builds.apache.org/job/beam_Release_NightlySnapshot/ in beam, which
builds and pushes snapshot to maven every day. Current failure is like, the
jenkin machine cannot publish artifacts into maven owing to some
weird permission issue. I think +Yifan Zou <yi...@google.com> is
working on it actively.
On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ie...@gmail.com> wrote:
> And is there a way we can detect SNAPSHOTS not been published daily in
> the future?
>
> On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com> wrote:
> >
> > Any progress on this?
> >
> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <da...@google.com>
> wrote:
> > >
> > > I made a bug for this specific issue (artifacts not publishing to the
> Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
> > >
> > > While I was gathering info for the bug report I also noticed +Yifan
> Zou has an experimental PR testing a fix:
> https://github.com/apache/beam/pull/8148
> > >
> > > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com>
> wrote:
> > >>
> > >> +Daniel Oliveira
> > >>
> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com>
> wrote:
> > >>>
> > >>> Sorry for the typo. Ideally, the snapshot publish is independent
> from postrelease_snapshot.
> > >>>
> > >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com>
> wrote:
> > >>>>
> > >>>> Hey,
> > >>>>
> > >>>> I'm trying to publish the artifacts by commenting "Run Gradle
> Publish" in my PR, but there are several errors saying "cannot write
> artifacts into dir", anyone has idea on it? Ideally, the snapshot publish
> is dependent from postrelease_snapshot. The publish task is to build and
> publish artifacts and the postrelease_snapshot is to verify whether the
> snapshot works.
> > >>>>
> > >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com>
> wrote:
> > >>>>>
> > >>>>> I believe this is related to
> https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a
> fix in progress https://github.com/apache/beam/pull/8132
> > >>>>>
> > >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com>
> wrote:
> > >>>>>>
> > >>>>>> I was trying to validate a fix on the Spark runner and realized
> that
> > >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
> > >>>>>>
> > >>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
> > >>>>>>
> > >>>>>> Can somebody please take a look at why this is not been updated?
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>> Ismaël
>
Re: SNAPSHOTS have not been updated since february
Posted by Ismaël Mejía <ie...@gmail.com>.
And is there a way we can detect SNAPSHOTS not been published daily in
the future?
On Thu, Apr 18, 2019 at 6:37 PM Ismaël Mejía <ie...@gmail.com> wrote:
>
> Any progress on this?
>
> On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira <da...@google.com> wrote:
> >
> > I made a bug for this specific issue (artifacts not publishing to the Apache Maven repo): https://issues.apache.org/jira/browse/BEAM-6919
> >
> > While I was gathering info for the bug report I also noticed +Yifan Zou has an experimental PR testing a fix: https://github.com/apache/beam/pull/8148
> >
> > On Tue, Mar 26, 2019 at 11:42 AM Boyuan Zhang <bo...@google.com> wrote:
> >>
> >> +Daniel Oliveira
> >>
> >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <bo...@google.com> wrote:
> >>>
> >>> Sorry for the typo. Ideally, the snapshot publish is independent from postrelease_snapshot.
> >>>
> >>> On Tue, Mar 26, 2019 at 9:55 AM Boyuan Zhang <bo...@google.com> wrote:
> >>>>
> >>>> Hey,
> >>>>
> >>>> I'm trying to publish the artifacts by commenting "Run Gradle Publish" in my PR, but there are several errors saying "cannot write artifacts into dir", anyone has idea on it? Ideally, the snapshot publish is dependent from postrelease_snapshot. The publish task is to build and publish artifacts and the postrelease_snapshot is to verify whether the snapshot works.
> >>>>
> >>>> On Tue, Mar 26, 2019 at 8:45 AM Ahmet Altay <al...@google.com> wrote:
> >>>>>
> >>>>> I believe this is related to https://issues.apache.org/jira/browse/BEAM-6840 and +Boyuan Zhang has a fix in progress https://github.com/apache/beam/pull/8132
> >>>>>
> >>>>> On Tue, Mar 26, 2019 at 7:09 AM Ismaël Mejía <ie...@gmail.com> wrote:
> >>>>>>
> >>>>>> I was trying to validate a fix on the Spark runner and realized that
> >>>>>> Beam SNAPSHOTS have not been updated since February 24 !
> >>>>>>
> >>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.12.0-SNAPSHOT/
> >>>>>>
> >>>>>> Can somebody please take a look at why this is not been updated?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Ismaël