* Merge branch 'action-test' of github.com:openziti/ziti into simple-transfer-test
* added metricbeat initialization
* updates to the simple network testing
* update zitilab and fablad deps and integrate env variables
* removed incorrect file
* move env up to top
* added run and test
* mod tidy
* mod got out of sync
* remove influx logging from ziti-probe due to being removed from metrics
* add ls to see why simple-transfer isnt built
* dig deeper
* need to copy not move
* back to release dir
* might need to sudo
* mke files executable
* bootsrap from correct directory
* add extra restart to confirm network spins up
* add retry for inrastructure
* build correct binaries
* add build ignore ot stages as well
* don't return error after successful retry
* fix err assign
* update zitilab version
* removed local testing paths
* update configs and env variables
* added env prepend
* remove build number for debugging
* add different formatting
* updated build/run number
* paren in incorrect place
* added specific version of metricbeat to install
* flip back correct ziti loc
* removed builds for mac & windows
* Removed test build for mac & windows
* remove ziti-probe
* flip ziti test to run alongside mac & windows builds
* remove unneeded needs
* remove for sanity check
* remove old uploads
* remove space
* setup ziti version properly
* remove zitilab testing to confirm running
* try removing all changes?
* remove even comments?
* I dont understand
* revert
* start from scratch. Small increments.
* simplify first job?
* try spearating build and publish
* run all 3 builds at the same time
* missed env variables
* update to run zitilab tests
* corrected dirs
* fixing ziti root
* redo build in publish step
* applied pr comments
* add in mkdir and remove buildint test binaries in publish step
* forgot to remove move
* update linux build requirement to 1.19
run Docker steps on troubleshooting branch
Add run_id suffix to upload/download artifact steps to avoid race condition between multiple runs of the same job
only run ziti-ci if GITHUB_TOKEN is defined
check for gh_ci_key, not GITHUB_TOKEN
stop checking for gh_ci_key
use a temp Docker tag for troubleshooting
fixup workflow syntax
disable Docker build cache so we can see what the builder sees despite prior runs
recursively list contents of release/
innocuous modify of Dockerfile to miss cache
list later
try explicit artifacts dir
use workspace ref
revert to relative build dir
Revert "revert to relative build dir"
This reverts commit a72ae3ddaef207daf89bae6a4087f7b4979fd0f6.
stop ignoring /release/ in Docker context to workaround BuildKit bug until https://github.com/docker/buildx/pull/955 becomes available in the build-push-buildx Action
prune troubleshooting changes
Kenneth Bingham