Lately I've been wondering about Continuous Integration and Delivery best practices for an Alfresco project. Unfortunately, I found mainly dated presentation (SDK 1.0). I think that with the SDK 3.0 things change a little bit:-)
I personally think that the best solution is to deliver the final .war file. This guarantees no further manipulation (apply_amps.sh), no generation error and easier rollback.
But in any case, here are all the possibilities I thought:
- Generate amp file and deliver it
- Generate .jar file and deliver it
- In the CI take the generated amp from apply it to a war and deliver that war
- run the "alfresco:run" command with "generate-wars-only" profile and get the resulting war. (Not a big fan)
What do you think:
- Do you see other possibilities?
- How do you manage your CI/CD on your Alfresco projects?
- Make it possible to generate WARs without alfresco:run in SDK 3.0 · Issue #420 · Alfresco/alfresco-sdk · GitHub
- GitHub - toonconvents/alfresco-sdk: The Alfresco SDK based on Apache Maven, includes support for rapid and standard deve…
- Enabling Test-Driven, Rapid Dev, & Continuous Delivery of Alfresco Apps | Alfresco Summit is becoming Alfresco Days