You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally the builds are not failing when the expected binary is not found within GCS. This means that the latest set of images are broken (e.g. docker.elastic.co/observability-ci/golang-crossbuild:1.21.6-npcap-1.79-debian9) because they don't have the npcap oem installer.
Put gs://ingest-buildkite-ci/private/npcap-1.79-oem.exe in place.
Overwrite the images that were published for npcap-1.79.
It would be awesome if there were a buildkite job to automate grabbing the latest npcap. I can provide the npcap credentials (they are in Vault).
# Check what the newest release is using Github.
latest_version=$(curl https://api.github.com/repos/nmap/npcap/releases/latest | jq -r .tag_name | sed 's/^v//g')
# Check if we already have the OEM installer in our GCS bucket.
if gcloud storage ls gs://ingest-buildkite-ci/private/npcap-${latest_version}-oem.exe ; then
echo "Already present."
exit
else
# Download it into our GCS bucket.
echo "Fetching new npcap installer"
curl -L -O --digest -u "$NPCAP_USER:$NPCAP_USER" "https://npcap.com/oem/dist/npcap-${latest_version}-oem.exe"
gcloud storage cp ./npcap-${version}-oem.exe gs://ingest-buildkite-ci/private/npcap-${latest_version}-oem.exe
# Open a PR to bump the version in `Makefile.common`.
In the docs at https://github.com/elastic/golang-crossbuild/blame/43f2c4205fe38de4fecf61c39df80a9177062388/NPCAP.md#L8 the bucket name for storing npcap is documented as
gs://obs-ci-cache/private
, but the builds are looking atgs://ingest-buildkite-ci
.Additionally the builds are not failing when the expected binary is not found within GCS. This means that the latest set of images are broken (e.g. docker.elastic.co/observability-ci/golang-crossbuild:1.21.6-npcap-1.79-debian9) because they don't have the npcap oem installer.
gs://ingest-buildkite-ci/private/npcap-1.79-oem.exe
in place.The text was updated successfully, but these errors were encountered: