PCRE2 infrastructure has moved

[Philip Hazel]

Hi,

I sent the message below on December 11, and as I hadn't had a reply, I
checked on your buildfarm for PCRE2. It doesn't seem to have done anything
since July last year, which is odd, because there has been plenty of
activity since then.

Regards,
Philip


On Sat, 11 Dec 2021 at 09:45, Philip Hazel <philip.hazel at gmail.com> wrote:

> Hi,
>
> I have at last got round to dealing with this. I think I have followed
> your instructions for setting up the webhook in GitHub, and the personal
> access token is
>
> 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
>
> I hope I've done it right!
>
> Regards,
> Philip
>
>
> On Thu, 2 Sept 2021 at 09:48, Dagobert Michelsen <dam at opencsw.org> wrote:
>
>> Hi Philip,
>>
>> Am 27.08.2021 um 17:11 schrieb Philip Hazel <philip.hazel at gmail.com>:
>> > For some time now the OpenCSW project Buildbot has been (very usefully!
>> thank you) running builds of PCRE and PCRE2. The original PCRE (PCRE1) is
>> now at end of life and no more changes are planned, so there is no point in
>> continuing with those builds. The PCRE2 project has just moved from
>> vcs.exim.org to a new home on GitHub (
>> https://github.com/PhilipHazel/pcre2) and that is where development will
>> now happen. I'd be grateful if you could update your Waterfall
>> configuration to pull the sources from the new repository. The old one will
>> no longer change, and at some point soon it will disappear. Note also that
>> my primary email has moved to this gmail account.
>>
>> Sure. There is also the possibility to integrate the CI more tightly in
>> the GitHub build process: the build can be triggered via GitHub push
>> and pull requests. For this to work it would be nice if you could set
>> up a hook in the GitHub pcre2 project:
>>
>> Payload URL:
>> http://github:buildbotcsw@buildbot.opencsw.org:8010/change_hook/github
>> Content Type: application/json
>> Secret: c0b145501adb70e910cd384f2c4034e9
>> Events: pull request, push
>>
>> Then either generate a personal access token with the scope „repo:status“
>> or add
>> @buildbot-opencsw to the collectd-project as collaborator (token is
>> probably more secure).
>> Please send me the token so I can configure it properly in our buildbot.
>>
>> After that hopefully pull requests will be automatically checked on
>> Solaris and status
>> easily visible directly in GitHub next to the commit.
>>
>> Of course I can also stick to the existing polling method if you think
>> this is
>> not helpfull or too much work :-)
>>
>>
>> Best regards
>>
>>   — Dago
>>
>>
>> --
>> "You don't become great by trying to be great, you become great by
>> wanting to do something,
>> and then doing it so hard that you become great in the process." - xkcd
>> #896
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/buildfarm/attachments/20220114/5667fa41/attachment.html>