# Travis Published articles for Travis. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Branch predictor: How many "if"s are too many? Including x86 and M1 benchmarks! DevFeed: [Branch predictor: How many "if"s are too many? Including x86 and M1 benchmarks!]() Original publisher: [Read original article]() Author: Marek Published: 2021-05-05T22:00:00Z Content type: article Language: en Sources: [Marek Majkowski]() Topics: [x86](), [Cloudflare]() Tags: [architecture](), [article](), [benchmarks](), [blog](), [cloudflare](), [discussion](), [hacker-news](), [travis](), [x86]() ### AI overview The article examines how many conditional branches affect branch prediction, with benchmarks covering x86 and M1 systems. It also points to discussions about BTB behavior, M1 branch-predictor interactions with the iCache prefetcher, and related commentary. ### Source excerpt Branch predictor: How many "if"s are too many? Including x86 and M1 benchmarks! I published an article on Cloudflare blog: Notable discussions mentioning this work: - Looking at BTB behavior and size: a comment on my work from Travis Downs, followed by response from Linus Torvalds. - Discussion on M1 architecture, with fascinating take on branch predictor interactions with iCache prefetcher. - Hacker News commentary ## Migrating a JS project from Travis to GitHub Actions DevFeed: [Migrating a JS project from Travis to GitHub Actions]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2020-10-27T11:45:00Z Content type: tutorial Language: en Sources: [HTTP Toolkit]() Topics: [GitHub Actions](), [JavaScript](), [TypeScript](), [ci](), [Testing](), [Chrome](), [Puppeteer](), [npm](), [chmod]() Tags: [chmod](), [chrome](), [ci](), [cli](), [github-actions](), [js](), [node-js](), [testing](), [travis](), [typescript]() ### AI overview This tutorial explains how to migrate a JavaScript/TypeScript project from Travis to GitHub Actions. It uses an HTTP Toolkit UI repository as an example, covering Node.js version selection, Chrome and XVFB setup for Puppeteer and Karma tests, dependency installation with npm ci, and test execution with npm test. It also discusses reproducing the cloud CI environment locally to debug environment-specific failures. ### 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 ## Validating OAS 3 specification in your CI build DevFeed: [Validating OAS 3 specification in your CI build]() Original publisher: [Read original article]() Published: 2019-02-15T17:29:41Z Content type: tutorial Language: en Sources: [Miro Cupak]() Topics: [OpenAPI Specification](), [Continuous integration](), [YAML](), [GitHub](), [Swagger](), [Testing](), [pull-requests]() Tags: [ci](), [continuous-integration](), [github](), [openapi](), [pull-requests](), [specifications](), [swagger](), [swagger-validator-badge](), [testing](), [travis](), [travis-ci](), [yaml]() ### AI overview This tutorial explains how to validate an OpenAPI 3 specification on every pull request as part of continuous integration. It uses the Swagger Validator Badge tool in Travis CI, building version 2.0.0 locally because hosted support for OpenAPI 3 was incomplete at the time of writing. ### Source excerpt As part of my work on standards under GA4GH, I frequently deal with API specifications, most often written in OpenAPI 3 (OAS 3). The setup is always similar - there's a public GitHub repository containing an OAS 3 YAML file and a few common auxiliary files (.gitignore, LICENSE, CONTRIBUTING.md, and README.md). Reference implementations of... ## Obtaining a URL to a file in a GitHub repository in a Travis CI build DevFeed: [Obtaining a URL to a file in a GitHub repository in a Travis CI build]() Original publisher: [Read original article]() Published: 2019-01-24T22:51:37Z Content type: tutorial Language: en Sources: [Miro Cupak]() Topics: [ci](), [GitHub](), [pull-requests](), [OpenAPI Specification](), [Swagger]() Tags: [ci](), [continuous-integration](), [devops](), [github](), [open-source](), [openapi-specification](), [pull-requests](), [swagger](), [travis](), [travis-ci]() ### AI overview A tutorial explaining how to construct a URL to a repository file in a Travis CI build while accounting for push builds, pull requests from forks, branches, and tags. ### Source excerpt I'm a fan of Travis CI and use it for continuous integration across pretty much all my open-source projects on GitHub. From time to time, I need to obtain a URL to a file in the repository in my build, e.g. to point a particular tool to it, in a way that respects branches as well as pull requests... ## Travis CI Integration DevFeed: [Travis CI Integration]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2018-01-08T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [ci](), [GitHub](), [Emulator](), [Android](), [iOS]() Tags: [android](), [ci](), [emulator](), [github](), [integration](), [ios](), [simulator](), [test](), [travis](), [travis-ci](), [unit-tests](), [workflow]() ### AI overview Codename One added Travis CI support for automatically running unit tests on configured platforms whenever project changes are committed to GitHub. Projects can enable the integration in Codename One settings, push the generated Travis configuration, and activate the project on Travis. ### Source excerpt We've just added support for Travis CI in your Codename One projects. Travis can be set up to automatically test your project (i.e. run unit tests) on a variety of different platforms every time you commit changes to github. There is a wiki page with full documentation of this feature, but the general idea and workflow are: Enable Travis CI for your project via Codename One settings Push your project (including .travis.yml and .travis directory, which are created for you when you enable Travis) to Github. ## 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. ## A 2016 Year-End Update on Work, a JavaScript Meetup, and Projects DevFeed: [A 2016 Year-End Update on Work, a JavaScript Meetup, and Projects]() Original publisher: [Read original article]() Author: Stanko Published: 2016-12-21T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Development](), [JavaScript](), [Open Source](), [Go](), [GitHub Pages](), [Jekyll](), [GitHub]() Tags: [articles](), [blog](), [developer](), [github-pages](), [go](), [javascript](), [jekyll](), [meetup](), [open-source](), [startup](), [travis]() ### AI overview A personal year-end update covering the author's move into a Technology Director role at Work & Co, plans for a Belgrade winter tech meetup, recommended startup articles, and ongoing small projects. The post also notes that the blog is open source and powered by Jekyll, Travis, and GitHub Pages. ### Source excerpt 2016 was quite a ride. I just want to write a couple of random things, to close this year with one last post. Work & Co # Big news here, my company became a part of Work & Co. We're really excited about that, and I'm looking forward to the great stuff we are going to build. Our collaboration goes back for a few years now, it was very productive, and this is a great step forward. My current title is a Technology Director and I'm in charge of a tech team, here in the Belgrade office. Winter Meetup # We are preparing a new tech meetup, this time a bit bigger one, with four speakers. I'll talk about JavaScript, if it is going in the right direction. About it's problems, misunderstandings, fear and hate that are involved around it. Don't worry, I'll talk about the good parts too. All of the presentations include: Five senses in a business performance - Nikola Pantović Go fast with Web Workers - Ivan Nikitović Become more professional developer - Saša Ranisavljević State of a modern JavaScript development - Stanko Tadić (myself) It will probably happen on the first Saturday in February of 2017, but I'll post updates with the exact date and venue. So be sure to come to Work & Co Belgrade Winter Meetup. Few articles I want to share # I rarely find articles that I think are really worth sharing. But there are two that I like a lot. How to Make Wealth Short guide for Startup Software Engineers in 2nd/3rd World Countries The first one is a cliche in the startup world,. In case you haven't read it yet, and you are interested in making a startup, please do. The second one, unfortunately, is not online anymore, but I found it cached, and made a gist copy of it. It is written by a colleague Serbian, here in Belgrade. He really puts some light on how startup scene is totally different here, and in The valley and western world. To me, it was really an eye opener when I first read it. I hope original author won't mind I shared it. Here are links to the original blog, and the cached v ## 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. ## semantic-release - @kentcdodds talks to @boennemann DevFeed: [semantic-release - @kentcdodds talks to @boennemann]() Original publisher: [Read original article]() Published: 2015-08-18T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [changelog](), [npm](), [GitHub]() Tags: [changelog](), [github](), [npm](), [release](), [talks](), [tests](), [travis](), [video]() ### AI overview A short blog post highlights a talk about semantic-release, a tool that automates npm releases, determines semantic versions from conventional commit messages, generates GitHub changelogs, and can detect breaking changes through tests run on Travis. ### Source excerpt Lorem ipsum dolor sit amet ## Objective-C on Travis-CI DevFeed: [Objective-C on Travis-CI]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-04-11T22:58:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Objective-C](), [Continuous integration](), [iOS](), [Xcode](), [Testing](), [GitHub](), [Jenkins](), [Open Source]() Tags: [apple](), [ci](), [configuration](), [continuous-integration](), [dependencies](), [github](), [ios](), [jenkins](), [objective-c](), [open-source](), [self-hosted](), [submodules](), [testing](), [travis](), [travis-ci](), [xcode]() ### AI overview A practical guide to configuring Travis CI for Objective-C projects targeting OS X and iOS. It covers repository setup, the .travis.yml configuration file, Xcode shared schemes and test targets, dependency handling, and additional scripts for projects using CocoaPods or submodules. ### 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 ' ## Raking Podspecs DevFeed: [Raking Podspecs]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-01-04T19:09:00Z Content type: article Language: en Sources: [Keith Smiley]() Topics: [Ruby](), [rubygems](), [Objective-C](), [pull-requests]() Tags: [code](), [dependency](), [libraries](), [lint](), [objective-c](), [pull-requests](), [repo](), [rewrite](), [ruby](), [rubygems](), [tool](), [tools](), [travis]() ### AI overview The article describes automating CocoaPods podspec linting across multiple Ruby versions with rbenv and a Rakefile. ### Source excerpt I spend a decent amount of time these days helping maintain the CocoaPods specs repo by managing pull requests and issues. CococaPods is an awesome dependency manager similar to Rubygems for Objective-C projects. Unfortunately a lot of submitted podspecs haven't been correctly formatted or they're missing required information. CocoaPods has an awesome build in command pod spec lint that allows you to make sure the spec is valid and complete. Understandably people who are new to CocoaPods trying to submit their libraries are unaware of this awesome tool. Therefore when I look through the pull requests, I like to lint them myself (CocoaPods does utilize Travis but unfortunately it can't do everything). Since CocoaPods supports multiple versions of Ruby (1.8.7 and 1.9.3) to be complete ideally you'd lint them on both versions. Tools like RVM and rbenv(my tool of choice) make it easy to quickly switch between different versions of Ruby using .rvmrc and .rbenv-version respectively. As you can probably assume I wanted to automate this. So I wrote a quick Rakefile to do this for me. #!/usr/bin/env rake # NOTE: Must be using rbenv 4.0 to use `system` and `.ruby-version` ## Set your preferred ruby versions $V18 = 'system' $V19 = '1.9.3-p385' $RBENV = '.ruby-version' # The gem to use $GEM = 'cocoapods' task :default => :lint task :c => :clean desc "Lint podspecs on multiple versions of ruby with rbenv" task :lint do if Dir.glob('*.podspec').count < 1 puts "No podspecs in #{ Dir.pwd }" exit end existed = versionFileExists? if existed old_version = currentVersion end # Loop through all podspecs Dir.glob('*.podspec').each do |file| # Loop through ruby versions 2.times do |x| version = x == 0 ? $V18 : $V19 writeVersion(version) puts "Linting #{ file } on Ruby version #{ currentVersion }" puts lint(file) end end # If the dotfile already existed rewrite the original code if existed writeVersion(old_version) else File.delete($RBENV) if versionFileExists? end end desc "Delete all pod