Terasology Jenkins now tied to GitHub via OAuth


Org Co-Founder & Project Lead
For anybody who might notice (probably few): Our Jenkins is now tied directly to use GitHub's user system rather than its separate internal system where you had to register (or get detected in commits). On logging on you'll now get redirected to GitHub just once to authorize the integration and after that you'll automatically be logged in for Jenkins as long as you're logged in for GitHub, no need to enter user/pass a second time :)

This may help clean the user / committer duplication / mis-attribution up a bit when looking at commits in Jenkins. Not sure though, some comments suggest you can still end up with dupes if using Git from different machines.

Also: No more Git polling, which I think was causing occasional weird issues. Using push hooks from GitHub instead.