search

junit-pioneer / junit-pioneer.github.io

Org site for JUnit Pioneer
0 stars 2 forks source link

GitHub Actions for Sitebuild #6

Closed aepfli closed 4 years ago

aepfli commented 4 years ago

Currently we rely on a travis, shell scripts and gradle magic to generate the side. There is a lot of knowledge involved, what does what, and how.

We want to migrate as much as possible to GitHub Actions. Therefore we should check our possibilities.

eg. instead of triggering it via gradle we could simply use Repository-Dispatch to trigger the build.

eg. instead of checking out the repository vie shell scripts called by gradle, we could use Checkout

eg. instead of building via gradle we could use Jekyll Action.

Overall switching to Actions will it make easier to understand what is going on, and we might get rid of the grandmaster branch which contains gradle and shell scripts for building. This will in my opinion improve maintainability.

This issue is part of junit-pioneer/junit-pioneer#192 and relates to junit-pioneer/junit-pioneer#124

nipafx commented 4 years ago

Yes, simplifying that process is a good idea. (I transferred the issue to the correct repo.)

nipafx commented 4 years ago

Duplicate of #5.