settingsLogin | Registersettings

[openstack-dev] [tripleo]

0 votes

Greetings,

I'd like to propose we remove the upgrade jobs that are consistently
failing from the upstream infrastructure and instead focus our efforts in
RDO Software Factory.

The jobs listed in https://review.openstack.org/#/c/518405/ are
consistently failing after being reviewed by myself and Mathieu. I am
leaving legacy-tripleo-ci-centos-7-multinode-upgrades in place as it's
passing with an overall rate of 87%.

It doesn't make any sense to continue to tax upstream resources on failing
jobs, lets get the jobs running correctly and consistently in rdo software
factory before moving these back to our mainline CI.

Please let me know what you think of the proposal.
Thanks

The upgrade job configuration for upgrades can be found in [1]
[1]
https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/jobs/tripleo-upstream.yml


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Nov 8, 2017 in openstack-dev by Wesley_Hayutin (2,320 points)   2

6 Responses

0 votes

On 11/07/2017 03:29 PM, Wesley Hayutin wrote:
Greetings,

I'd like to propose we remove the upgrade jobs that are consistently
failing from the upstream infrastructure and instead focus our efforts in
RDO Software Factory.

The jobs listed in https://review.openstack.org/#/c/518405/ are
consistently failing after being reviewed by myself and Mathieu.  I am
leaving legacy-tripleo-ci-centos-7-multinode-upgrades in place as it's
passing with an overall rate of 87%.

It doesn't make any sense to continue to tax upstream resources on failing
jobs, lets get the jobs running correctly and consistently in rdo software
factory before moving these back to our mainline CI.

Please let me know what you think of the proposal.
Thanks

The upgrade job configuration for upgrades can be found in [1]
[1]
https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/jobs/tripleo-upstream.yml


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Seconded.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Nov 7, 2017 by Jason_Rist (2,740 points)   1 2
0 votes

On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin whayutin@redhat.com wrote:
Greetings,

I'd like to propose we remove the upgrade jobs that are consistently failing
from the upstream infrastructure and instead focus our efforts in RDO
Software Factory.

The jobs listed in https://review.openstack.org/#/c/518405/ are consistently
failing after being reviewed by myself and Mathieu. I am leaving
legacy-tripleo-ci-centos-7-multinode-upgrades in place as it's passing with
an overall rate of 87%.

It doesn't make any sense to continue to tax upstream resources on failing
jobs, lets get the jobs running correctly and consistently in rdo software
factory before moving these back to our mainline CI.

Please let me know what you think of the proposal.

+1 to remove them if we have the scenario upgrades (with parity from
what we had upstream) in RDO CI.
We'll need to make the job experimental in RDO CI, so we can only run
them at demand until they actually work. Can we do that as well?

Thanks,
--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Nov 7, 2017 by emilien_at_redhat.co (36,940 points)   2 5 7
0 votes

On Tue, Nov 7, 2017 at 5:47 PM, Emilien Macchi emilien@redhat.com wrote:

On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin whayutin@redhat.com
wrote:

Greetings,

I'd like to propose we remove the upgrade jobs that are consistently
failing
from the upstream infrastructure and instead focus our efforts in RDO
Software Factory.

The jobs listed in https://review.openstack.org/#/c/518405/ are
consistently
failing after being reviewed by myself and Mathieu. I am leaving
legacy-tripleo-ci-centos-7-multinode-upgrades in place as it's passing
with
an overall rate of 87%.

It doesn't make any sense to continue to tax upstream resources on
failing
jobs, lets get the jobs running correctly and consistently in rdo
software
factory before moving these back to our mainline CI.

Please let me know what you think of the proposal.

+1 to remove them if we have the scenario upgrades (with parity from
what we had upstream) in RDO CI.
We'll need to make the job experimental in RDO CI, so we can only run
them at demand until they actually work. Can we do that as well?

Thanks,

There are already several upgrade jobs defined in the experimental queue
that can be triggered with "check rdo experimental"
Let's iterate on those, and then make them full 3rd party check jobs.
We talked about allowing rdo sf to -2 reviews upstream as well which would
be handy.

Thanks guys

--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Nov 7, 2017 by Wesley_Hayutin (2,320 points)   2
0 votes

On Wed, Nov 8, 2017 at 9:54 AM, Wesley Hayutin whayutin@redhat.com wrote:
[...]
There are already several upgrade jobs defined in the experimental queue
that can be triggered with "check rdo experimental"
Let's iterate on those, and then make them full 3rd party check jobs.
We talked about allowing rdo sf to -2 reviews upstream as well which would
be handy.

LGTM. Thanks for the clarification.
--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Nov 7, 2017 by emilien_at_redhat.co (36,940 points)   2 5 7
0 votes

On 7.11.2017 23:29, Wesley Hayutin wrote:
Greetings,

I'd like to propose we remove the upgrade jobs that are consistently
failing from the upstream infrastructure and instead focus our efforts in
RDO Software Factory.

The jobs listed in https://review.openstack.org/#/c/518405/ are
consistently failing after being reviewed by myself and Mathieu. I am
leaving legacy-tripleo-ci-centos-7-multinode-upgrades in place as it's
passing with an overall rate of 87%.

It doesn't make any sense to continue to tax upstream resources on failing
jobs, lets get the jobs running correctly and consistently in rdo software
factory before moving these back to our mainline CI.

I think the most useful job being removed is
containers-multinode-upgrades, and that one i already see coming back
green from RDO CI as green (not experimental anymore). So +1 on the removal.

Please let me know what you think of the proposal.
Thanks

The upgrade job configuration for upgrades can be found in [1]
[1]
https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/jobs/tripleo-upstream.yml


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Nov 8, 2017 by =?UTF-8?B?SmnFmcOtIF (3,860 points)   2 3
0 votes

On 11/07/2017 11:47 PM, Emilien Macchi wrote:
On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin whayutin@redhat.com wrote:

Greetings,

I'd like to propose we remove the upgrade jobs that are consistently failing
from the upstream infrastructure and instead focus our efforts in RDO
Software Factory.

The jobs listed in https://review.openstack.org/#/c/518405/ are consistently
failing after being reviewed by myself and Mathieu. I am leaving
legacy-tripleo-ci-centos-7-multinode-upgrades in place as it's passing with
an overall rate of 87%.

It doesn't make any sense to continue to tax upstream resources on failing
jobs, lets get the jobs running correctly and consistently in rdo software
factory before moving these back to our mainline CI.

Please let me know what you think of the proposal.
+1 to remove them if we have the scenario upgrades (with parity from
what we had upstream) in RDO CI.
We'll need to make the job experimental in RDO CI, so we can only run
them at demand until they actually work. Can we do that as well?

Thanks,

+1,

I missed this thread due to no subject ;)

Thank you Wes for having moved those jobs in SF and for raising this thread.

Mathieu


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Nov 10, 2017 by mathieu_bultel (640 points)  
...