|
1 | 1 | .. title: Automating Nikola rebuilds with Travis CI
|
2 | 2 | .. slug: automating-nikola-rebuilds-with-travis-ci
|
3 | 3 | .. date: 2016-08-24 18:05:25 UTC
|
4 |
| -.. updated: 2017-03-17 16:20:00 UTC |
| 4 | +.. updated: 2017-03-17 17:15:00 UTC |
5 | 5 | .. tags: Travis CI, GitHub, automation, tips
|
6 | 6 | .. author: Chris Warrick
|
7 | 7 | .. type: text
|
@@ -57,9 +57,10 @@ are a few important things you need to take care of:
|
57 | 57 | into an infinite loop.
|
58 | 58 | * We assume your source branch is ``src`` and you deploy to ``master``. Any
|
59 | 59 | other configuration requires editing ``.travis.yml``.
|
60 |
| -* If you ever commit to ``master`` manually, make sure to add ``[ci skip]`` to |
61 |
| - your commit messages, otherwise there might be failed builds (with errors |
62 |
| - about ``Rakefile`` missing) |
| 60 | +* We enable builds only for the ``src`` branch by default. Older versions of |
| 61 | + the script did not include this provision, and thus committing to ``master`` |
| 62 | + (which you should not do, as your changes will be overwritten on next Travis |
| 63 | + rebuild) used to cause ``Rakefile`` errors. |
63 | 64 |
|
64 | 65 | If everything works, you can make some change to your site (so you see that
|
65 | 66 | rebuilding works), but don’t commit it just yet.
|
@@ -125,4 +126,4 @@ Hopefully, Travis CI will build your site and deploy. Check the Travis CI
|
125 | 126 | website or your e-mail for a notification. If there are any errors, make sure
|
126 | 127 | you followed this guide to the letter.
|
127 | 128 |
|
128 |
| -(Revision 2, 2017-03-17: added master/src branching information, clarified some things) |
| 129 | +(Revision 3, 2017-03-17: added master/src branching information, blocked non-src builds, clarified some things) |
0 commit comments