Univention Bugzilla – Bug 35148
Jenkins jobs for UCS 4
Last modified: 2014-11-26 06:55:40 CET
We should add jenkins jobs for UCS 4: * Autotest: - UCS 3.2 to 4.0 Autotest MultiEnv see "UCS 3.1 to 3.2 Autotest MultiEnv" as example - UCS 4.0-0 Autotest MultiEnv see "UCS 3.2-2 Autotest MultiEnv" as example * App Center - UCS 3.1 to 3.2 App Autotest Update MultiEnv see "UCS 3.1 to 3.2 App Autotest Update MultiEnv" as example - UCS 4.0 App Autotest MultiEnv see "UCS 3.2 App Autotest MultiEnv" as example - UCS 4.0 App Autotest Update MultiEnv see "UCS 3.2 App Autotest Update MultiEnv" as example The pyckage test/ucs-ec2-tools should be migrated to UCS 4. Please consider the package migration list: https://hutten.knut.univention.de/mediawiki/index.php/UCS-4.0_Univention_Package_Update
I've already added <http://jenkins.knut.univention.de:8080/job/UCS-4.0-0%20Release%20Notes/> to also built the Release notes for UCS-4.0.
Added the following projects and adapted the belonging scripts inclusive the names if needed: # UCS 3.2 to 4.0 Autotest MultiEnv autotest-07*.cfg # UCS 4.0-0 Autotest MultiEnv autotest-09*.cfg # UCS 4.0 App Autotest MultiEnv autotest-10*.cfg # UCS 3.2 to 4.0 App Autotest Update MultiEnv autotest-11*.cfg # UCS 4.0 App Autotest Update MultiEnv autotest-12*.cfg The projects are not activated yet. You will find them under the tab "Alle" at th jenkins overview.
(In reply to Stefan Gohmann from comment #0) > The package test/ucs-ec2-tools should be migrated to UCS 4. Please consider > the package migration list: > https://hutten.knut.univention.de/mediawiki/index.php/UCS-4. > 0_Univention_Package_Update REOPEN: * There is still a python2.6 hashbang * debian/compat is still 7 instead of 9 * no XS-Python-Version / no python-support
* version number not increased
# did not changed hashbang in ./examples/jenkins/utils/schoolinstaller.py, because jenkins still use Python 2.6 but adapted some other files: # debian/compat: 7 --> 9 # debian/control: add XS-Python-Version: 2.6 2.7 # debian/rules: dh $@ --> dh $@ --wtih python_support # debian/changelog: add new entry with updated version number # updated the copyright
I adapted the amis to a newer Version # AMI: Univention Corporate Server (UCS) 4.0 (test image) - ami-beda04c9 - UCS 4.0-0 Autotest MultiEnv (autotest-09*.cfg) - UCS 4.0 App Autotest MultiEnv (autotest-10*.cfg) - UCS 4.0 App Autotest Update MultiEnv (autotest-12*.cfg) # AMI: Univention Corporate Server (UCS) 3.2 (official image) rev. 4 - ami-3c34e84b - UCS 3.2 to 4.0 App Autotest Update MultiEnv autotest-11*.cfg - UCS 3.2 to 4.0 Autotest MultiEnv autotest-07*.cfg # I also deactivated the following line in all *.cfg-files ~/ec2/scripts/activate-3.2-errata-test-scope.sh /root/ expect in the autotest-07* files because they don't have this line ;)
Please set the server role for master systems in the profile: server/role="domaincontroller_master" and cleanup the sources.list (Bug #35636) before setup_join is started: echo >/etc/apt/sources.list
Added the server role and cleaned up the source list for # UCS 4.0-0 Autotest MultiEnv (autotest-09*.cfg) to test the changes. The Jenkins job failed because the machines got stuck during rebooting.
(In reply to Alexander Kramer from comment #8) > Added the server role and cleaned up the source list for > # UCS 4.0-0 Autotest MultiEnv (autotest-09*.cfg) to test the changes. > > The Jenkins job failed because the machines got stuck during rebooting. I think we should skip the reboot and create a new bug report for the failed reboot.
I added a bug for the rebooting problem: Bug 35733 - Jenkins failed reboot Added sources.list cleanup for all roles in: - autotest-09* UCS 4.0-0 Autotest MultiEnv - autotest-10* UCS 4.0 App Autotest MultiEnv - autotest-12* UCS 4.0 App Autotest Update MultiEnv Added server/role="domaincontroller_master" for all master profiles in: - autotest-07* UCS 3.2 to 4.0 Autotest MultiEnv - autotest-09* UCS 4.0-0 Autotest MultiEnv - autotest-10* UCS 4.0 App Autotest MultiEnv - autotest-11* UCS 3.2 to 4.0 App Autotest Update MultiEnv - autotest-12* UCS 4.0 App Autotest Update MultiEnv
During the autotest-090 the instance got stuck while running the test. Stefan ask me do add a bug for this: # Bug 35741 - Test 25reconnect_uldap failed in jenkins
OK: r51362 51367 51368 51369 51376 51395 51396 51398 51401 51403 51412 51421 51424 51431 51433 51434 51435 51436 51438 51470 52074 52929 52953 53111 53112 OK: grep -L server/role examples/jenkins/*.cfg OK: grep ^ec2_ami examples/jenkins/*.cfg OK: grep upgrade_to_latest[^_] examples/jenkins/*.cfg OK: <http://jenkins.knut.univention.de:8080/view/Autotest/job/UCS%203.2%20to%204.0%20Autotest%20MultiEnv/> OK: <http://jenkins.knut.univention.de:8080/view/Autotest/job/UCS-4.0/job/UCS-4.0-0/job/Autotest%20MultiEnv/> OK: <http://jenkins.knut.univention.de:8080/view/App%20Center/job/UCS%203.2%20to%204.0%20App%20Autotest%20Update%20MultiEnv/> OK: <http://jenkins.knut.univention.de:8080/view/App%20Center/job/UCS%204.0%20App%20Autotest%20MultiEnv/> OK: <http://jenkins.knut.univention.de:8080/view/App%20Center/job/UCS%204.0%20App%20Autotest%20Update%20MultiEnv/> OK: comment #5 OK: Bug #35741 wait OK: Bug #35733 reboot FIXED: r53252 | Bug #35148 EC2: Fix UCS-4.0 adaption r53253 | Bug #35148 EC2: Update from latest UCS-3 r53257 | Bug #35148 EC2: Fix Python exception
UCS 4.0-0 has been released: http://docs.univention.de/release-notes-4.0-0-en.html http://docs.univention.de/release-notes-4.0-0-de.html If this error occurs again, please use "Clone This Bug".