# Add build user to shadow group and vboxuser group # How the machines were created VBoxManage createhd --filename deb32.vdi --size 16384 --variant fixed VBoxManage showhdinfo deb32.vdi VBoxManage createvm --name "deb32" --ostype Debian --register VBoxManage list VBoxManage showvminfo "deb32" # Port 67xx - 32 for 32-bit, 64 for 64-bit, 13 for the unlucky OS, 01 for Ubuntu 64 VBoxManage modifyvm "deb32" --memory 2048 --vrdp on --vrdpport 6732 --vrdpauthtype external --vrdpmulticon on VBoxManage storagectl "deb32" --name "IDE Controller" --add ide --controller PIIX4 VBoxManage storageattach "deb32" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "deb32.vdi" VBoxManage openmedium dvd ~/vbox_install_cds/debian-504-i386-netinst.iso VBoxManage storageattach "deb32" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium ~/vbox_install_cds/debian-504-i386-netinst.iso VBoxHeadless --startvm "deb32" VBoxManage storageattach "deb32" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium emptydrive VBoxManage createvm --name "deb64" --ostype Debian_64 --register VBoxManage modifyvm "deb64" --memory 2048 --vrdp on --vrdpport 6764 --vrdpauthtype external --vrdpmulticon on VBoxManage storagectl "deb64" --name "IDE Controller" --add ide --controller PIIX4 VBoxManage createhd --filename deb64.vdi --size 16384 VBoxManage storageattach "deb64" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "deb64.vdi" VBoxManage openmedium dvd ~/vbox_install_cds/debian-504-amd64-netinst.iso VBoxManage storageattach "deb64" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium ~/vbox_install_cds/debian-504-amd64-netinst.iso VBoxHeadless --startvm "deb64" VBoxManage storageattach "deb64" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium emptydrive VBoxManage createvm --name "Windows7_64" --ostype Windows7_64 --register VBoxManage modifyvm "Windows7_64" --memory 2048 --vrdp on --vrdpport 6707 --vrdpauthtype external --vrdpmulticon on VBoxManage storagectl "Windows7_64" --name "IDE Controller" --add ide --controller PIIX4 VBoxManage createhd --filename win7.vdi --size 32768 #Windows7 8XGTQ-98DPX-BG4Y8-KMM4Q-DH8BC VBoxManage storageattach "Windows7_64" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "win7.vdi" VBoxManage openmedium dvd ~/vbox_install_cds/en_windows_7_professional_x64_dvd_X15-65805.iso VBoxManage storageattach "Windows7_64" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium ~/vbox_install_cds/en_windows_7_professional_x64_dvd_X15-65805.iso VBoxHeadless --startvm "Windows7_64" VBoxManage storageattach "Windows7_64" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium emptydrive # alias rdesktop-deb32='rdesktop -a 16 -N -u marsj -p - openmodelicabuild.ida.liu.se:6732' # alias rdesktop-deb64='rdesktop -a 16 -N -u marsj -p - openmodelicabuild.ida.liu.se:6764' # alias rdesktop-win7='rdesktop -a 24 -N -u marsj -p - openmodelicabuild.ida.liu.se:6707' # To manage the virtual machines via RDP. Or use the Windows client, or any other client # user build:open#modelica on the virtual machines user build on build.openmodelica.org runs the virtual machines, and a crontab to make a debian repository * openmodelica packages should be put there automatically by the virtual machines * omlibrary and rml-mmc packages will be put there manually whenever needed * virtual machines should probably build every night at around 21:00, by doing "apt-get update && apt-source openmodelica && debuild -B -us -uc", followed by running the testsuite or copying the package to server; I don't know which should be done first * deb repository has 2 targets - stable and nightly. stable release numbers are updated manually, which means only the current stable release is put in the stable repository * TODO: apt repository scripts should be a makefile or use another way to make sure every command succeeds * /var/www/apt symlinks to ~build/debian-apt/, which is where the apt repository exists