www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Wu <mchl....@gmail.com>
Subject Re: [BuildBot Registry] Could anyone of infras team please kindly help setup the CI for incubator-eagle?
Date Fri, 20 May 2016 08:36:44 GMT
Paste the ticket link of this requirement for reference:
https://issues.apache.org/jira/browse/INFRA-11738

Details could also be found in previous emails of this thread. Thanks.



On Fri, May 20, 2016 at 4:32 PM, Michael Wu <mchl.wu5@gmail.com> wrote:

> Hi guys,
>
> Could anyone from builds and infra group kindly help on this requirement?
> If it's a tricky job, is it possible just let me know what information of
> the project I shall provide or what step I shall follow?
>
> Really appreciated!
>
> Michael
>
> On Wed, May 18, 2016 at 10:14 AM, Michael Wu <mchl.wu5@gmail.com> wrote:
>
>> Hi Gav,
>>
>> Is there any progress we get on this, please? We're eagerly waiting for
>> response, what further we can provide, please feel free to let me know.
>> Thanks!
>>
>> Michael
>>
>> On Fri, May 13, 2016 at 5:08 PM, Michael Wu <mchl.wu5@gmail.com> wrote:
>>
>>> Gav,
>>>
>>> Really appreciate your response. Now that some information of the
>>> project has been updated, I'd like to list them here for your reference
>>> (anything missed for you to continue, please do let me know). Also, I've
>>> got some questions for the working flow of this build service, I'll list
>>> them at the bottom, it'll be appreciated if you are convenient to give some
>>> comments.
>>>
>>> Project information:
>>> ***************************
>>> *Project name:*                                   incubator-eagle
>>> *Project github repo:*
>>> https://github.com/apache/incubator-eagle
>>> *Expected access url after builds:*
>>> https://ci.apache.org/projects/eagle/
>>> *Documentation branch:*                   master
>>> *Containing folder in project:*           incubator-eagle/eagle-docs/
>>> *Site content generating tool:*          MkDocs (http://www.mkdocs.org/)
>>> ***************************
>>>
>>> Remaining questions:
>>> 1. After you setup auto-jobs for building this project, will we get the
>>> access to manage the job by ourselves as future needs come across? E.g.
>>> trigger new builds, modify configuration of the job, etc?
>>> 2. Is there any guide materials for manipulating the builds as a
>>> maintainer?
>>> 3. Suppose we have the files in eagle-docs evolve as the version of the
>>> project moves forward, what shall be the mechanism for keeping different
>>> version docs accessable? Could it be adding version-info in the uri, i.e.
>>> ci.apache.org/project/eagle/*v1.0* (maybe some other formats)?
>>>
>>>
>>> Thank you very much!
>>>
>>> Best Regards,
>>> Michael
>>>
>>> On Fri, May 13, 2016 at 3:39 PM, Gav <gmcdonald@apache.org> wrote:
>>>
>>>> I will work on it tomorrow morning
>>>>
>>>> Gav...
>>>>
>>>> On Thu, May 12, 2016 at 10:24 PM, Michael Wu <mchl.wu5@gmail.com>
>>>> wrote:
>>>>
>>>> > Hi Builds Team,
>>>> >
>>>> > I'm a contributor of incubator-eagle group, we met the needs to
>>>> > ask Buildbot to build and test our website branch and have available
>>>> for
>>>> > display at ci.apache.org/projects/eagle/, could anyone kindly help
>>>> guide
>>>> > me
>>>> > what steps we should follow to make it, please?
>>>> >
>>>> > A jira ticket for this task was filed on Api. 25th, and we're still
>>>> eagerly
>>>> > waiting for further instructions. The jira ticket is at:
>>>> > https://issues.apache.org/jira/browse/INFRA-11738
>>>> >
>>>> > It'll be highly appreciated if anyone can help us on it.
>>>> >
>>>> > Best regards,
>>>> > Michael
>>>> >
>>>>
>>>
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message