Many of you may have already seen the news, but I like to create a roll up to make it easy to see what’s been newly released. Yesterday Tuesday August 23rd 2016 VMware released a number of much awaited Management product updates. See below for a breakdown of the updates per product.
vRealize Automation 7.1
vRealize Automation 7.1 is optimized for growing clouds thanks to significant improvements in the automated installation experience.
vRealize Automation 7.1 continue simplifying the primarily and secondary setup process by adding ability to automate the setup process among similar deployments leveraging the new Silent Installer. Cloud Admins are now able to scale out existing vRealize deployment by adding more vRA components and manage them automatically though the new Command Line(CLI) interface.
vRA 7.1 release is also equipped with a brand new Migration tool which allows you to perform safe and sound side by side upgrade (migration) existing vRealize Automation systems 6.2.X to the latest and greatest release. During the migration process the source production environment remains intact which guarantees a minimum downtime of the production environment.
If you haven’t looked at Code Stream, you may want to now. Code Stream as you may or may not know is VMware’s DevOps product, but what you may not know is that with this management pack it adds some features to your vRA deployment that you may be interested in. Now this isn’t totally new it is in version 2.0 as you can see. The management pack allows you to utilize Code Stream to automate the SDDC lifecycle of templates, blueprints, workflows, dashboards, scripts and more within vRA. This is pretty cool right. If you want to use a blueprint for two tenants your can automate the lifecycle of these blueprints which I think is awesome.
Version 1.1.0 of vRelize Code Stream has been released today. For those who are not familiar vRealize Code Stream is a release automation tool for continuos integration / continuos development environments allowing for a rapid development, testing, and provisioning of environments.
New features in this latest release include:
Getting Started Tab – Provide step-by-step instructions on how to do initial vRCS configuration and create a release pipeline with the help of videos and documentation.
Release Pipeline Modeling Enhancements – Drag & Drop Stages and Tasks, Copy Tasks and Cancel pipeline execution.
Simplified Endpoint Registration Support for Jenkins server and vRealize Automation server.
For those of you who are fortunate enough to be able to get a trial for Code Stream this article will walk you through the installation and initial configuration of the product. Code stream as the name suggest is part of the vRealize product line and shares the same identity appliance and virtual appliance as vRealize Automation. Because of this I will be referring to articles I have already written for portions of the installation in an effort to not re-invent the wheel.
*Note – The instructions in the above referenced article may vary slightly from the vRCS Virtual Appliance, however it should be close enough that you should not have any issues following along.
On step 21 input the Code Stream License Key instead of the vRA license key, or both if you like.
3. For instructions on how to setup Tenants in vRealize Code Stream please see Adding Tenants in vRealize Autoamtion 6.x.
On step 7 you will not be able to add a user to the “Infrastructure Administrator” role as that is a construct of vRealize Automation. If you are running code stream and vRealize Automation on the same virtual appliance you can add users/groups to this role.
In part 1 of this article we deployed both GitLab and Jenkins, configured a Git project and connected it to the Eclipse IDE. In this article we will focus on configuring the Jenkins server to work with our GitLab repository and crate a Jenkins job to build our project.
Configuring Jenkins for GitLab
1. Before we can create a job we need to add some plugins to the Jenkins server for GitLab. We need to make sure we have the following plugins installed by going to the Jenkins server, the Manage Jenkins, and then Manage Plugins.
2. Next go to the “Installed” tab to see which if any of the needed plugins are already installed. The plugings that are needed are: