Set up continuous integration & deployment with Travis

lunduniversity / schoolprog

Programming exercises for primary and secondary education, in Swedish.

https://lunduniversity.github.io/schoolprog/

15 stars 6 forks source link

Set up continuous integration & deployment with Travis #14

Closed ErikBjare closed 6 years ago

ErikBjare commented 6 years ago

For this to go into effect, we need to start using the develop branch as our default branch and use the master branch only as a place for builds of the website which GitHub will serve.
- An example is here where an identical setup is used for activitywatch.net.

gorelhedin commented 6 years ago

What do you intend to check with the continuous integration?

ErikBjare commented 6 years ago

@gorelhedin Not much being checked right now, it just builds the site and should then push the build to the right branch for GitHub to host it.

We might not need to switch default branch after all as it turns out that's only needed if the website is to be hosted on the organizations main site (as is the case for ActivityWatch).

gorelhedin commented 6 years ago

Ok. Sounds good if we don't need two branches.

ErikBjare commented 6 years ago

We'll still need two branches, but no one will ever have to touch the gh-pages branch manually and they won't share any history.