Manual AEM bundle deployment Issues | Community
Skip to main content
akhilraj
Level 5
September 12, 2022
Solved

Manual AEM bundle deployment Issues

  • September 12, 2022
  • 1 reply
  • 1259 views

Hi,

 

We came across below issue in our instances.

 

Initially we were doing bundle deployments manually always to author and publishers and everything was working fine.

 

Recently we did Jenkins integration for deployment and that also working fine.

 

But Issue is, after Jenkins deployment, any time if we try to deploy bundles manually, the changes are not reflecting, even after service restart also it will not work.

If we do the changes via Jenkins it is working even without service restart.

 

Issues will occur for bundles only if we do manually  and package installation will work in either ways.

 

We are not clear about the logic behind it.

 

Did anyone came across this kind of issues, or any possible solutions ?

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

but there are no subnodes(nt:unstructured node which contain pause) inside/system/sling/installer/jcr/pauseInstallation so this is not a reason of your issue.

 

Probably check the logs and event logs and see what is happening

1 reply

arunpatidar
Community Advisor
Community Advisor
September 12, 2022

Hi,

Check the bundle version. both bundle has same version or different if you are going to deploy lower version then it will not work.

One more thing check the jcrinstaller , Any pauseInstallation nodes below /system ? e.g. /system/sling/installer/jcr/pauseInstallation

delete if there are any pause installation.

 

Arun Patidar
akhilraj
akhilrajAuthor
Level 5
September 13, 2022

Yes, we have that folder available.

 

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
September 13, 2022

but there are no subnodes(nt:unstructured node which contain pause) inside/system/sling/installer/jcr/pauseInstallation so this is not a reason of your issue.

 

Probably check the logs and event logs and see what is happening

Arun Patidar