-
Notifications
You must be signed in to change notification settings - Fork 24
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
Added possibility to specify different priorities per status #57
base: master
Are you sure you want to change the base?
Conversation
@Castaglia could you give me a hint, why checks are failing? I don't see any relation to the PR |
Both of the failed builds look to have failed during package installation. It doesn't look like I have the TravisCI permissions there to re-run the builds, to see if it's a transient build issue. |
I have kicked off another build, you can always use the empty commit trick to kick off CI builds if your CI provider supports build/run on commit. |
I think the issue is that the base image we use is actually based on jessie which is now in the LTS phase and maybe some repositories are no longer accessible or contain the artifacts requested. When I have some time I will try to sit down and figure it out. |
I will have to look at if its possible for us to inject this early enough without going to newer builds: https://superuser.com/questions/1423486/issue-with-fetching-http-deb-debian-org-debian-dists-jessie-updates-inrelease |
This works like expected except when alert recovers and needs to be updated, it hits this error:
I suppose this is because |
Pull Request Checklist
Is this in reference to an existing issue?
#36
General
[+] Update Changelog following the conventions laid out here
[+] Update README with any necessary configuration snippets
[-] Binstubs are created if needed
[-] RuboCop passes
[+] Existing tests pass