Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Incremental CRX package deployment | AEM Community Blog Seeding

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,198 likes

Total Posts

6,375 posts

Correct Reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,198 likes

Total Posts

6,375 posts

Correct Reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

12-05-2020

BlogImage.jpg

Incremental CRX package deployment by Krystian Panek

Abstract

One of the Gradle fundamentals is to build everything incrementally - in case of GAP, we already got an incremental AEM package building.
The missing part in GAP was the incremental AEM package deployment.

Build ends extremely fast, as there are no new dependent packages to be installed, no new provisioning steps to be executed on AEM instances, and also no changes detected in built AEM packages when comparing with deployed ones.
Still, if any of these changes will be done in future, GAP will detect them automatically and apply a particular change only. All in an automatic and transparent manner.

Read Full Blog

Incremental CRX package deployment

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager