Developer and Deployment Manager Tasks developer-deployment-manager
In this optional part of the onboarding journey, you learn how developers and deployment managers can access git to develop applications and use pipelines to deploy them.
The Story So Far story-so-far
You have come a long way in your onboarding journey! Congratulations! The system administrator has completed the onboarding journey by setting up the necessary cloud resources and granting access in the document Assigning AEM Product Profiles.
At this point your developers and deployment managers can begin creating your own applications while your AEM users can start creating content. In this sense, your onboarding is complete and now it is time to use your new AEM as a Cloud Service system, which this document will illustrate.
Audience audience
This document is therefore written from the perspective of the developer and deployment manager.
The system administrator can also perform these same tasks, but generally these roles are held by different users.
Objective objective
This document is a supplement to the onboarding journey to demonstrate the basic tasks of a developer and deployment manager once the system administrator has onboarded all the users and created the necessary cloud resources.
After reading this document, you should:
- As a developer, understand how to access and manage your Cloud Manager git repositories.
- As a deployment manager, be able set up pipelines and deploy your code in Cloud Manager.
Developers and Deployment Managers roles
Once the system administrator has completed the main onboarding tasks of creating users and setting up cloud resources, the users generally most anxious to access the system are the developers and deployment managers. This is because they are the users responsible for building your custom applications on top of AEM as a Cloud Service.
- Developers - These users access the Cloud Manager git repositories where they will manage the code for your AEM custom applications.
- Deployment Managers - These users use Cloud Manager to create and run pipelines that deploy the code from the git repositories to your running AEM environments.
Depending on your organizational needs, the same user(s) can have both roles.
Prerequisites prerequisites
Before you begin the tasks described in this document as a developer or deployment manager, ensure that your system administrator has completed all the steps in this onboarding journey. This means that:
- Your system administrator has assigned developers and deployment managers to their respective product profiles.
- Developers must additionally be assigned to AEM Users or AEM Administrators product profiles ito also use AEM.
- Cloud resources have been set up.
Accessing git accessing-git
You can access and manage your git repositories using self-service git account management from Cloud Manager.
-
Log into Cloud Manager at and select the appropriate organization and program.
-
Navigate to Pipelines card from your Program Overview page and find the Access Repo Info button to access and manage your git Repository.
-
Click the View Repo Info button to open a dialog to view:
- The URL to the Cloud Manager git repository.
- The git username.
- The git password, the value of which is shown when the Generate Password button is clicked.
Using these credentials, the user can clone a local copy of the repository, and make changes in that local repository, and when ready can commit any code changes back to the remote code repository in Cloud Manager.
Pipeline Setup setup-pipeline
Once developers have added their custom code to your git repositories, the deployment manager can create and execute pipelines to deploy that code to your AEM environments.
Follow these steps to create your first non-production deployment pipeline.
-
Log into Cloud Manager at and select the appropriate organization and program.
-
Access the Pipelines card from the Cloud Manager home screen. Click +Add and select Add Non-Production Pipeline.
-
On the Configuration tab of the Add Non-Production Pipeline dialog, select the type of non-production pipeline you with to add. For this example, select Deployment Pipeline.
-
Provide a Non-Production Pipeline Name to identify your pipeline along with the following additional information.
-
For the Deployment Trigger select Manual so that the pipeline runs only when you start it.
-
Click Continue.
-
On the Source Code tab of the Add Non-Production Pipeline dialog, you must select which type of code the pipeline should process. For this example, select Full Stack Code.
-
On the Source Code tab, you must define the following options.
- Eligible Deployment Environments - You must choose which environment to which the pipeline should deploy.
- Repository - This options defines from which git repo the pipeline should retrieve the code.
- Git Branch - This option defines from which branch in the selected the pipeline should retrieve the code.
- Enter the first few characters of the branch name and the auto-complete feature of this field will find the matching branches to help you select.
-
Click Save.
You have now created your first pipeline! Users with the deployment manager role can now start the pipeline from the Cloud Manager UI.
Deploy deploy
Now that developers have added their custom code to the git repositories and you have a pipeline created to deploy that code, it is time to execute the pipeline to actually move that code from git to your environment.
-
Log into Cloud Manager at and select the appropriate organization and program.
-
Navigate to the Pipelines card from the Program Overview page and click the ellipsis button next to the pipeline you created in the previous section and select Run from the menu.
-
The pipeline run begins and is indicated by the Status column.
You can see the details of the run by clicking the ellipsis button again and selecting View details.
Congratulations! You have now deployed code from your git repository to a non-production environment!
What’s Next whats-next
Now that you have read this document you should:
- As a developer, understand how to access and manage your Cloud Manager git repositories.
- As a deployment manager, be able set up pipelines and deploy your code in Cloud Manager.
You have hit the ground running as a developer or deployment manager with not only working knowledge of Cloud Manager but also working environments, repositories, and pipelines! But there is more to learn about AEM as a Cloud Service’s powerful CI/CD tools. Check out the Additional Resources section for more details.
If you are interested in how content authors access and use AEM as a Cloud service, continue on to the final part of the onboarding journey, AEM User Tasks.
Additional Resources additional-resources
The following are additional, optional resources if you would like to go beyond the content of the onboarding journey.
- Accessing Repositories - Learn how to access and manage your git repository using the self-service git account management from Cloud Manager.
- Using git with Cloud Manager - Learn how to use Cloud Manager’s git repositories and how to integrate your own on-premise customer-managed git repository with Cloud Manager.
- Local Development Environment Set up - This tutorial walks you through setting up a local development environment for ÃÛ¶¹ÊÓƵ Experience Manager (AEM) using the AEM as a Cloud Service SDK.
- Getting Started with AEM Sites - WKND Tutorial - This multi-part tutorial is designed for developers new to ÃÛ¶¹ÊÓƵ Experience Manager (AEM). This tutorial walks through the implementation of an AEM site for a fictitious lifestyle brand the WKND. The tutorial covers fundamental topics like project setup, Core Components, Editable Templates, Client-side libraries, and component development with ÃÛ¶¹ÊÓƵ Experience Manager Sites.
- Getting Started with SPAs in AEM Using React - This article presents a sample SPA application, explains how it is put together, and lets you get up-and-running with your own SPA quickly using the React framework.
- Getting Started with SPAs in AEM Using Angular - This article presents a sample SPA application, explains how it is put together, and lets you get up-and-running with your own SPA quickly using the Angular framework.
- Headless Developer Journey - Start here for a guided course for developing headless applications with AEM.