<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jenkins on Junian Dev</title>
    <link>https://www.junian.dev/tags/jenkins/</link>
    <description>Recent content in Jenkins on Junian Dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>author@junian.dev (Junian Triajianto)</managingEditor>
    <webMaster>author@junian.dev (Junian Triajianto)</webMaster>
    <copyright>Copyright &amp;copy; 2014 - 2026 Junian.dev</copyright>
    
	    <atom:link href="https://www.junian.dev/tags/jenkins/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Xamarin Mobile Apps Continuous Integration and Delivery with Jenkins and HockeyApp</title>
      <link>https://www.junian.dev/dev/xamarin-jenkins-hockeyapp/</link>
      <pubDate>Tue, 30 May 2017 09:38:00 +0000</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/xamarin-jenkins-hockeyapp/</guid>
      <description>&lt;p&gt;Laziness is probably the middle name of every programmer, especially when it comes to doing repetitive (usually) boring stuff, again and again. One of them is building app from latest source code.&lt;/p&gt;
&lt;p&gt;Traditionally, we commit our work, pull our colleague&amp;rsquo;s code, merge them, build the binary file, and send it to testers. Not sure how many times we do that stuff every day.&lt;/p&gt;
&lt;p&gt;Luckily, there is always a solution for that kind of repetitive task, by using Continuous Integration (CI) and Continuous Delivery (CD).&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
