<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CI on iMil.net</title>
    <link>http://imil.net/blog/tags/ci/</link>
    <description>Recent content in CI on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 01 May 2020 16:25:17 +0200</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/ci/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Publish Binary Releases on Gitlab</title>
      <link>http://imil.net/blog/posts/2020/binary-releases-on-gitlab/</link>
      <pubDate>Fri, 01 May 2020 16:25:17 +0200</pubDate>
      <guid>http://imil.net/blog/posts/2020/binary-releases-on-gitlab/</guid>
      <description>&lt;p&gt;I switched to &lt;a href=&#34;https://gitlab.com&#34;&gt;Gitlab&lt;/a&gt; when &lt;em&gt;Github&lt;/em&gt; was bought by &lt;em&gt;Microsoft&lt;/em&gt;. Call me extremist, stupid, and all the names you like, I personally felt the need to do it.&lt;br&gt;&#xA;And quite honestly, I&amp;rsquo;m pretty happy with that choice, &lt;em&gt;Gitlab&lt;/em&gt; is an incredibly useful suite, we use the community version at work and would never go back. But there&amp;rsquo;s one thing that&amp;rsquo;s pretty annoying with &lt;em&gt;Gitlab&lt;/em&gt;, their documentation organization. Honestly it&amp;rsquo;s like they &lt;strong&gt;don&amp;rsquo;t&lt;/strong&gt; want you to figure out how to do things. It&amp;rsquo;s often split into tens of various links and you end up reading issues discussions without really knowing if the feature you&amp;rsquo;d like is implemented or just an idea at that point.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Gitlab CI caching for Go projects</title>
      <link>http://imil.net/blog/posts/2019/gitlab-ci-caching-for-go-projects/</link>
      <pubDate>Sat, 07 Dec 2019 10:50:14 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2019/gitlab-ci-caching-for-go-projects/</guid>
      <description>&lt;p&gt;The reference documentation when it comes to couple &lt;em&gt;golang&lt;/em&gt; and &lt;em&gt;continuous integration&lt;/em&gt; in &lt;a href=&#34;https://gitlab.com&#34;&gt;Gitlab&lt;/a&gt; is &lt;a href=&#34;https://about.gitlab.com/blog/2017/11/27/go-tools-and-gitlab-how-to-do-continuous-integration-like-a-boss/&#34;&gt;this one&lt;/a&gt;, it&amp;rsquo;s well put, easy to read and pretty accurate. Except for the &lt;code&gt;caching&lt;/code&gt; part, or at least nowadays with &lt;a href=&#34;https://github.com/golang/go/wiki/Modules&#34;&gt;go modules&lt;/a&gt;. This is what happens when a commit is pushed with the &lt;code&gt;.gitlab-ci.yml&lt;/code&gt; given as an example in that document:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-plaintext&#34; data-lang=&#34;plaintext&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;131 Creating cache default...&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;132 WARNING: /apt-cache: no matching files&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;133 WARNING: /go/src/github.com: no matching files&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;134 WARNING: /go/src/gitlab.com: no matching files&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;135 WARNING: /go/src/golang.org: no matching files&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;136 WARNING: /go/src/google.golang.org: no matching files&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;137 WARNING: /go/src/gopkg.in: no matching files&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;And as a matter of fact, the cache is empty for next stage.&lt;/p&gt;</description>
    </item>
    <item>
      <title>From GitLab CI to Docker Hub</title>
      <link>http://imil.net/blog/posts/2018/from-gitlab-ci-to-docker-hub/</link>
      <pubDate>Sun, 04 Nov 2018 09:24:59 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2018/from-gitlab-ci-to-docker-hub/</guid>
      <description>&lt;p&gt;With all the noise around those topics I would have imagined this one had been covered thousands of time, yet I did not find a single complete resource on this subject which I found to be a basic building block: pushing docker images from &lt;a href=&#34;https://about.gitlab.com/product/continuous-integration/&#34;&gt;GitLab CI&lt;/a&gt; to the &lt;a href=&#34;https://hub.docker.com/&#34;&gt;Docker Hub registry&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;There&amp;rsquo;s actually an opened issue on &lt;a href=&#34;https://github.com/docker/hub-feedback/issues/334&#34;&gt;Docker GitHub&lt;/a&gt;&amp;rsquo;s that&amp;rsquo;s sitting there for 3 years, and it really feels more like a political / strategic / commercial issue than a technical one. Point being, there&amp;rsquo;s no straightforward integration between &lt;em&gt;GitLab.com&lt;/em&gt; and &lt;em&gt;Docker Hub&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
