Univention Bugzilla – Bug 31785
App tests in jenkins
Last modified: 2013-11-19 06:43:16 CET
Currently we start an UCS autotest environment in jenkins. We should also be able to start a similar environment which installs the app.
I've added the following jenkins jobs: - UCS 3.1 App Autotest MultiEnv - UCS 3.1 App Autotest SingleEnv (S4 Master) - UCS 3.2 App Autotest MultiEnv - UCS 3.2 App Autotest SingleEnv (S4 Master) It lacks jobs for the App update.
The ucs-test-udm tests should be re-checked which one should be tagged with apptest.
(In reply to Stefan Gohmann from comment #2) > The ucs-test-udm tests should be re-checked which one should be tagged with > apptest. Done. I've added more UCS 3.1 to UCS 3.2 upgrade projects in jenkins: - UCS 3.1 to 3.2 Autotest MultiEnv - UCS 3.1 to 3.2 App Autotest Update MultiEnv Both projects upgrade from UCS 3.1 to UCS 3.2. The project 'UCS 3.2 App Autotest MultiEnv' uses testsing and appcenter.test and can be used now. 'UCS 3.2 App Autotest Update MultiEnv' uses the normal appcenter and that will currently fail, but it can be used after the 3.2 release.
No changelog entry needed.
Jenkins projects okay
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".