If a blueprint is testing in a private lab, one option is to use their own Jenkins master. There are many ways to setup Jenkins and create the projects in Jenkins. This is only one example. The primary requirements are that the Jenkins jobs be run multiple times over time (not just a single successful run) and the log results are are pushed to the Akraino Nexus server.
You can find documentation on how to install Jenkins on the Jenkins project web site: https://www.jenkins.io/doc/book/installing/
/var/jenkins_home
directory in the container to the Docker volume with the name jenkins-data
. Instead of mapping the /var/jenkins_home
directory to a Docker volume, it is recommended that you map this directory to one on your machine’s local file system. For example, specifying the option --volume /jenkins:/var/jenkins_home
would map the container’s /var/jenkins_home
directory to the /jenkins
directory on your local machine. This will allow easy access to the files and scripts used by the Jenkins container.Once Jenkins is installed and running, then projects need to be created to deploy and test the blueprint. There are multiple ways to create a project, but here is one example: https://java2blog.com/freestyle-projects-jenkins/