Daniel Leidert dleidert

I've recently found a way to test build a NSIS-based installer project on a Windows host on https://travis-ci.org. I had to figure out quite a bit how to run the makensis command there and how to set the PATH environment variable. But now that it works, let me share my configuration file .travis.yml with you:

language: shell
sudo: false

notifications:
  email:
    on_success: never

Setting up TRAVIS CI for GitHub Pages

I recently set up TRAVIS CI support for my personal github pages. There are some github and jekyll support pages, that cover the basics. Unfortunately I ran into several build failures and issues not covered there until the builds finally succeeded. The following sections cover the issues and their solutions.

The results can be seen here: https://travis-ci.org/dleidert/dleidert.github.io/builds. I'm planning to add support for different ruby versions. This will probably require different Gemfile variants.

**Please note, that I don''t use TRAVIS to deploy the res

Below is an example for a jekyll template to provide structed data in JSON-LD for a software application using the site.github namespace (provided by the github-metadata) plugin). Assuming there is at least one release, this snippet is a starting point. Content represented by three dots ... usually needs to be added manually to the snippet:

{%- assign release = site.github.latest_release -%}
{
  "@context": "http://schema.org/",
  "@type": "SoftwareApplication",
  "codeRepository": "{{ repository_url }}",
  "programmingLanguage": {
    "@type": "ComputerLanguage",

TRAVIS builds are triggered by every commit to the repository. When hosting github pages with the source (e.g. in the docs folder), changes to the documentation are (usually) not critical to the build itself, so they could be easily skipped. Unfortunately TRAVIS does not offer a file-/foldername-based skip instruction like e.g. AppVeyor's skip_commits field.

But there seem to be two ways of achieving (almost) the same effect. In the following examples changes to the files

.appveyor.yml
.gitattributes
.gitignore
docs/**

I usually host a projects GitHub pages (docs/) and build service configration files (e.g. .travis.yml or .appveyor.yml) together with the projects source in the master branch. When creating a release, github creates a zip and a tar archive (the so called zipball and tarball), which can also be created these links:

https://api.github.com/repos/:user/:project/tarball
https://api.github.com/repos/:user/:project/zipball

or for a specific release:

This will prevent AppVeyor from running a job, when commits are done regarding the docs directory only. It might be useful, when the projects repository contains the GitHub pages in the master branch and changes to them are not critical to the build.

skip_commits:
  files:
    - docs/**/*

I further exclude some other files too. This is my minimal list

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\text\shell\edit\command /f /ve /t REG_EXPAND_SZ /d "\"^%ProgramFiles^%\Notepad++\notepad++.exe\" %1"

This will overwrite the default value!

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\text\shell\edit\command /f /ve /t REG_EXPAND_SZ /d "\"^%ProgramFiles^%\Notepad++\notepad++.exe\" %1"

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\.html\shell\edit\command /f /ve /t REG_EXPAND_SZ /d "\"^%ProgramFiles^%\Notepad++\notepad++.exe\" %1"

This will create a new key and add an Edit option to the file context menu!