AEM Maintenance Update does not pick up the latest Git Tag or Commit for deployment in AEMaaCS

[Rohan_Garg]

Hi AEM Community,

We had a trigger on our release/production pipeline by the AEM Maintenance Update.

The weird issue was that the pipeline was triggered with an old git tag and Commit ID.

The auto update picked up the Git Tag and Commit ID in the release branch from October 5, 2023.

The most recent Git Tag and Commit were from today's date October 31, 2023.

Is there any particular reason why the AEM Maintenance Update will not pick up the last commit from the deployment/release branch?

Thanks,

Rohan Garg

[aanchal-sikka]

@Rohan_Garg 

The CM should have picked the latest code in the current branch + Create a new Tag is its an updated code. Else an old tag, if nothing changed since last execution.

If you are noticing a discrepancy, please raise an Adobe ticket

[Rohan_Garg · Accepted solution]

Hi @aanchal-sikka, thanks for the response! We have raised the Adobe ticket as well but just wanted to get an idea if the issue's been seen before.

It came up only in this release when the AEM instances got upgraded to 2023.10.14029.20231020T111912Z.

[Jörg_Hoh]

was the git commit of Oct 31s deployed to PROD or only to Stage?

[Rohan_Garg]

@Jörg_Hoh - The git commit from 5th Oct was picked up instead of 31st Oct & it was deployed to PROD as well