Currently doc builds for `release_22.01` and `master` branches
incorrectly show the "This document is for an in-development version
of Galaxy." warning banner.
Partially backport commit 318a1d7056
and drop the unused `TARGET_BRANCH` variable from `Makefile` which
shadows the shell environment variable of the same name set
in `.github/workflows/docs.yaml` and used in
`doc/source/conf.versioning.py` .
1) Download conformance tests to `test/functional/tools/cwl_tools` where
they can be used also by framework and unit tests in the future.
2) Add populators to enable executing CWL conformance tests
3) Generate CWL conformance API tests only when needed for tests
- Convert release Makefile targets to a script
- Update package versions from Galaxy version instead of leaving them
uncoupled
- Use next-dev-version process on release branches when in between point
releases
- Automatically detect and increment versions
- Test merging release branches forward before pushing releases
- Support multiple rc versions (will be more useful for package testing)
- Support building local versions of packages
- Tests for the release script
The new Makefile-based command ``make serve-selenium-notebooks`` will serve notebooks in lib/galaxy_test/selenium/jupyter.
The notebooks will target a Galaxy host running on port 8080 - but are parameterized to be run with papermill (https://papermill.readthedocs.io/) for automate targeting different Galaxy servers, remote Selenium servers, etc..
Screenshots will be embedded right into the notebook.
Example notebooks setup to target just the library code in ``galaxy-selenium`` as well as one appropriate to leverage the Galaxy testing framework are included and documented in depth via modules docstring for ``galaxy_test.selenium.jupyter``.
Development target uses 4 cores (I use 8 locally), shows all warnings about issues (instead of failing on first), and skips the viewcode step which isn't parallelized and doesn't really exercise anything the developer has useful control over or would need to see during doc tweaking.
Prevent error messages when `requests` or `six` are not available, e.g.:
```
$ make
Traceback (most recent call last):
File "scripts/bootstrap_history.py", line 658, in <module>
main(sys.argv)
File "scripts/bootstrap_history.py", line 419, in main
raise Exception("Requests library not found, please pip install requests")
Exception: Requests library not found, please pip install requests
client-eslint Run client linting
client-format Reformat client code
...
```
instead of converting the Markdown to reStructuredText with pandoc.
Fix the broken tables, but code inside tables is not coloured as
in the rest of the document.
mvdbeek