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

When contents generation fails, don't bail out #534

Merged
merged 1 commit into from
Mar 31, 2017

Conversation

smira
Copy link
Contributor

@smira smira commented Mar 30, 2017

Description of the Change

This replaces panic which aborts aptly execution with warning
message on console. So aptly continues publishing actions, but
Contents indexes might be incomplete.

Error will be printed every time contents generation is triggered.

Fixes #533, #451

Checklist

  • unit-test added (if change is algorithm)
  • functional test added/updated (if change is functional)
  • man page updated (if applicable)
  • bash completion updated (if applicable)
  • documentation updated
  • author name in AUTHORS

@smira smira added the 1.1.0 label Mar 30, 2017
@smira smira mentioned this pull request Mar 30, 2017
This replaces `panic` which aborts aptly execution with warning
message on console. So aptly continues publishing actions, but
`Contents` indexes might be incomplete.

Error will be printed every time contents generation is triggered.
@smira smira force-pushed the 533-ignore-contents-failures branch from 0b10b8f to 7a5be67 Compare March 30, 2017 21:57
@smira smira merged commit bc01d9e into master Mar 31, 2017
@smira smira deleted the 533-ignore-contents-failures branch March 31, 2017 13:38
@smira
Copy link
Contributor Author

smira commented Mar 31, 2017

aptly_1.0.0+11+gbc01d9e nightly build includes this fix

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

Successfully merging this pull request may close these issues.

1 participant