August 2022 - kovair.com

OpenShift Plugin Details

Plugin Version: 1.0

Overview

OpenShift is a family of containerization software products developed by Red Hat. Its flagship product is the OpenShift Container Platform — a hybrid cloud platform as a service built around Linux containers orchestrated and managed by Kubernetes on a foundation of Red Hat Enterprise Linux. It is an open source development platform, which enables the developers to develop and deploy their applications on cloud infrastructure. It is very helpful in developing cloud-enabled services.

OpenShift is capable of managing applications written in different languages, such as Node.js, Ruby, Python, Perl, and Java. One of the key features of OpenShift is it is extensible, which helps the users support the application written in other languages. OpenShift comes with various concepts of virtualization as its abstraction layer. The underlying concept behind OpenShift is based on virtualization.

This plug-in has been designed to manage OpenShift cluster from Kovair DevOps platform.

OpenShift Information:

More information can be found at OpenShift .

Version Supported:

This plugin was developed and tested against OpenShift Container Platform v4.10 and OpenShift CLI client (oc) v4.10.

Plugin Operation:

1. 1. CreateProject
Creates a new project in the OpenShift cluster..

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
Project Name	true	Name for the project to be created. The project name must consist of lower case alphanumeric characters or ‘-‘, and must start and end with an alphanumeric character.
Other Options	false	Other optional flag(s) for creating a project. Ex: –description=’Project description’

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

2. CreateNewApp

Creates a new application by specifying source code, templates and/or images.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
Application Name	false	Set name to use for generated application artifacts. The application name must consist of lower case alphanumeric (a-z, and 0-9) string with a maximum length of 58 characters, where the first character is a letter (a-z), and the ‘-‘ character is allowed anywhere except the first or last character.
Image Name	false	Name of a container image or an image stream to use in the app.
Source Code Path	false	Path to the source code available in the local or remote repository.
File Path	false	Path to a JSON/YAML template file to use for the app. Please ensure necessary privileges of the user account in the provided path through which the agent service is running.
Other Options	false	Other optional flag(s) for creating an application. Ex: –labels=’app=label’, –param=MYSQL_USER=admin

Note: The new application in the OpenShift cluster can only be created with any one of the following conditions are met:

Either ‘Application Name’ and ‘Image Name’ together or ‘Image Name’ only. If ‘Other Options’ is provided, then it will be included.
With the ‘Source Code Path’ only. If ‘Other Options’ is provided, then it will be included.
With the template ‘File Path’ only. If ‘Other Options’ is provided, then it will be included.
If valid parameters are provided only in the ‘Other Options’ field. Ex: Create an application based on a stored template: –template=ruby-helloworld-sample

* Any other combinations will be an error. * ‘Application Name’ is optional while creating the application using ‘Image Name’. * The ‘File Path’ value will not be considered if all values are provided. The application will be created based on the values of ‘Application Name’ and ‘Image Name’ including ‘Other Options’ (if present).

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

3. CreateRoute

Expose containers externally via secured routes.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
TLS Termination	false	Select a TLS termination type. Do not select any termination type if you want to create an unsecured route.
Route Name	false	Name for the route to be created. The route name must consist of lower case alphanumeric characters, ‘-‘ or ‘.’, and must start and end with an alphanumeric character. If the route name is omitted, the service name will be used.
Service Name	true	Name of the service for which route to be created.
Other Options	false	Other optional flag(s) for creating a route. Ex: –hostname=www.example.com

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

4. CreateDeployment

Creates a deployment with the specified name.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
Deployment Name	false	Name for the deployment to be created. The deployment name must consist of lower case alphanumeric characters, ‘-‘ or ‘.’, and must start and end with an alphanumeric character.
Image Name	false	Name of the container image to be used in the deployment.
Other Options	false	Other optional flag(s) for creating a deployment. Ex: –replicas=3
File Path	false	Path to a JSON/YAML file based on which new deployment will be created. Please ensure necessary privileges of the user account in the provided path through which the agent service is running.

Note: The new deployment in the OpenShift cluster can only be created with any one of the following conditions are met:

With ‘Deployment Name’ and ‘Image Name’ together only. If ‘Other Options’ is provided, then it will be included.
With the template ‘File Path’ only.

* Any other combinations will be an error. * ‘Deployment Name’ is mandatory while creating the deployment using ‘Image Name’. * The ‘File Path’ value will not be considered if all values are provided. The deployment will be created based on the values of ‘Deployment Name’ and ‘Image Name’ including ‘Other Options’ (if present).

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

5. CreateService

Creates a service using a specified service type. Available service types are: clusterip, externalname, loadbalancer, nodeport.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
Service Type	false	Select a service type.
Service Name	false	Name for the service to be created. The service name must consist of lower case alphanumeric characters or ‘-‘, and must start and end with an alphanumeric character.
Other Options	false	Other optional flag(s) for creating a service. Ex: –tcp=5678:8080, –clusterip=’None’, –external-name bar.com
File Path	false	Path to a JSON/YAML file based on which new service will be created. Please ensure necessary privileges of the user account in the provided path through which the agent service is running.

Note: The new service in the OpenShift cluster can only be created with any one of the following conditions are met:

With ‘Service Type’ and ‘Service Name’ including the ‘Other Options’.
With the template ‘File Path’ only.

* Any other combinations will be an error. * ‘Service Name’ and ‘Other Options’ are mandatory while creating the service by selecting ‘Service Type’. * The ‘File Path’ value will not be considered if all values are provided. The service will be created based on the values of ‘Service Type’ and ‘Service Name’ including ‘Other Options’.

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

6. CreateConfigMap

Creates a config map based on a file, directory, or specified literal value.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
ConfigMap Name	true	Name for the configmap to be created. The configmap name must consist of lower case alphanumeric characters, ‘-‘ or ‘.’, and must start and end with an alphanumeric character.
Source	true	Select a source for creating a configmap.
Value	true	Value of the file path, directory, literal or env file path through which the configmap to be created.
Other Options	false	Other optional flag(s) for creating a configmap. Ex: –template=’template string or file path’

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

7. CreateJob:

Creates a job with the specified name.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
Job Name	false	Name for the job to be created. The job name must consist of lower case alphanumeric characters or ‘-‘, and must start and end with an alphanumeric character.
Image Name	false	Name of the container image to be used in the job.
Other Options	false	Other optional flag(s) for creating a job. Ex: — date, –from=cronjob/name
File Path	false	Path to a JSON/YAML file based on which new job will be created. Please ensure necessary privileges of the user account in the provided path through which the agent service is running.

Note: The new job in the OpenShift cluster can only be created with any one of the following conditions are met:

With ‘Job Name’ and ‘Image Name’ together only. If ‘Other Options’ is provided, then it will be included.
With the template ‘File Path’ only.

* Any other combinations will be an error.
* ‘Job Name’ is mandatory while creating the job using ‘Image Name’.
* The ‘File Path’ value will not be considered if all values are provided. The job will be created based on the values of ‘Job Name’ and ‘Image Name’ including ‘Other Options’ (if present).

Output parameter(s):

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

8. ExecuteCommand

This operation executes the supplied command in the OpenShift cluster.

Parameter	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the operation.

Input parameter(s):

Parameter	Is Mandatory	Help Text
API Server URL	true	API server url of OpenShift cluster.
Authentication Type	true	Select an authentication type. Provide either API token or username with password based on the selected authentication type.
API Token	false	API token for authentication with API server.
Username	false	Username for authentication with API server.
Password	false	Password for authentication with API server.
Other Auth Options	false	Other optional flag(s) for authentication with API server.
Command	true	Command that will be executed as in the cmd/shell prompt.
Error Text	false	If the given text is found in the console log, the overall task status will be an error. To concatenate multiple error text use ‘\|\|’ operator.

Output parameter(s):

OutputLog	Help Text
OutputLog	Output log of the operation.
OpenShiftStatus	Status of the command execution.

Pass/Fail Conditions:

Method	Status	Condition
CreateProject	Passed	If the Output Log contains ‘Now using project <project-name>’.
CreateProject	Failed	If the Output Log contains the word ‘Error’ or ‘invalid’.
CreateNewApp	Passed	If the Output Log contains the word ‘created’ for all resources.
CreateNewApp	Failed	If the Output Log does not contain the word ‘created’ for all resources.
CreateRoute CreateDeployment CreateService CreateConfigMap CreateJob	Passed	If the Output Log contains the word ‘created’.
CreateRoute CreateDeployment CreateService CreateConfigMap CreateJob	Failed	If the Output Log does not contain the word ‘created’.
ExecuteCommand	Passed	If the Output Log contains output of the command.
ExecuteCommand	Failed	If the Output Log is not empty and contains any of the following: h. ‘Login failed’ or ‘connection refused’ i. ‘error’ or ‘label must consist of lower case alphanumeric characters’ j. ‘Error from server’ or ‘specified subcommand’ k. ‘is not recognized as an internal or external command’ l. ‘ERROR’ or ‘Invalid’ or ‘invalid’ m. ‘FullyQualifiedErrorId’ or ‘Could not find’ n. ‘command not found’ or ‘Incorrect syntax’ o. ‘No such file or directory’ or ‘doesn’t exist’ p. ‘The system cannot find the file specified’ or ‘The system cannot find the path specified’ q. ‘already exists and is not an empty directory’ or ‘Invalid filename’ r. ‘fatal’ or ‘Access denied’

Limitations:

The OpenShift CLI (oc)should be installed in the agent machine.
The functionality solely depends on the OpenShift CLI, if the command behaviour changes the result may vary.

Release Details:

OpenShift: 1.0
Initial version with basic functionalities.

Contact us:

Any Git Plugin Details

Plugin Version: 1.0.0

Overview

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. This plug-in has been designed to manage any git based scm tool from Kovair DevOps platform.

Git Information:

More information can be found at Git. (as on 2021/03/26)

Version Supported:

This plugin was developed and tested against version git 2.31.0, version present on Git.(as on 2021/03/26)

Prerequisites

Git client should be downloaded and installed in client node(machine) and path variable of git client should be added into environment variable before perform any operation.

Plugin Operation:

1. CheckOutCode
This operation allows to check out code and pulls them in a local repository path;..

Input parameter(s):

Parameter	Is Mandatory	Help Text
Git Repository	true	URL of the repository to pull from, i.e. http://192.168.12.211:7990/scm/abc/xyz-repository.git; Note:If repository is private then username and password of private repository must be added to repository url, i.e.http://username:password@192.168.12.211:7990/scm/abc/xyz-repository.git;
Destination Directory	false	Indicate the path where the source tree will be created (can be relative to the job’s workspace) Ex: C:\Git\Demo. If user don’t give destination directory then a “Default” directory will be created under DevOps agent service folder.
Branch	false	Git branch name which branch you want to clone(that branch should present into that particular repository that you are cloning).

Output parameter(s):

Parameter	Help Text
IsFilePresent	Is file downloaded.
GitStatus	Status of the operation.

Pass/Fail Condition:

Status	Required string in outputlog
Passed	If files are physically present in the provided directory, output log is not empty, and doesn’t contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’
Failed	If the output log is not empty and contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’

Status

Required string in outputlog

Passed

If files are physically present in the provided directory, output log is not empty, and doesn’t contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

Failed

If the output log is not empty and contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

2. ExecuteCommand

This operation allows to execute raw git command.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Command	true	Raw git command to be executed. Ex: git commit -m “MyFirstCommit”
Error Text	false	This field can be used to supply error text to search in console log after execution. If given text found in console log, overall task status will be error. To concat multiple error text use ‘\|\|’ operator. Leading and trailing space will be trimmed before searching. i.e. Sample Error Text : Fatal \|\| Error.

Output parameter(s):

Parameter	Help Text
GitStatus	Status of the operation.

Pass/Fail Condition:

Status	Required string in outputlog
Passed	If the outputlog is not empty, doesn’t contains any value of “Error Text” parameter and doesn’t contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’
Failed	If the outputlog is not empty, contains any value of “Error Text” parameter or contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’

Status

Required string in outputlog

Passed

If the outputlog is not empty, doesn’t contains any value of “Error Text” parameter and doesn’t contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

Failed

If the outputlog is not empty, contains any value of “Error Text” parameter or contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

Sample Commands

These are sample commands that can be tested through this plugin.

Sample Command(s):

Command	Description	Example
git config –global user.name “<Registered UserName>” git config –global user.email “<Registered EmailId>”	To configure the git terminal first time.	git config –global user.name “xyz” git config –global user.email “spal@xyz.com”
git clone <Path to your repository>	If you want to simply clone a repository then run this command in your terminal.	git clone http://192.168.12.211:7990/scm/abc/xyz-repository.git
cd existing-project git init git add –all git commit -m “<Commit message>” git remote add origin <Path to your repo> git push -u origin HEAD:master	If you already have code ready to be pushed to this repository then run this in your terminal.	cd /d E:\Git git init git add –all git commit -m “Initial Commit” git remote add origin http://192.168.12.211:7990/scm/abc/xyz-repository.git git push -u origin HEAD:master
cd existing-project git remote set-url origin <Path to your repo> git push -u origin –all git push origin –tags	If your code is already tracked by Git and you have added some new files or you have made some changes in any file and you want to push it to your repo then use this command.	cd /d E:\Git git remote set-url origin http://192.168.12.211:7990/scm/abc/xyz-repository.git git push -u origin –all git push origin –tags
cd existing project git push origin master	To send changes to the master branch of your remote repository.	cd /d E:\Git git push origin master
cd existing project git status	To see list the files you’ve changed and those you still need to add or commit.	cd /d E:\Git git status
cd existing project git remote add origin <server>	If you haven’t connected your local repository to a remote server, run this command to add the server to be able to push to it	cd /d E:\Git git remote add origin http://192.168.12.211:7990/scm/abc/xyz-repository.git
cd existing project git remote -v	To see list of all currently configured remote repositories.	cd /d E:\Git git remote -v
cd existing project git checkout -b <branchname>	To create a new branch locally and switch to it.	cd /d E:\Git git checkout -b project-xyz-Branch
cd existing project git checkout <branchname>	To switch from one branch to another.	cd /d E:\Git git checkout project-xyz-Branch
cd existing project git branch	To get list of all the branches in your repo, and also tell you what branch you’re currently in.	cd /d E:\Git git branch
cd existing project git push origin <branchname>	To push the branch to your remote repository, so others can use it.	cd /d E:\Git git push origin xyz-Branch

Disclaimers:

Command other than git are also supported but are not recommended.

Release Details:

AnyGit: 1.0.0
2. Initial version with basic functionalities.

Contact us:

Bitbucket Plugin Details

Plugin Version: 1.0.0

Overview

Bitbucket is a Git repository management solution designed for professional teams. It gives you a central place to manage git repositories, collaborate on your source code and guide you through the development flow. Bitbucket Cloud is a Git based code hosting and collaboration tool, built for teams. Bitbucket’s best-in-class Jira and Trello integrations are designed to bring the entire software team together to execute on a project. Bitbucket provides one place for your team to collaborate on code from concept to Cloud, build quality code through automated testing, and deploy code with confidence. This plug-in has been designed to manage Bitbucket On-Premise tool from Kovair DevOps platform.

Bitbucket Information:

More information can be found at Bitbucket . (as on 2021/02/18)

Version Supported:

This plugin was developed and tested against bitbucket on-premise server and git client.

Plugin Operation:

1. CheckOutCode
This operation allows to check out code and pulls them in a local repository path;.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Bitbucket Repository	true	URL of the repository to pull from, i.e. http://192.168.12.211:7990/scm/abc/xyz-repository.git; Note:If repository is private then username and password of private repository must be added to repository url, i.e.http://username:password@192.168.12.211:7990/scm/abc/xyz-repository.git;
Destination Directory	false	Indicate the path where the source tree will be created (can be relative to the job’s workspace) Ex: C:\Bitbucket\Demo. If user don’t give destination directory then a “Default” directory will be created under DevOps agent service folder.
Branch	false	Bitbucket branch name which branch you want to clone(that branch should present into that particular repository that you are cloning).

Output parameter(s):

Parameter	Help Text
IsFilePresent	Is file downloaded.
BitbucketStatus	Final CheckOutCode Status.

Pass/Fail Condition:

Status	Required string in outputlog
Passed	If files are physically present in the provided directory, output log is not empty, and doesn’t contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’
Failed	If the output log is not empty and contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’

Status

Required string in outputlog

Passed

If files are physically present in the provided directory, output log is not empty, and doesn’t contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

Failed

If the output log is not empty and contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

2. ExecuteCommand

This operation allows to execute raw git command or any bitbucket specific command.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base URL	true	Provide the base URL of Boomi instance.
Command	true	Raw git command or any bitbucket command to be executed. Ex: git commit -m “MyFirstCommit”
Error Text	false	This field can be used to supply error text to search in console log after execution. If given text found in console log, overall task status will be error. To concat multiple error text use ‘\|\|’ operator. Leading and trailing space will be trimmed before searching. i.e. Sample Error Text : Fatal \|\| Error.

Output parameter(s):

Parameter	Help Text
BitbucketStatus	Final ExecuteCommand Status.

Pass/Fail Condition:

Status	Required string in outputlog
Passed	If the outputlog is not empty, doesn’t contains any value of “Error Text” parameter and doesn’t contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’
Failed	If the outputlog is not empty, contains any value of “Error Text” parameter or contains any of the following: ‘is not recognized as an internal or external command’ ‘ERROR’ ‘FullyQualifiedErrorId’ ‘command not found’ ‘No such file or directory’ ‘already exists and is not an empty directory’ ‘fatal’

Status

Required string in outputlog

Passed

If the outputlog is not empty, doesn’t contains any value of “Error Text” parameter and doesn’t contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

Failed

If the outputlog is not empty, contains any value of “Error Text” parameter or contains any of the following:

‘is not recognized as an internal or external command’
‘ERROR’
‘FullyQualifiedErrorId’
‘command not found’
‘No such file or directory’
‘already exists and is not an empty directory’
‘fatal’

Sample Commands

These are sample commands that can be tested through this plugin.

Sample Command(s):

Command	Description	Example
git config –global user.name “<Registered UserName>” git config –global user.email “<Registered EmailId>”	To configure the git terminal first time.	git config –global user.name “xyz” git config –global user.email “spal@xyz.com”
git clone <Path to your repository>	If you want to simply clone a repository then run this command in your terminal.	git clone http://192.168.12.211:7990/scm/abc/xyz-repository.git
cd existing-project git init git add –all git commit -m “<Commit message>” git remote add origin <Path to your repo> git push -u origin HEAD:master	If you already have code ready to be pushed to this repository then run this in your terminal.	cd /d E:\Bitbucket git init git add –all git commit -m “Initial Commit” git remote add origin http://192.168.12.211:7990/scm/abc/xyz-repository.git git push -u origin HEAD:master
cd existing-project git remote set-url origin <Path to your repo> git push -u origin –all git push origin –tags	If your code is already tracked by Git and you have added some new files or you have made some changes in any file and you want to push it to your repo then use this command.	cd /d E:\Bitbucket git remote set-url origin http://192.168.12.211:7990/scm/abc/xyz-repository.git git push -u origin –all git push origin –tags
cd existing project git push origin master	To send changes to the master branch of your remote repository.	cd /d E:\Bitbucket git push origin master
cd existing project git status	To see list the files you’ve changed and those you still need to add or commit.	cd /d E:\Bitbucket git status
cd existing project git remote add origin <server>	If you haven’t connected your local repository to a remote server, run this command to add the server to be able to push to it	cd /d E:\Bitbucket git remote add origin http://192.168.12.211:7990/scm/abc/xyz-repository.git
cd existing project git remote -v	To see list of all currently configured remote repositories.	cd /d E:\Bitbucket git remote -v
cd existing project git checkout -b <branchname>	To create a new branch locally and switch to it.	cd /d E:\Bitbucket git checkout -b project-xyz-Branch
cd existing project git checkout <branchname>	To switch from one branch to another.	cd /d E:\Bitbucket git checkout project-xyz-Branch
cd existing project git branch	To get list of all the branches in your repo, and also tell you what branch you’re currently in.	cd /d E:\Bitbucket git branch
cd existing project git push origin <branchname>	To push the branch to your remote repository, so others can use it.	cd /d E:\Bitbucket git push origin xyz-Branch

Disclaimers:

Git client should be downloaded and installed in client node(machine) and path variable of git client should be added into environment variable before perform any operation.

Release Details:

Bitbucket: 1.0.0
Initial version with basic functionalities.

Contact us:

Comprehensive DevOps Implementation using Kovair

Download eCopy

Kovair Offering Accelerates the Application Delivery Process

In today’s fast-paced world, organizations need to be effectively agile to match the ever-changing market needs and keep them responsive to different consumer demands. While business innovation is largely driven by software in this digital age, it is important for enterprises to ensure the rapid release of application updates to win, serve and retain customers’ needs.

Agile practice of software development brings collaboration between the business and its developers. DevOps provides collaboration between IT operations, developers, and security teams for timely and efficient release of changes and upgrades. Kovair provides a complete end-to-end solution to manage different Agile templates for planning and release. Kovair DevOps provides consolidated visibility to the progress of the application delivery for achieving an organization’s goals.

DevOps Core Values and Practices

Automation is the primary value that DevOps provides. The two major core values are the “DevOps pipeline” and “DevOps life cycle management” that provides the Organization level culture shift in the way the products and projects are being planned and executed. The traditional Software Life cycle process was more of chunks of code modules delivered with long gaps, deployed at a later stage, and deployments that often result in gaps and disruption. Refer Fig 1.0 Fundamentally, embracing DevOps provides 4 core values -Automation, Sharing, Culture change, and Measurement.

Fig 1.0

Implement End-to-End DevOps

Identifying a proper DevOps platform like Kovair DevOps is the key step to start. Leveraging the Platform which must support VSMP DevOps solution with CI/CD functionality to deploy applications to any platform at any scale and provide complete visibility across the toolchain. DevOps helps organizations in their Software applications deployment journey in various ways covering different aspects of the DevOps process. Following are the key capabilities of Kovair DevOps.

Multiple OS – can be deployed on any Platform – Windows or Linux. Highly scalable across multiple hosts.
Multi Database Support – can work with MongoDB, My SQL, and SQL Server.
Project & Release – the platform provides complete isolation of the Pipeline through other projects. Allows to define, run and monitor your releases through a task-based DevOps pipeline
Containerized -the platform is Docker enabled, which can be managed through Kubernetes or OpenShift.
Build & Deployment Automation – ability to continuously build and deploy processes through 3rd party tools or plug-ins and custom routines. Provides centralized governance and control for every deployment
Manage pipelines from handheld devices through e-mail
Manage parallel and sequential tasks with optional pre & post-conditions for every task
YAML – Supports Pipeline-as-Code. Can convert Pipeline to YAML and vice-versa
Tightly integrated with Omnibus ESB with 110+ tools integration and Kovair ALM for managing the Agile practices.

An Agile Delivery Process

The mainstream agile methods are focused on different aspects of the software development life cycle with an implicit focus on development methodology. Some focus on the practices (Extreme Programming, Pragmatic Programming, Agile Modeling), while others focus on managing the software projects (the Agile approach). Yet, there are approaches providing full coverage over the development life cycle, such as Dynamic Systems Development Method (DSDM). Thus, there is a clear difference between the various agile software development methods in this regard. Kovair with its product-centric focus, provides an excellent foundation on which scalable delivery processes can be built seamlessly with multiple choices of the methods.

Continuous Integration ROI

Continuous integration implemented through Kovair DevOps not only merges codes checked in by different developers but integrates the development team with other functional areas as stated below. Some of the benefits that developers get through this implementation are:

Plug-in based integration for IDEs to view different artifacts of ALM “in place”
An ability to initiate unit testing, code coverage, and code analysis from the IDE with tools such as NetBeans, Eclipse, Visual Studio.
Traceability view of test artifacts and their execution status from the IDE allows them to identify what % of code is being tested
Ability to perform static code analysis from the IDE allowing to validate their code even before checking in
Helps them in better understanding of features without much manual interaction and dependency on other team members
Gives them real-time visibility of defects and related information raised against their code

DevOps beyond CI/CD Process – ready for the Next Generation

A DevOps Platform provides two key core aspects – Continuous Integration and Continuous Deployment

Continuous Integration (CI) is a key benefit of agile development and DevOps processes. In this software development process, continuous integration is the practice of merging all code files from all the developers to a central repository, after which automated builds and tests are run.

Continuous Delivery (CD) is the practice of regular delivery of applications (under development or changes) to QA and Operations for validation, and potential release and deployment to customers.

Prior to the CI/CD and release pipeline, there is a large pre-processing of data across tools. Figure 2.0 below shows a DevOps platform that connects to an ESB that provides a unified flow of data from Epic, User Story, Code, to Test Automation. Opting for a platform that is well connected to an ESB will leapfrog the power of the platform. The power of ESB-connected tools from the various domains such as ITSM, ALM, Security, Release, and Deployment significantly enhance DevOps capabilities of Kovair.

DevOps beyond CI/CD Process – ready for the Next Generation

Conclusion

In order to meet the challenges of getting early to the market, more and more organizations are moving towards DevOps. However, purchasing new tools to achieve this is a huge challenge for organizations that have already invested on different tools. But, choosing the right one is a real challenge. End-to-end automation requires the entire work to flow unimpeded through multiple tools and teams. Kovair DevOps is also tightly integrated with Omnibus ESB and Kovair ALM, which currently has integrations with 110+ commercial tools covering different aspects of the application lifecycle, CRM, ITSM, PPM, ITM, PLM, and delivery. All these integrations along with capabilities like task-based workflow, notifications, and business rules help organizations to reduce time to market. Kovair DevOps not only supports integrations and plug-ins with commercial tools but also integrates with in-house tools of an organization helping them to protect their investment while implementing DevOps.

Download eCopy

Boomi Plugin Details

Plugin Version: 1.0

Overview

Boomi is a software company that specializes in integration platform as a service (iPaaS), API management, master data management and data preparation. Boomi was founded in Berwyn, Pennsylvania, and first launched its services in 2007. This plug-in has been designed to manage Boomi environment from Kovair DevOps platform.

Boomi Information:

More information can be found at Boomi. (as on 2022/06/29)

Version Supported:

This plugin was developed and tested against Boomi iPaaS Cloud instance.

Plugin Operation:

1. PackageComponent
This operation packages any boomi component, that will be deployed to Test/Production environment.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base Url	true	Provide the base URL of Boomi instance.
Account Id	true	Provide the corresponding user’s account id of Boomi.
Username	true	Provide the corresponding user’s username of Boomi.
Password	false	Provide the corresponding user’s password of Boomi.
API Token	false	Provide the API token for authorization.
Authentication Type	true	Select authentication type, need to specify authentication mechanism, Password/API Token.
Components	true	Select component, which will be packaged.

Output parameter(s):

Parameter	Help Text
Status	Status of the operation.
OutputLog	Response message content.
PackageId	Id of the packaged component, that will be used further to deploy or execute any packaged component.

2. DeployComponent

Deploy any packaged component to Test/Production environment in boomi platform.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base URL	true	Provide the base URL of Boomi instance.
Account Id	true	Provide the corresponding user’s account id of Boomi.
Username	true	Provide the corresponding user’s username of Boomi.
Password	false	Provide the corresponding user’s password of Boomi.
API Token	true	Provide the API token for authorization.
Authentication Type	true	Select authentication type, need to specify authentication mechanism, Password/API Token.
Environment Type	true	Select environment type accordingly.
Environments	true	Select environment, where package will be deployed.
Package Id	true	Provide package id, which will be deployed.
Deployment Notes	false	Provide deployment notes.

Output parameter(s):

Parameter	Help Text
Status	Status of the operation.
OutputLog	Response message content.
ComponentId	Component id, which is deployed.

3. ExecuteComponent

Execute component to test/production environment.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base URL	true	Provide the base URL of Boomi instance.
Account Id	true	Provide the corresponding user’s account id of Boomi.
Username	true	Provide the corresponding user’s username of Boomi.
Password	false	Provide the corresponding user’s password of Boomi.
API Token	false	Provide the API token for authorization.
Authentication Type	true	Select authentication type, need to specify authentication mechanism, Password/API Token.
Atoms	true	Select atom accordingly.
Component Id	true	Provide component id, which will be executed.

Output parameter(s):

Parameter	Help Text
Status	Status of the operation.
OutputLog	Response message content
ExecutionRequestId	Request id, after sending execute request of the component.

4. GetExecutionStatus

This operatoin inform us, about the status of the initiated execution request.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base URL	true	Provide the base URL of Boomi instance.
Account Id	true	Provide the corresponding user’s account id of Boomi.
Username	true	Provide the corresponding user’s username of Boomi.
Password	false	Provide the corresponding user’s password of Boomi.
API Token	false	Provide the API token for authorization.
Authentication Type	true	Select authentication type, need to specify authentication mechanism, Password/API Token.
ExecutionRequestId	true	Provide execution request id, that has been initiated.

Output parameter(s):

Parameter	Help Text
Status	Status of the operation.
OutputLog	Response message content
ExecutionStatus	Execution status of the component.

5. MakeEnvironmentReady

This operatoin create new environment, by performing some internal operation by itself.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base URL	true	Provide the base URL of Boomi instance.
Account Id	true	Provide the corresponding user’s account id of Boomi.
Username	true	Provide the corresponding user’s username of Boomi.
Password	false	Provide the corresponding user’s password of Boomi.
API Token	false	Provide the API token for authorization.
Authentication Type	true	Select authentication type, need to specify authentication mechanism, Password/API Token.
Clouds	true	Select cloud accrodingly.
Environment Type	true	Select environment type accrodingly.
Environment Name	true	Provide the environment name, which will be created.
Atom Name	true	Provide the atom name, which will be created.

Output parameter(s):

Parameter	Help Text
Status	Status of the operation.
OutputLog	Response message content.
EnvironmentId	Id of the newly created environment.
EnvironmentName	Name of the newly created environment.
AtomId	Id of the newly created atom.
AtomName	Name of the newly created atom.

6. SaveComponentScript

This operatoin save script of any component as .xml file in local system.

Input parameter(s):

Parameter	Is Mandatory	Help Text
Base URL	true	Provide the base URL of Boomi instance.
Account Id	true	Provide the corresponding user’s account id of Boomi.
Username	true	Provide the corresponding user’s username of Boomi.
Password	false	Provide the corresponding user’s password of Boomi.
API Token	false	Provide the API token for authorization.
Authentication Type	true	Select authentication type, need to specify authentication mechanism, Password/API Token.
ComponentId	true	Provide component id to save it’s script.
Destination Directory	true	Provide the directory path, where component script will be saved.

Output parameter(s):

Parameter	Help Text
Status	Status of the operation.
OutputLog	Response message content.
FileName	Name of component script xml file.
DestinationDirectory	Destination directory, where component script xml will be saved.

Pass/Fail Conditions:

Method	Status	Condition
PackageComponent	Passed	If the value of Status is Success and if OutputLog contains PackageId, Package Version, Component Id, Component Version
PackageComponent	Failed	If the value of Status is not Success and if OutputLog doesn’t contains Package Id, Package Version, Component Id, Component Version
DeployComponent	Passed	If the value of Status is Success and if OutputLog contains following parameters Deployment Id, Deployment Version, Package Id, Package Version, EnvironmentId, Component Id, Component Version
DeployComponent	Failed	If the value of Status is not Success and if OutputLog doesn’t contains any parameters.
ExecuteComponent	Passed	If the value of Status is Success and if OutputLog contains following parameters Component Id, Atom Id, ExecutionRequestId Id
ExecuteComponent	Failed	If the value of Status is not Success and if OutputLog doesn’t contains any parameters.
GetExecutionStatus	Passed	If the value of Status is Success and if OutputLog contains following parameters Execution Status
GetExecutionStatus	Failed	If the value of Status is not Success and if OutputLog doesn’t contains any parameters.
SaveComponentScript	Passed	If the value of Status is Success and if OutputLog contains following text Component script has been saved successfully.
SaveComponentScript	Failed	If the value of Status is not Success and if OutputLog doesn’t contains following text Component script has been saved successfully.
MakeEnvironmentReady	Passed	If the value of Status is Success and if OutputLog contains following parameters Environment Id, Environment Name, Atom Id, Atom Name
MakeEnvironmentReady	Failed	If the value of Status is not Success and if OutputLog doesn’t contains any parameters.

Limitations:

This plug-in has been implemented for Process type component only.

Release Details:

Boomi: 1.0
Initial version with basic functionalities.

Month: August 2022

OpenShift Plugin Details

Overview

OpenShift Information:

Version Supported:

Plugin Operation:

Pass/Fail Conditions:

Release Details:

Contact us:

Categories

Category Posts

Any Git Plugin Details

Overview

Git Information:

Version Supported:

Prerequisites

Plugin Operation:

Release Details:

Contact us:

Categories

Category Posts

Bitbucket Plugin Details

Overview

Bitbucket Information:

Version Supported:

Plugin Operation:

Release Details:

Contact us:

Categories

Category Posts

Kovair Offering Accelerates the Application Delivery Process

DevOps Core Values and Practices

Implement End-to-End DevOps

An Agile Delivery Process

Continuous Integration ROI

DevOps beyond CI/CD Process – ready for the Next Generation

Conclusion

Download PDF version

Categories

Category Posts

Boomi Plugin Details

Overview

Boomi Information:

Version Supported:

Plugin Operation:

Pass/Fail Conditions:

Release Details:

Contact us:

Categories

Category Posts