Closed tripathihsr closed 7 years ago
Please share your comment
Hi @tripathihsr -
It's hard for me to make out the screenshots above as the resolution is poor. A few things would help me understand better.
Thanks, Zach
uff..i dont know why couldn't see your reply, sorry
Please find response below..
..
deployrelease: [echo] Initializing ydeploy [echo] ydeploy yenv: [echo] ydeploy yserverid: [echo] ydeploy yreleaseid: 0
-init:
Hi Zmcmahon, do you think you can help here?
Regards!
@tripathihsr -
As mentioned previously, ydeploy does not modify the localextensions.xml file, but the core hybris build process may. You may want to try just modifying the localextensions.xml in the expanded releases/0 directory to point to the correct path, and then invoke the hybris build process directly just to make sure everything is working and building. To me it sounds like some step is failing quietly (such as the symbolic link creation), the ydeploy configurations are incorrect based upon the actual directory layout you are using, or perhaps there is a fully qualified path somewhere in your configuration (possibly localextensions.xml) during build time. Will need more details regarding your configuration & layout to know.
What are the contents of the localextensions.xml before running the build (i.e. before deploy)? Can you please post the full contents before & after for comparison? In code repository: <?xml version="1.0" encoding="UTF-8"?>
After ‘ant build’ (no change) <?xml version="1.0" encoding="UTF-8"?>
some text messages are distorted see reference for #4
@tripathihsr -
Thanks for providing all the info.
I had a chance to test your setup using 6.3 on windows & linux today, and it does look like you've run into an issue for linux setups caused by changes in the hybris 6.3 'production' build task. Specifically, they are now regenerating the config/localextensions.xml file by default (can disable with production.generate.extensionsxml=false property), but the paths are not being generated correctly when symbolic links are used for the bin/custom directory.
I've made some updates in the branch below which seemed to resolve the issue for me. Can you integrate these changes into your setup and retry? https://github.com/avatria/ydeploy/commit/37e26f0d9ea3e3aa80778bebe86f1658439afba1
You will need to run both 'build' and 'genrelease' again in a clean setup (i.e. delete anything under the ydeploy/temp directory) before running 'deployrelease'.
If all works well on your end, I will merge these changes into the master branch.
Thanks, Zach
Hi Zach, glad to confirm that it is working fine. Thank you so much for quick assistance, have a great time! Regards!
@tripathihsr - Glad to hear! Thanks again for reporting the issue and working through.
Merged to master. Cut new release v0.1.4.
Hi Zmcmahon,
Thanks for providing the custom build framework.
I was trying to utilize this for my research but it is failing at an specific point.
I am able to successfully execute 'ant build' and 'ant genrelease' but it fails while executing 'any deployrelease'
while troubleshooting i find that some additional paths are added in 'localextension.xml' after 'ant genrelease' but didn't get any clue how to fix it
Please take a look at screnshot
This is path of custom extensions which i can in the package 'hybrisServer-Release-0.zip' generated after 'ant genrelease'
snippets after 'ant deployrelease' filure
Please share some pointers to fix it