testpool-beat

command module
v0.0.0-...-54935fa Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 3, 2018 License: Apache-2.0 Imports: 3 Imported by: 0

README

Testpool-beat

Welcome to Testpool-beat.

Ensure that this folder is at the following location: ${GOPATH}/github.com/testcraftsman

Getting Started with Testpool-beat

Requirements
Init Project

To get running with Testpool-beat and also install the dependencies, run the following command:

make setup

It will create a clean git history for each major step. Note that you can always rewrite the history if you wish before pushing your changes.

To push Testpool-beat in the git repository, run the following commands:

git remote set-url origin https://github.com/testcraftsman/testpool-beat
git push origin master

For further development, check out the beat developer guide.

Build

To build the binary for Testpool-beat run the command below. This will generate a binary in the same directory with the name testpool-beat.

make
Run

To run Testpool-beat with debugging output enabled, run:

./testpool-beat -c testpool-beat.yml -e -d "*"
Test

To test Testpool-beat, run the following command:

make testsuite

alternatively:

make unit-tests
make system-tests
make integration-tests
make coverage-report

The test coverage is reported in the folder ./build/coverage/

Update

Each beat has a template for the mapping in elasticsearch and a documentation for the fields which is automatically generated based on etc/fields.yml. To generate etc/testpool-beat.template.json and etc/testpool-beat.asciidoc

make update
Cleanup

To clean Testpool-beat source code, run the following commands:

make fmt
make simplify

To clean up the build directory and generated artifacts, run:

make clean
Clone

To clone Testpool-beat from the git repository, run the following commands:

mkdir -p ${GOPATH}/github.com/testcraftsman
cd ${GOPATH}/github.com/testcraftsman
git clone https://github.com/testcraftsman/testpool-beat

For further development, check out the beat developer guide.

Packaging

The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires docker and vendoring as described above. To build packages of your beat, run the following command:

make package

This will fetch and create all images required for the build process. The hole process to finish can take several minutes.

Documentation

The Go Gopher

There is no documentation for this package.

Directories

Path Synopsis

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL