<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipelines on Camping Coder</title><link>https://www.campingcoder.com/tags/pipelines/</link><description>Recent content in Pipelines on Camping Coder</description><generator>Hugo</generator><language>en-US</language><copyright>All rights reserved</copyright><lastBuildDate>Thu, 15 Mar 2018 00:00:00 -0500</lastBuildDate><atom:link href="https://www.campingcoder.com/tags/pipelines/index.xml" rel="self" type="application/rss+xml"/><item><title>Scheduling code deployment with Bitbucket</title><link>https://www.campingcoder.com/2018/03/scheduling-code-deployment-with-bitbucket/</link><pubDate>Thu, 15 Mar 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/03/scheduling-code-deployment-with-bitbucket/</guid><description>&lt;p&gt;Having a deployment pipeline is an awesome thing, it eliminates the mundane task of deploying changes. Really let&amp;rsquo;s face it, if a task is boring or mundane, then there&amp;rsquo;s likely a chance where a mistake could happen. Sometime though there&amp;rsquo;s a need to re-deploy, or at least deploy code at a certain time, and that&amp;rsquo;s where an overlooked feature in Bitbucket pipeline comes in which is simply called &lt;strong&gt;Schedules&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;&lt;figure class="image-figure"&gt;&lt;img src="https://www.campingcoder.com/post/20180315-bitbucket-pipelines-scheduled-runs-2.png" alt="Schedule button" loading="lazy" decoding="async"&gt;&#10; &#10; &#10; &lt;figcaption&gt;Schedule button&lt;/figcaption&gt;&#10; &#10; &#10;&lt;/figure&gt;&#10;&lt;/p&gt;</description></item><item><title>Automated code deployment with Bitbucket and Docker</title><link>https://www.campingcoder.com/2018/01/automated-code-deployment-with-bitbucket-and-docker/</link><pubDate>Thu, 11 Jan 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/01/automated-code-deployment-with-bitbucket-and-docker/</guid><description>&lt;p&gt;You&amp;rsquo;ve probably heard of Docker, but don&amp;rsquo;t have the time needed to learn or implement it - you probably also want to start automating your builds, because who likes to deploy code? In this post, we&amp;rsquo;ll cover using Docker to deploy code using Bitbucket Pipelines. It will be high level on what docker is and enough to either use someone else&amp;rsquo;s Docker image or build your own - without needing to install Docker on your machine. We will then use that image to deploy our projects source code using Bitbucket Pipelines.&lt;/p&gt;</description></item></channel></rss>