user avatar
Add release process to Jenkinsfile for the CLI
Zain Asgar authored
Summary: This adds a job that runs on Jenkins to build the release CLI when tags are pushed. It also adds the infromation to the artifact DB.

Test Plan: Tested on Jenkins.

Reviewers: michelle, #engineering

Reviewed By: michelle, #engineering

Differential Revision: https://phab.corp.pixielabs.ai/D2335

GitOrigin-RevId: 45eb917d3cecb58b1084942f226117d71555efa9
78d98f52
Name Last commit Last update
.idea Add Go script that dynamically finds user includes in bpf files and expands with the header's content.
.vscode PL-406 Allow optional args
bazel Add release process to Jenkinsfile for the CLI
chef Enabled shellcheck linter
ci Add release process to Jenkinsfile for the CLI
demos Sock-shop: use app/v1 instead of extensions/v1beta1
docker Update Clang/LLVM to version 8.0
docs PixieDocs: remove out-of-date content.
k8s Add release process to Jenkinsfile for the CLI
linters Add shellcheck linter and configs
scripts Enabled shellcheck linter
skaffold Add ArtifactTracker yamls
src Add release process to Jenkinsfile for the CLI
third_party Adding glice to the repo
.arcconfig Add shellcheck linter and configs
.arclint Enable YAML linter
.bazelignore Change experimental build to use pl_exp_ variants
.bazelproject Clion with bazel setup
.bazelrc Add release process to Jenkinsfile for the CLI
.clang-format Clang-format: Make pointer bind to type
.clang-tidy Add ability to run clang-tidy
.flake8rc Add standard linters
.gitignore Adding npm license checker script that parses the license-checker output
.gitmodules Adding glice to the repo
.yamllint Fix DB update utils and add Job to update the database.
BUILD.bazel
Doxyfile
Jenkinsfile
LICENSE.txt
Makefile
README.md
WORKSPACE
docker.properties
go.mod
go.sum
pixielabs.sublime-project
workspace.bzl

Pixie Labs Main Repository

  • bazel/: Bazel workspace scripts.
  • chef/: Chef scripts. For setting up your laptop, building dev docker images, etc.
  • demos/: Demo apps for showcasing PixieLabs product in a realistic usage scenario.
  • docker/: Dockerfiles for various distributable software packages.
  • docs/: Documentations for PixieLabs customers.
  • experimental/: Sandbox for experimental code. Not reviewed or maintained as strictly as other code.
  • k8s/: Kubernetes deploy yaml files.
  • linters/: Linters. Their settings are in .arclint.
  • scripts/: Scripts for one-off tasks.
  • src/: Main sources of PixieLabs product.
  • templates/skaffold: System for building and deploying our product on Kubernetes.
  • third_party/: Assets for pulling in external repos.