Skip to content

Migrating jtk to a Github Organization #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chrisengelsma opened this issue Mar 22, 2017 · 5 comments
Open

Migrating jtk to a Github Organization #28

chrisengelsma opened this issue Mar 22, 2017 · 5 comments
Assignees

Comments

@chrisengelsma
Copy link
Collaborator

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?

@dhale
Copy link
Owner

dhale commented Mar 23, 2017

I vote yes!

Let's also ensure that you can submit updates to the jars on Maven.

@chrisengelsma
Copy link
Collaborator Author

Cool! You'd have to be the one to set that up if/when it needs to happen

@chrisengelsma
Copy link
Collaborator Author

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?

@chrisengelsma
Copy link
Collaborator Author

chrisengelsma commented May 2, 2017

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.

@dhale
Copy link
Owner

dhale commented May 10, 2017

While I have wifi just want to say thanks for all your work on enhancements like this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants