Hi all,
In order to avoid unacceptable load on the CI infra during our planned bug
day on Monday[1], the PR scanner will be switched to manual-only mode[2]
for the whole day.
As such, you'll need to comment [test] to get tests to run even if you
normal are in the testing whitelist. Please only do this once a PR is
ready to go from a review perspective - testing many fast iterations of a
branch is what causes the load.
On Tuesday the change will be reverted and we'll return to normal.
See you all on Monday for the bug day!
Thanks
Greg
[1] https://groups.google.com/d/topic/foreman-users/WVLNY3Cq7VA/discussion
[2] https://github.com/theforeman/foreman-infra/pull/215
Just to emphasize that for today Pull requests will appear 'green' even
if jenkins has not run. DO NOT MERGE just because a PR is green.
Here is what a tested PR looks like:
http://imgur.com/wzXgSvOl.png
Notice the TWO green check marks. One green check mark means it has not
been tested.
-Justin
···
On 02/26/2016 11:36 AM, Greg Sutcliffe wrote:
> Hi all,
>
> In order to avoid unacceptable load on the CI infra during our planned
> bug day on Monday[1], the PR scanner will be switched to manual-only
> mode[2] for the whole day.
>
> As such, you'll need to comment [test] to get tests to run *even* if
> you normal are in the testing whitelist. Please *only* do this once a
> PR is ready to go from a review perspective - testing many fast
> iterations of a branch is what causes the load.
>
> On Tuesday the change will be reverted and we'll return to normal.
>
> See you all on Monday for the bug day!
>
> Thanks
> Greg
>
> [1] https://groups.google.com/d/topic/foreman-users/WVLNY3Cq7VA/discussion
> [2] https://github.com/theforeman/foreman-infra/pull/215
> --
> You received this message because you are subscribed to the Google
> Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-dev+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
> Hi all,
>
> In order to avoid unacceptable load on the CI infra during our planned bug
> day on Monday[1], the PR scanner will be switched to manual-only mode[2]
> for the whole day.
>
> As such, you'll need to comment [test] to get tests to run even if you
> normal are in the testing whitelist. Please only do this once a PR is
> ready to go from a review perspective - testing many fast iterations of a
> branch is what causes the load.
>
> On Tuesday the change will be reverted and we'll return to normal.
It seems still to be off?
···
On 26.02.2016 17:36, Greg Sutcliffe wrote:
See you all on Monday for the bug day!
Thanks
Greg
[1] https://groups.google.com/d/topic/foreman-users/WVLNY3Cq7VA/discussion
[2] https://github.com/theforeman/foreman-infra/pull/215
–
Daniel Helgenberger (helge000)
daniel@helgenberger.net
I re-enabled it late on Monday. What's not working?
···
On 02/03/16 10:15, Daniel Helgenberger wrote:
>
>
> On 26.02.2016 17:36, Greg Sutcliffe wrote:
>> Hi all,
>>
>> In order to avoid unacceptable load on the CI infra during our planned bug
>> day on Monday[1], the PR scanner will be switched to manual-only mode[2]
>> for the whole day.
>>
>> As such, you'll need to comment [test] to get tests to run *even* if you
>> normal are in the testing whitelist. Please *only* do this once a PR is
>> ready to go from a review perspective - testing many fast iterations of a
>> branch is what causes the load.
>>
>> On Tuesday the change will be reverted and we'll return to normal.
> It seems still to be off?
–
Dominic Cleal
dominic@cleal.org
I think this is related to
https://github.com/theforeman/smart-proxy/pull/388, which is a PR
against 1.11-stable branch, not develop.
Hence no CI.
-d
···
On Wed, Mar 2, 2016 at 10:16 AM, Dominic Cleal wrote:
> On 02/03/16 10:15, Daniel Helgenberger wrote:
>>
>>
>> On 26.02.2016 17:36, Greg Sutcliffe wrote:
>>> Hi all,
>>>
>>> In order to avoid unacceptable load on the CI infra during our planned bug
>>> day on Monday[1], the PR scanner will be switched to manual-only mode[2]
>>> for the whole day.
>>>
>>> As such, you'll need to comment [test] to get tests to run *even* if you
>>> normal are in the testing whitelist. Please *only* do this once a PR is
>>> ready to go from a review perspective - testing many fast iterations of a
>>> branch is what causes the load.
>>>
>>> On Tuesday the change will be reverted and we'll return to normal.
>> It seems still to be off?
>
> I re-enabled it late on Monday. What's not working?
>
> --
> Dominic Cleal
> dominic@cleal.org
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Ah yes. I think I've fixed that now, it should start testing all smart
proxy branches in an hour or so.
The Jenkins jobs needed the base branch parameter adding, older jobs are
missing this so some projects only test on develop/master.
···
On 02/03/16 10:18, Dmitri Dolguikh wrote:
> I think this is related to
> https://github.com/theforeman/smart-proxy/pull/388, which is a PR
> against 1.11-stable branch, not develop.
> Hence no CI.
–
Dominic Cleal
dominic@cleal.org
> I think this is related to
> https://github.com/theforeman/smart-proxy/pull/388, which is a PR
> against 1.11-stable branch, not develop.
> Hence no CI.
Right, thanks. Sorry for the confusion and thanks for clarifying Dmitri.
···
On 02.03.2016 11:18, Dmitri Dolguikh wrote:
-d
On Wed, Mar 2, 2016 at 10:16 AM, Dominic Cleal dominic@cleal.org wrote:
On 02/03/16 10:15, Daniel Helgenberger wrote:
On 26.02.2016 17:36, Greg Sutcliffe wrote:
Hi all,
In order to avoid unacceptable load on the CI infra during our planned bug
day on Monday[1], the PR scanner will be switched to manual-only mode[2]
for the whole day.
As such, you’ll need to comment [test] to get tests to run even if you
normal are in the testing whitelist. Please only do this once a PR is
ready to go from a review perspective - testing many fast iterations of a
branch is what causes the load.
On Tuesday the change will be reverted and we’ll return to normal.
It seems still to be off?
I re-enabled it late on Monday. What’s not working?
–
Dominic Cleal
dominic@cleal.org
–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Daniel Helgenberger (helge000)
daniel@helgenberger.net
