dhale
Migrating jtk to a Github Organization
I propose we create a GitHub Organization (Mines JTK) and reassign this repo to that organization. This will allow for collaborators to do more deployment and testing-related things with this repo. For example, I'd like to start setting up continuous integration builds that can run automatically with every merge but unfortunately don't have the access to set these up.
Thoughts?
I vote yes!
Let's also ensure that you can submit updates to the jars on Maven.
Cool! You'd have to be the one to set that up if/when it needs to happen
I do have a concern though that moving to the new org will break people's scripts. Is there a way this is best handled?
I've mirrored this repository and added it here: https://github.com/MinesJTK/jtk All commits and branches have been retained.
I've also added some new devops features:
Continuous Integration: Travis-CI
This tests the basic build (without the signing portion) against OpenJDK 7, Oracle JDK 7 and Oracle JDK 8. It triggers a build everytime there's a merge on the master branch, and trigger pull-request builds as well. Find details in the .travis.yml file in the root dir.
URL: https://travis-ci.org/MinesJTK/jtk
Test Coverage: Jacoco & CodeCov
I've added the Jacoco Gradle plugin to run code coverage. Once Travis is done with a successful build, it uploads the results to CodeCov where you can check the results. When you run a build locally, it will place the code coverage results in jtk/core/build/reports/jacoco
URL: https://codecov.io/gh/MinesJTK/jtk
Static code analysis: Code Climate
Code climate is great at static code analysis (like a free version of Coverity). Results are triggered with each commit and results are published on Code Climate.
URL: https://codeclimate.com/github/MinesJTK/jtk
README badges
The results of each of these are shown as "badges" in the readme file. That way you can see at a glance how the current build is doing.
While I have wifi just want to say thanks for all your work on enhancements like this one.