I have recently updated my Organizational Super POM to start doing SNAPSHOT deployments on my `master` branch and release builds on tags using Travis for my open source projects. This is based off the work on Automatically publishing to GitHub Pages where I just have something more complicated than a simple token.
Continue reading Maven Deploy Using Travis
This is the approach I took for my new developer portfolio page where I wanted to see changes being put on the “test” site while I am doing my development.
Continue reading Automatically publish to GitHub Pages using Travis
Since I was doing a bit of experiments for my new portfolio site which will replace my blog’s front page eventually especially with the automatic publishing, I do realize that during the course of debugging and other fixes that I may have exposed the token values in the logs.
Continue reading Quickly removing Travis build logs
This post is able how I had integrated Travis-CI.org, SonarQube.com and GitHub so it will process pull requests and put them as part of the GitHub commit.
Continue reading Integrating Travis, SonarQube and GitHub
Setting up a continuous integration system for your application regardless if it is Meteor or not is generally a good idea as it will help detect errors sooner than later. Travis on Github has one extra nice feature that one of my old projects had to explicitly implement for me on Jenkins a few years back and that is “Pull Request” builds. Travis’ build system is pretty simple which makes it an ideal candidate for less structured builds. For structured enterprise builds like those with Maven I would still recommend Jenkins overall. This post describes how to set up a Meteor project to work with Travis.
Continue reading Continuous Integration for Meteor with Travis