We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#87 and #89 shown that since the packaging process is quite different from producing static binaries, old and new bugs can appear quite unexpectedly.
We should have a testing scenario similar to what is already done for static binaries, that will install the latest packages and test them.
However, the process of building binary packages is quite long, so, apparently, this should be done either on schedule or via the manual trigger.
Binaries that are packed in native Ubuntu and Fedora packages are tested.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Clarification and motivation
#87 and #89 shown that since the packaging process is quite different from producing static binaries,
old and new bugs can appear quite unexpectedly.
We should have a testing scenario similar to what is already done for static binaries, that will install
the latest packages and test them.
However, the process of building binary packages is quite long, so, apparently, this should be done either on
schedule or via the manual trigger.
Acceptance criteria
Binaries that are packed in native Ubuntu and Fedora packages are tested.
The text was updated successfully, but these errors were encountered: