Feature Request: Enable parallel build in CI for Mainnet and Testnet #226

New issue

Closed

opened 2021-12-13 16:23:39 +00:00 by rilesdun · 4 comments

rilesdun commented

2021-12-13 16:23:39 +00:00

(Migrated from gitlab.com)

Currently CI only supports one build, of the mainnet versions of witness_node and cli_wallet.

We must add support to build both mainnet and testnet cmake options at the same time, as this will enable pipeline artifacts for both mainnet and testnet to be downloaded, compared to needed to recompile.

Steps required:

Upgrade build server to have resources to handle two simultaneous builds (128GB of Ram, 32vCPUs)
Create new branch for testing
Update gitlab-ci.yml file to include two separate builds, at the same time
Compare time taken to build both; optimize to be same build time as currently (50~ minutes)

Currently CI only supports one build, of the mainnet versions of `witness_node` and `cli_wallet`. We must add support to build both mainnet and testnet cmake options at the same time, as this will enable pipeline artifacts for both mainnet and testnet to be downloaded, compared to needed to recompile. Steps required: - Upgrade build server to have resources to handle two simultaneous builds (128GB of Ram, 32vCPUs) - Create new branch for testing - Update gitlab-ci.yml file to include two separate builds, at the same time - Compare time taken to build both; optimize to be same build time as currently (50~ minutes)

rilesdun commented

2021-12-13 16:23:40 +00:00

(Migrated from gitlab.com)

assigned to @rilesdun

serkixenos commented

2021-12-14 06:15:49 +00:00

(Migrated from gitlab.com)

Build job fails with

make -j$(nproc)

What is the number of CPUs vs RAM?

Build job fails with ``` make -j$(nproc) ``` What is the number of CPUs vs RAM?

rilesdun commented

2021-12-15 16:19:57 +00:00

(Migrated from gitlab.com)

A fix has been found, but a pipeline was already running here. -j$(nproc) will work as expected after another reboot

I upgraded the CPUs here yesterday but ran into an issue with memory allocation on Proxmox due to a bug with hot-plug options: https://forum.proxmox.com/threads/kvm-vm-64gb-wont-start-with-memory-hotplug-enabled.90117/ A fix has been found, but a pipeline was already running here. `-j$(nproc)` will work as expected after another reboot

serkixenos commented

2022-03-28 14:14:38 +00:00

(Migrated from gitlab.com)

Abandoning this one, as we opted for testnet build on request.
https://gitlab.com/PBSA/peerplays/-/merge_requests/71

Abandoning this one, as we opted for testnet build on request. https://gitlab.com/PBSA/peerplays/-/merge_requests/71

serkixenos (Migrated from gitlab.com) closed this issue

2022-03-28 14:14:39 +00:00