Hi Mark, This bugfix will be included in v6.1.11 due out this Friday. Thank you for your patience. Thanks, -John

Please disable the "Overwrite Package" permission in Admin > Tasks. Then, you will get "Package Already Exists" error

Generally, you "subscribe" to a feed to get notifications; however, there will be a "webhook" feature coming soon that will allow you to send webhook notifications to other tools. We will be posting more information about it soon... stay tuned.

Hello Glenn, The payload will contain: Event_Code (BLDCPP) Event_Description (Build Promotion Completed) Release_Number Build_Number PipelineStage_Name For other types of event listeners, Event_Code and Event_Description are always included and the rest of the fields are from Event Details in the event log for that event type.

I agree whoever owns the event listener, should get the email. What I mean is the default email address doesn't seem to work. E.g., ideally, if I create a event listener, and expect that I should be the one who owns the listener, therefore gets the email, without explicitly putting in my email address to the box again. Currently, I'd have to enter my email address again to get the email, that's kind of unexpected.

There is an open issue with this, [BM-2273] that should be addressed in an upcoming release.

This is working as designed*, as a user can still approve the package even if there was a failed target. We have been thinking of ways to improve this (events / notifications in general, across the products), and will likely add something a lot better on the roadmap. [*] which is not to say the design needs work :)

This would require creating an after-push adapter using the sdk. Several folks have done this in their own instances, but we currently don't hav ea tutorial for how exactly to write one;, but the classes should be fairly self-explanatory to assist with this.

For reference, I have logged this issue as BM-1636, it should likely be included in the v4.4.7 maintenance release.

I'm sorry, I'm an idiot. I had chosen a long name for the application, so the "succeeded" or "failed" part of the subject line was cutting off in my email client. Sorry to waste your time.

One thing we could do is modify the "Execution Complete Notifier" to send a notification out when a warning occurs. There is currently an option to send the notification only on failure. Would that be helpful?

Not currently; but you could use a combination of actions (Generate RElease Notes, SEnd Email) to accomplsih a similar effect.

Looks like this is a bug in the text :-) Should be "," separated.