Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use continuous integration #76

Open
sebschrader opened this issue Feb 13, 2018 · 1 comment
Open

Use continuous integration #76

sebschrader opened this issue Feb 13, 2018 · 1 comment
Milestone

Comments

@sebschrader
Copy link
Member

We do already have a Docker-based development and testing environment and integration tests. Having Travis build Hades shouldn't be too hard.

@sebschrader sebschrader added this to the 0.5 milestone Feb 13, 2018
@sebschrader sebschrader changed the title Use continous integration Use continuous integration Feb 13, 2018
@lukasjuhrich
Copy link
Collaborator

s/Travis/Github Actions/

A CI pipeline should also handle:

  1. Basic python Linting (without the docker setup)
  2. Building the docs in nit-picky mode (-n)
  3. Building Hades (with the docker setup)

We can run (1/2, 3) in parallel.
Deployment of the docs by means of a push to the gh-pages branch is not important, but we should build the docs anyway

  1. we can catch errors in the documentation earlier
  2. we are forced to keep the sphinx build itself working (a dev could easily forget adding a plugin to the [docs] requirements after introducing it to the docs).

@sebschrader sebschrader modified the milestones: 0.5, 0.6 Sep 11, 2022
@lukasjuhrich lukasjuhrich mentioned this issue Sep 11, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants