Univention Bugzilla – Bug 31790
Backport of ucs-test to UCS 3.1-1
Last modified: 2023-03-25 06:47:11 CET
In order to get a better test coverage we should backport ucs-test from 3.2 to UCS 3.1-1. After that we can copy the following jenkins jobs to UCS 3.1: - UCS 3.2 App Autotest MultiEnv - UCS 3.2 App Autotest SingleEnv (S4 Master) - UCS 3.2 Autotest MultiEnv - UCS 3.2 Autotest SingleEnv (S4 Master)
Instead of announcing ucs-test as erratum we could create an unmaintained component.
The current version has been backported: ucr set repository/online/component/ucs3.1-1-ucs-test=true repository/online/component/ucs3.1-1-ucs-test/unmaintained=true
Or include deb http://ucs-test-repo.s3-website-eu-west-1.amazonaws.com/ ./ as an additional repository, which contains the latest ucs-test version automatically built by http://jenkins.knut.univention.de:8080/job/ucs-test_BUILD/ and published through http://jenkins.knut.univention.de:8080/job/ucs-test_PUBLISH/ (currently disabled since the old single-master-test is now disabled) Benefit: no manual work needed, that is no (repo-admin import, b3x-scope build, announce, update), just svn commit.
(In reply to Philipp Hahn from comment #3) > Or include > deb http://ucs-test-repo.s3-website-eu-west-1.amazonaws.com/ ./ > as an additional repository, which contains the latest ucs-test version > automatically built by > http://jenkins.knut.univention.de:8080/job/ucs-test_BUILD/ > and published through > http://jenkins.knut.univention.de:8080/job/ucs-test_PUBLISH/ > (currently disabled since the old single-master-test is now disabled) > > Benefit: no manual work needed, that is no (repo-admin import, b3x-scope > build, announce, update), just svn commit. I think we should use it in the same way as the rest of UCS. So every ISV can use it like other components.
For this bug is no separate QA needed.