Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Create a Bamboo Event Listener


I'm trying to create a Bamboo event listener for DeploymentFinishedEvent ( with the Atlassian SDK. Unfortunately, the documentation for creating a Bamboo event listener seems to be out of date, as HibernateEventListener is deprecated as of Bamboo 5.6 ( and the alternative that is recommended by the Java Docs is an Annotation.


What is the correct approach for creating an event listener for Bamboo? I see that Alexey Chystoprudov posted this block of code yesterday ( but the technique used doesn't appear to be documented anywhere.

<bambooEventListener key="environmentDependencyListener" 
public class MyListener {
public void onChainCompleted(final ChainCompletedEvent event) {
System.out.println("chain complete ");



Cross-posted this to

1 answer

0 votes
Bill Carreon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 01, 2018 • edited

Hi Jared,

Allow me to summarize the developer community post here so the entire answer is located in one place.


Alexey listed 2 possible options for creating an event listener in his post:


Option 1: Add the following line to the atlassian-plugin.xml

<bambooEventListener key="environmentDependencyListener" 
class="com.test.MyListener"/>Have the class register itself:
public class MyListener {
public void onChainCompleted(final ChainCompletedEvent event) {
System.out.println("chain complete ");


Option 2: Have the code register itself

private final EventPublisher eventPublisher;

private void postConstruct() {

private void preDestroy() {

public void onChainRemoved(@NotNull ChainDeletedEvent chainDeletedEvent) {


Ollitech then offered the following explanation in their post:

You can find more information on the event framework and @EventListener1 annotation.

UNfortunately bamboo docs for the listener module are outdated, and half right (you need to register the listener class) and half wrong (you don't extend any classes). To find events in addition to the ones listed on the docs, you'll need to explore the javadocs to find actual events. I use the full class index for bamboo and just filter for "Event" to see what possible events to listen to.

YOu only need to register 1 event listener in your atlassian-plugin.xml which specifies a class with annotated methods (as seen in the example you shared). You may decide to use multiple classes for clear isolation of responsibility however.

So in short, Alexey was right, and it not fits the more general pattern used across atlassian tools. I have not confirmed, but if using Spring Scanner2 (which I certainly recommend), you may not need to declare <bambooEventListener> at all, and just annottate the class with @Component.


If you have any additional questions or insights please don’t hesitate to reach out.




Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events