How to Set Up CI/CD pipeline in AWS

AWS,

Jenkins,

Bitbucket (though Git repository)

JIRA (for reporting and task delegation)

• continuous integration (CI) is a practice that focuses on preparing a release easier. In this, isolated changes are immediately tested and reported on when they are added to a larger code base.

• continuous delivery (CD) is a software release approach in which development teams produce and test code in short cycles.

How to configure CD/CD pipeline:

What you gain:

• Less bugs get shipped to production as regressions are captured early by the automated tests.

• Building the release is easy as all integration issues have been solved early.

• Less context switching as developers are alerted as soon as they break the build and can work on fixing it before they move to another task.

• Testing costs are reduced drastically - CI server can run hundreds of tests in the matter of seconds.

• QA team spend less time testing and can focus on significant improvements to the quality culture.

• can release more often, thus accelerating the feedback loop with your customers.

• There is much less pressure on decisions for small changes, hence encouraging iterating faster.

For more details contact :91-9298259093

Micro Focus ALM Octane vs Jira

Micro Focus ALM Octane vs Jira

Micro Focus (HPE Software) ALM Octane
HPE, now MicroFocus, ALM Octane is designed with a user interface
 providing a targeted and simplified user flow and architected using responsive design.

Accessible in any HTML5 supported Web browser, or operating system, including many tablet devices, ALM Octane ensures users get access to what they want,

when they want, and where they want. ALM Octane platform easily integrates with the team’s existing Jenkins/CI system for visibility into the release pipeline, as well as into source code control systems like GIT, allowing for stronger collaboration, and supporting a faster path from manual testing to test automation.

MicroFocus ALM Octane also provides a foundation for common terminology across the application development lifecycle facilitating more closely connected teams.

With many out-of-the-box integrations to common industry and other Software technologies, ALM Octane platform boasts an extensive REST API, documented with Swagger, to allow users to work within the environment they’re most comfortable in, without sacrificing collaboration, governance, and process guidance.

ALM Octane & Jira: Added Value

Agile tool agnostic

• ALM Octane optimized for Enterprise scale.

• Business unit teams have different tools.

• JIRA is a team centric tool.

Additional modules required to implement enterprise wide process and control frameworks.

JIRA not intended to provide e2e insight across your entire SDLC; leaves gaps in traceability, audit and compliance

• ALM Octane seamlessly integrates with JIRA.

Use your existing JIRA investments with ALM Octane to gain an overarching framework of control and insight.

Ask about QC/ALM license swap.

Scaled Agile Framework

• ALM Octane was built for Enterprise needs.

• SAFe support is a key ALM Octane capability.

• ALM Octane is flexible enough to support both

traditional SDLC as well as Agile processes, helping

you transition when needed.

• By synchronizing JIRA with ALM Octane

 you can leverage SAFe framework.

• JIRA requires 3rd party solutions to support an

 enterprise level Agile implementation.

• This is costly and requires 3rd party involvement in

 your key IT transformation processes.

•  Ask about using ALM Octane to implement an

enterprise scale Agile framework. 

ALM Octane & Jira: Added Value

Enterprise Grade Security

• ALM Octane was designed with security at its core.

The default configuration provides

 comprehensive security and applies

the settings to all synchronized

 records even as new projects are added.

• JIRA requires administrative changes to enable

 issue level security.

Once issue level security is enabled, it must be applied to all projects.

Any projects subsequently added to JIRA also require

 this additional setup to be secured

Ask about using ALM Octane to implement a secure

solution for workload management without administrative overhead

ALM Octane & Jira: Added Value 

Scalability

• ALM Octane was architected to support large
 scale deployments.

There are no additional fees for High
 Availability and the system scales seamlessly.

By using JIRA sync, ALM Octane can provide
 full HA for JIRA records too

• Atlassian requires customers to purchase
 “Data Center” for high availability.

License fees for Data Center increase rapidly
 as users increase, e.g. 1,000 JIRA users with
HA support costs an additional US $24,000  PER YEAR

Data Center is a 1 Year Term license, there are
 no perpetual license options

• Ask about using ALM Octane to implement a High
 Availability system without paying additional fees.

ALM Octane & Jira: Added Value 

Audit Compliance

• Audit is a key requirement for many organizations.

• ALM Octane was engineered to deliver full audit and
 compliance reporting in real-time, at any time,
 even to synchronized records.

• JIRA does not and cannot provide full audit compliance.

JIRA audit is designed to track configuration changes,
 not record changes to issues themselves

An issue update (any change) is a KEY activity

• Ask about using ALM Octane to identify who changed what,
 when, and why across your entire enterprise.

ALM Octane CI Pipelines

• ALM Octane Pipelines provide quality based insights about the health of your CI build processes.

• ALM Octane incorporates data from your pipelines into your application delivery process.

Analyze quality, progress, change impact, code coverage and more.

Identify issues before builds are handed over.

• ALM Octane Pipeline can also use records synchronized from JIRA.

To track commits associated with a specific build run

Provide full insight and visibility into end to end processes

• ALM Octane Quality metrics can include JIRA user stories and Epics

• Ask about using ALM Octane to gain a single point of control for insight into your CI system.

 ALM Octane vs. Jira: Benefits

• ALM Octane enables teams to easily and readily understand the current quality of their applications, in real time, without additional software

• Out of the box integration with QC / ALM to support and extend the lifespan of your existing investments

• Full integration with CI servers allows ALM Octane to deliver real-time data on the state and health of your applications, down to the level of any test failures that have been recorded against the latest build of your software

• ALM Octane supports modern test management approaches out of the box as part of the integrated platform, quality is a key component of the present and future of ALM Octane

• JIRA requires additional tools to support test management, for example Zephyr or X-Ray. These tools add additional incremental cost to the JIRA system, require additional vendor / procurement time and effort and may be withdrawn at any time.

The Single Source of Truth

• ALM Octane provides a unified, end to end lifecycle management platform with no dependency on 3rd party components for core lifecycle functionality. From requirements to delivery, ALM Octane manages, track and audits all activities

• ALM Octane is built to support Agile across the enterprise, with tight integrations to PPM and other Agile solutions. ALM Octane consolidates data and provides the “single source of truth” and advanced data analytics.

• Extending far beyond Agile workload management, ALM Octane provides an integrated DevOps platform with full toolchain capabilities for modern product and application lifecycle management at enterprise scale.

• JIRA requires many different modules, connected by plug-ins to provide an end to end solution. To scale to enterprise grade Agile, JIRA requires third party solutions

How to Setting up different workflows for your Jira project ?

A workflow is like a flowchart in which issues can go from one state to another by following the direction paths between the states. In JIRA's workflow terminology, the states are called statuses, and the paths are called transitions.

We will use these two major components when customizing a workflow.

In this recipe, we will create a new, simple workflow from scratch. We will look at how to use existing statuses, create new statuses, and link them together using transitions.

The first step is to create a new skeleton workflow in JIRA:

1. Log in to JIRA as a JIRA administrator.

2. Navigate to Administration | Issues | Workflows.

3. Click on the Add Workflow button, and name the workflow Simple Workflow.

4. Click on the Diagram button to use the workflow designer or the diagram mode.

The following screenshot explains some of the key elements of the workflow designer:

As of now, we have created a new, inactive workflow. 

The next step is to add various statuses for the issues to go through. JIRA comes with a number of existing statuses, such as In Progress and Resolved, for us to use:

1. Click on the Add status button.

2. Select the In Progress status from the list and, click on Add.

You can type the status name into the field, and JIRA will automatically find the status for you.

3.Repeat the steps to add the Closed status, as shown in the following screenshot:

3. Repeat the steps to add the Closed status, as shown in the following screenshot:

Once you have added the statuses to the workflow, you can drag them around to re position

them on the canvas. We can also create new statuses as follows:

1. Click on the Add status button.

2. Name the new status Frozen, and click on Add.

JIRA will let you know if the status you are entering is new by showing the text (new status) next to the status name.

Now that we have added the statuses, we need to link them using transitions:

1. Select the originating status, which, in this example, is Open.

2. Click on the small circle around the OPEN status, and drag your cursor onto the IN PROGRESS status. This will prompt you to provide details for the new transition, as shown in the following screenshot         

                

3. Name the new transition Start Progress, and select the None option for the Screen.

4. Repeat the steps to create a transition called Close between the IN PROGRESS

and CLOSED statuses.

You should finish with a workflow that looks like the following screenshot:

At this point, the workflow is inactive, which means it is not being used by a project and you can edit it without any restrictions. Workflows are applied on a project and issue type basis. Perform the following steps to apply the new workflow to a project:

1. Select the project to apply the workflow to.

2. Click on the Administration tab to go to the project administration page.

3. Select Workflows from the left-hand side of the page.

4. Click on Add Existing from the Add Workflow menu.

5. Select the new Simple Workflow from the dialog, and click on Next.

6. Choose the issue types to apply (for example, Bug) the workflow to, and click on Finish.

After we have applied the workflow to a project, the workflow is placed in the active state.

So, if we now create a new issue in the target project of the selected issue type, our new

Simple Workflow will be used.

What is Jira workflow?

Workflows are one of the core and most powerful features in JIRA. They control how issues in JIRA move from one stage to another as they are being worked on, often passing from one assignee to another. For this reason, workflows can be thought of as the life cycle of issues.

Unlike many other systems, JIRA allows you to create your own workflows to resemble the work processes you may already have in your organization.

This is a good example of how JIRA is able to adapt to your needs without having you to change the way you work.

In this chapter, we will learn not only about how to create workflows with the new workflow designer, but also how to use workflow components, such as conditions and validators, to add additional behavior to your workflows.

We will also look at the many different add-ons that are available to expand the possibilities of what you can do with workflows.

What is jira tool?

It is an enterprise issue tracker system from Atlassian.

One of its key strengths is its ability to adapt to the needs of the organization from the frontend user interface to providing a platform for add-ons to extend its capabilities.

However, understanding its flexibility and picking the right add-ons can often be a daunting task for many administrators.

Learning how to take advantage of JIRA's power while keeping the overall design simple and clean is important to the success of the implementation and future growth.

You can make full of use recipes with real-life JIRA administration challenges, solutions,and examples. Each recipe contains easy-to-follow, step-by-step instructions and illustrations from the actual application.

Jira Integrating and importing users from LDAP

By default, JIRA manages its users and groups internally. Most organizations today often
useLDAP such as Microsoft Active Directory (AD) for centralized user management, and
you can integrate JIRA with LDAP. JIRA supports many different types of LDAP, including
AD, OpenLDAP, and more.

There are two options to integrate JIRA with LDAP. In this recipe, we will explore the first
option by using an LDAP Connector, and we will look at the second option in the next
recipe, Integrating with LDAP for authentication only.