<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>loci on Junpei Kawamoto</title>
    <link>https://www.jkawamoto.info/tags/loci/</link>
    <description>Recent content in loci on Junpei Kawamoto</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>junpei.kawamoto@acm.org (Junpei Kawamoto)</managingEditor>
    <webMaster>junpei.kawamoto@acm.org (Junpei Kawamoto)</webMaster>
    <copyright>&amp;copy; 2016-2017 Junpei Kawamoto</copyright>
    <lastBuildDate>Fri, 06 Jan 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.jkawamoto.info/tags/loci/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Test a test script for remote CI services locally</title>
      <link>https://www.jkawamoto.info/blogs/test-remote-ci-scripts-locally/</link>
      <pubDate>Fri, 06 Jan 2017 00:00:00 +0000</pubDate>
      <author>junpei.kawamoto@acm.org (Junpei Kawamoto)</author>
      <guid>https://www.jkawamoto.info/blogs/test-remote-ci-scripts-locally/</guid>
      <description>Summary You usually employ remote CI services such as Travis CI to automatically test your projects hosted in GitHub. Your tests should be passed in such CI services always because you have made sure your codebase passes the tests before pushing. However, .travis.yml, the configuration file of Travis, sometimes has bugs and your dependency list sometime loses any libraries.
If your codebase fails tests in remote CI services, you need to fix bugs and re-push, and your commit history gets messy.</description>
    </item>
    
  </channel>
</rss>