-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nexus is redeployed everytime #90
Comments
I am seeing this as well. Definitely makes running chef-client in daemon mode a non-starter. |
I had the same issue using nexus cookbook from supermarket, this did not create "shared/tmp" folder and symlink to it - so generated manifest file differs each time. Maybe this info help to nail down your issue. |
okay thanks i will check this out |
i have found my problem nexus is trying to redeploy it self every time |
i see now that it is the artifact cookbook is checking file changes but this must be set in the nexus cookbook itself :( so the best option should be to integrate this possibility
and set
under line i can make a pull request if needed |
pull request see #119 |
I have this issue as well 👍 |
As a workaround add the following in a wrapper cookbook after including the nexus recipe (e.g. resources("artifact_deploy[#{node['nexus']['name']}]").skip_manifest_check true |
+1 to merge this pull request from my side. I also have to edit the wrapper to set memory sizes, which causes a nexus restart. |
i noticed that every chef-run nexus is redeployed
is this normal behavior or did i do something wrong
The text was updated successfully, but these errors were encountered: