CI and release process for pdig

[leodido]

Motivation

This tool is the opensource userspace instrumentation for Falco.

Thus, we need to build and test it in the open. For this reason, I propose to set up a CI process for this repository as we have for other Falco projects.

Furthermore, we should also establish a release process so as to be able to distribute pdig binaries to our community.

Feature

• CI
  • build step
  • test step
  • release step
• Release process documentation

Additional context

Notice that pdig depends on the underlying libsinsp/libscap libraries that have their own versioning (to which we refer as "driver version" into Falco).

We have two possible versioning approaches here:

1. version pdig with the same hash for the underlying libsinsp/libscap libraries
   • Falco already has a concept of "driver version"
   • Community can lookup pdig by the "driver version" supported by a specific Falco version
2. version pdig separately using GitHub releases

Blocks falcosecurity/falco#1195

[leodido]

Revamped the discussion about this in the community call on Sept 23th 2020.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[poiana]

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

[poiana]

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[leodido]

/remove-lifecycle rotten

On Sun, 21 Feb 2021 at 22:01 poiana ***@***.***> wrote: @poiana <https://github.com/poiana>: Closing this issue. In response to this <#16 (comment)>: Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Provide feedback via https://github.com/falcosecurity/community. /close Instructions for interacting with me using PR comments are available here <https://git.k8s.io/community/contributors/guide/pull-requests.md>. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra <https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:> repository. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5J46OYCQFMPLRBDOLNQDTAFYEPANCNFSM4O2MB42Q> .

-- L.