I was just alerted to the fact that Jenkins was throwing proxy errors via
Apache. On the hunch that the JAR had got itself wedged, I gave the box an
"/etc/init.d/jenkins try-restart". Seems fine now, but do shout if there's
any lingering weirdness.
There something wrong with "theforeman-bot", I've just created a new PR[1]
and it hasn't come along and done it's thing
Posting [test] seemed to work, but it hasn't added any labels.
···
On Mon, Feb 15, 2016 at 9:13 PM, Greg Sutcliffe wrote:
Hi all,
I was just alerted to the fact that Jenkins was throwing proxy errors via
Apache. On the hunch that the JAR had got itself wedged, I gave the box an
"/etc/init.d/jenkins try-restart". Seems fine now, but do shout if there’s
any lingering weirdness.
When a PR is opened, a small number of webhook requests from GitHub to
our prprocessor
(PrProcessor - Foreman) are
failing as the GitHub API is returning a 404 when it tries to retrieve
the commit list for the new PR.
I re-ran the failed hook and it labelled the PR (committer can do this
manually, nothing special here).
···
On 15/02/16 23:26, Sean O'Keeffe wrote:
> Greg,
>
> There something wrong with "theforeman-bot", I've just created a new
> PR[1] and it hasn't come along and done it's thing :)
> Posting [test] seemed to work, but it hasn't added any labels.
>
> [1] - https://github.com/theforeman/foreman/pull/3189
The fix for this is live, please let me know if you see it occur again.
···
On 16/02/16 08:11, Dominic Cleal wrote:
> On 15/02/16 23:26, Sean O'Keeffe wrote:
>> Greg,
>>
>> There something wrong with "theforeman-bot", I've just created a new
>> PR[1] and it hasn't come along and done it's thing :)
>> Posting [test] seemed to work, but it hasn't added any labels.
>>
>> [1] - https://github.com/theforeman/foreman/pull/3189
>
> When a PR is opened, a small number of webhook requests from GitHub to
> our prprocessor
> (http://projects.theforeman.org/projects/foreman/wiki/PrProcessor) are
> failing as the GitHub API is returning a 404 when it tries to retrieve
> the commit list for the new PR.
>
> I re-ran the failed hook and it labelled the PR (committer can do this
> manually, nothing special here).
>
> I've filed the bug as https://github.com/theforeman/prprocessor/issues/33.