<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to build when a change is pushed to Bitbucket	</title>
	<atom:link href="https://www.scmgalaxy.com/tutorials/build-when-a-change-is-pushed-to-bitbucket/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scmgalaxy.com/tutorials/build-when-a-change-is-pushed-to-bitbucket/</link>
	<description>A Platform for Software Engineers</description>
	<lastBuildDate>Fri, 02 Jan 2026 11:36:26 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>
		By: Aanya		</title>
		<link>https://www.scmgalaxy.com/tutorials/build-when-a-change-is-pushed-to-bitbucket/#comment-1024</link>

		<dc:creator><![CDATA[Aanya]]></dc:creator>
		<pubDate>Fri, 02 Jan 2026 11:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.scmgalaxy.com/tutorials/2017/08/01/build-when-a-change-is-pushed-to-bitbucket/#comment-1024</guid>

					<description><![CDATA[Awesome tutorial! Triggering automated builds when code is pushed to Bitbucket is a core practice in modern CI/CD workflows — it eliminates manual polling and ensures your integration and test processes run immediately after changes are committed. To achieve this with Jenkins, you typically install the Bitbucket Plugin, configure a webhook in your Bitbucket repo pointing to your Jenkins &lt;code&gt;bitbucket-hook&lt;/code&gt; endpoint, and enable the &lt;strong&gt;Build when a change is pushed&lt;/strong&gt; trigger in your job configuration. Make sure your webhook targets the correct job URL (including the trailing “/”) and that the repository push event is selected, because without that the build may not trigger even if Bitbucket returns a 200 response. This setup helps teams get fast feedback on code quality and accelerates delivery cycles.]]></description>
			<content:encoded><![CDATA[<p>Awesome tutorial! Triggering automated builds when code is pushed to Bitbucket is a core practice in modern CI/CD workflows — it eliminates manual polling and ensures your integration and test processes run immediately after changes are committed. To achieve this with Jenkins, you typically install the Bitbucket Plugin, configure a webhook in your Bitbucket repo pointing to your Jenkins <code>bitbucket-hook</code> endpoint, and enable the <strong>Build when a change is pushed</strong> trigger in your job configuration. Make sure your webhook targets the correct job URL (including the trailing “/”) and that the repository push event is selected, because without that the build may not trigger even if Bitbucket returns a 200 response. This setup helps teams get fast feedback on code quality and accelerates delivery cycles.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
