openstack
/
tripleo-image-elements
Code Issues Proposed changes
2,919 Commits 3 Branches 24 Tags 30 MiB
Commit Graph

7 Commits

Author SHA1 Message Date
Ghanshyam Mann a43311b7ef Retire Tripleo: remove repo content 
TripleO project is retiring
- https://review.opendev.org/c/openstack/governance/+/905145

this commit remove the content of this project repo

Change-Id: Ic209179b0be9c3746a702ccea2dd35e883e78bee
 2024-02-24 11:43:49 -08:00
LiZekun 918b802ec2 remove unicode literal from code 
All strings are considered as unicode string from Python 3.

This patch drops the explicit unicode literal (u'...')
appearances from the unicode strings.

Change-Id: I7247c37d7e082ffa4ea9e8540b25351bb9b851c5
 2022-02-23 02:53:21 +00:00
Hervé Beraud 3ce55b5039 Add doc/requirements 
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removed specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to
pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug and it already faced
it previously [1].

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

NOTE: Also fix CI clear pbr constraints, relax hacking contraints,
fix H214 Use assertIn/NotIn(A, B) rather than assertTrue/False

Change-Id: Id7ed00333ba9571ef9e0d8f300714835ba63551b
 2021-01-06 16:22:12 +02:00
Andreas Jaeger 6e7d0123ec Switch to newer openstackdocstheme and reno versions 
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems

Update Sphinx version as well.

Disable openstackdocs_auto_name to use 'project' variable as name.

Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.

openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.

See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html

Change-Id: I5aedf5a96bc39825dac6b0ddd0005c9e8e0b1619
 2020-06-03 20:37:04 +02:00
Emilien Macchi 35068ac7ea Switch from oslosphinx to openstackdocstheme 
As part of the docs migration work[0] for Pike we need to switch to use the
openstackdocstheme.

[0] https://review.openstack.org/#/c/472275/

Change-Id: I497a3d33d70a6464ab642f7b1009efe19ba4ea8e
 2017-07-06 12:38:48 -07:00
Gonéri Le Bouder 0172b5aacc PEP8 on the doc and elements files 
ensure the Python scripts in the doc and elements directories are PEP8
compliant.

test_os_svc_daemon.py test is fixed in another patch:
  I9b1859f9fc5846c7c42606644231105618e1a1a0.

Change-Id: If5068ef77d6643c19de36bfcf4b4bf790f86b538
 2014-08-19 10:02:00 +02:00
Clint Byrum 4b8b11e8b9 Create stub for build_sphinx 
This will allow the docs jobs to pass which allows us to conform to the
OpenStack infra without specialness.

Change-Id: I4c80d71f211ed396cabda82dde088291a4bfe08d
 2014-04-18 10:17:36 -07:00