https://github.com/osquery/osquery logo
#core
Title
# core
s

seph

08/18/2022, 1:25 PM
I just cut https://github.com/osquery/osquery/releases/tag/5.5.1 This includes a sqlite update. We do not believe osquery to be effected, but like ever, people like to know we’re on top of these.
z

zwass

08/18/2022, 3:12 PM
I don't see assets on the release page -- is there another step we need to complete?
s

seph

08/18/2022, 3:12 PM
It’s building.
z

zwass

08/18/2022, 3:13 PM
Ah, thank you!
s

Stefano Bonicatti

08/18/2022, 3:14 PM
From the codesign repo I see the last job failed; seems some internal error at Github?
s

seph

08/18/2022, 3:14 PM
In meeting. Feel free to rerun or something
I’ll debug in a few hours
s

sharvil

08/18/2022, 3:16 PM
Yeah, github actions is having "degraded performance" https://www.githubstatus.com/
s

Stefano Bonicatti

08/18/2022, 3:17 PM
I’ve also noticed a warning on the previous successful job: https://github.com/actions/runner-images/issues/6002. It’s probably unrelated (as Sharvil shows)
s

seph

08/18/2022, 4:05 PM
@zwass This process looks like: 1. Human cuts release tag 2. Automation runs build on
master
they take about an hour 3. Human triggers codesign build (depends on 2) 4. automation codesigns and uploads to the release
z

zwass

08/18/2022, 4:08 PM
Can we use a repository_dispatch event to trigger the codesign?
m

Mike Myers

08/18/2022, 5:06 PM
I believe that might have been manual, as a failsafe
s

seph

08/18/2022, 5:43 PM
repository_dispatch
is surprisingly hard — it requires permissions that get dicy. If we wanted to automate it, I’d probably look at something cron based. Not perfect, but maybe good enough.
4 Views