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 <boyu...@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 <yifan...@google.com> is >> working on it actively. >> >> On Thu, Apr 18, 2019 at 9:44 AM Ismaël Mejía <ieme...@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 <ieme...@gmail.com> wrote: >>> > >>> > Any progress on this? >>> > >>> > On Wed, Mar 27, 2019 at 5:38 AM Daniel Oliveira < >>> danolive...@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 <boyu...@google.com> >>> wrote: >>> > >> >>> > >> +Daniel Oliveira >>> > >> >>> > >> On Tue, Mar 26, 2019 at 9:57 AM Boyuan Zhang <boyu...@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 <boyu...@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 <ieme...@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 >>> >>
