-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 25/10/14 00:16, James E. Blair wrote:
Andrea Frittoli andrea.fritt...@gmail.com writes:
I also believe we can find ways to make post-merge / periodic
checks useful. We need to do that to keep the gate to a sane
scale.
Yes, we have a plan
I'm sorry I've missed the email that you referred to before. Indeed,
it looks like I'm not the first one who started to think about the
matter. Summit wise, will there be any sessions where the subject will
be discussed?
Yes.
About post merge CI:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/10/14 12:07, Thierry Carrez wrote:
Ihar Hrachyshka wrote:
[...] For stable branches, we have so called periodic jobs that
are triggered once in a while against the current code in a
stable branch, and report to openstack-stable-maint@
Ihar Hrachyshka wrote:
Another question to solve is how we disseminate state of those jobs.
Do we create a separate mailing list for that? Obviously we should not
reuse -dev one, and it's overkill to create one mailing list per
interest group.
Should we explore other avenues than email for
I also believe we can find ways to make post-merge / periodic checks useful.
We need to do that to keep the gate to a sane scale.
On 24 October 2014 17:33, Thierry Carrez thie...@openstack.org wrote:
Ihar Hrachyshka wrote:
Another question to solve is how we disseminate state of those jobs.
Do
Andrea Frittoli andrea.fritt...@gmail.com writes:
I also believe we can find ways to make post-merge / periodic checks useful.
We need to do that to keep the gate to a sane scale.
Yes, we have a plan to do that that we outlined at the infra/QA meetup
this summer and described to this list in
Ihar Hrachyshka wrote:
[...]
For stable branches, we have so called periodic jobs that are
triggered once in a while against the current code in a stable branch,
and report to openstack-stable-maint@ mailing list. An example of
failing periodic job report can be found at [2]. I envision that
On Wed, 22 Oct 2014, Thierry Carrez wrote:
So while I think periodic jobs are a good way to increase corner case
testing coverage, I am skeptical of our collective ability to have the
discipline necessary for them not to become a pain. We'll need a strict
process around them: identified groups
On 10/22/2014 06:07 AM, Thierry Carrez wrote:
Ihar Hrachyshka wrote:
[...]
For stable branches, we have so called periodic jobs that are
triggered once in a while against the current code in a stable branch,
and report to openstack-stable-maint@ mailing list. An example of
failing periodic job
