持续集成有时候成了一种固定的模式后，就难以摆脱定式思维，其实我们还有很多可优化的空间。

习以为常的CI流程

我们通常习惯的CI模式基本上如下图所示，运行于Jenkins，开发基于Maven Spring AngularJS等。

](/images/2014/09/Untitled-Diagram-1.png)

各个步骤的用途如下：

• BUILD & UNIT TEST：构建和单元测试，生成后续步骤所需要的artifacts。
• INTEGRATION TEST：集成测试外部依赖。
• END TO END TEST：有时候称之为Functional Test，测试整个系统的功能，通常运行于Windows+Jetty环境运行。成功后进行部署。
• DEV ENV：开发人员的测试环境，运行于Linux+Tomcat环境。
• SYS ENV：测试人员的环境，运行于Linux+Tomcat环境。
• UAT ENV：通常是business的人进行用户验收测试，运行于Linux+Tomcat环境。

这样的步骤确保了在END TO END TEST之后的代码都是已经测试过，品质量好的代码。但我们还是发现了其中存在的若干问题。

问题一：DEV环境通常闲置

在我经历的两个项目中，开发人员一般都在本地进行调试好了以后，不会在DEV环境再进行调试。DEV环境的唯一用途恐怕就是测试部署是否正常。所以一般情况下都闲置，利用率较低。

问题二：END TO END测试的环境和真实产品环境不匹配

在目前我们的END TO END TEST阶段，主要是用本地的Jetty来运行测试，整个测试过程都是在CI的Windows服务器上进行，和真实环境中的Linux+Tomcat环境还是有差异。由于环境的差异，虽然测试可能通过，但还是可能遗留一些和环境相关的问题。

问题三：END TO END测试出错后，不容易找到问题来源

由于END TO END通常都是比较脆弱的环境，第三方的依赖的不稳定和测试工具的不稳定都很容易使之失败。失败后，开发人员通常会查看Jenkins上的日志，然后分析原因。然而这些原因非常难找，例如Protractor的Stack就基本上没太大用户，assert失败后就只能靠猜测。对于很多概率性的问题或者本地环境没有的问题，需要反复的checkin代码进行尝试，更难进行调试。

另外END TO END处于比较后期，一旦发现问题需要修改某些代码然后在进行测试，将会变得异常的漫长。

解决方案：重新布置CI流程

我们仅仅需要做一点点小的修改，将DEV环境移到END TO END之前，就能解决上述的问题

和之前的CI流程相比，DEV会在集成测试之后，直接进行部署。END TO END的测试脚本将会指向于DEV环境进行测试而不是之前的本地Jetty环境。

解决的问题

• 问题一：DEV环境通常闲置。

DEV环境将作为END TO END环境的测试对象，利用率更高。

• 问题二：END TO END测试的环境和真实产品环境不匹配

DEV环境运行于和的Production一样的环境，END TO END测试更为真实可靠。

• 问题三：END TO END测试出错后，不容易找到问题来源

DEV环境可以直接访问，并且已经部署，出错后，可在本地将END TO END测试指向DEV环境，进行测试。如果是测试代码问题，修改后马上可以重新测试；如果是产品代码的问题，修改提交后只需要重新单元测试及集成测试即可，速度比之前会更快。

带来的问题

这样做当然也带来一个问题：对比之前，此时的DEV环境将不是可靠的一个环境。但DEV环境本来不是给开发人员玩的环境么？所以我个人认为这不是一个问题，我将其命名为TEST DEV ENV以便和之前的DEV ENV进行区分。

I was thinking for a long time to move my blog back to Wordpress. I tried ghost blog but found it was at beginning stage and not mature to use, although the markdown feature seems very attractive. Now Wordpress can write blog using markdown too.

It took me a day to move it back. One reason is I couldn’t import markdown to Wordpress easily. It was lucky that I had a full backup of the database at Feb, 2014. Another reason is that I’d like to try some new technology, yes, docker.

I have being using linux server for several years as playground. One major problem I faced before was after a long time running, the server was installed a lot of softwares that were not needed. “apt-get remove” could not remove all the files totally. I tried vagrant but it is at machine level and too heavy. Then I found docker. It is a tool to address this problem. Docker images could be removed or installed easily. You can even have a base image then install and remove any software without damage host.

Installation of docker is supported by most major linux operation, you can find them at docker’s main site.
To install a wordpress on docker, it is quite easy.

mkdir -p /docker/data/wordpress/db
mkdir -p /docker/data/wordpress/site
docker run --name wordpress-mysql -e MYSQL_ROOT_PASSWORD=mypassword -v /docker/data/wordpress/db:/var/lib/mysql -d mysql
docker run --name wordpress --link wordpress-mysql:mysql -p 80:80 -v /docker/data/wordpress/site:/var/www/html -d wordpress

After several minutes, it is done. You can visit localhost to setup the site.

NOTICE: you must mount the volume to your host’s directory to keep data, otherwise all the data will lost after you delete container.

Enjoy.

UPDATED: Another way is to install using docker, see here

看了一下GitLab的安装方法，就被打败了，后来发现了一个官方推荐的方法

GitLab packages (beta) These packages contain GitLab and all its depencies (PostgreSQL, Redis, Nginx, Unicorn, etc.). They are made with omnibus-gitlab that also contains the installation instructions. These packages currently support a reduced selection of GitLab’s normal features. For instance, it is not yet possible to create/restore application backups or to use HTTPS.

GitLab virtual machine images contain an operating system and a preinstalled GitLab. They are made with GitLab Packer that also contains the installation instructions.

https://gitlab.com/gitlab-org/gitlab-ce/blob/master/README.md#installation

如果是Ubuntu的话，仅需要安装一个package就可以了：

https://www.gitlab.com/downloads/

如果需要改变GitLab的port，编辑：

/var/opt/gitlab/nginx/etc

中的listen即可。

初始密码在这里找到

After the steps below your GitLab instance should reachable over HTTP, and have an admin user with username root and password 5iveL!fe.

ngGrid is a powerful grid system by AngularJS. But when binded data is empty, there’s no options to let ngGrid show any messages inside the grid.

I googled and found an issues here:
https://github.com/angular-ui/ng-grid/issues/496
He provides us a directive for us to use. I tried that but his code is not good. I wrote my own:

angular.module("grid.ext", []).directive('showEmptyMsg', function($compile, $timeout) {
    return {
        restrict : 'A',
        link : function(scope, element, attrs) {
            var msg = (attrs.showEmptyMsg) ? attrs.showEmptyMsg : 'Nothing to display';
            var template = "<div class='no-results-msg'>" + msg + "</div>";
            var tmpl = angular.element(template);
            $compile(tmpl)(scope);
            scope.$watch('gridData', function() {
                if (_.size(scope.gridData) === 0) {
                    element.find('.ngViewport').append(tmpl);
                } else {
                    element.find(tmpl).remove();
                }
            });
        },
        scope : {
            gridData : '='
        }
    };
})

And you could use it like this:

<div class="gridStyle" ng-grid="gridOptions" show-empty-msg="No Results Found" grid-data="myGridData">
</div>

前一篇文章提到了Chrome提供了远程inspect WebView的功能，给Cordova的程序开发提供了很多的便利。

可是用了没多久就遇到了一现象，点了inspect以后弹出一个空窗口，无法调试。试过重启手机、电脑、重装Chrome，似乎都不管用，偶尔能够用一会儿。

后来用了GoAgent发现了一个秘密，工具会访问chrome-devtools-frontend.appspot.com:443这个地址，但由于伟大的长城的存在，这个地址有时候会无法访问，所以会弹出一个空窗口了。

解决方法就是用代理访问，就可以了。