Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
34 lines (34 sloc) 2 KB
<meta name="subtitle" content="Notifications" />
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta name="keywords" content="buildmaster, manual" />
<meta name="sequence" content="500" />
Event listeners are useful for monitoring the actions and operations that occur in deployment plans and pipelines in BuildMaster.
Event Listeners trigger certain actions or tasks (such as sending an email) once the specified event occurs.
BuildMaster has a handful of common built-in event listeners.
<p> <img class="screenshot" src="/resources/documentation/buildmaster/event-listeners.png" alt="Built-in Event Listeners" /></p>
Event listeners can be added either as a post deployment step in a <a href="/docs/buildmaster/verification/pipelines">pipeline</a> or specific to user via the <em>My Event Listener</em> user drop down.
<img class="screenshot" src="/resources/documentation/buildmaster/myevent-listeners.png" alt="My Event Listener" />
<h2 id="example" data-title="Example">Real-world example</h2>
Organizations often use event listeners when a specific person has ownership of an application or group of applications.
In this scenario, the owner of the application would receive an email when a build has been successfully deployed to production.
<p> <img class="screenshot" src="/resources/documentation/buildmaster/listener-deployed.png" alt="Individual Listener Example" /></p>
<div class="attention">
<p>The <strong>Email Notification: Approval Required</strong> event listener triggers on pipeline stage <em>completion</em>, not the start of a new pipeline stage. Because of this, when filtering to a specific pipeline stage, the name of the stage <em>before</em> the approval gate should be used, not the stage that is blocked by the gate.</p>
You can’t perform that action at this time.