Thanks Udi for taking care of it! Please let me know if anything I can help with.
-Rui On Thu, Apr 16, 2020 at 11:32 AM Udi Meiri <[email protected]> wrote: > I did get a response but I didn't see it because I'm not subscribed to > builds@. > > This is the original announcement of the breaking change: > > https://lists.apache.org/thread.html/r00c669dd82bbde47958e81ecb330116de131d774e2d4df26a06fe92f@%3Cbuilds.apache.org%3E > > > On Thu, Apr 16, 2020 at 11:14 AM Udi Meiri <[email protected]> wrote: > >> I emailed them yes >> >> On Thu, Apr 16, 2020, 11:09 Ahmet Altay <[email protected]> wrote: >> >>> Did we end up emailing builds@ or should this be filed as a ticket to >>> infra ? >>> >>> +Rui Wang <[email protected]> -- This is preventing Rui from updating >>> the website post 2.20 release. >>> >>> On Tue, Apr 14, 2020 at 9:01 PM Kenneth Knowles <[email protected]> wrote: >>> >>>> Indeed, publish jobs have write access to things, which normal builds >>>> do not. >>>> >>>> I suggest reaching out to [email protected] >>>> >>>> Kenn >>>> >>>> On Tue, Apr 14, 2020 at 5:58 PM Udi Meiri <[email protected]> wrote: >>>> >>>>> Hey, I was looking at this today but could not figure it out. >>>>> The machines we run the publish jobs probably vary from our regular >>>>> apache-beam-testing Jenkins ones. >>>>> I tried researching all the reasons why this might be happening but >>>>> came up empty. >>>>> >>>>> On Tue, Apr 14, 2020 at 10:19 AM Kyle Weaver <[email protected]> >>>>> wrote: >>>>> >>>>>> I think Udi is fixing it. Jira: >>>>>> https://issues.apache.org/jira/browse/BEAM-9737 >>>>>> >>>>>> On Tue, Apr 14, 2020 at 1:11 PM Mikhail Gryzykhin <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Have anyone seen the following error of website publish? >>>>>>> <https://builds.apache.org/view/A-D/view/Beam/view/All/job/beam_PostCommit_Website_Publish/6018/console> >>>>>>> >>>>>>> *16:33:47* jekyll 3.6.3 | Error: Permission denied @ dir_s_mkdir - >>>>>>> /repo/build/website/generated-local-content/security >>>>>>> >>>>>>> I tried the failed target locally and it succeeded. Seems there's >>>>>>> some issue with jenkins configuration. >>>>>>> >>>>>>> Regards, >>>>>>> Mikhail. >>>>>>> >>>>>>> >>>>>>> >>>>>>>
