Class BuildIssueChangedPublisher


  • public class BuildIssueChangedPublisher
    extends Object
    Listens on internal events. If it detects event that has possibly changed JIRA issue it will publish new event that is then possibly redistributed outside Bamboo
    • Constructor Detail

      • BuildIssueChangedPublisher

        @Inject
        public BuildIssueChangedPublisher​(com.atlassian.event.api.EventPublisher eventPublisher,
                                          ResultsSummaryManager resultsSummaryManager,
                                          IssueChangedPublisher issueChangedPublisher)
    • Method Detail

      • handleResultsSummaryUpdatedEvent

        @EventListener
        public void handleResultsSummaryUpdatedEvent​(ResultsSummaryUpdatedEvent event)
      • handleChainCompletedEvent

        @EventListener
        public void handleChainCompletedEvent​(ChainCompletedEvent event)
      • handleChainDeletedEvent

        @EventListener
        public void handleChainDeletedEvent​(ChainDeletedEvent event)
      • handleMultipleChainsDeletedEvent

        @EventListener
        public void handleMultipleChainsDeletedEvent​(MultipleChainsDeletedEvent event)
      • handleChainMovedEvent

        @EventListener
        public void handleChainMovedEvent​(ChainMovedEvent event)
      • handleChainResultDeletedEvent

        @EventListener
        public void handleChainResultDeletedEvent​(ChainResultDeletedEvent event)
        This event may generate change from JIRA point of view but doesn't have to. I send it every time simplifying Bamboo side implementation. I prefer not to do any checks that assume specific JIRA side implementation (unless it would generate too many irrelevant events causing performance problems) That way it's more flexible for the future even if something will change on JIRA side.
        Parameters:
        event -