OpenStack Task Tracking API
Go to file
Clark Boylan b502ec35b0 Omnibus fixups for storyboard testing and CI
Linting fails due to two different hacking rules: H214 and H216. We fix
H214 by using assertNotIn and assertIn over assertFalse(foo in bar) and
assertTrue(foo in bar). We ignore H216 as it says don't use the mock
library but storyboard actually does use mock and updating to use
unittest.mock appears to be a fair bit of work.

In the sqlaclhemy models we move some classes around to address this
error:
  sqlalchemy.exc.InvalidRequestError: When initializing mapper mapped
  class Story->stories, expression 'TimeLineEvent' failed to locate a
  name ('TimeLineEvent'). If this is a class name, consider adding this
  relationship() to the <class 'storyboard.db.models.Story'> class after
  both dependent classes have been defined.

In the project loader we switch to using yaml.safe_load() to avoid the
missing Loader argument to yaml.load().

We pin jinja2 to < 3.0.0 as the old sphinx we've pinned to uses
contextfunction which appears to have been replaced in jinja2 3.0.0.
We should probably attempt to update the doc toolchain for storyboard
when we have time.

We pin MarkupSafe for similar reasons to the jinja2 pin. Version 2.1.0
of MarkupSafe removed the soft_unicode name which is used by sphinx.

Finally we run the python 3.6 and 3.7 jobs on ubuntu-bionic.

Change-Id: Ifcb6660ce2c89c21ba867aa88d942461bcff125d
2022-04-18 16:00:35 -07:00
doc Omnibus fixups for storyboard testing and CI 2022-04-18 16:00:35 -07:00
docker Optimise the Story browsing query 2020-09-11 12:27:55 +01:00
etc Add a Swift storage backend implementation 2019-11-16 21:03:37 +00:00
storyboard Omnibus fixups for storyboard testing and CI 2022-04-18 16:00:35 -07:00
tools Unpin webob and hacking to fix compatibility issues 2020-09-11 12:26:47 +01:00
.coveragerc remove final vestiges of incubated oslo code 2016-11-07 13:31:55 -05:00
.gitignore Remove vagrant setup 2018-01-10 00:30:08 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:02 +00:00
.stestr.conf Use one database per test class rather than per test 2019-03-18 15:24:05 +00:00
.zuul.yaml Omnibus fixups for storyboard testing and CI 2022-04-18 16:00:35 -07:00
CONTRIBUTING.rst Replace broken links and http links in the doc 2018-06-30 00:04:59 +02:00
Dockerfile Build container images 2019-12-09 16:09:20 -05:00
LICENSE Initial import 2013-07-01 18:09:56 +02:00
MANIFEST.in Introducing basic REST API 2014-01-22 11:37:54 -08:00
README.rst Replace broken links and http links in the doc 2018-06-30 00:04:59 +02:00
babel.cfg Add SQLalchemy database model 2014-01-13 18:52:47 +04:00
bindep.txt Build container images 2019-12-09 16:09:20 -05:00
requirements.txt Unpin webob and hacking to fix compatibility issues 2020-09-11 12:26:47 +01:00
setup.cfg Drop Python 2.7 support 2020-03-28 14:25:33 +00:00
setup.py Drop Python 2.7 support 2020-03-28 14:25:33 +00:00
test-requirements.txt Unpin webob and hacking to fix compatibility issues 2020-09-11 12:26:47 +01:00
tox.ini Omnibus fixups for storyboard testing and CI 2022-04-18 16:00:35 -07:00

README.rst

Storyboard

Storyboard is a task tracker created to serve the needs of highly-distributed systems that span multiple projects, to enable cross-project work on a massive scale. Concepts were adapted from existing tools, and as many potential points of contention were removed as possible, to better facilitate coordination of project work by stakeholders with widely varied interests and needs.

Project Resources

Project status, bugs, and blueprints are tracked at:

https://storyboard.openstack.org

Source code can be found at:

https://git.openstack.org/cgit/openstack-infra/storyboard/

Documentation can be found here:

https://docs.openstack.org/infra/storyboard/

Additional resources are linked from the project wiki page:

https://wiki.openstack.org/wiki/StoryBoard

Anyone wishing to contribute to an OpenStack project should find plenty of helpful resources here:

https://docs.openstack.org/infra/manual/developers.html

All OpenStack projects use Gerrit for code reviews. A good reference for that is here:

https://docs.openstack.org/infra/manual/developers.html#development-workflow