On 23 May 2018 at 22:47, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> great, thank you Sebb!
>
> the last question is:

I think this is a separate question which needs a new thread.

> do we try to import Attic svn history (which may be
> complex, as seen with projects.apache.org [1]) or do we just get the current
> state?
>
> For Attic, history does not seem absolutely necessary
>
> Do we launch Git + separate branch for output with just the current state?
>
> Regards,
>
> Hervé
>
> [1] https://issues.apache.org/jira/browse/INFRA-16355
>
> Le mardi 22 mai 2018, 17:37:20 CEST sebb a écrit :
>> Finally managed to get the GitBox attic-test repo working with Buildbot.
>>
>> The sample runs are at:
>>
>> [1] https://ci.apache.org/builders/attic-test-alt
>>
>> (Run 40 onwards represents the working setup; earlier runs had various
>> failures)
>>
>> The source data is at:
>>
>> [2] https://github.com/apache/attic-test
>>
>> If you commit an edit to the GitHub master branch, you should see a
>> build at [1].
>> Also the asf-site branch at [2] should be updated.
>>
>> The dummy build script always updates date.txt and copies any files under
>> src/
>>
>> The resulting files are not deployed anywhere so have to be viewed in
>> GitHub or GitBox.
>>
>> Feel free to try it out.
>>
>> ====
>>
>> The config is at:
>>
>> [3]
>> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaste
>> r/master1/projects/attic-site.conf
>>
>> This needs tidying up when the PoC is chosen.
>> It will also need to be updated to add the real GitBox repo when that
>> move happens.
>>
>> ====
>>
>> FTR, this took a long while because of various issues:
>> - Buildbot config update scanner was broken, so could not test changes
>> - Buildbot was not set up to allow commit to GitBox
>> - The asf-test repo was not set up to send changes to Buildbot
>>
>> These have all been fixed in conjunction with Infra.
>>
>> I hope this means that migration of the main site to GitBox will be a
>> bit smoother.
>> Though I'm sure there will be some other minor issues to resolve.
>>
>> S.
>
>
>
>

Reply via email to