Please set up VM to host plugin builds.

[Lesya Novaselskaya]

Jenkins Product is a legacy outdated service. We need to move all critical tasks out of it. Please set up up-to-date VM to process plugin builds. Plugins builds are used in swarm, so links should be updated. VM is meant to reside in Product CI.

outdated VM: http://plugins-msk.vm.mirantis.net/

related bug: #1567375

[Andrey Nikitin (heos)]

Created a ticket on IT-team to create new VM: https://mirantis.jira.com/browse/IT-27987.

[Andrey Nikitin (heos)]

plugins02-bud.infra.mirantis.net is ready, 'build_plugins' role is deployed there. The server has the similar configuration as plugins-msk.

[Lesya Novaselskaya (onovaselskaya)]

I've failed to start Jenkins slave:
https://product-ci.infra.mirantis.net/computer/plugins02-bud.infra.mirantis.net/log

I guess it's because credentials are wrong. The old VM (plugins-msk) lived in old Jenkins (http://jenkins-product.srt.mirantis.net:8080/) and had jenkins(plugins_builder) key. The new one (plugins02-bud) should have the same dependencies and setup, but as soon as it resides in new Jenkins (https://product-ci.infra.mirantis.net), they key should be jenkins(Master).

[Lesya Novaselskaya (onovaselskaya)]

Things are smooth and working fine: https://product-ci.infra.mirantis.net/computer/plugins02-bud.infra.mirantis.net/

[Andrey Nikitin (heos)]

Ssh public key were missed in the role for the server. Fixed by adding the key to the role.