Jenkins test for 4.0-1 should be created.
Cloned UCS-4.0/UCS-4.0-0/ to UCS-4.0/UCS-4.0-1/ Disbaled <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/Autotest%20MultiEnv/> until QA is done. Moved <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/Handbooks%20Checker/> one level up as it works on webroot/
(In reply to Philipp Hahn from comment #1) > Cloned UCS-4.0/UCS-4.0-0/ to UCS-4.0/UCS-4.0-1/ > Disbaled > <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/ > Autotest%20MultiEnv/> until QA is done. I've enabled the "cron job" for 4.0-1 and disabled the "cron job" for 4.0-0. Could you also add a 4.0-0 to 4.0-1 Multienv upgrade job?
(In reply to Stefan Gohmann from comment #2) > (In reply to Philipp Hahn from comment #1) > > Cloned UCS-4.0/UCS-4.0-0/ to UCS-4.0/UCS-4.0-1/ > > Disbaled > > <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/ > > Autotest%20MultiEnv/> until QA is done. > > I've enabled the "cron job" for 4.0-1 and disabled the "cron job" for 4.0-0. > > Could you also add a 4.0-0 to 4.0-1 Multienv upgrade job? Is the 3.2→4.0 Job still needed, that is should it be replaced by 4.0-0→4.0-1 or should it be an additional job? As we don't have UCS-4.0-1 AMIs yet, the 4.0-0 AMI will be used anyway and the system well perform an update from testing. r57844 | Bug #37659: UCS-4.0-1 Tests sed -i 's/\<upgrade_to_\(latest_errata\|latest_test_errata\|latest\)\>/upgrade_to_testing/' autotest-[01]* autotest-22*
(In reply to Philipp Hahn from comment #3) > (In reply to Stefan Gohmann from comment #2) > > (In reply to Philipp Hahn from comment #1) > > > Cloned UCS-4.0/UCS-4.0-0/ to UCS-4.0/UCS-4.0-1/ > > > Disbaled > > > <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/ > > > Autotest%20MultiEnv/> until QA is done. > > > > I've enabled the "cron job" for 4.0-1 and disabled the "cron job" for 4.0-0. > > > > Could you also add a 4.0-0 to 4.0-1 Multienv upgrade job? > > Is the 3.2→4.0 Job still needed, that is should it be replaced by > 4.0-0→4.0-1 or should it be an additional job? The 3.2 to 4.0 jobs are needed when we need to test the upgrade from UCS 3.2-5 to UCS 4.0. Please create additional jobs. > As we don't have UCS-4.0-1 AMIs yet, the 4.0-0 AMI will be used anyway and > the system well perform an update from testing. But this upgrade is done before setup the domain.
r57863 | Bug #37659: UCS-4.0-1 Update tests <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/Autotest%20MultiEnv%20Update/>
(In reply to Philipp Hahn from comment #5) > r57863 | Bug #37659: UCS-4.0-1 Update tests > > <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-1/job/ > Autotest%20MultiEnv%20Update/> I think the test definitions should be in the same directory like every other test definition. Otherwise we must always keep in mind that these special upgrade tests are in a different directory.
(In reply to Stefan Gohmann from comment #6) > I think the test definitions should be in the same directory like every > other test definition. Otherwise we must always keep in mind that these > special upgrade tests are in a different directory. r57904 | Bug #37659 Jenkins: Rename UCS-4.0-1 tests As they re-use the 09 license files, I've added compatibility symbolic-links in examples/jenkins/ and renamed the directory to "setup-testing", as the tests first setup the damain and then upgrade to latest testing (currently UCS-4.0-1).
OK
UCS 4.0-1 has been released: http://docs.univention.de/release-notes-4.0-1-en.html http://docs.univention.de/release-notes-4.0-1-de.html If this error occurs again, please use "Clone This Bug".