lazylead 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 51f5479222983a306e063eb06e764100ea069e9a62854c478f9e0a14efdac5dd
+  data.tar.gz: 8e0052a4432740bd347c85c96267ecdc53f182e4a6716035839ad3ef5aec8d98
+SHA512:
+  metadata.gz: 863fb878c397f0cb5b4861dae0db83ea02b9f795a4625af97c7b5426cd376e490270d98d90b1cda07fb960835fe90cb481ee6d315ecaa171221e4e3ac8ebb4e7
+  data.tar.gz: dd47bb278d2eef49b36820ffc9c181c87118b2d6e2a7099784ec8c17f97ed8165af1f3d01615ef8e4011c374d5054c4b74389e8b4625777db53798e63da48585

data/ .dockerignore

@@ -0,0 +1,12 @@
+.docker
+.github
+/coverage
+/test
+*.yml
+*.sh
+.gitignore
+.gitattributes
+.pdd
+.ruby-version
+.simplecov
+*.log

data/.0pdd.yml

@@ -0,0 +1,5 @@
+errors:
+  - yurii.dubinka@gmail.com
+
+tags:
+  - pdd

data/.circleci/config.yml

@@ -0,0 +1,50 @@
+# @todo #/DEV Define automatic integration between rultor and Circle CI.
+#  Right not its not clear how to automatically accept the merge requests into master.
+#  Without this integration the release history won't be clear.
+version: 2
+jobs:
+  test:
+    docker:
+      - image: ruby:2.6.5-alpine
+    steps:
+      - checkout
+      - run: |
+          apk add libc-dev gcc make git sqlite sqlite-dev sqlite-libs
+          bundler install
+      - run: rake test rubocop xcop
+  deploy:
+    machine: true
+    steps:
+      - checkout
+      # build the application image
+      - run:
+          name: "Build docker image"
+          command: |
+            set -e
+            COMMIT_URL="https://github.com/dgroup/rll/commit/${CIRCLE_SHA1}"
+            docker build --build-arg release_tags="${CIRCLE_SHA1}, ${CIRCLE_BRANCH}, ${COMMIT_URL}" \
+              -t dgroup/lazylead:$CIRCLE_BRANCH . \
+              -f .docker/Dockerfile
+            docker run --rm dgroup/lazylead:${CIRCLE_BRANCH} bin/lazylead --verbose > trace.log
+            cat trace.log
+            expected="No tasks found"
+            echo "Ensure that app prints the line '${expected}'."
+            grep --color "${expected}" trace.log
+      # publish the image
+      - run:
+          name: "Deploy docker image"
+          command: |
+            chmod +x .circleci/release_image.sh
+            .circleci/release_image.sh
+workflows:
+  version: 2
+  build_and_test:
+    jobs:
+      - test
+      - deploy:
+          filters:
+            branches:
+              only:
+                - master
+          requires:
+            - test

data/.circleci/release_image.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+export docker_release_tags="latest 1 1.0.1 0.1.1"
+docker login --username $DOCKER_USER --password $DOCKER_TOKEN
+if [ "${CIRCLE_BRANCH}" == "master" ]; then
+    for tag in ${docker_release_tags// / } ; do
+        docker tag dgroup/lazylead:$CIRCLE_BRANCH dgroup/lazylead:${tag}
+        docker push dgroup/lazylead:${tag}
+        echo "dgroup/lazylead:${tag} released"
+    done
+else
+    docker push dgroup/lazylead:$CIRCLE_BRANCH
+    echo "dgroup/lazylead:${CIRCLE_BRANCH} released"
+fi

data/.circleci/validate.sh

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+#
+# Verify that Circle CI config is valid.
+#  - https://support.circleci.com/hc/en-us/articles/360006735753-Validating-your-CircleCI-Configuration
+#  - https://circleci.com/docs/2.0/local-cli/
+#
+# For OSX you need to install the command-line client
+#   brew install circleci
+#
+circleci config validate config.yml

data/.docker/Dockerfile

@@ -0,0 +1,31 @@
+FROM ruby:2.6.5-alpine
+
+ARG release_tags
+
+LABEL about="https://github.com/dgroup/lazylead" \
+      ci.contact="yurii.dubinka@gmail.com" \
+      ci.release.tag="${release_tags}" \
+      ll.docker.issues="https://github.com/dgroup/lazylead/issues?utf8=✓&q=label%3Adocker"
+
+ENV APP_HOME=/lazylead \
+    version=${release_tags}
+
+WORKDIR $APP_HOME
+
+# @todo #/DEV The current image size is about 150MB.
+#  The original alpine image is ~20MB.
+#  Image cleanup is required.
+RUN echo "Install 3rd-party libraries." \
+  && apk add libc-dev gcc make git sqlite sqlite-dev sqlite-libs tree less vim man bash unzip
+
+COPY Gemfile lazylead.gemspec ./
+
+RUN bundler install
+
+COPY bin/lazylead ./bin/lazylead
+ADD lib ./lib
+ADD upgrades ./upgrades
+
+CMD ["bin/lazylead", "--trace", "--verbose", "--memory-dump"]
+
+MAINTAINER 'Yurii Dubinka (yurii.dubinka@gmail.com)'

data/.docker/build.sh

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+echo ""
+set -e
+config=docker-compose.yml
+clear
+docker-compose -f ${config} rm --force && docker-compose -f ${config} up --build

data/.docker/docker-compose.yml

@@ -0,0 +1,23 @@
+version: '2.3'
+
+# @todo #/DEV Define openshift template in order to deploy into Openshift/Kubernetes/etcN environment.
+services:
+
+  lazylead:
+    image: dgroup/lazylead:latest
+    container_name: lazylead
+    mem_limit: 128m
+    build:
+      context: ../
+      dockerfile: .docker/Dockerfile
+    environment:
+      # @todo #/DEV Add SHA2, version, release date, and url to commit.
+      release_tags: "0.1.0"
+    ports:
+      - 82:8080
+      - 1082:1082 # remote debug
+      - 1282:1282 # JMX connection for jvisualvm debug
+    volumes:
+      - .local/dumps:/lazylead/dumps
+      - .local/logs:/lazylead/logs
+    entrypoint: bin/lazylead --trace --verbose

data/.docker/readme.md

@@ -0,0 +1,21 @@
+#### Docker F.A.Q.
+ - Prepare environment
+    ````bash
+    docker start <container_name>               # start particular container
+    docker start -i <container_name>            # start particular container in interactive mode
+    docker stop <container_name>                # stop particular container
+    docker ps                                   # display all running containers
+    docker ps -a                                # display all existing containers (stopped)
+    docker exec -it <container_name> /bin/bash  # join to the container via bash
+    docker rm <container_name>                  # remove particular container
+    docker rmi <image_name>                     # remove particular image
+    docker pull <image_name>                    # download particular image from the remote repository (NC Artifactory, dockerhub, etc)
+    ````
+ - Monitoring
+    ```bash
+    # Display on-line information regarding system usage (CPU,RAM,IO) per container    
+    docker stats $(docker ps --format '{{.Names}}')        
+    docker stats $(docker ps | awk '{if(NR>1) print $NF}')
+    ```
+ - [Cheat sheet](https://gist.github.com/dgroup/5046bac5531fae11242dd03201626f5b)
+ - [Basics](https://github.com/wsargent/docker-cheat-sheet)

data/.gitattributes

@@ -0,0 +1,9 @@
+# Check out all text files in UNIX format, with LF as end of line
+# Don't change this file. If you have any ideas about it, please
+# submit a separate issue about it and we'll discuss.
+
+* text=auto eol=lf
+*.rb ident
+*.xml ident
+*.png binary
+*.pdf binary

data/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 github@dgroup. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

data/.github/CONTRIBUTING.md

@@ -0,0 +1,9 @@
+Just send a pull request and call it a day.
+
+
+
+
+
+Only if the build is green, you send us your pull request.
+
+Thanks!

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,14 @@
+Make sure the title of the issue explains the problem you are having. Also, the description of the issue must clearly explain what is broken, not what you want us to implement. Go through this checklist and make sure you answer "YES" to all points:
+
+  - You have all pre-requisites listed in README.md installed
+  - You are sure that you are not reporting a duplicate (search all issues)
+  - You say "is broken" or "doesn't work" in the title
+  - You tell us what you are trying to do
+  - You explain the results you are getting
+  - You suggest an alternative result you would like to see
+
+These articles will help you understand what we are looking for: 
+ * http://www.yegor256.com/2014/11/24/principles-of-bug-tracking.html
+ * https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
+
+Thank you for your contribution!

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+Many thanks for your contribution, we truly appreciate it. We will appreciate it even more, if you make sure that you can say "YES" to each point in this short checklist:
+
+  - You made a small amount of changes (less than 100 lines, less than 10 files)
+  - You made changes related to only one bug (create separate PRs for separate problems)
+  - You are ready to defend your changes (there will be a code review)
+  - You don't touch what you don't understand
+  - You ran the build locally and it passed
+
+This article will help you understand what we are looking for: http://www.yegor256.com/2015/02/09/serious-code-reviewer.html
+
+Thank you for your contribution!

data/.github/tasks.yml

@@ -0,0 +1,24 @@
+version: '2.3'
+services:
+
+  lazylead:
+    image: dgroup/lazylead:latest
+    container_name: lazylead
+    mem_limit: 128m
+    environment:
+      # The jira server details.
+      # Please ensure that your jira filter(s) grants this user to see issues.
+      # Sometimes jira filter(s) may be created with restricted visibility, thus
+      #  lazylead can't find the issues.
+      jira_url: https://jira.spring.io
+      jira_user: theuser
+      jira_password: thepass
+      # The MS Exchange server details, please ensure that '/ews/Exchange.asm`
+      #  will be after your server url. Just change the url to your server.
+      exchange_url: https://your.ms.exchange.server/ews/Exchange.asmx
+      exchange_user: theuser
+      exchange_password: the password
+    volumes:
+      - ./:/lazylead/db
+    # db/ll.db is sqlite file with jira related annoying tasks
+    entrypoint: bin/lazylead --sqlite db/ll.db --trace --verbose

data/.github/trello.md

@@ -0,0 +1,18 @@
+###Trello Development guide
+
+**Enable integration requsites**\
+Before start testing integration with Trello you need to retrieve *API key* and *API token* from Trello by following link https://developers.trello.com/page/authorization
+
+**Environment Variables**\
+To run tests with integration to Trello you have to setup following environment variables:
+
+Varable|Description
+--- | --- 
+|*TRELLO_BOARD*| your existing board in Trello
+|*TRELLO_KEY* | your API key
+|*TRELLO_TOKEN*|you API token
+
+Example:
+```bash
+mvn -P quilice clean install -DTRELLO_KEY={TRELLO_KEY} -DTRELLO_TOKEN={TRELLO_TOKEN} -DTRELLO_BOARD={TRELLO_BOARD}
+```

data/.gitignore

@@ -0,0 +1,12 @@
+coverage/
+Gemfile.lock
+*.gem
+.bundle/
+.DS_Store
+rdoc/
+*.db
+*.lock
+*.log
+*.iml
+*.iws
+/.idea/

data/.pdd

@@ -0,0 +1,5 @@
+--source=.
+--verbose
+--exclude target/**/*
+--exclude coverage/**/*
+--rule min-words:5