Univention Bugzilla – Bug 39349
Seperate ucs-{ec2,kvm}-* tools from Jenkins configuration
Last modified: 2023-03-25 06:51:10 CET
Currently ucs-?.?/ucs-?.?-?/test/ucs-ec2-tools/ contains both the executable and the configuration files for a specific UCS release. They should be separated into two packages, fixes and changes to ucs-*-create have to be back-ported to all branches. (Bug #38984 is fixed in 4.0-3 and 4.1-0, but 3.2-7 is still used by our internal Jenkins server and for at least on customer project.) 1. The tools should go to trunk/internal/ucs-ec2-tools/ or branches/ucs-3.2/internal/ucs-ec2-tools/ 2. The configs should go to branches/ucs-?.?/ucs-?.?-?/test/ucs-jenkins-tests/ While at that, they should be moved up two levels from examples/jenkins/.
The scripts also reference several other files, which are not under version control: ~/ec2/keys/tech.pem ~/ec2/license/*.ldif ~/ec2/scripts/activate-errata-test-scope.sh ~/ec2/license/license.secret
r69522 | Bug #39349 ec2: autosh r69521 | Bug #39349 ec2: autopep8 r69520 | Bug #39349 ec2: Move to trunk/ r69519 | Bug #39349 ec2: Copy to trunk/ TBC...
r72623 | Bug #39349 ec2: Use ec2-tools from trunk/ r72615 | Bug #39349 EC2: Move to trunk r72614 | Bug #39349 EC2: Remove absolute logfile paths
The config files were not moved. The tools are now in dev/trunk/jenkins/ucs-ec2-tools/ and linked as SVN externals.
For this bug is no separate QA needed.