Cum constructio systematis distributa sit, logicum est creare singulas turmas aedificandi pro unaquaque arte architecturae et operandi. In nostro casu hae erunt continentia LXC (in Linux) et qemu (in Fenestra);
vin-srv-build1 - centos 7, erit dominus Γ¦dificator & unus ex operariis
vm-srv-build2 - debian 10, ad aedificationem DEB packages
vin-srv-build3 - fenestris X, pro concione, nostis quid for?
Non colligemus Rac GUI - graphical interface pro 1C rac ad botrum ministrantium administrandi. Pro Linux, instrumenta vexillum pro singulis OS adhibebitur, lima exe pro Fenestra ex tcl scripto utere, utere freewrap.
occasum
GNU / Linux
Satis est documenta in Interreti ad institutionem 1,2. Etiam nec aliquam nisl.
Nam dominus;
Profecto rectius esset singulas OS sarcinas colligere, sed hoc est extra ambitum articuli. Omittemus etiam descriptionem vasis ad opus constituendum, tantum notabo me uti ProxMox VE. Atque etiam fasciculos pro quolibet axe ad conventum requisitos instituere debebis (centos: rpmdevtools, etc.; debian: aedificare-essentiale, dh-fac, pbuilder, etc.)
Incepta aedificare et operas aedificandi ut inexpugnabilis usor deducetur, ut unum ex omnibus exercitibus in processu participando creare debes;
adduser buildbot
Deinceps deductionem automaticam configurabimus servitiorum, respective ad singulas exercituum (continentes);
Post hoc, directorium infrastructuram "opificum" (in omnibus exercitibus) creare potes, ut hoc facias, sub usoris aedificatoris subcriptio ac sequentia mandata persequor:
In primo exercitu vin-srv-aedificare 1;
su - buildbot
mkdir /home/buildbot/worker
cd ~
buildbot-worker create-worker --umask=0o22 --keepalive=60 worker vm-srv-build1:4000 CentOS 123456
Altero exercitui vm-srv-aedificati;
su - buildbot
mkdir /home/buildbot/worker
cd ~
buildbot-worker create-worker --umask=0o22 --keepalive=60 worker vm-srv-build1:4000 Debian-10 123456
In opificibus exercitibus, servicium aedificatoris operarius iniri potest
systemctl start buildbot-worker
MS Fenestra
Sicut "operarius" pro contione sub Fenestra, machina virtualis cum recentissima emissione Win10 adhibebitur.
Laborare debes;
Postquam omnia supradicta inaugurata sunt, ipsum fabricam instituere potes;
pip install buildbot-worker
Sit scriptor creare opus Directory
md c:worker
Et Lorem
buildbot-worker start c:worker
Si omnia opera (vide stipes c: operariusd.log), tunc potes subcriptio nostrum "opificem" ut servitium addendo item cum directorio operantis ad registratum (praecepta in potesta- silla currens administratoris exsecuta sunt);
Omnia cum "opifices", eas ulterius tangere non debes, omnis potestas a magistro venit.
Veneficus setup
Incipiendum est, infrastructuram magistro (in exercitu principali), hoc facere, sub usore constructo subcriptio ac sequentia mandata curramus:
su - buildbot
mkdir /home/buildbot/master
cd ~
buildbot create-master master
Ad sarcinas parata facta, aedificare Directory creare
mkdir /home/buildbot/builds
A master.cfg fasciculus in /home/buildbot/master/ directorio creatus est. Hic fasciculus pythonis signum est ac descriptionem omnium machinarum systematis continet, cum eo in futuro laboramus.
Ad conventum fasciculorum variarum versionum automate, ne in codicem magistri fasciculi influat, in summa scriptura programmatis rac_gui.tcl, lineae cum emendatione et remissione additae sunt in titulo. :
Et his lineis fundatum, buildbot fasciculos numerabit. Extrahere data, uti vocant grep console. In buildbot you only cannot define variables for "workers" (saltem, quomodo non inveni). Hoc est quod proprietates adhibentur. Illae. In processu comitiali addimus gradus ad versionem determinandam et remissionem et, proinde, versionem et proprietates emissionem constituimus. Possessiones varie exponi possunt, in hoc casu vocando solatium mandatum;
Ad rectam remissionis et versionis numeros, vexillum sed vocatio utere, i.e. imperium notificata locum tenet values ββββintra amet lima cum inquisita
Exscribimus confectam sarcinam conglobatam et archivum cum fontibus ad dominum. Sed statim imitari potes tabellas e documenti operis tui ad repositorium vel locum tuum.
Id cum RPM. Nunc incipiamus algorithmum describere ad sarcinam DEB aedificandam. Cum processus ad sarcinas aedificandas pro diversis systematibus inter se independentes sint, multi gradus repetentur.
Serva tabella et magus officium experiri potes incipere:
systemctl restart buildbot-master
In stipes nos reprehendo omnia esse in ordine cum config et omnia sicut normaliter operantur. Omnes nostri opifices nunc coniungere debent, quae feliciter nuntiabuntur in stipes »»'/home/buildbot/master/twistd.log»»':
2019-07-24 16:50:35+0300 [-] Loading buildbot.tac...
2019-07-24 16:50:35+0300 [-] Loaded.
2019-07-24 16:50:35+0300 [-] twistd 19.2.1 (/usr/bin/python3.6 3.6.8) starting up.
2019-07-24 16:50:35+0300 [-] reactor class: twisted.internet.epollreactor.EPollReactor.
2019-07-24 16:50:35+0300 [-] Starting BuildMaster -- buildbot.version: 2.3.1
2019-07-24 16:50:35+0300 [-] Loading configuration from '/home/buildbot/master/master.cfg'
2019-07-24 16:50:36+0300 [-] /usr/local/lib/python3.6/site-packages/buildbot/config.py:90: buildbot.config.ConfigWarning: [0.9.0 and later] `buildbotNetUsageData` is not configured and defaults to basic.
This parameter helps the buildbot development team to understand the installation base.
No personal information is collected.
Only installation software version info and plugin usage is sent.
You can `opt-out` by setting this variable to None.
Or `opt-in` for more information by setting it to "full".
2019-07-24 16:50:36+0300 [-] Setting up database with URL 'sqlite:/state.sqlite'
2019-07-24 16:50:36+0300 [-] setting database journal mode to 'wal'
2019-07-24 16:50:36+0300 [-] adding 1 new services, removing 0
2019-07-24 16:50:36+0300 [-] adding 1 new change_sources, removing 0
2019-07-24 16:50:36+0300 [-] gitpoller: using workdir '/home/buildbot/master/gitpoller-work'
2019-07-24 16:50:36+0300 [-] adding 3 new builders, removing 0
2019-07-24 16:50:36+0300 [-] adding 1 new schedulers, removing 0
2019-07-24 16:50:36+0300 [-] initializing www plugin 'waterfall_view'
2019-07-24 16:50:36+0300 [-] initializing www plugin 'console_view'
2019-07-24 16:50:36+0300 [-] initializing www plugin 'grid_view'
2019-07-24 16:50:36+0300 [-] NOTE: www plugin 'sitenav' is installed but not configured
2019-07-24 16:50:36+0300 [-] initializing www plugin 'waterfall_view'
2019-07-24 16:50:36+0300 [-] initializing www plugin 'console_view'
2019-07-24 16:50:36+0300 [-] initializing www plugin 'grid_view'
2019-07-24 16:50:36+0300 [-] NOTE: www plugin 'sitenav' is installed but not configured
2019-07-24 16:50:36+0300 [-] BuildbotSite starting on 80
2019-07-24 16:50:36+0300 [-] Starting factory <buildbot.www.service.BuildbotSite object at 0x7fe31c2657b8>
2019-07-24 16:50:36+0300 [-] adding 3 new workers, removing 0
2019-07-24 16:50:36+0300 [-] PBServerFactory starting on 4000
2019-07-24 16:50:36+0300 [-] Starting factory <twisted.spread.pb.PBServerFactory object at 0x7fe31c147470>
2019-07-24 16:50:37+0300 [-] BuildMaster is running
2019-07-24 16:50:37+0300 [-] buildbotNetUsageData: sending {'installid': 'b6193b126b96689351d2fe95787c5a03fc0879f9', 'versions': {'Python': '3.6.8', 'Buildbot': '2.3.1', 'Twisted': '19.2.1'}, 'platform': {'platform': 'Linux-4.15.18-10- pve-x86_64-with-centos-7.6.1810-Core', 'system': 'Linux', 'machine': 'x86_64', 'processor': 'x86_64', 'python_implementation': 'CPython', 'version': '#1 SMP PVE 4.15.18-32', 'distro': 'centos:7'}, 'plugins': {'buildbot/worker/base/Worker': 3, 'buildbot/config/BuilderConfig': 3, 'buildbot/schedulers/basic/SingleBranchScheduler': 1, 'buildbot/reporters/mail/MailNotifier': 1, 'buildbot/changes/gitpoller/GitPoller': 1, 'buildbot/steps/worker/MakeDirectory': 1, 'buildbot/steps/source/git/Git': 3, 'buildbot/steps/shell/ShellCommand': 9, 'buildbot/steps/package/rpm/rpmbuild/RpmBuild': 1}, 'db': 'sqlite', 'mq': 'simple', 'www_plugins': ['waterfall_view', 'console_view', 'grid_view']}
2019-07-24 16:50:37+0300 [Broker,0,127.0.0.1] worker 'CentOS' attaching from IPv4Address(type='TCP', host='127.0.0.1', port=37332)
2019-07-24 16:50:37+0300 [Broker,0,127.0.0.1] Got workerinfo from 'CentOS'
2019-07-24 16:50:37+0300 [-] bot attached
2019-07-24 16:50:37+0300 [Broker,0,127.0.0.1] Worker CentOS attached to Rac-GUI-RPM-builder
2019-07-24 16:50:37+0300 [-] buildbotNetUsageData: buildbot.net said: ok
2019-07-24 16:50:39+0300 [Broker,1,192.168.55.15] worker 'Windows-10' attaching from IPv4Address(type='TCP', host='192.168.5.145', port=49831)
2019-07-24 16:50:39+0300 [Broker,1,192.168.55.15] Got workerinfo from 'Windows-10'
2019-07-24 16:50:40+0300 [-] bot attached
2019-07-24 16:50:40+0300 [Broker,1,192.168.55.15] Worker Windows-10 attached to Rac-GUI-WIN-builder
2019-07-24 16:50:41+0300 [Broker,2,192.168.55.99] worker 'Debian-10' attaching from IPv4Address(type='TCP', host='192.168.5.9', port=44430)
2019-07-24 16:50:41+0300 [Broker,2,192.168.55.99] Got workerinfo from 'Debian-10'
2019-07-24 16:50:41+0300 [-] bot attached
2019-07-24 16:50:41+0300 [Broker,2,192.168.55.99] Worker Debian-10 attached to Rac-GUI-DEB-builder
Hoc complet processus setup. Status hodiernus per interfaciem interreti inspicere potes. Ubi etiam videre poteris errores construere, calcitrare processus gelidum si quid erravit, etc.
Statim post launch, laboratores duri per menu "Aedificare" -> "Opifices" considerari possunt.
Post primum processum constructum perficitur (i.e. mutationes ad Git repositorium), status processuum in prima pagina apparebit.
Si in optatam lineam cum mure deprimes, pagina ostendet currenti statu huius processus, ubi videas quid agatur, quid errores, etc.