# Travis CI Travis CI is a continuous integration platform that automatically builds and tests code changes and can automate deployments and notifications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Dockerized e2e tests DevFeed: [Dockerized e2e tests]() Original publisher: [Read original article]() Published: 2018-02-15T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Docker](), [Selenium](), [Browser Automation](), [CI/CD](), [Testing](), [Travis CI](), [webDriver](), [Chrome](), [Firefox]() Tags: [browser](), [ci](), [containers](), [docker](), [firefox](), [selenium](), [testing](), [travis-ci](), [webdriver]() ### AI overview This tutorial explains how to run Selenium end-to-end tests in Docker and integrate them with CI tools such as Travis CI, GitLab CI, or Jenkins. It describes using Selenium Hub and Chrome and Firefox node containers, configuring WebdriverIO, capturing screenshots for failed tests, and organizing tests with a Page Object. ### Source excerpt In my free time, I'm trying to learn something new and best of way learning is by doing. To avoid spinning my wheels in vain I'm helping to develop some product. In the previous post, I've described what we've decided to use for the UI and pointed out that I'm going to write integration tests. Here is how I integrated selenium e2e tests with gitlab-ci/travis-ci/whatever by running them in docker. Read more ## Codename One 3.8 Code Freeze, Versioning Changes, and Test Updates DevFeed: [Codename One 3.8 Code Freeze, Versioning Changes, and Test Updates]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-10-30T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [releases](), [ci](), [Travis CI]() Tags: [ci](), [releases](), [travis]() ### AI overview Codename One plans a code freeze for version 3.8 and will move from 3.8 directly to 4.0 under a major-version milestone scheme. The post also reports an Eclipse Oxygen simulator issue, an overflow-menu regression fix, automated-test repository integration with Travis CI and GitHub, and the callSeriallyOnIdle method. ### Source excerpt We will enter code freeze for Codename One 3.8 next week and have a lot of things to clear off the table in order to get there! The first order of business is that there will be no Codename One 3.9... Instead we will go right to 4.0 and switch to major version number update scheme only. This will align us better with industry standards. We spent ages in 3.x and far less in 1.x or 2.x numbering. That doesn't make sense. It's hard to tell what feature is big enough for a "major version number update" and it doesn't indicate as much with the fast pace of releases. So switching to major version numbers in terms of milestones will simplify and give a better indication of the work we put in. ## Continuous Deployment: Hugo + Travis CI -\> GitHub Pages DevFeed: [Continuous Deployment: Hugo + Travis CI -\> GitHub Pages]() Original publisher: [Read original article]() Author: Chris Hager Published: 2017-04-25T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [CI/CD](), [Continuous Deployment (CD)](), [GitHub Pages](), [Hugo](), [Travis CI](), [GitHub](), [Git](), [Go Language](), [container]() Tags: [builds](), [ci](), [continuous-deployment](), [deployment](), [git](), [github](), [github-pages](), [go](), [how-to](), [hugo](), [travis-ci]() ### AI overview A tutorial on automating Hugo static website builds and deployment to GitHub Pages with Travis CI. Builds run when changes are pushed to Git, and deployment occurs after a successful build on the master branch. ### Source excerpt This post shows how to automate building and deployment of Hugo static websites to GitHub Pages using Travis CI. Builds are automatically triggered when pushing to the Git repository, and deployment when a build on the master branch succeeds. Hugo is a static website generator written in Go, and only requires a single binary. The easiest way to run Hugo in the Travis CI container is by including the specific hugo binary with which to build the site as part of the repository (eg. ## Building a 64bit Docker OS for the Raspberry Pi 3 DevFeed: [Building a 64bit Docker OS for the Raspberry Pi 3]() Original publisher: [Read original article]() Published: 2017-03-02T10:28:42Z Content type: tutorial Language: en Sources: [Hypriot]() Topics: [Docker](), [Raspberry Pi](), [Containers](), [Operating system](), [Debian](), [Kernel](), [boot](), [ci](), [Travis CI](), [GitHub](), [pull-requests]() Tags: [boot](), [bootloader](), [bugs](), [ci](), [containers](), [debian](), [docker](), [github](), [how-to](), [kernel](), [linux](), [opensource](), [os](), [pull-requests](), [raspberry-pi](), [travis-ci](), [workshop]() ### AI overview A workshop introduces the step-by-step construction of HypriotOS, a 64-bit Debian-based operating system for Raspberry Pi 3 focused on running Docker containers. It covers the bootloader, kernel, root filesystem, and SD card image, using Docker for builds and Travis CI for cloud builds. ### Source excerpt I'm happy to announce the start of a "short" workshop were I'm going through all the steps to build a complete 64bit operating system for the Raspberry Pi 3. This 64bit HypriotOS is mainly focused on running Docker containers easily on this popular DIY and IoT device. You'll see that I'm using Docker heavily for each and every build step, because it really helps us a lot to run a local build with Docker-for-Mac or later on the cloud build servers at Travis CI. This workshop is sponsored by bee42 solutions Follow @bee42solutions Background and Contents As you may already know, a complete Linux operating system consists of several important building blocks and I'd like to show you how to build all of these step by step. For this purpose I'm not going to reinvent the wheel and so I'll reuse all of the existing parts which are already published by the Raspberry Pi Organisation, by the Debian Linux project and will add some more glue code. At the end you should have learned how to build all the necessary parts and how to automatically create a finished SD card image which could be flashed on an empty SD card. Then boot your Raspberry Pi 3 with and in less than a minute you have a fully running Docker Engine on a Debian-based 64bit Linux OS. Here is a short overview of the contents of the workshop: Part 1: Bootloader Part 2: Kernel Part 3: Root filesystem Part 4: SD Card Image So, that's enough for explaining the background of this workshop. For more informations please follow along the details I'll publish on the coming tweets at Twitter and in the GitHub repos until all the parts of this workshop are finished and available as OpenSource. Please be aware that this OS is in a development phase and far from being perfect. So you are encouraged to help me with reporting issues and filing pull-requests to add features and fix bugs. Further Links I'm going to publish all the details and steps to build the new operating system in a public GitHub repo. All other details and nec ## Best Practices and Common Mistakes with Travis CI DevFeed: [Best Practices and Common Mistakes with Travis CI]() Original publisher: [Read original article]() Author: Kevin Deisz Published: 2017-01-10T13:46:39Z Content type: tutorial Language: en Sources: [Localytics]() Topics: [Travis CI](), [Continuous integration](), [Testing](), [build performance](), [GitHub]() Tags: [best-practices](), [continuous-integration](), [github](), [parallelism](), [speed](), [testing](), [travis-ci]() ### AI overview This article presents five internal best practices for using Travis CI, focusing on continuous integration, efficient testing, and reducing build time. It explains how Travis CI integrates with GitHub and supports configurable build environments, build matrices, and test parallelism. ### Source excerpt What is Travis At Localytics, we've worked hard to ensure that all of our services are built and deployed using our own internal best practices. One of those core best practices is that the service in question is using continuous integration (CI). CI greatly reduces the amount of ## Setting up Travis, Jekyll and GitHub pages DevFeed: [Setting up Travis, Jekyll and GitHub pages]() Original publisher: [Read original article]() Author: Stanko Published: 2016-10-24T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [Travis CI](), [GitHub](), [GitHub Pages](), [ci](), [Ruby]() Tags: [ci](), [github](), [github-pages](), [github-personal-access-token](), [jekyll](), [ruby](), [security](), [travis](), [travis-ci]() ### AI overview This tutorial explains how to use Travis CI to build a Jekyll site and publish the generated files through GitHub Pages. It describes branch setup, webhook activation, a GitHub Personal Access Token, Ruby gem configuration, and a Rake task. The author warns that the setup may be outdated and no longer uses it. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. Update, November 2017 # I don't use this setup anymore, it might be outdated, proceed with caution. Original post # As I already mentioned, GitHub pages do not work with the Jekyll plugins. It is a security measure. So I researched it a bit, and colleague of mine proposed a simple solution - Travis CI. There is a great repo with instructions how to set everything up - jekyll-travis. But few steps are kinda confusing, and it took me 10 failed builds to make it work. So I'll try to help you with those. I copied the steps from the original repo and updated steps where I got stuck. Be sure to check the original readme as well. Flow # When you push to your GitHub repo, it triggers Travis Travis starts up a virtual machine and installs all required software (mostly Ruby gems). We use a custom rake task to tell Travis how to build our Jekyll site and push the updated content back to Github Travis clones a source branch (usually master or source, in my case source) Travis runs jekyll build on the source branch Travis does a git push to the branch holding static site files (usually gh-pages or master, in my case master) Github Pages starts serving the updated site Steps to make it work # Move your Jekyll source files to the source branch (name it as you like). We'll use master or gh-pages branch to host generated HTML website. Make sure you have enabled your source repo in the Travis CI admin dashboard so that the webhook is triggered Create a GitHub Personal Access Token from you profile page. If you haven't already, create a Gemfile, and add rake gem to it. source "http://production.cf.rubygems.org/" gem "rake", "~> 10.1.1" gem "jekyll-paginate" gem "jekyll-archives" We have seen intermittent timeouts fetching gems from Rubygems.org. install: bundle install lets Travis CI automatically retry, and we are using source "http://production.cf.rubygems.org/" in Gemfile to point to a different reposito ## Test gem with multiple dependencies on Travis CI DevFeed: [Test gem with multiple dependencies on Travis CI]() Original publisher: [Read original article]() Published: 2016-07-03T05:27:56Z Content type: tutorial Language: en Sources: [Jolly Good Code]() Topics: [ci](), [Travis CI](), [test](), [Tool]() Tags: [ci](), [dependencies](), [how-to](), [learn](), [test](), [tool](), [travis](), [travis-ci]() ### AI overview A tutorial on testing a Gem with multiple dependencies on Travis CI using thoughtbot's appraisal tool. ### Source excerpt Learn how to test your Gem with multiple dependencies on Travis CI with thoughtbot's appraisal tool. ## Set up Travis CI and code coverage for open-source Android projects DevFeed: [Set up Travis CI and code coverage for open-source Android projects]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2015-11-13T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [ci](), [test-coverage](), [Travis CI](), [GitHub](), [unit tests](), [Android]() Tags: [also](), [android](), [blogs](), [ci](), [code-coverage](), [continuous-integration](), [coverage](), [github](), [tools](), [travis-ci](), [unit-tests]() ### AI overview This tutorial explains how to configure Travis CI to build open-source Android projects, run unit tests, generate code coverage reports, and integrate with GitHub pull requests. ### Source excerpt Wouldn't you love to have your open source projects built automatically by a continuous integration server? And to have a detailed code coverage report for all your unit tests?