-
Notifications
You must be signed in to change notification settings - Fork 22
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
Failed Packages #2
Comments
Thanks Nona! |
I have updated the deployer so packages that throw exceptions while installing are renamed, preventing the deployer from re-trying the package. |
Thanks so much! Should I just get the latest dll? |
Hi Nona, Thanks Charlie |
There doesn't seem to be a v1.1 update package in the repo. Am I missing it? |
Hi Brad, Thanks Charlie |
OK cool. Where can I find 1.2? |
Hi Brad, Charlie |
Oh gosh, duh. Thanks! |
Anytime! Let me know if you run into any issues. Thanks Charlie |
Hey guys,
Loving this module. I do have a slight problem in that update packages that have errors (still troubleshooting why it's an error, probably missing related content) remain in the initial folder. Impact is that the task runs over and over and over again for the same update package. Could it be possible to move the failed packages into a different folder?
The text was updated successfully, but these errors were encountered: