I've got an update on this, but no resolution yet. To give you some context (given you've asked how this has happened 3 times) New
Relic were the very first add-on in the Marketplace and as a result
there has been a lot of gnarly code very specific to their
implementation. On their side they've also had to . And as you've
gathered unfortunately much of it was not well tested. We've been
working with New Relic all year to finally fix that, and we've moved
them across to the standard API that all other add-ons and most PaaS
providers now adhere to. Any new customers since May have been on that
new integration so we've been testing it out for 6 months. The final
part of that process was to remove customers on the legacy integration
and that occurred as part of the migration onto the new pricing we
announced at the start of this month.
It's only after this migration we realized there was no support for deploy notifications.
New customers since may had never been exposed to the feature so
didn't notice it was missing, and it appears none of the legacy
customers we tested with in October noticed it was missing either. To
rectify the situation we've had to try and build this feature out in
the Add-ons API. That's been documented and deployed, and we're now
working with New Relic to help their engineers implement it as soon as
they possibly can.
这应该是自动发生的,但是NewRelic部署跟踪与Heroku的集成从11月1日开始就被破坏了
我有一张关于这个问题的支持票,它应该在下周的某个时候修复。在
编辑(2013年11月23日):
Heroku承认这是一个由NewRelic插件大修引起的bug。以下是他们在我的支持票上说的根本原因:
我不认为您可以查看我的支持票证,但如果您提交自己的票证,欢迎您与Heroku一起参考:
https://help.heroku.com/tickets/102722
编辑(2014年6月1日):
NewRelic/Heroku似乎已经修复了它们的集成,这样部署就可以被成功跟踪了。这似乎在2014年1月2日之前生效。在
相关问题 更多 >
编程相关推荐