![]() ![]() Install the bundler gem $ gem install bundler When you are done, you should be able to see the version of Ruby. ![]() Be sure to install the same ruby version as our development system. But before we can do our automated testing, we need to configure our Jenkins server to run Ruby for us just like we did on our test system.įollow the same steps as before to install RBENV on our Jenkins server. You can see this by clicking the Workspace link and looking at what Jenkins has pulled from git. Not much will happen at this point, but Jenkins will pull our module repository down to the Jenkins server. This will allow our GitLab server to automatically call the Jenkins job when an update is pushed.Ĭlick on Build Now to start our first build job. Jenkins automatically tests the connection and will display an error if there is an issue. Next to Credentials, click on Add and configure the settings like the following:Ĭlick on Add to add the credentials. Under Source Code Management, select git and enter the git URL of your repository. For our example, the name would be ‘cdbook-sample.’ Then select Freestyle as the job type. Name the job the same as your full module name. Click on Create New Jobs to start the process. Our first task is to create our Jenkins job. $ ssh-keygen -t rsaĬopy the contents of the key and add the SSH key to the Jenkins user on Gitlab. ![]() On the Jenkins server login as the Jenkins user from the root user # su – JenkinsĬreate an SSH keypair like we did for your user account. To do this, you will need to create a user on Gitlab named Jenkins and give the user Reporter permissions to your repository. We now need to give our Jenkins server access to our GitLab repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |