Commit Graph

8 Commits

Author SHA1 Message Date
Nate Johnston 3d3098c893 Retire the Congress Tempest Plugin project
Recently the TC has worked on determining the criteria for when an
OpenStack project should be retired.  When there was not a PTL nominee
for the Congress project, that triggered the TC to review the project
health per [1], and the TC has determined [2] that development work on
the project has ceased.  This decision was announced in the
openstack-discuss mailing list in April 2020 [3].

This commit retires the repository per the process for governance
removal in the Victoria cycle as specified in the Mandatory Repository
Retirement resolution [4] and detailed in the infra manual [5].

Should interest in developing Congress as part of OpenStack revive,
please revert this commit to have the project rejoin the list of active
projects.

The community wishes to express our thanks and appreciation to all of
those who have contributed to the Congress project over the years.

[1] https://governance.openstack.org/tc/reference/dropping-projects.html
[2] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/latest.log.html#t2020-04-20T15:36:59
[3] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014292.html
[4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html
[5] https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#retiring-a-project

Change-Id: I74824174861c394e75b8c733ae9bbc3c9b410268
2020-05-28 12:15:14 -04:00
Ghanshyam Mann f924c6cd98 [ussuri][goal] Drop python 2.7 support and testing
OpenStack is dropping the py2.7 support in ussuri cycle.

Congress-tempest-plugin is ready with python 3 and ok to drop the
python 2.7 support.

Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

Depends-On: https://review.opendev.org/#/c/693631/
Change-Id: I47cda983c99ec6fb05956f09a0b395350a97d791
2020-01-22 22:12:24 +00:00
akhiljain23 d1fb7a7e3a Changes for url transition to OpenDev
This commit changes openstack.org URL to opendev.org URL

Change-Id: I4f67a9afffa12b07da554f6f3c696276d57f5de6
2019-04-24 09:47:25 +05:30
OpenDev Sysadmins bce11f9098 OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:30:03 +00:00
Ian Wienand d886a2350e Replace openstack.org git:// URLs with https://
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.

This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.

This update should result in no functional change.

For more information see the thread at

 http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html

Change-Id: I8833914dcfd75441bf99074d33802c5b26852928
2019-03-24 20:33:22 +00:00
Eric K 2b4c0ba868 disable murano scenario test in queens-py35 job
Persistent instability in the test on queens branch and only in the
py35 job (py27 seems fine).
The instability makes the test more trouble than it's worth.
Because we are unlikely to make changes to queens going forward,
and even less likely that the changes would break murano integration,
it makes sense to simply disable to test for queens-py35 job, but
keeping it in all other jobs including queens-py27.

Also folding in the following patch resolving gate instability because
both patches are blocked on its own.
---------------------------------------
Increase policy rule create retry limit

Because in the vitrage pub-sub tests, occassionally the retry runs
out before the schema from the datasource is available to the
policy engine to allow the creation of the test rule.

https://review.openstack.org/#/c/637681/

Change-Id: I4915023258b455005e1ac2e2d1492beb368f0184
2019-02-19 21:09:10 +00:00
Eric K 3d1a06d161 Update CI jobs in sync with migration in congress repo
- Run newly migrated congress-tempest-* jobs from congress repo.
- Hold legacy jobs and playbooks deleted from congress repo. They
are used to run jobs against stable branches. Can be removed when
all supported stable branches use new style jobs.
- Fixes the problem where stable branch jobs do not correctly use
the specified branches.

Depends-On: https://review.openstack.org/#/c/631609/
Change-Id: I03cfb7a1dae0ee3fab70be61203fc07f324e8a41
2019-01-17 17:11:06 -08:00
ghanshyam 0beba1db12 Fix queens py35 job
Current job of queens py35 try to override
the stable/queens branch using override_branch
var which is zuulv3 var not legacy zuul job.

On legacy zuul job, branch can be overridden by
BRANCH_OVERRIDE var.

This is problem in all stable branch job running
on congress-tempest-plugin master gate. Other stable
branch job somehow not failing and master version of all
repo are working fine there but they do not actually test
stable branch.

queens py35 job is failing when using master version
of other repo.

Plan is to migrate thw congress jobs to zuulv3 which
will be easy to fix and use override_branch for all
stable branch jobs running on master. But this can
take time so let's fix broken job only as of now.

This commit fixes this job only to unblock the gate.
Change-Id: I328cf0330a054e76e8ac7895a2f844fdb7ab4226
2019-01-15 05:41:34 +00:00