未加星标

Turning deployment tracking upside down

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二03 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏

Thomas Ardal, February 8, 2017

In September last year, we released the first add-on for elmah.io:Deployment Tracking. In the time passed, we've talked with quite a few users, that didn't understand the associations between logs, organizations and deployments. When evaluating the launch of the add-on, I can see that deployment tracking is simply too hard to set up. Needing to both call the deployments endpoint and decorating all messages with a version number, isn’t possible or requires too much work in most scenarios. Today we are turning things upside down, which should make a lot of the WTF’s go away.


Turning deployment tracking upside down

When creating a new deployment through thedeployments endpoint, all messages automatically inherit this version. This means that you will no longer need to decorate each message with a version string. The option is still there and elmah.io will use any version number set on the message over the recent version created through the API. Another issue that a lot of you have had is, that deployments don’t show up until the first message with that version is logged. Since every message automatically gets a version going forward, this is no longer a problem either. As soon as the deployment is created through the API, the version is shown on the UI. Even deployments without any errors are shown, which should help you feel good about yourself, releasing bug free software :)

When creating a new deployment, the deployment is shown on all logs on the organization as default. While this may be the desired behavior when releasing every piece of your application as a whole, it’s not when building and releasing microservices individually. To accommodate that process, we’ve added a new property name logId on each deployment. Setting a log ID on a deployment, binds the new deployment to a specific log. This means that the new deployment will show up on a single log only. This approach is the solution to choose, if you have multiple services, released individually with each one log on elmah.io.

I hope that the changes to deployment tracking, will make the feature much easier to set up and use. The Set Up Deployment Tracking documentation has been fully updated and new versions of the integrations forVSTS andOctopus are available. Let us know through the support, if you want to trial Deployment Tracking.

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

分页:12
转载请注明
本文标题:Turning deployment tracking upside down
本站链接:http://www.codesec.net/view/531336.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(41)