This is a cache of https://docs.openshift.com/aro/3/dev_guide/application_lifecycle/development_process.html. It is a snapshot of the page at 2024-11-27T21:02:25.103+0000.
Planning Your D<strong>e</strong>v<strong>e</strong>lopm<strong>e</strong>nt Proc<strong>e</strong>ss - Application Lif<strong>e</strong> Cycl<strong>e</strong> Manag<strong>e</strong>m<strong>e</strong>nt | D<strong>e</strong>v<strong>e</strong>lop<strong>e</strong>r Guid<strong>e</strong> | Azur<strong>e</strong> R<strong>e</strong>d Hat Op<strong>e</strong>nShift 3
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. explore the new docs experience today.
  1. Documentation
&times;

Planning Your Development Process

Important

Azure Red Hat OpenShift 3.11 will be retired 30 June 2022. Support for creation of new Azure Red Hat OpenShift 3.11 clusters continues through 30 November 2020. Following retirement, remaining Azure Red Hat OpenShift 3.11 clusters will be shut down to prevent security vulnerabilities.

Follow this guide to create an Azure Red Hat OpenShift 4 cluster. If you have specific questions, please contact us

Overview

Azure Red Hat OpenShift is designed for building and deploying applications. Depending on how much you want to involve Azure Red Hat OpenShift in your development process, you can choose to:

  • focus your development within an Azure Red Hat OpenShift project, using it to build an application from scratch then continuously develop and manage its lifecycle, or

  • bring an application (e.g., binary, container image, source code) you have already developed in a separate environment and deploy it onto Azure Red Hat OpenShift.

Using Azure Red Hat OpenShift as Your Development environment

Deploying then developing on Azure Red Hat OpenShift

You can begin your application’s development from scratch using Azure Red Hat OpenShift directly. Consider the following steps when planning this type of development process:

Initial Planning

  • What does your application do?

  • What programming language will it be developed in?

Access to Azure Red Hat OpenShift

Develop

  • Using your editor or IDe of choice, create a basic skeleton of an application. It should be developed enough to tell Azure Red Hat OpenShift what kind of application it is.

  • Push the code to your Git repository.

Generate

Manage

  • Start developing your application code.

  • ensure your application builds successfully.

  • Continue to locally develop and polish your code.

  • Push your code to a Git repository.

  • Is any extra configuration needed? explore the Developer Guide for more options.

Verify

  • You can verify your application in a number of ways. You can push your changes to your application’s Git repository, and use Azure Red Hat OpenShift to rebuild and redeploy your application. Alternatively, you can hot deploy using rsync to synchronize your code changes into a running pod.

Bringing an Application to Deploy on Azure Red Hat OpenShift

Developing then deploying on Azure Red Hat OpenShift

Another possible application development strategy is to develop locally, then use Azure Red Hat OpenShift to deploy your fully developed application. Use the following process if you plan to have application code already, then want to build and deploy onto an Azure Red Hat OpenShift installation when completed:

Initial Planning

  • What does your application do?

  • What programming language will it be developed in?

Develop

  • Develop your application code using your editor or IDe of choice.

  • Build and test your application code locally.

  • Push your code to a Git repository.

Access to Azure Red Hat OpenShift

Generate

Verify

  • ensure that the application that you have built and deployed in the above Generate step is successfully running on Azure Red Hat OpenShift.

Manage

  • Continue to develop your application code until you are happy with the results.

  • Rebuild your application in Azure Red Hat OpenShift to accept any newly pushed code.

  • Is any extra configuration needed? explore the Developer Guide for more options.