- 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.
when `VERSION_MINOR` in `lib/galaxy/version.py` is e.g. `rc1`.
Also:
- Do not require awk
- Remove unused functions
- Do not require the presence of `~/.github.json` file
- Speed up qunit testing but not re-building production bundles that aren't used anyway.
- Add a watch option for qunit.
- Add option to speed up running all tests by building tests as single bundle instead of many bundles. (May be future default for ``make client-test``.)
This is as close as I think we are going to get to closing #4843.
- Rework pattern for linting dependencies to work for dev-requirements.txt.
- Get rid of dev-requirements.txt and replace it with a symbolic link to the latest pinned versions of dependencies.
Rebased against dev to bring in @nsoranzo's bashism bashings in #4876 and fixed up to strip trailing whitespace from generated requirement files.
- Use completely pinned and hashed dependencies for more consistent, reproducible linting.
- Leverage the awesomeness of pipenv to automate updating these.
- These will always be locked now so builds don't break randomly on other people updating their software. When we finally have the bot up and running that forward merges fixes for Galaxy we can add another if statement that runs this check against dev once a day and opens a PR if needed.
Nate Coraor