Your buildbot script apex.conf

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Your buildbot script apex.conf

sebb
I happened to notice that the Apex buildbot conf file has a comment
that the SingleBranchScheduler is not working.

The same problem affected a builder that I was working on; it turns
out that the Gitbox config needed to be updated. (INFRA-16554)

This has also been done for Apex, so you should now be able to switch
to using build-on-change if you want.

S.
Reply | Threaded
Open this post in threaded view
|

Re: Your buildbot script apex.conf

Vlad Rozov-2
What build is affected by the change?

Thank you,

Vlad

On 5/22/18 03:01, sebb wrote:

> I happened to notice that the Apex buildbot conf file has a comment
> that the SingleBranchScheduler is not working.
>
> The same problem affected a builder that I was working on; it turns
> out that the Gitbox config needed to be updated. (INFRA-16554)
>
> This has also been done for Apex, so you should now be able to switch
> to using build-on-change if you want.
>
> S.

Reply | Threaded
Open this post in threaded view
|

Re: Your buildbot script apex.conf

sebb
On 22 May 2018 at 15:11, Vlad Rozov <[hidden email]> wrote:
> What build is affected by the change?

See line 217 - it looks like this applies to several core builds.

> Thank you,
>
> Vlad
>
>
> On 5/22/18 03:01, sebb wrote:
>>
>> I happened to notice that the Apex buildbot conf file has a comment
>> that the SingleBranchScheduler is not working.
>>
>> The same problem affected a builder that I was working on; it turns
>> out that the Gitbox config needed to be updated. (INFRA-16554)
>>
>> This has also been done for Apex, so you should now be able to switch
>> to using build-on-change if you want.
>>
>> S.
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Your buildbot script apex.conf

Vlad Rozov-2
line 217 where and how that affects Apex in a practical way.

Thank you,

Vlad

On 5/22/18 07:19, sebb wrote:

> On 22 May 2018 at 15:11, Vlad Rozov <[hidden email]> wrote:
>> What build is affected by the change?
> See line 217 - it looks like this applies to several core builds.
>
>> Thank you,
>>
>> Vlad
>>
>>
>> On 5/22/18 03:01, sebb wrote:
>>> I happened to notice that the Apex buildbot conf file has a comment
>>> that the SingleBranchScheduler is not working.
>>>
>>> The same problem affected a builder that I was working on; it turns
>>> out that the Gitbox config needed to be updated. (INFRA-16554)
>>>
>>> This has also been done for Apex, so you should now be able to switch
>>> to using build-on-change if you want.
>>>
>>> S.
>>

Reply | Threaded
Open this post in threaded view
|

Re: Your buildbot script apex.conf

Thomas Weise-2
Administrator
Earlier it wasn't possible to build on a new commit, it currently runs
nightly whether needed or not.


On Tue, May 22, 2018 at 9:18 AM, Vlad Rozov <[hidden email]> wrote:

> line 217 where and how that affects Apex in a practical way.
>
> Thank you,
>
> Vlad
>
>
> On 5/22/18 07:19, sebb wrote:
>
>> On 22 May 2018 at 15:11, Vlad Rozov <[hidden email]> wrote:
>>
>>> What build is affected by the change?
>>>
>> See line 217 - it looks like this applies to several core builds.
>>
>> Thank you,
>>>
>>> Vlad
>>>
>>>
>>> On 5/22/18 03:01, sebb wrote:
>>>
>>>> I happened to notice that the Apex buildbot conf file has a comment
>>>> that the SingleBranchScheduler is not working.
>>>>
>>>> The same problem affected a builder that I was working on; it turns
>>>> out that the Gitbox config needed to be updated. (INFRA-16554)
>>>>
>>>> This has also been done for Apex, so you should now be able to switch
>>>> to using build-on-change if you want.
>>>>
>>>> S.
>>>>
>>>
>>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Your buildbot script apex.conf

Vlad Rozov-2
What it builds and how it is used? If we change it to build on a new
commit, what script needs to be changed?

Thank you,

Vlad

On 5/22/18 09:23, Thomas Weise wrote:

> Earlier it wasn't possible to build on a new commit, it currently runs
> nightly whether needed or not.
>
>
> On Tue, May 22, 2018 at 9:18 AM, Vlad Rozov <[hidden email]> wrote:
>
>> line 217 where and how that affects Apex in a practical way.
>>
>> Thank you,
>>
>> Vlad
>>
>>
>> On 5/22/18 07:19, sebb wrote:
>>
>>> On 22 May 2018 at 15:11, Vlad Rozov <[hidden email]> wrote:
>>>
>>>> What build is affected by the change?
>>>>
>>> See line 217 - it looks like this applies to several core builds.
>>>
>>> Thank you,
>>>> Vlad
>>>>
>>>>
>>>> On 5/22/18 03:01, sebb wrote:
>>>>
>>>>> I happened to notice that the Apex buildbot conf file has a comment
>>>>> that the SingleBranchScheduler is not working.
>>>>>
>>>>> The same problem affected a builder that I was working on; it turns
>>>>> out that the Gitbox config needed to be updated. (INFRA-16554)
>>>>>
>>>>> This has also been done for Apex, so you should now be able to switch
>>>>> to using build-on-change if you want.
>>>>>
>>>>> S.
>>>>>
>>>>

Reply | Threaded
Open this post in threaded view
|

Re: Your buildbot script apex.conf

sebb
In reply to this post by Vlad Rozov-2
On 22 May 2018 at 17:18, Vlad Rozov <[hidden email]> wrote:
> line 217 where

In the apex.conf buildbot file:

https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/apex.conf

> and how that affects Apex in a practical way.

Apex should now be able to switch to using build-on-change.
(At present it uses a nightly - timed - build.)

If you want further information I suggest you ask some of the
committers who have updated the file.

> Thank you,
>
> Vlad
>
>
> On 5/22/18 07:19, sebb wrote:
>>
>> On 22 May 2018 at 15:11, Vlad Rozov <[hidden email]> wrote:
>>>
>>> What build is affected by the change?
>>
>> See line 217 - it looks like this applies to several core builds.
>>
>>> Thank you,
>>>
>>> Vlad
>>>
>>>
>>> On 5/22/18 03:01, sebb wrote:
>>>>
>>>> I happened to notice that the Apex buildbot conf file has a comment
>>>> that the SingleBranchScheduler is not working.
>>>>
>>>> The same problem affected a builder that I was working on; it turns
>>>> out that the Gitbox config needed to be updated. (INFRA-16554)
>>>>
>>>> This has also been done for Apex, so you should now be able to switch
>>>> to using build-on-change if you want.
>>>>
>>>> S.
>>>
>>>
>