Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

Hi all,

I've noticed links from Jira issues to related Github PRs have not been
generated the past few days. Does anyone know why?

Kyle

Re: Jira PR links not being generated?

[Udi Meiri <eh...@google.com>]

I think it's a recent change. The page https://s.apache.org/asfyaml-notify
was updated last week but I didn't see an announcement.

On Mon, Apr 27, 2020 at 3:34 PM Kyle Weaver <kc...@google.com> wrote:

> I made a PR for this, though I still haven't found sufficient explanation
> as to why we did not need this file last week, and now we do this week.
> https://github.com/apache/beam/pull/11541
>
> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>
>> We had such a file for a short while but it was removed:
>> https://github.com/apache/beam/pull/10645
>> I don't believe it contained any PR link settings though
>> +Pablo Estrada <pa...@google.com>
>>
>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
>>> it looks like this is how things will be done from now on. Which raises the
>>> question, does anyone know how Beam managed these settings before? Or were
>>> there previously no project-level controls?
>>>
>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and found
>>>> [1] (among others). Looks like we may need to add a .asf.yaml file [2]. I
>>>> guess infra must have changed this recently without us picking up on it?
>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>
>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>> [2]
>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>
>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>> wrote:
>>>>
>>>>> I suggest filing an issue with INFRA.
>>>>>
>>>>> Kenn
>>>>>
>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I've noticed links from Jira issues to related Github PRs have not
>>>>>> been generated the past few days. Does anyone know why?
>>>>>>
>>>>>> Kyle
>>>>>>
>>>>>

Re: Jira PR links not being generated?

[Ahmet Altay <al...@google.com>]

Thank you!

On Wed, Apr 29, 2020 at 3:23 PM Kyle Weaver <kc...@google.com> wrote:

> Added a comment on https://issues.apache.org/jira/browse/INFRA-19967
>
> On Wed, Apr 29, 2020 at 5:57 PM Ahmet Altay <al...@google.com> wrote:
>
>> Would it be worth filing this as an infra ticket?
>>
>> On Mon, Apr 27, 2020 at 4:29 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> Slight correction.. Jira to Github links are back. Github to Jira links
>>> (which were only recently added) are not being added.
>>>
>>> On Mon, Apr 27, 2020 at 7:20 PM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> Well, links seem to work again at least.
>>>>
>>>> On Mon, Apr 27, 2020 at 7:10 PM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> Thanks Pablo. I merged it. Everyone should keep an eye on Jira and the
>>>>> mailing lists to make sure I didn't accidentally mess something up.
>>>>>
>>>>> On Mon, Apr 27, 2020 at 7:01 PM Pablo Estrada <pa...@google.com>
>>>>> wrote:
>>>>>
>>>>>> I added it to add a list of non-committers that can trigger tests
>>>>>> from PR. I added like 100+, so they asked us to not do that : )
>>>>>> I've approved your PR, Kyle.
>>>>>>
>>>>>> On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I made a PR for this, though I still haven't found sufficient
>>>>>>> explanation as to why we did not need this file last week, and now we do
>>>>>>> this week. https://github.com/apache/beam/pull/11541
>>>>>>>
>>>>>>> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>>>>>>>
>>>>>>>> We had such a file for a short while but it was removed:
>>>>>>>> https://github.com/apache/beam/pull/10645
>>>>>>>> I don't believe it contained any PR link settings though
>>>>>>>> +Pablo Estrada <pa...@google.com>
>>>>>>>>
>>>>>>>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I went ahead and filed
>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-9833 since it looks
>>>>>>>>> like this is how things will be done from now on. Which raises the
>>>>>>>>> question, does anyone know how Beam managed these settings before? Or were
>>>>>>>>> there previously no project-level controls?
>>>>>>>>>
>>>>>>>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and
>>>>>>>>>> found [1] (among others). Looks like we may need to add a .asf.yaml file
>>>>>>>>>> [2]. I guess infra must have changed this recently without us picking up on
>>>>>>>>>> it?
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>>>>>>>
>>>>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>>>>>>>> [2]
>>>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>>>>>>>
>>>>>>>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> I suggest filing an issue with INFRA.
>>>>>>>>>>>
>>>>>>>>>>> Kenn
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <
>>>>>>>>>>> kcweaver@google.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>> I've noticed links from Jira issues to related Github PRs have
>>>>>>>>>>>> not been generated the past few days. Does anyone know why?
>>>>>>>>>>>>
>>>>>>>>>>>> Kyle
>>>>>>>>>>>>
>>>>>>>>>>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

Added a comment on https://issues.apache.org/jira/browse/INFRA-19967

On Wed, Apr 29, 2020 at 5:57 PM Ahmet Altay <al...@google.com> wrote:

> Would it be worth filing this as an infra ticket?
>
> On Mon, Apr 27, 2020 at 4:29 PM Kyle Weaver <kc...@google.com> wrote:
>
>> Slight correction.. Jira to Github links are back. Github to Jira links
>> (which were only recently added) are not being added.
>>
>> On Mon, Apr 27, 2020 at 7:20 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> Well, links seem to work again at least.
>>>
>>> On Mon, Apr 27, 2020 at 7:10 PM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> Thanks Pablo. I merged it. Everyone should keep an eye on Jira and the
>>>> mailing lists to make sure I didn't accidentally mess something up.
>>>>
>>>> On Mon, Apr 27, 2020 at 7:01 PM Pablo Estrada <pa...@google.com>
>>>> wrote:
>>>>
>>>>> I added it to add a list of non-committers that can trigger tests from
>>>>> PR. I added like 100+, so they asked us to not do that : )
>>>>> I've approved your PR, Kyle.
>>>>>
>>>>> On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com>
>>>>> wrote:
>>>>>
>>>>>> I made a PR for this, though I still haven't found sufficient
>>>>>> explanation as to why we did not need this file last week, and now we do
>>>>>> this week. https://github.com/apache/beam/pull/11541
>>>>>>
>>>>>> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>>>>>>
>>>>>>> We had such a file for a short while but it was removed:
>>>>>>> https://github.com/apache/beam/pull/10645
>>>>>>> I don't believe it contained any PR link settings though
>>>>>>> +Pablo Estrada <pa...@google.com>
>>>>>>>
>>>>>>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I went ahead and filed
>>>>>>>> https://issues.apache.org/jira/browse/BEAM-9833 since it looks
>>>>>>>> like this is how things will be done from now on. Which raises the
>>>>>>>> question, does anyone know how Beam managed these settings before? Or were
>>>>>>>> there previously no project-level controls?
>>>>>>>>
>>>>>>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and
>>>>>>>>> found [1] (among others). Looks like we may need to add a .asf.yaml file
>>>>>>>>> [2]. I guess infra must have changed this recently without us picking up on
>>>>>>>>> it?
>>>>>>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>>>>>>
>>>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>>>>>>> [2]
>>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>>>>>>
>>>>>>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I suggest filing an issue with INFRA.
>>>>>>>>>>
>>>>>>>>>> Kenn
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> I've noticed links from Jira issues to related Github PRs have
>>>>>>>>>>> not been generated the past few days. Does anyone know why?
>>>>>>>>>>>
>>>>>>>>>>> Kyle
>>>>>>>>>>>
>>>>>>>>>>

Re: Jira PR links not being generated?

[Ahmet Altay <al...@google.com>]

Would it be worth filing this as an infra ticket?

On Mon, Apr 27, 2020 at 4:29 PM Kyle Weaver <kc...@google.com> wrote:

> Slight correction.. Jira to Github links are back. Github to Jira links
> (which were only recently added) are not being added.
>
> On Mon, Apr 27, 2020 at 7:20 PM Kyle Weaver <kc...@google.com> wrote:
>
>> Well, links seem to work again at least.
>>
>> On Mon, Apr 27, 2020 at 7:10 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> Thanks Pablo. I merged it. Everyone should keep an eye on Jira and the
>>> mailing lists to make sure I didn't accidentally mess something up.
>>>
>>> On Mon, Apr 27, 2020 at 7:01 PM Pablo Estrada <pa...@google.com>
>>> wrote:
>>>
>>>> I added it to add a list of non-committers that can trigger tests from
>>>> PR. I added like 100+, so they asked us to not do that : )
>>>> I've approved your PR, Kyle.
>>>>
>>>> On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> I made a PR for this, though I still haven't found sufficient
>>>>> explanation as to why we did not need this file last week, and now we do
>>>>> this week. https://github.com/apache/beam/pull/11541
>>>>>
>>>>> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>>>>>
>>>>>> We had such a file for a short while but it was removed:
>>>>>> https://github.com/apache/beam/pull/10645
>>>>>> I don't believe it contained any PR link settings though
>>>>>> +Pablo Estrada <pa...@google.com>
>>>>>>
>>>>>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I went ahead and filed
>>>>>>> https://issues.apache.org/jira/browse/BEAM-9833 since it looks like
>>>>>>> this is how things will be done from now on. Which raises the question,
>>>>>>> does anyone know how Beam managed these settings before? Or were there
>>>>>>> previously no project-level controls?
>>>>>>>
>>>>>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and
>>>>>>>> found [1] (among others). Looks like we may need to add a .asf.yaml file
>>>>>>>> [2]. I guess infra must have changed this recently without us picking up on
>>>>>>>> it?
>>>>>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>>>>>
>>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>>>>>> [2]
>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>>>>>
>>>>>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I suggest filing an issue with INFRA.
>>>>>>>>>
>>>>>>>>> Kenn
>>>>>>>>>
>>>>>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> I've noticed links from Jira issues to related Github PRs have
>>>>>>>>>> not been generated the past few days. Does anyone know why?
>>>>>>>>>>
>>>>>>>>>> Kyle
>>>>>>>>>>
>>>>>>>>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

Slight correction.. Jira to Github links are back. Github to Jira links
(which were only recently added) are not being added.

On Mon, Apr 27, 2020 at 7:20 PM Kyle Weaver <kc...@google.com> wrote:

> Well, links seem to work again at least.
>
> On Mon, Apr 27, 2020 at 7:10 PM Kyle Weaver <kc...@google.com> wrote:
>
>> Thanks Pablo. I merged it. Everyone should keep an eye on Jira and the
>> mailing lists to make sure I didn't accidentally mess something up.
>>
>> On Mon, Apr 27, 2020 at 7:01 PM Pablo Estrada <pa...@google.com> wrote:
>>
>>> I added it to add a list of non-committers that can trigger tests from
>>> PR. I added like 100+, so they asked us to not do that : )
>>> I've approved your PR, Kyle.
>>>
>>> On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> I made a PR for this, though I still haven't found sufficient
>>>> explanation as to why we did not need this file last week, and now we do
>>>> this week. https://github.com/apache/beam/pull/11541
>>>>
>>>> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>>>>
>>>>> We had such a file for a short while but it was removed:
>>>>> https://github.com/apache/beam/pull/10645
>>>>> I don't believe it contained any PR link settings though
>>>>> +Pablo Estrada <pa...@google.com>
>>>>>
>>>>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com>
>>>>> wrote:
>>>>>
>>>>>> I went ahead and filed
>>>>>> https://issues.apache.org/jira/browse/BEAM-9833 since it looks like
>>>>>> this is how things will be done from now on. Which raises the question,
>>>>>> does anyone know how Beam managed these settings before? Or were there
>>>>>> previously no project-level controls?
>>>>>>
>>>>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and
>>>>>>> found [1] (among others). Looks like we may need to add a .asf.yaml file
>>>>>>> [2]. I guess infra must have changed this recently without us picking up on
>>>>>>> it?
>>>>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>>>>
>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>>>>> [2]
>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>>>>
>>>>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I suggest filing an issue with INFRA.
>>>>>>>>
>>>>>>>> Kenn
>>>>>>>>
>>>>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> I've noticed links from Jira issues to related Github PRs have not
>>>>>>>>> been generated the past few days. Does anyone know why?
>>>>>>>>>
>>>>>>>>> Kyle
>>>>>>>>>
>>>>>>>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

Well, links seem to work again at least.

On Mon, Apr 27, 2020 at 7:10 PM Kyle Weaver <kc...@google.com> wrote:

> Thanks Pablo. I merged it. Everyone should keep an eye on Jira and the
> mailing lists to make sure I didn't accidentally mess something up.
>
> On Mon, Apr 27, 2020 at 7:01 PM Pablo Estrada <pa...@google.com> wrote:
>
>> I added it to add a list of non-committers that can trigger tests from
>> PR. I added like 100+, so they asked us to not do that : )
>> I've approved your PR, Kyle.
>>
>> On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> I made a PR for this, though I still haven't found sufficient
>>> explanation as to why we did not need this file last week, and now we do
>>> this week. https://github.com/apache/beam/pull/11541
>>>
>>> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>>>
>>>> We had such a file for a short while but it was removed:
>>>> https://github.com/apache/beam/pull/10645
>>>> I don't believe it contained any PR link settings though
>>>> +Pablo Estrada <pa...@google.com>
>>>>
>>>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
>>>>> it looks like this is how things will be done from now on. Which raises the
>>>>> question, does anyone know how Beam managed these settings before? Or were
>>>>> there previously no project-level controls?
>>>>>
>>>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and
>>>>>> found [1] (among others). Looks like we may need to add a .asf.yaml file
>>>>>> [2]. I guess infra must have changed this recently without us picking up on
>>>>>> it?
>>>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>>>
>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>>>> [2]
>>>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>>>
>>>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I suggest filing an issue with INFRA.
>>>>>>>
>>>>>>> Kenn
>>>>>>>
>>>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I've noticed links from Jira issues to related Github PRs have not
>>>>>>>> been generated the past few days. Does anyone know why?
>>>>>>>>
>>>>>>>> Kyle
>>>>>>>>
>>>>>>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

Thanks Pablo. I merged it. Everyone should keep an eye on Jira and the
mailing lists to make sure I didn't accidentally mess something up.

On Mon, Apr 27, 2020 at 7:01 PM Pablo Estrada <pa...@google.com> wrote:

> I added it to add a list of non-committers that can trigger tests from PR.
> I added like 100+, so they asked us to not do that : )
> I've approved your PR, Kyle.
>
> On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com> wrote:
>
>> I made a PR for this, though I still haven't found sufficient explanation
>> as to why we did not need this file last week, and now we do this week.
>> https://github.com/apache/beam/pull/11541
>>
>> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>>
>>> We had such a file for a short while but it was removed:
>>> https://github.com/apache/beam/pull/10645
>>> I don't believe it contained any PR link settings though
>>> +Pablo Estrada <pa...@google.com>
>>>
>>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
>>>> it looks like this is how things will be done from now on. Which raises the
>>>> question, does anyone know how Beam managed these settings before? Or were
>>>> there previously no project-level controls?
>>>>
>>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and
>>>>> found [1] (among others). Looks like we may need to add a .asf.yaml file
>>>>> [2]. I guess infra must have changed this recently without us picking up on
>>>>> it?
>>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>>> [2]
>>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>>
>>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I suggest filing an issue with INFRA.
>>>>>>
>>>>>> Kenn
>>>>>>
>>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I've noticed links from Jira issues to related Github PRs have not
>>>>>>> been generated the past few days. Does anyone know why?
>>>>>>>
>>>>>>> Kyle
>>>>>>>
>>>>>>

Re: Jira PR links not being generated?

[Pablo Estrada <pa...@google.com>]

I added it to add a list of non-committers that can trigger tests from PR.
I added like 100+, so they asked us to not do that : )
I've approved your PR, Kyle.

On Mon, Apr 27, 2020 at 3:33 PM Kyle Weaver <kc...@google.com> wrote:

> I made a PR for this, though I still haven't found sufficient explanation
> as to why we did not need this file last week, and now we do this week.
> https://github.com/apache/beam/pull/11541
>
> On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:
>
>> We had such a file for a short while but it was removed:
>> https://github.com/apache/beam/pull/10645
>> I don't believe it contained any PR link settings though
>> +Pablo Estrada <pa...@google.com>
>>
>> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
>>> it looks like this is how things will be done from now on. Which raises the
>>> question, does anyone know how Beam managed these settings before? Or were
>>> there previously no project-level controls?
>>>
>>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> Thanks for the pointer Kenn. I searched existing INFRA issues and found
>>>> [1] (among others). Looks like we may need to add a .asf.yaml file [2]. I
>>>> guess infra must have changed this recently without us picking up on it?
>>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>>
>>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>>> [2]
>>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>>
>>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org>
>>>> wrote:
>>>>
>>>>> I suggest filing an issue with INFRA.
>>>>>
>>>>> Kenn
>>>>>
>>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I've noticed links from Jira issues to related Github PRs have not
>>>>>> been generated the past few days. Does anyone know why?
>>>>>>
>>>>>> Kyle
>>>>>>
>>>>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

I made a PR for this, though I still haven't found sufficient explanation
as to why we did not need this file last week, and now we do this week.
https://github.com/apache/beam/pull/11541

On Mon, Apr 27, 2020 at 6:24 PM Udi Meiri <eh...@google.com> wrote:

> We had such a file for a short while but it was removed:
> https://github.com/apache/beam/pull/10645
> I don't believe it contained any PR link settings though
> +Pablo Estrada <pa...@google.com>
>
> On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com> wrote:
>
>> I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
>> it looks like this is how things will be done from now on. Which raises the
>> question, does anyone know how Beam managed these settings before? Or were
>> there previously no project-level controls?
>>
>> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> Thanks for the pointer Kenn. I searched existing INFRA issues and found
>>> [1] (among others). Looks like we may need to add a .asf.yaml file [2]. I
>>> guess infra must have changed this recently without us picking up on it?
>>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>>> [2]
>>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>>
>>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org> wrote:
>>>
>>>> I suggest filing an issue with INFRA.
>>>>
>>>> Kenn
>>>>
>>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I've noticed links from Jira issues to related Github PRs have not
>>>>> been generated the past few days. Does anyone know why?
>>>>>
>>>>> Kyle
>>>>>
>>>>

Re: Jira PR links not being generated?

[Udi Meiri <eh...@google.com>]

We had such a file for a short while but it was removed:
https://github.com/apache/beam/pull/10645
I don't believe it contained any PR link settings though
+Pablo Estrada <pa...@google.com>

On Mon, Apr 27, 2020 at 1:56 PM Kyle Weaver <kc...@google.com> wrote:

> I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
> it looks like this is how things will be done from now on. Which raises the
> question, does anyone know how Beam managed these settings before? Or were
> there previously no project-level controls?
>
> On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com> wrote:
>
>> Thanks for the pointer Kenn. I searched existing INFRA issues and found
>> [1] (among others). Looks like we may need to add a .asf.yaml file [2]. I
>> guess infra must have changed this recently without us picking up on it?
>> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-20171
>> [2]
>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>>
>> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org> wrote:
>>
>>> I suggest filing an issue with INFRA.
>>>
>>> Kenn
>>>
>>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've noticed links from Jira issues to related Github PRs have not been
>>>> generated the past few days. Does anyone know why?
>>>>
>>>> Kyle
>>>>
>>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

I went ahead and filed https://issues.apache.org/jira/browse/BEAM-9833 since
it looks like this is how things will be done from now on. Which raises the
question, does anyone know how Beam managed these settings before? Or were
there previously no project-level controls?

On Mon, Apr 27, 2020 at 4:39 PM Kyle Weaver <kc...@google.com> wrote:

> Thanks for the pointer Kenn. I searched existing INFRA issues and found
> [1] (among others). Looks like we may need to add a .asf.yaml file [2]. I
> guess infra must have changed this recently without us picking up on it?
> <https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>
>
> [1] https://issues.apache.org/jira/browse/INFRA-20171
> [2]
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
>
> On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org> wrote:
>
>> I suggest filing an issue with INFRA.
>>
>> Kenn
>>
>> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com> wrote:
>>
>>> Hi all,
>>>
>>> I've noticed links from Jira issues to related Github PRs have not been
>>> generated the past few days. Does anyone know why?
>>>
>>> Kyle
>>>
>>

Re: Jira PR links not being generated?

[Kyle Weaver <kc...@google.com>]

Thanks for the pointer Kenn. I searched existing INFRA issues and found
[1] (among others). Looks like we may need to add a .asf.yaml file [2]. I
guess infra must have changed this recently without us picking up on it?
<https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories>

[1] https://issues.apache.org/jira/browse/INFRA-20171
[2]
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories

On Mon, Apr 27, 2020 at 4:25 PM Kenneth Knowles <ke...@apache.org> wrote:

> I suggest filing an issue with INFRA.
>
> Kenn
>
> On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com> wrote:
>
>> Hi all,
>>
>> I've noticed links from Jira issues to related Github PRs have not been
>> generated the past few days. Does anyone know why?
>>
>> Kyle
>>
>

Re: Jira PR links not being generated?

[Kenneth Knowles <ke...@apache.org>]

I suggest filing an issue with INFRA.

Kenn

On Fri, Apr 24, 2020 at 10:12 AM Kyle Weaver <kc...@google.com> wrote:

> Hi all,
>
> I've noticed links from Jira issues to related Github PRs have not been
> generated the past few days. Does anyone know why?
>
> Kyle
>