GitXplorerGitXplorer
m

githubhistorybeat

public
3 stars
0 forks
0 issues

Commits

List of commits on branch master.
Verified
33f087103ccdc70bd21864d4675b80faeed8a768

Preapre version 1.3.0

mmmatur committed 7 years ago
Verified
86520b200f7be609f022207f816a93e5dfdbd7a2

Fix issue with duplicate timestamp

mmmatur committed 7 years ago
Verified
2a926a9972b3b6c78c7b64aba05d0f49917c6d2b

Fix travisci

mmmatur committed 7 years ago
Verified
fd808ea15d026f8f585f58052e1eab88e1de0d00

Upgrade go version in travis

mmmatur committed 7 years ago
Verified
017044f1bc0ec338e585e853290f42349c165852

Upgrade to new beat version

mmmatur committed 7 years ago
Verified
fb92a8d066f74f5e8da973b1df5d4e8bd44b694d

Disable SNAPSHOT on build

mmmatur committed 8 years ago

README

The README file for this repository.

Githubhistorybeat

Welcome to Githubhistorybeat.

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

Getting Started with Githubhistorybeat

Requirements

Init Project

To get running with Githubhistorybeat 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 Githubhistorybeat in the git repository, run the following commands:

git remote set-url origin https://github.com/mmatur/githubhistorybeat
git push origin master

For further development, check out the beat developer guide.

Build

To build the binary for Githubhistorybeat run the command below. This will generate a binary in the same directory with the name githubhistorybeat.

make

Run

To run Githubhistorybeat with debugging output enabled, run:

./githubhistorybeat -c githubhistorybeat.yml -e -d "*"

Test

To test Githubhistorybeat, 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/githubhistorybeat.template.json and etc/githubhistorybeat.asciidoc

make update

Cleanup

To clean Githubhistorybeat 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 Githubhistorybeat from the git repository, run the following commands:

mkdir -p ${GOPATH}/github.com/mmatur/githubhistorybeat
cd ${GOPATH}/github.com/mmatur/githubhistorybeat
git clone https://github.com/mmatur/githubhistorybeat

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.