teleport/.gitignore

81 lines
903 B
Plaintext
Raw Normal View History

# this file gets generated by make
2016-06-14 23:52:32 +00:00
gitref.go
.data
debug
2017-01-16 07:25:37 +00:00
default.etcd
darwin
2016-06-14 23:52:32 +00:00
# web asset directory
/lib/web/build
# usually release tarballs get in the way
*.gz
*.zip
2016-12-24 19:54:23 +00:00
# editors
.vscode
*.swp
.idea
2016-12-24 19:54:23 +00:00
2016-01-17 22:50:00 +00:00
# Compiled binaries, Object files, Static and Dynamic libs (Shared Objects)
out
2016-03-23 01:22:48 +00:00
build
*.o
2015-03-02 19:36:00 +00:00
*.a
*.so
# Folders
_obj
_test
tmp
target/
test-logs/
2015-03-02 19:36:00 +00:00
# Architecture specific extensions/prefixes
[568vq].out
*.cgo1.go
*.cgo2.c
_cgo_defun.c
_cgo_gotypes.go
_cgo_export.*
2016-03-19 17:41:54 +00:00
.bash_history
2015-03-02 19:36:00 +00:00
_testmain.go
*.exe
*.test
*.prof
*.tmp
flymake*
# mkdocs
docs/latest
docs/latest.yaml
2017-11-10 20:22:47 +00:00
# terraform
.terraform
2018-01-17 19:59:55 +00:00
terraform.tfstate
# macOS
**/.DS_Store
2018-02-06 21:26:57 +00:00
# ansible stuff
ssh.config
*.retry
Sign tsh.exe on tag builds (#7897) * Sign tsh.exe on tag builds This adds a Makefile step to sign tsh.exe when the `$WINDOWS_SIGNING_CERTIFICATE` env var is set to a base64-encoded pkcs12 code signing certificate. The certificate must not be password protected. This includes a sample cert (`cert-dummy.pfx`) for CI pipeline testing. It should be removed in any eventual PR, along with the other modifications to the drone pipeline. The cert is imported into the environment in the `Makefile` for testing purposes; in practice it will be imported from a secure secret store (drone secrets, etc). * Improve Windows code signing - Split signing into a separate step; `release-windows-unsigned` now performs the build, `release-windows` signs the binary. - Require `release-windows` to successfully generate a signed binary. - Clearly mark unsigned binaries and archives as such. - Guard against stdout secret leakage in Makefiles. - Move temporary cert data from Makefile into dronegen to test full pipeline. * Use an invalid cert string for testing purposes. * Pass certs to the build process via a statically named file Signed Windows builds now depend on a `.gitignore`'d `windows-signing-cert.pfx` at the root of the source directory. This should ease testing and help avoid accidental secret leakage. * Use production secret * Remove windows-signing-cert.pfx before continuing to the next step Additionally, fix variable reference as the bracket syntax does not seem to play nice with Drone. * Update .gitignore Co-authored-by: Andrew Lytvynov <andrew@goteleport.com> Co-authored-by: Andrew Lytvynov <andrew@goteleport.com>
2021-09-02 22:34:57 +00:00
# Code signing certificate for Windows binaries
/windows-signing-cert.pfx
Attempts to make CI integration test logs more useful (#9626) Actually tracking down the cause of a failure in the integration tests can be hard: * It's hard to get an overall summary of what failed * The tests sometimes emit no output before timing out, meaning any diagnostic info is lost * The emitted logs are too voluminous for a human to parse * The emitted logs can present information out of order * It's often hard to tell where the output from one test ends and the next one begins This patch attempts to address these concerns without attempting to rewrite any of the underlying teleport logging. * It improves the render-tests script to (optionally) report progress per- test, rather than on a per-package basis. My working hypothesis on the tests that time out with no output is that go test ./integration is waiting for the entire set of integration tests tests to be complete before reporting success or failure. Reporting on a per-test cycle gives faster feedback and means that any timed-out builds should give at least some idea of where they are stuck. * Adds the render-tests filter to the integration and integration-root make targets. This will show an overall summary of test results, as well as - Discarding log output from passing tests to increase signal-to-noise ratio, and - Strongly delimiting the output from each failed test, making failures easier to find. * Removes the notion of a failure-only logger in favour of post-processing the log events with render-tests. The failure-only logger catches log output from the tests and only forwards it to the console if the test fails. Unfortunately, not all log output is guaranteed to pass through this logger (some teleport packages do not honour the configured logger, and reports from the go race detector certainly don't), meaning some output is presented at the time it happens, and other output is batched and displayed at the end of the test. This makes working out what happened where harder than it need be. In addition, this patch also promotes the render-tests script into a fully- fledged program, with appropriate makefile targets, make clean support, etc. It is now also more robust in the face on non-JSON output from go test (which happens if a package fails to compile).
2022-01-04 23:42:07 +00:00
# Build cache and tooling
/build.assets/.cache
/build.assets/tooling/bin/**
# Teleport binaries
/tctl
/teleport
/tsh
# Go workspace files
go.work
go.work.sum