Hi @mario248 ,
AIO workspace is NOT cloudmanager controlled. But you can sure automate with Jenkins if required.
Adobe provides even better CI-CD devops experience using Github Actions. There are lot of documentation:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/configuring-and-extending/app-builder/deploy
https://developer.adobe.com/app-builder/docs/guides/deployment/
https://developer.adobe.com/app-builder/docs/getting_started/publish_app/
https://developer.adobe.com/app-builder/docs/guides/deployment/ci_cd_for_firefly_apps/
I ll summarize if documentation is overwhelming
Adobe recommended way: Github Workflows
- Inside your Github project, create .github/workflows folder
- Create deploy_stage.yaml and copy this script
- Create deploy_prod.yaml and copy this script
- Add required github secrets. CD done. Next time commit happens to stage branch, it will automatically deploy the action.
- I simplified my Prod script like stage, to deploy when commit happens to `main` branch
Custom way using Jenkins:
- You may not like the adobe Github workflows, maybe coz, you dont have enterprise github. Or want traditional waterfall methodology to deploy during production nights etc.
- If you are writing Jenkins job, it is reinventing. You ll follow exact steps as adobe workflow
- Checkout code
- Install node, npm i
- install adobe/aio-cli-setup-action, adobe/aio-apps-action
- setup secrets as env variables
- Finally run `aio app deploy`. If required add --force-build, verbose, --no-action, whatever required flags.
One comment though, we tried converting workflow into curl commands and running inside a our client github runners. It failed due to client firewall restrictions. Advice would be to make adobe workflows run. And then explore alternate solutions if required.