CI integration

Quality Assurance (codacy), Continuous Improvements (circle) Coordinates (DockerHUB) integration

Author: jancajthaml

.circleci/config.yml

@@ -0,0 +1,74 @@
+version: 2
+
+jobs:
+  test:
+    docker:
+      - image: circleci/golang:1.9
+      
+    working_directory: /go/src/jancajthaml
+    steps:
+      - checkout
+
+      - run:
+          name: Sync dependencies
+          command: |
+            go get -u github.com/kardianos/govendor
+            govendor sync -v
+
+      - run:
+          name: Run tests
+          command: |
+            cd /go/src/jancajthaml/src/datadog-mock
+            go test -v ./...
+
+      - run:
+          name: Build server
+          command: |
+            cd /go/src/jancajthaml/src/datadog-mock
+            go clean
+            CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o /go/src/github.com/jancajthaml/target/datadog_mock
+
+      - persist_to_workspace: 
+          root: /go/src/github.com/jancajthaml
+          paths:
+            - target/datadog_mock
+
+  deploy:
+    docker:
+      - image: docker:17.05.0-ce-git
+
+    working_directory: /app
+    steps:
+      - attach_workspace:
+          at: /go/src/github.com/jancajthaml
+
+      - checkout
+
+      - setup_remote_docker
+
+      - run:
+          name: Build application Docker image
+          command: |
+            cp -r /go/src/github.com/jancajthaml/target /app/target
+            docker build -t bundle .
+
+      - run:
+          name: List images
+          command: |
+            docker images
+
+      - deploy:
+          name: Push image to DockerHUB
+          command: |
+            docker login -e ${DOCKER_EMAIL} -u ${DOCKER_USER} -p ${DOCKER_PASSWORD}
+            docker tag bundle "jancajthaml/datadog_mock:${CIRCLE_SHA1}"
+            docker push "jancajthaml/datadog_mock:${CIRCLE_SHA1}"
+
+workflows:
+  version: 2
+  test_and_deploy:
+    jobs:
+      - test
+      - deploy:
+          requires:
+            - test

AUTHORS

@@ -1 +1 @@
-AUTHORS
+Jan Cajthaml <[email protected]>

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING

@@ -0,0 +1,4 @@
+All development activity takes place on github.
+
+If you think you've discovered a bug, or you would like
+to make a feature request please do this through github.

ISSUE_TEMPLATE.md

@@ -0,0 +1,26 @@
+### Step 1: Are you in the right place?
+
+  * For issues or feature requests related to the code **in this repository** file a Github issue.
+  * For general technical questions, post a question on [StackOverflow](http://stackoverflow.com/) tagged appropriately.
+
+### Step 2: Describe the problem:
+
+#### Steps to reproduce:
+
+  1. _____
+  2. _____
+  3. _____
+  
+#### Observed Results:
+
+  * What happened?  This could be a description, log output, etc.
+  
+#### Expected Results:
+
+  * What did you expect to happen?
+  
+#### Relevant Code:
+
+  ```
+  // TODO(you): code here to reproduce the problem
+  ```

Makefile

@@ -6,6 +6,10 @@ all: install test authors run
 .PHONY: install
 install: prepare-dev lint bundle
 
+.PHONY: perf
+perf:
+	@./dev/siege.sh
+
 .PHONY: fmt
 fmt:
 	docker-compose run --rm fmt

README.md

@@ -1,44 +1,24 @@
-# DataDog Server mock
+# datadog-mock #
 
-2MB golang server listening on port 8125 writing metrics to stdout.
+datadog-mock is a golang statsd mock server listening on port 8125 and relaying events to stdout.
 
-### Bootstrap
+[![Build Status](https://circleci.com/gh/jancajthaml/datadog-mock.svg?style=svg)](https://circleci.com/gh/jancajthaml/datadog-mock) [![Static Analysis](https://api.codacy.com/project/badge/Grade/c5c255a292f84cf88972f92f74f9174d)](https://www.codacy.com/app/jan-cajthaml/datadog-mock?utm_source=github.com&utm_medium=referral&utm_content=jancajthaml/datadog-mock&utm_campaign=Badge_Grade) [![Test Coverage](https://coveralls.io/repos/github/jancajthaml/datadog-mock/badge.svg?branch=master)](https://coveralls.io/github/jancajthaml/datadog-mock?branch=master)
 
-```
-make install
-make test
-```
+## Getting started ##
 
-### Running
+Bootstrap environment with `make install test` then grab `./target/datadog_mock`
+or docker image `datadog/mock`.
 
-```
-make run
-```
+## Usage ##
 
-or
+Run in docker with `make run` or `./target/datadog_mock` locally.
 
-```
-docker run -it --log-driver none --rm -p 0.0.0.0:8125:8125/UDP datadog/mock
-```
+## Testing ##
 
-or
+When datadog/mock is running you can either test simple relay
+`./dev/event-producer.sh` or siege with `make perf`.
 
-```
-./target/datadog_mock
-```
-
-
-### Verify
-
-When datadog/mock is running 
-
-```
-echo "deploys.test.myservice:1|c" > /dev/udp/127.0.0.1/8125
-```
-
-or
-
-```
-EACH=.001 ./dev/event-producer.sh
-```
+## License ##
 
+This service is distributed under the Apache License, Version 2.0 license found
+in the [LICENSE](./LICENSE) file.

dev/event-producer.sh

@@ -1,20 +1,19 @@
 #!/bin/bash
 
 set -eo pipefail
-
 trap exit INT TERM
 
 ####
-sample="deploys.test.myservice:1|c"
 
-[ -z $EACH ] && EACH=2 || :
+if [ -z $EACH ]; then EACH=2; fi
+if [ -z $MESSAGE ]; then MESSAGE="deploys.test.myservice:1|c"; fi
 
-printf "[info] sending \"%s\" every %ssec\n" $sample $EACH
+printf "[info] sending \"%s\" every %ssec\n" $MESSAGE $EACH
 
 ####
 
 while true; do
-    echo $sample > /dev/udp/127.0.0.1/8125
+    echo $MESSAGE > /dev/udp/127.0.0.1/8125
     sleep $EACH
 done
 

dev/siege.sh

@@ -0,0 +1,28 @@
+#!/bin/bash
+
+set -eo pipefail
+
+exec 3>&1 4>&2
+
+post_stop() {
+    exit_code=$?
+    printf "\n"
+    if [ -n "$error" ]; then
+        printf "Error: %s\n" $error
+    fi
+    exec 3>&- 4>&-
+    exit $exit_code
+}
+
+trap post_stop INT TERM
+trap "kill 0" EXIT
+
+MESSAGE="deploys.test.myservice:1|c" EACH=.0001 ./dev/event-producer.sh &> /dev/null &
+MESSAGE="deploys.test.myservice:2|c" EACH=.0001 ./dev/event-producer.sh &> /dev/null &
+MESSAGE="deploys.test.myservice:3|c" EACH=.0001 ./dev/event-producer.sh &> /dev/null &
+
+docker rm -f $(docker ps -aq --filter="name=datadog" --filter="status=running") &> /dev/null || :
+
+printf "processing [0 / sec]"
+
+error=$( { (docker-compose run --rm --no-deps --service-ports artefact 2>&4 || :) | perl -e 'open(TTY, ">:unix", "/dev/tty");while (<>) {$l++;if (time > $e) {$e=time;print TTY "\rprocessing [$l / sec]";$l=0}}' 1>&3; } 2>&1 )

src/datadog-mock/main.go

@@ -26,7 +26,7 @@ func main() {
 	stream, err := net.ResolveUDPAddr("udp", ":8125")
 
 	if err != nil {
-		fmt.Println("Fatal: %v", err)
+		fmt.Println(err)
 		os.Exit(1)
 	}