# 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.

## Infra at Scale: Agents, Tools and Infra-as-Code

DevFeed: [Infra at Scale: Agents, Tools and Infra-as-Code](<https://devfeed.tech/articles/infra-at-scale-agents-tools-and-infra-as-code-122088.md>)

Original publisher: [Read original article](<https://benchling.engineering/infra-at-scale-agents-tools-and-infra-as-code-105645ea7b58?source=rss----3d4aa8fb07ea---4>)

Author: Brendan Neutra

Published: 2026-11-06T21:51:13Z

Content type: article

Language: en

Sources: [Benchling](<https://devfeed.tech/sources/benchling.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [github](<https://devfeed.tech/tags/github.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [iac](<https://devfeed.tech/tags/iac.md>), [infra](<https://devfeed.tech/tags/infra.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Benchling uses scheduled Cursor Cloud Agents to raise staged Terraform PRs for routine Kubernetes component updates, increasing rollout cadence about fivefold across more than thirty components. Version constants keyed by development, staging, and production compile into per-cluster variables, so each stage's update is a one-line change; PRs advance through stages after testing and bake periods. Per-component configs guide release detection, compatibility research, health checks, and expected Terraform changes. Agents can run plans and test in a development sandbox but need no privileged production access. An authorized engineer reviews PRs, and production runs still require review: a Plan Matcher lets the Reviewer service apply only Terraform changes matching the approved expression; unmatched changes wait for human review. The article's example shows an agent identifying a release-note warning that applied to Benchling's configuration, preserving a controller default and verifying it in development. Staging is intended to limit production risk if an agent misses a breaking change.

### Source excerpt

In a previous post, How We Run Terraform At Scale, we shared how Benchling moved from a painful, laptop-driven, apply-then-merge workflow to an automated infrastructure release system built on Terraform Cloud (TFC). That migration dramatically reduced conflicts and drift, saved an estimated 8,000 developer hours annually, and gave us the foundation to scale from 350 to 625 workspaces managing many thousands of cloud resources across 38 AWS accounts. We also walked through the ecosystem of custom tooling we built around TFC to make it work at our scale: a CLI for bulk review and approval, Slack notifications for pending runs, and automated workspace dependency mapping. Benchling continues to expand both in platform capabilities and geographical reach (close to a thousand Terraform workspaces!). This post will discuss how we leverage AI agents to operate faster and more safely than ever before. We will focus on how we now roll out routine updates to our Kubernetes clusters. What's good for humans is good for agents Before we dive into our AI agent workflows it's important to state what has not changed: Infrastructure as Code (IaC). It turns out the values we embraced to ensure human change management was safe still hold true when AI agents are introduced into the mix: Modular, declarative Terraform: changes at scale are clearly represented in code Changes require authorized human review/approval in a GitHub Pull Request (PR) before merge Terraform Cloud (or any CI/CD) provides a secure environment where approved changes are rolled out automatically Since our customers and their work are our highest priority, it was critical that AI agents be incorporated into this process in the safest manner possible, with a human in the loop. So this is where we landed: AI agents can produce PRs but an authorized engineer must review and approve them. This is a great fit because the majority of effort lies in understanding the required change, making the right code change and testin

## Migrating a JS project from Travis to GitHub Actions

DevFeed: [Migrating a JS project from Travis to GitHub Actions](<https://devfeed.tech/articles/migrating-a-js-project-from-travis-to-github-actions-19083.md>)

Original publisher: [Read original article](<https://httptoolkit.com/blog/migrating-javascript-from-travis-to-github-actions/>)

Author: HTTP Toolkit; Tim Perry

Published: 2020-10-27T11:45:00Z

Content type: tutorial

Language: en

Sources: [HTTP Toolkit](<https://devfeed.tech/sources/http-toolkit.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [js](<https://devfeed.tech/tags/js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [share](<https://devfeed.tech/tags/share.md>), [testing](<https://devfeed.tech/tags/testing.md>), [travis](<https://devfeed.tech/tags/travis.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

The excerpt frames a migration of HTTP Toolkit's TypeScript UI build from Travis CI to GitHub Actions, prompted in part by a Travis backlog and GitHub integration. The existing Travis job pins Node 14, installs dependencies with `npm ci`, and runs `npm test`; tests also require Chrome and XVFB, with setup workarounds for Chrome's sandbox. Native Node extensions need a working native build environment. The author also values reproducing the cloud CI environment locally to diagnose failures caused by differences such as tool versions or leftover build files. The excerpt ends as the author begins consulting GitHub's JavaScript Actions guide, so it does not provide the actual workflow configuration or migration outcome.

### Source excerpt

Travis has been the most popular place to build open-source code for a long time, but the world is moving on. GitHub Actions is modern, tightly integrated with the most popular code hosting platform in the world, flexible, fast, and free (for public repos). Travis has been popular for years though, there's still a lot of projects being built there, including many of HTTP Toolkit's own repos. Last week, I decided to bite the bullet, and start migrating. Travis was having a particularly bad build backlog day, and HTTP Toolkit is entirely open source on GitHub already, so it's super convenient. I've been looking longingly at GitHub Actions builds on other projects for a little while, and I'd already seen lots of useful extensions in the marketplace of drop-in action steps that'd make my life much easier. Unfortunately, I knew very little about GitHub actions, and I already had some Travis configuration that worked. In this post, I want to share how I converted my JavaScript (well, TypeScript) build from Travis to GitHub, so you can do the same. The Goal I decided to start with the simplest Travis setup I had: the HTTP Toolkit UI repo. Here's the previous travis.yml file: dist: xenial sudo: required language: node_js node_js: - '14' install: - npm ci services: - xvfb before_script: - sudo chown root /opt/google/chrome/chrome-sandbox - sudo chmod 4755 /opt/google/chrome/chrome-sandbox script: - npm test addons: chrome: stable There's a few notable things here: I want to build with a specific node version. I need Chrome & XVFB installed for testing with Puppeteer & Karma. There's some existing workarounds (before_script) for Travis.yml in here. The build itself is just npm ci to install dependencies and then npm test. Although not shown here, some of the npm dependencies include native node extensions, and need a working native build environment. One other feature I'd really like, and which I'd strongly recommend for everybody, is the option to run an equivalent CI enviro

## How GitHub Classroom and Travis CI improved students' grades

DevFeed: [How GitHub Classroom and Travis CI improved students' grades](<https://devfeed.tech/articles/how-github-classroom-and-travis-ci-improved-students-grades-69100.md>)

Original publisher: [Read original article](<https://github.blog/developer-skills/career-growth/how-github-classroom-and-travis-ci-improved-students-grades/>)

Author: Vanessa Gennarelli

Published: 2019-02-12T17:00:48Z

Content type: article

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Google Classroom](<https://devfeed.tech/topics/google-classroom.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [career-growth](<https://devfeed.tech/tags/career-growth.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [developer-skills](<https://devfeed.tech/tags/developer-skills.md>), [github-classroom](<https://devfeed.tech/tags/github-classroom.md>), [students](<https://devfeed.tech/tags/students.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### AI overview

Dr. Shane Wilson combined GitHub Classroom with Travis CI to automate testing and grading in a C++ course. Students received feedback each time they pushed code, while repository activity helped him identify students who might need support. He reported spending days or at most a week evaluating assignments instead of four to six weeks, and the module's progression rate rose from 76 to 90 percent.

### Source excerpt

Learn how Dr. Shane Wilson saved time and boosted student performance with the help of GitHub Classroom and Travis CI.

## Give students live feedback and scale your assessment with Travis CI Enterprise

DevFeed: [Give students live feedback and scale your assessment with Travis CI Enterprise](<https://devfeed.tech/articles/give-students-live-feedback-and-scale-your-assessment-with-travis-ci-enterprise-69170.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/the-library/give-students-live-feedback-and-scale-your-assessment-with-travis-ci-enterprise/>)

Author: Vanessa Gennarelli

Published: 2018-10-15T19:00:00Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [github-education](<https://devfeed.tech/tags/github-education.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [practical](<https://devfeed.tech/tags/practical.md>), [students](<https://devfeed.tech/tags/students.md>), [the-library](<https://devfeed.tech/tags/the-library.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### AI overview

Travis CI Enterprise gives participating GitHub Education schools unlimited builds at no additional cost, supporting live feedback and assessment of student projects.

### Source excerpt

This spring, GitHub Education schools have unlimited builds with Travis CI Enterprise

## Travis CI integration now available

DevFeed: [Travis CI integration now available](<https://devfeed.tech/articles/travis-ci-integration-now-available-75135.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2018-05-07-travis-ci-integration>)

Author: admin

Published: 2018-05-08T00:45:20Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [branch](<https://devfeed.tech/tags/branch.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [ci](<https://devfeed.tech/tags/ci.md>), [integration](<https://devfeed.tech/tags/integration.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [project](<https://devfeed.tech/tags/project.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [results](<https://devfeed.tech/tags/results.md>), [share](<https://devfeed.tech/tags/share.md>), [team](<https://devfeed.tech/tags/team.md>), [travis](<https://devfeed.tech/tags/travis.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>), [view](<https://devfeed.tech/tags/view.md>)

### AI overview

GitHub's Checks API integrates with Travis CI to show branch and pull request build results directly on GitHub. The excerpt says teams can view build stages, jobs, results, and associated configuration to assess project health.

### Source excerpt

Checks API now integrates with Travis CI, letting you share the results of your project's branch and pull request builds with your team. View your build's stages, jobs, results, and...

## Dockerized e2e tests

DevFeed: [Dockerized e2e tests](<https://devfeed.tech/articles/dockerized-e2e-tests-27294.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201802/dockerized-e2e/>)

Published: 2018-02-15T00:00:00Z

Content type: tutorial

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Selenium](<https://devfeed.tech/topics/selenium.md>), [Browser Automation](<https://devfeed.tech/topics/browser-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [webDriver](<https://devfeed.tech/topics/webdriver.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [ci](<https://devfeed.tech/tags/ci.md>), [containers](<https://devfeed.tech/tags/containers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [selenium](<https://devfeed.tech/tags/selenium.md>), [testing](<https://devfeed.tech/tags/testing.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>), [webdriver](<https://devfeed.tech/tags/webdriver.md>)

### 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](<https://devfeed.tech/articles/new-milestones-and-features-19406.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/new-milestones-features/>)

Author: Shai Almog

Published: 2017-10-30T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [releases](<https://devfeed.tech/tags/releases.md>), [travis](<https://devfeed.tech/tags/travis.md>)

### 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](<https://devfeed.tech/articles/continuous-deployment-hugo-travis-ci-github-pages-31845.md>)

Original publisher: [Read original article](<https://www.metachris.dev/2017/04/continuous-deployment-hugo--travis-ci-github-pages/>)

Author: Chris Hager

Published: 2017-04-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [Chris Hager](<https://devfeed.tech/sources/chris-hager.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous Deployment (CD)](<https://devfeed.tech/topics/continuous-deployment.md>), [GitHub Pages](<https://devfeed.tech/topics/github-pages.md>), [Hugo](<https://devfeed.tech/topics/hugo.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Git](<https://devfeed.tech/topics/git.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [container](<https://devfeed.tech/topics/container.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [ci](<https://devfeed.tech/tags/ci.md>), [continuous-deployment](<https://devfeed.tech/tags/continuous-deployment.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [github-pages](<https://devfeed.tech/tags/github-pages.md>), [go](<https://devfeed.tech/tags/go.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### 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](<https://devfeed.tech/articles/building-a-64bit-docker-os-for-the-raspberry-pi-3-29463.md>)

Original publisher: [Read original article](<https://blog.hypriot.com/post/building-a-64bit-docker-os-for-rpi3/>)

Published: 2017-03-02T10:28:42Z

Content type: tutorial

Language: en

Sources: [Hypriot](<https://devfeed.tech/sources/hypriot.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Raspberry Pi](<https://devfeed.tech/topics/raspberry-pi.md>), [container](<https://devfeed.tech/topics/container.md>), [Operating system](<https://devfeed.tech/topics/operating-system.md>), [Debian](<https://devfeed.tech/topics/debian.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [boot](<https://devfeed.tech/topics/boot.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [boot](<https://devfeed.tech/tags/boot.md>), [bootloader](<https://devfeed.tech/tags/bootloader.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [ci](<https://devfeed.tech/tags/ci.md>), [containers](<https://devfeed.tech/tags/containers.md>), [debian](<https://devfeed.tech/tags/debian.md>), [docker](<https://devfeed.tech/tags/docker.md>), [github](<https://devfeed.tech/tags/github.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [opensource](<https://devfeed.tech/tags/opensource.md>), [os](<https://devfeed.tech/tags/os.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>), [workshop](<https://devfeed.tech/tags/workshop.md>)

### 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

## Real-time feedback for students using continuous integration tools

DevFeed: [Real-time feedback for students using continuous integration tools](<https://devfeed.tech/articles/real-time-feedback-for-students-using-continuous-integration-tools-69517.md>)

Original publisher: [Read original article](<https://github.blog/developer-skills/github-education/real-time-feedback-for-students-using-continuous-integration-tools/>)

Author: Vanessa Gennarelli

Published: 2017-03-02T00:15:40Z

Content type: tutorial

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>)

Tags: [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [code](<https://devfeed.tech/tags/code.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [developer-skills](<https://devfeed.tech/tags/developer-skills.md>), [developers](<https://devfeed.tech/tags/developers.md>), [github-education](<https://devfeed.tech/tags/github-education.md>), [students](<https://devfeed.tech/tags/students.md>)

### AI overview

The article describes how teachers can use automated tests and Travis CI with GitHub Classroom to give programming students immediate feedback on assignments. It outlines a C++ course workflow in which student repositories are built after each push, helping instructors identify failing tests and focus their grading support.

### Source excerpt

For teachers it can be a challenge to get students the help they need exactly when they get stuck, especially in large courses. But when teachers use an automated testing...

## Best Practices and Common Mistakes with Travis CI

DevFeed: [Best Practices and Common Mistakes with Travis CI](<https://devfeed.tech/articles/best-practices-and-common-mistakes-with-travis-ci-28622.md>)

Original publisher: [Read original article](<https://eng.localytics.com/best-practices-and-common-mistakes-with-travis-ci/>)

Author: Kevin Deisz

Published: 2017-01-10T13:46:39Z

Content type: tutorial

Language: en

Sources: [Localytics](<https://devfeed.tech/sources/localytics.md>)

Topics: [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [build performance](<https://devfeed.tech/topics/build-performance.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [github](<https://devfeed.tech/tags/github.md>), [parallelism](<https://devfeed.tech/tags/parallelism.md>), [speed](<https://devfeed.tech/tags/speed.md>), [testing](<https://devfeed.tech/tags/testing.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### 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](<https://devfeed.tech/articles/setting-up-travis-jekyll-and-github-pages-37366.md>)

Original publisher: [Read original article](<https://muffinman.io/blog/travis-jekyll-and-github-pages/>)

Author: Stanko

Published: 2016-10-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Stanko Tadić](<https://devfeed.tech/sources/stanko-tadic.md>)

Topics: [Jekyll](<https://devfeed.tech/topics/jekyll.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Pages](<https://devfeed.tech/topics/github-pages.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [github](<https://devfeed.tech/tags/github.md>), [github-pages](<https://devfeed.tech/tags/github-pages.md>), [github-personal-access-token](<https://devfeed.tech/tags/github-personal-access-token.md>), [jekyll](<https://devfeed.tech/tags/jekyll.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [security](<https://devfeed.tech/tags/security.md>), [travis](<https://devfeed.tech/tags/travis.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### 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

## 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](<https://devfeed.tech/articles/level-up-github-builds-with-ci-and-code-coverage-28640.md>)

Original publisher: [Read original article](<https://jeroenmols.com/blog/2015/11/13/traviscoveralls/>)

Author: info@jeroenmols.com (Jeroen Mols)

Published: 2015-11-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Jeroen Mols](<https://devfeed.tech/sources/jeroen-mols.md>)

Topics: [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [blogs](<https://devfeed.tech/tags/blogs.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [github](<https://devfeed.tech/tags/github.md>), [tools](<https://devfeed.tech/tags/tools.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>)

### 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?

## semantic-release - @kentcdodds talks to @boennemann

DevFeed: [semantic-release - @kentcdodds talks to @boennemann](<https://devfeed.tech/articles/semantic-release-kentcdodds-talks-to-boennemann-21254.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2015/08/link-semantic-release-talk/>)

Published: 2015-08-18T00:00:00Z

Content type: article

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [version](<https://devfeed.tech/topics/version.md>), [changelog](<https://devfeed.tech/topics/changelog.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [automatically](<https://devfeed.tech/tags/automatically.md>), [based](<https://devfeed.tech/tags/based.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [commit](<https://devfeed.tech/tags/commit.md>), [github](<https://devfeed.tech/tags/github.md>), [npm](<https://devfeed.tech/tags/npm.md>), [process](<https://devfeed.tech/tags/process.md>), [release](<https://devfeed.tech/tags/release.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [talks](<https://devfeed.tech/tags/talks.md>), [tests](<https://devfeed.tech/tags/tests.md>), [travis](<https://devfeed.tech/tags/travis.md>), [version](<https://devfeed.tech/tags/version.md>), [video](<https://devfeed.tech/tags/video.md>), [watch](<https://devfeed.tech/tags/watch.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The excerpt describes semantic-release as automating releases to NPM and other destinations. It determines the semantic version from conventional commit messages, generates a GitHub changelog, and can detect breaking changes from tests failing on Travis. The author says they have not yet watched the interview video.

### Source excerpt

Lorem ipsum dolor sit amet

## How often is the build broken?

DevFeed: [How often is the build broken?](<https://devfeed.tech/articles/how-often-is-the-build-broken-77659.md>)

Original publisher: [Read original article](<https://danluu.com/broken-builds/>)

Published: 2014-11-10T00:00:00Z

Content type: article

Language: en

Sources: [Danluu](<https://devfeed.tech/sources/danluu.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [open-source-projects](<https://devfeed.tech/tags/open-source-projects.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [testing](<https://devfeed.tech/tags/testing.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### AI overview

The author analyzes Travis CI data from 40 popular GitHub projects and finds that many have frequent build failures, while noting that the sample is biased toward projects already attentive to testing. The article argues that broken builds waste contributor time and can drive potential contributors away, and points to tools and practices for keeping builds clean.

### Source excerpt

I've noticed that builds are broken and tests fail a lot more often on open source projects than on "work" projects. I wasn't sure how much of that was my perception vs. reality, so I grabbed the Travis CI data for a few popular categories on GitHub1. For reference, at every place I've worked, two 9s of reliability (99% uptime) on the build would be considered bad. That would mean that the build is failing for over three and a half days a year, or seven hours per month. Even three 9s (99.9% uptime) is about forty-five minutes of downtime a month. That's kinda ok if there isn't a hard system in place to prevent people from checking in bad code, but it's quite bad for a place that's serious about having working builds. By contrast, 2 9s of reliability is way above average for the projects I pulled data for2 -- only 8 of 40 projects are that reliable. Almost twice as many projects -- 15 of 40 -- don't even achieve one 9 of uptime. And my sample is heavily biased towards reliable projects. There are projects that were well-known enough to be "featured" in a hand curated list by GitHub. That's already biases the data right there. And then I only grabbed data from the projects that care enough about testing to set up TravisCI3, which introduces an even stronger bias. To make sure I wasn't grabbing bad samples, I removed any initial set of failing tests (there are often a lot of fails as people try to set up Travis and have it misconfigured) and projects that that use another system for tracking builds that only have Travis as an afterthought (like Rust)4. Why doesn't the build fail all the time at work? Engineers don't like waiting for someone else to unbreak the build and managers can do the back of the envelope calculation which says that N idle engineers * X hours of build breakage = $Y of wasted money. But that same logic applies to open source projects! Instead of wasting dollars, contributor's time is wasted. Web programmers are hyper-aware of how 100ms of extra lat

## Objective-C on Travis-CI

DevFeed: [Objective-C on Travis-CI](<https://devfeed.tech/articles/objective-c-on-travis-ci-25388.md>)

Original publisher: [Read original article](<https://smileykeith.com/2013/04/11/objective-c-on-travis-ci/>)

Author: Keith Smiley

Published: 2013-04-11T22:58:00Z

Content type: tutorial

Language: en

Sources: [Keith Smiley](<https://devfeed.tech/sources/keith-smiley.md>)

Topics: [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [travis-ci](<https://devfeed.tech/tags/travis-ci.md>)

### AI overview

The excerpt describes setting up Travis CI for an Objective-C project: add a `.travis.yml` file at the repository root, enable the GitHub repository in Travis, and share the Xcode scheme with its test target enabled in the build action. It assumes an existing test framework and a public GitHub repository (or a Travis Pro account). For projects with a root-level `Podfile`, Travis automatically runs `pod install`; other projects may need setup commands such as a `before_install` script to fetch submodules and configure dependencies. The author reports that the default Objective-C build script worked for their projects, though some needed extra setup.

### Source excerpt

Recently Travis added support for Objective-C and there for OS X and iOS projects for continuous integration testing. I gather that people have previously done this with self-hosted dedicated Jenkins machines but since Apple is so aggressive about dropping support for previous versions of the OS it seems like a pain to have to replace your build server every few years. Enter Travis, a great hosted continuous integration server that hosts a huge amount of open source projects. I figured with this new support I could host some of my smaller libraries just to set how well it worked. The initial setup process was a bit tedious but I eventually got it to work. Assumtions: You have a test framework already integrated with your project (I like Specta/Expecta) You have your project on Github in a public repository. Travis offers a pro account if you'd rather Steps Create a .travis.yml file in the root of your repository (leading dot is intentional). For many projects a file may just look like: language: objective-c By default Travis runs this script for Objective-C projects I was informed on Twitter that the current script that runs Objective-C projects is actually located here. It was originally created by Justin Spahr-Summers here. This script seems to run my projects without any issue, they just occasionally require more initial setup (we'll get to that). Enable your repository in Travis' settings. From your Travis profile page (after signing in with Github) you should see a list of your repositories, you may have to press 'Sync now', where you can switch on the repository you're planning on adding. Configure your project within Xcode. As I assumed above you already have a test target setup. You do have to do a few things in Xcode to make everything work correctly. Go to 'Manage Schemes' in Xcode. Check the 'Shared' box for the scheme that needs to be run. Click 'Edit...' in the bottom left and go to your build action. On the row of your Tests target check the box in the '