-
Notifications
You must be signed in to change notification settings - Fork 14
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
GitHub / CI Integration #256
Comments
Building the LaTeX summaries in GitHub workflows would be nice 🙂 And yep, maybe the Studentenportal could add "auto-updateable" summaries that point to a GitHub issue. However, authentication/authorization could be tricky. Another option could be a pull-based approach where GitHub workflows generate PDF releases and the Studentenportal pulls those. |
There's also some previous discussion about this here: #66 (comment) |
From #66 :
Yeah exactly, though atm I'm dedicating a bit of my free time to fix it with a LaTeX package and CI to simplify that messy (and newbie hostile) workflow.
This is pretty much exactly what I'd want. |
I'll leave another quick note for the future impl: Travis can deploy stuff using a custom script, which in terms would make the auth very easy since one can code whatever he wants as long as it runs on the CI VM. https://docs.travis-ci.com/user/deployment/script It would be easy as adding the following to deploy:
provider: script
script: python3 .travis/studentenportal/update.py
on:
tags: true or even: Travis could fetch the latest version on its own (using git) during the build process. |
I know it's not very active at the moment but it would be nice if those summaries hosted under the HSRStud organization could get automatically posted on studentenportal.ch through the Github's API.
I've seen that some repositories already have a CI with Travis (may need to be fixed a little), so it would make sense to have it connected to the studentenportal to always get the latest build (or maybe list all releases?). And the GH repos could have a button that points to the issue tracker to allow those who don't LaTeX to ask for corrections.
The text was updated successfully, but these errors were encountered: