We're trying to drop out the old images based on buster and 3.7 which
storyboard has based its images on. Update storyboard to bullseye and
python3.9 now that they have both been out for a while.
Depends-On: https://review.opendev.org/c/opendev/storyboard/+/838409
Change-Id: Ibf5f3eb63e22eb5b37cdfa74fe3bb6ce1f31bb62
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
The password in the storyboard-opendev-dockerhub Zuul secret was
encoded incorrectly. Reencrypt it the right way.
Change-Id: I7477c5b86a7e51121d2ec6da4250fad27986567e
Python 2.7 is deprecated now, and some dependencies have dropped their
support for it. We should also just drop support for it rather than
pinning the dependency versions.
This commit also switches to a generic Python 3 tox environment,
adds additional test jobs for more Python 3 versions, and cleans up
some Python 2 compatibility cruft.
Change-Id: I3e7cc1713dec1bada4a85f75362c4fa4f89ceae6
Rather than rely on the implicit docker-image provides/requires
list explicit per-image requirements for related jobs to reduce,
unecessarily serialization in change queues.
Depends-On: https://review.opendev.org/711119
Change-Id: Ie6b033652833bee84d2954b02a9014061756352f
In-tree zuul configuration does not need any project name stanza, remove
it.
Having it in, will make project renames difficult, so we do not want
these in.
Change-Id: I0871ba31ba89882271346398134258ca316ec7d7
We need to mark several things in the bindep file with the compile
tag so that we don't install them into the final image. Also, clean
up some of the extra things in the bindep file that are almost
certainly not needed.
Change-Id: I6e42d0191fd1db8482a4a0fbe208b669ef33bfee
The py35 env is unhappy on bionic. So we either need to update
that to use xenial nodes - or just update to 3.6 which is better
anyway.
Change-Id: Id2116657b9f497e213818bd905db7485c915ec0d
We use tox-py35 from zuul-jobs directly since we don't use the global
openstack/requirements constraints. However, this means that our
tox-py35 tests are now running on Bionic, which doesn't have Python
3.5.
This commit sets the nodeset for the tox-py35 job to ubuntu-xenial,
to continue not using the constraints but also allow the tests to
actually run again.
Change-Id: I7c4208521b25303d257cb22a84c3841d0b5e8c09
Declare variants of the tox-py27 and tox-py35 jobs with a one-hour
timeout instead of the default half-hour. Since we're declaring
these here in the repository, we can also add tox-pep8 and
publish-openstack-python-branch-tarball so that the
openstack-python-jobs-no-constraints and
openstack-python35-jobs-no-constraints templates can be removed from
project-config later.
Change-Id: I9d60ea9ef3973e957074bfe849b0d9c85f6d68c1
For most of the tests for storyboard sqlite is around 10 times faster
than MySQL (more for non-SSD systems). An sqlite database does not
support some operations, like modifying constraints or dropping
columns, so we cannot avoid testing with MySQL. We can however use
sqlite for local development to reduce the pain involved with running
tests as part of the development process.
This patch adds a tox environment for running the tests against
sqlite3. The new tox environment is intended to be used by developers
as well as the new check and gate job defined in .zuul.yaml.
The new job ensures that changes to alembic migration scripts continue
to work with sqlite.
This patch also modifies the existing alter scripts to skip steps not
supported under sqlite. Those steps aren't strictly needed, and they
are still tested when the CI system runs the tests with MySQL.
Change-Id: Icb979cb03e10c56519a90ea3976a4da2d9bddb05
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Zuul