Skip to content

Latest commit

 

History

History
34 lines (24 loc) · 1.71 KB

NPCAP.md

File metadata and controls

34 lines (24 loc) · 1.71 KB
Raw

NPCAP

If you'd like to bump the npcap version please follow the below steps:

  1. Update NPCAP_VERSION value in the Makefile.
  • NOTE: Make sure the PR adding this is back-ported to the Go versions required by the Packetbeat CrossBuild target in the mage file. This is specified in the beats .go-version file.
  1. Download the new artifact.
  2. Upload the artifact to gs://ingest-buildkite-ci/private.
  • NOTE: This particular Google Bucket can be accessible only by Elasticians who have got access to the Google project called elastic-platform-ingest.

Credentials to the artifact service can be found in the APM-Shared folder in the password management tool.

Backports

If you'd like to backport any NCAP_VERSION to any existing golang-crosbuild version, then you need to:

  • Create a branch called major.minor.patch.x for the vmajor.minor.patch tag
  • Cherry-pick your PR, you can use Mergifyio, with @mergifyio backport major.minor.path.x
  • Then the new PR that has been created can be merged when all the GitHub checks have passed.

For instance, if ncap version needs to be updated in 1.20.8 then:

git checkout v1.20.8
git checkout -b 1.20.8.x
git push upstream 1.20.8.x

Afterwards you can then backport your PR with ncap changes with the GitHub command @Mergifyio backport 1.20.8.x, see elastic#315 that illustrates this example.

elastic#320 is the one that has been created with the backport targeting 1.20.8.x. Automatically when it gets merged, the golang-crossbuild:1.20.8 will be regenerated and contain the new ncap changes.