HI Mike: I completed to refine our CI configuration to follow Ramy's comments. Does any missed or other attention I need respect? [1] Add "export DEVSTACK_GATE_TEMPEST_REGEX=volume" to verify all cinder volume testing. [2] Add each service configuration in the log. http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds vm-tempest-cinder-ci/5100/logs/etc/ [3] Add email alert when the devstack build failed to instead of you notify to me. [4] Integrate VMware snapshot revert feature in the Jenkins master to clean CI slave machine OS environment that avoid the devstack building failed due to previous devstack garbage configuration. [5] Latest CI result for you reference. http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds vm-tempest-cinder-ci/5100/logs/ http://download.prophetstor.com/prophetstor_ci/ [6] Logs need to be browsable online. Add Rewrite module and rule in the apache configuration. my gerrit account: prophetstor-ci gerrit account email: prophetstor.ci at prophetstor.com Many thanks. -----Original Message----- From: Mike Perez [mailto:thingee at gmail.com] Sent: Friday, August 14, 2015 11:41 PM To: Rick Chen <rick.chen at prophetstor.com> Cc: openstack-dev at lists.openstack.org Subject: Re: [cinder] [third-party]RE: [OpenStack-Infra] ProphetStor CI account On 09:44 Aug 14, Rick Chen wrote: > HI Mike: > Sorry again, I already add email alert agent in our CI Jenkins server > to capture each failed build result. > [1] - > http://lists.openstack.org/pipermail/third-party-announce/2015-June/00 > 0192.h > tml > [2] - > http://lists.openstack.org/pipermail/third-party-announce/2015-June/00 > 0193.h > tml > Solution 1: Our Jenkins client machine is vmware machine, I already > add snapshot revert script in the Jenkins Job script. Each git review job > trigger the client will revert to clean environment > to solve this problem. > Solution 2: I don't know whiched changed to make keystone "unable to > import pastedeploy". So I try to uninstall python-pastedeploy package > in the local to solve some > issue about unable to build devstack issue. > Sorry again to disturb you. Rick, I looked at your CI results directory [1], but it looks like the last time this ran was on July 28th according to the last modified dates. This should be actively running even if you account is disabled from leaving comments, so I can verify from the logs things are running fine again. In addition, see Ramy's comments with issues with the CI [2]. [1] - http://download.prophetstor.com/prophetstor_ci/?C=M;O=A [2] - http://lists.openstack.org/pipermail/openstack-infra/2015-August/003057.html -- Mike Perez