Skip to content
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

Open
WDrake98 opened this issue Sep 14, 2015 · 10 comments
Open

Failed Packages #2

WDrake98 opened this issue Sep 14, 2015 · 10 comments

Comments

@WDrake98
Copy link

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?

@cturano
Copy link
Contributor

cturano commented Sep 14, 2015

Thanks Nona!
That's a good idea. I'll take a look at doing that.

@cturano
Copy link
Contributor

cturano commented Sep 15, 2015

I have updated the deployer so packages that throw exceptions while installing are renamed, preventing the deployer from re-trying the package.

@WDrake98
Copy link
Author

Thanks so much! Should I just get the latest dll?

@cturano
Copy link
Contributor

cturano commented Sep 15, 2015

Hi Nona,
You should be able to get the v1.1 update package in the root and let it upgrade itself. Please let me know how that works with broken packages. If you still have issues, can you send me your Sitecore logs.

Thanks

Charlie

@BradKnowles
Copy link

There doesn't seem to be a v1.1 update package in the repo. Am I missing it?

@cturano
Copy link
Contributor

cturano commented Oct 14, 2015

Hi Brad,
1.2 is the latest. There was an issue with 1.1

Thanks

Charlie

@BradKnowles
Copy link

OK cool. Where can I find 1.2?

@cturano
Copy link
Contributor

cturano commented Oct 14, 2015

@BradKnowles
Copy link

Oh gosh, duh. Thanks!

@cturano
Copy link
Contributor

cturano commented Oct 14, 2015

Anytime! Let me know if you run into any issues.

Thanks

Charlie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants