search

samrocketman / jenkins-bootstrap-jervis

An automated Jenkins CI environment which provisions agent infrastructure on the fly per build.
Apache License 2.0
75 stars 30 forks source link

"vagrant up" fails with multiple errors #24

Open bgpanw opened 1 year ago

bgpanw commented 1 year ago

Hi, I cannot complete this build with the current instructions. I get this result after "vagrant up"

BUILD SUCCESSFUL in 42s
3 actionable tasks: 3 executed
Bringing machine 'default' up with 'libvirt' provider...
Error while connecting to Libvirt: Error making a connection to libvirt URI qemu:///system:
Call to virConnectOpen failed: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
samrocketman commented 1 year ago

This repository is currently in flux. The vagrant method may not be stable. However, your above error looks unrelated to this repo. Looks like you'd have trouble provisioning anything with vagrant due to libvirt.

What is your OS? What software do you have installed? Did you install virtualbox?

bgpanw commented 1 year ago

No it was definitely this one. I am testing this using a GCP Compute VM running Ubuntu 22.04 LTS . I didn't see anything in the README.md

I am looking for good demonstrations and explanations of how to use JCasC where I'm currently stuck:

  1. using a secret (or any method) during config/boostrap time to load my configuration from a private GitHub repo... (using the RAW link repeatedly doesnt work since the token changes, and using the perma-link fails to load yaml source

  2. Using (preferably) GCP secrets manager as a source credential provider when configuring GitHub OAuth client/secret ID in JCasC

  3. ultimately also pipelines as code , loaded through private GH repos as well.

bgpanw commented 1 year ago

Although , now that I've looked at all the examples I've tried to build today with varying success in following along... I could have easily gotten confused :-)

samrocketman commented 1 year ago

You can't use nested virtualization in the cloud. You can verify that with any other vagrant file. It will fail the same way.

I use AWS secrets manager with init hook groovy scripts for Jenkins. I package the SDK into a custom Jenkins plugin whose only purpose is to hold additional AWS SDKs.

On boot I read the secrets and configure Jenkins with the secrets separately from JCasC.