-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: NXFT-1.7.24
-
Fix Version/s: NXFT-1.7.25, NXFT-1.7.26, NXFT-1.8
-
Component/s: nuxeo-ftest
-
Tags:
-
Sprint:DevOps-13
Cleanup is currently only handled on databases using the default configuration:
Excerpt from nuxeo-ftest.xml:
<target name="mongodb-dbdrop" depends="_init,setup-mongodb-driver" if="maven.profile.mongodb"> <echo level="info">Dropping database named '${nuxeo.mongodb.dbname}' on '${nuxeo.mongodb.server}'</echo> <if> <equals arg1="${nuxeo.mongodb.server}" arg2="localhost:27017" /> <then> <exec executable="mongo"> <arg line="${nuxeo.mongodb.dbname} --eval 'db.default.remove({})'" /> </exec> </then> </if> </target>
echo line added with NXBT-1203 shows the following output on https://qa.nuxeo.org/jenkins/job/Deploy/job/IT-nuxeo-master-tests-cap-tomcat-mongodb/, causing NXP-19973:
04:15:42 cap-webdriver-tests.mongodb-dbdrop: 04:15:42 [INFO] [echo] Dropping database named 'dbjabba2' on '172.17.0.1'
172.17.0.1 != localhost:27017 ==> no cleanup
Maybe options with --host and maybe --port could be used in the command line for remote instances cleanup
- is required by
-
NXBT-1427 Properly cleanup MongoDB database at test startup
- Resolved
-
NXP-19973 Fix MongoDB integration test ITDomainTest
- Resolved
-
NXP-20530 Fix mongodb webdriver tests
- Resolved
-
NXBT-941 Enable mongodb configuration on CI
- Resolved
-
NXBT-1432 Fork tools-nuxeo-ftest 1.7 for Nuxeo 7.10
- Resolved
-
NXBT-1203 Add info logs when cleaning mongo database
- Resolved