This page is an overview of what you need to do to onboard your CI/CD systems and tools and maintain a single pane of solution on Opsera.
...
Solution - 1
Customers who already have tools running in their own Instance and want to integrate with Opsera
Solution - 2
Customers who don’t have tools in place and want to integrate directly with Opsera
Solution -1: Customers who already have tools:
Jenkins Integration
Follow the below process to configure the Webhook.
|
---|
Step 1Log into Opsera Portal and select Tool Registry from left navigation.
Image Modified |
Step 2In the Tool Registry screen below, Click + New Tool Button to add a tool.
Image Added Image Removed |
Step 3Once you click Add Tool, a popup will be displayed. Type Jenkins Tool Name in the Tool Name input and field. Type Jenkins as Tool Identifier in the dropdown.
Image ModifiedOnce you click Create tool from |
Step 4Click the Create Tool Button to continue.
Image Added |
Step 5In the Modal Popup, Choose your Tool Name from the Main Tool Registry screen. Then, Click the Connections TAB to enter: Container URL Jenkins User ID Jenkins Password
Image Added Once you have entered all the below fields. Image Removed, Hit the Save Button once you are done. With these steps completed, now Log into Jenkins Tool to complete below steps. Click the Create Tool Button once you have completed previous inputs in the popup. Image Removed |
Step 6Log into Jenkins tool Enter your Jenkins credentials.
|
Step 7From the Dashboard screen, Click Manage Jenkins from left navigation tool bar
Image Modified |
Step 8In the Manage Jenkins page, Choose Notification
Image Modified Once you select the Job and click install, |
Step 9Select the Job Name Click install Jenkins Installation will start as shown below.
Image Modified |
Step 10Wait for the installation to conplete. Once Installation is complete, Jenkins will restart.
|
Step 11Once the Restart is completedcomplete, Click Configure link from left Navigation. Image Modified Goto Job Notifications TAB and enter |
Step 12Select the 2nd Tab from the Navigation menu. Enter the Webhook URL details in the Notifications TAB.
Image ModifiedNow |
Step 13Congratulations, you have completed all the steps required. Once you run any job via Jenkins on your end, Analytics data will be available at Opsera Portal. For SonarQube installation, please proceed to next section.
|
SonarQube ConfigurationTo integrate SonarQube, follow the below steps. |
...
Login to SonarQube portal |
Step 1Objective is to create Auth token which is required for Opsera Integration. Once you login, to authorize Opsera to SonarQube. Login to SonarQube portal Click + Icon located on the top right menu.
Image Modified |
Step 2Enter an unique Project key name and Provide a Display name. Click the Setup button.
|
Step 3Note the Project Key you just created.
Image Modified |
Step 4Now we have to create a Token that you can use with Opsera. Click Administrator link from Top right menu.
Image Modified |
Step 5In the Administrator screen, click the Security TAB to create the Security Token.
Image Modified |
Step 6Once you have created, you should see a success message as shown below. Click Copy to copy the key to clipboard.
Image Modified |
Step 7Now that you have created the Token, let’s update Opsera settings. Log into Opsera Portal and select Select Tool Registry from left navigation.
Image Modified |
Step 8Click + New Tool Button to add a tool. A popup dialogbox will be displayed.
Image Modified |
Step 9In the Popup dialogbox, Type a tool name. Choose SonarQube as your Tool. Select Code Scan as Tool Type from the Dropdown Click Save Changes
Image Modified |
Step 10Once you click Save Changes, Choose your Tool Name you just created. In this case, choose Sonarqube-demo from the list. Choose your Tool Name from the main screen. In the Pop-up, Click Connections TAB to complete the highlighted fields Enter Sonar URL Sonar Port Sonar User ID Sonar Auth Token you created in SonarQube portal. Click save.
Image ModifiedOnce you click save, |
Step 11Now login to SonarQube Portalportal. Once you login, click Configuration from top left Menu and Choose Webhooks.
Image Modified |
Step 12Click Create Button located on the right side.
Image Modified |
Step 13Type the below information in the popup dialogbox. Image RemovedType an unique name Enter the URL that you received from Opsera. Finally Click Create button to complete the Webhook configuration.
Image Added |
|
To Unsubscribe, from sonarqube,
Administration > configuration > webhooks >Delete.
Screenshot : sonar-add-webhook.png
Image Modified
For JMeter, Junit and XUnit to work as expected, you must configure filebeat before proceeding.
...
Login into gitlab
Select project > Settings(left panel) > Webhook >
Add webhook to send all events to logstash
https://customerdomain-logstash.opsera.io/webhook/gitlab
Screenshot : gitlab-add-webhook.png
...
Codeship
Add webhook and point to
Login to codeship dashboard > projects > “select your project” > Project settings (top-right) > Notifications >
https://customerdomain-logstash.opsera.io/webhook/codeship
Create user with read privileges and share username and password with opsera via email
Screenshot : Screenshot : codeship-add-webhook.png
Solution -2: Direct Integration with Opsera |
SonarQube InstallationLog into Opsera Portal and Select Platform from the Left navigation |
Select Code Security Tool and click Deploy button. Click Confirm button in the popup window to confirm the installation. |
Jenkins InstallationIn the Platform page, Select Jenkins tool and click Confirm Button. |
Once you submit, Email will be sent with Tool/URL information. This will take approximately 15 mins. Logstash plugin and Filebeat is automatically configured by java-microservice. ELK stack and DB details will be sent via email.
|
|
...