Minecraft Forums

Does not fully work anymore. Some stuff might be interesting anyway.

Hello,

I recently created a versioning and upload system for myself and thought I could share it with you.

What this is:

• A custom system depending on Git and drone.io
• It automaticly builds the mod, uploads and uploads it and generates a changelog.
• It supports classification as "recommend" builds and generation of dev jars.
• A example, if anyone wants to build his own system.
• DOES NOT require Jenkins

How it works:

• Drone.io automaticly builds your mod after every commit you do (can be filter to "master" branch only)
• You can prefix your commit messages with "#changelog" to add this message to the next changelog.
• You can create a release with a commit containg "#release", which automaticly creates a release on github, generates a changelog and uploads and publishes the jar. You can specify the version with VERSION:2.1 at the end of the release message, otherwise it will just use the last one (with another buildnumber at the end)
• Files are uploaded to ge.tt and registered on your website. There you can see the different versions, recommend, latest etc, sorted by Minecraftversion. Changelogs can be found there as well.

What this is not:

• A ready to use system, you have to change a few things, it take a while to setup.
• A guranteedly working system, I designed it for myself and it should/must be modified to meet your requirements or it just can be used as a example for your own implementation.

Requirements:

Depending on your customisation:

• A forge mod with gradle build system
• A github repository for that mod (only tested with public ones)
• A website with php and mysql. (I'm using a free one offered by bplaced.net)

Instructions:

1. Add the release-managment.sh to your mods main directory
2. Add the Autoupload.jar to your mods main directory (Source can be found here)
3. If you haven't yet, create a REFERENCE java class and put modid, version, minecraftversion as constants there, then only reference them in all other java classes.
4. Replace the version string in the REFERENCE file with "@[email protected]" and the minecraftversion String with "@[email protected]" (example)
5. Create a build.properties file in your mods main directory (example)
6. Modify your build script to look like this
7. Make sure you mods main directory contains a gradle folder and a gradlew file, otherwise run "gradle wrapper" via cmd
8. Commit all your code/all changes to a Github repository. Then create a git tag, with a name like this v0.0.0
9. Go to drone io and login with your github account
10. Create a new project, choose your mod repository, choose Java.
11. Use this as buildscript:
chmod +x Autoupload.jar
chmod +x release-managment.sh
chmod +x gradlew

12. If you dont want to have all stuff uploaded and registered automaticly, just add bash release-managment.sh after chmod +x gradlew, then go to artifacts and add build/libs/*.jar and changelog.html there. Then you can get these files of the latest build via the download tab. Skip to step 23.
13. If you want to, continue. Create a mysql database on your webserver or use a existing one. Then Create two tables in your database one for the files, one for the changelog. FILES: version:text,link:text,minecraftversion:text,recommend:boolean,timestamp:int,devlink:text CHANGELOG major:int,minor:int,build:int,changelog:text
14. Put these files into a folder on your website called files https://gist.github.com/maxanier/9c1918014191e22099cf
15. Modify these to fit to your mod. Most stuff to replace is marked with "", 1. replace all text which doesnt fit your mod, mainly in index.php 2. fill in the connection details in each file 3. change the table names in the sql commands in the files to fit to yours 4. insert the same custom password where wanted in the files
16. Upload them to your webserver and open each site once and look out for php errors in case there is any typo
17. Go to your buildscript again and add bash release-managment.sh after "chmod +x gradlew"
18. Create a github application key and add this to the environment variables TOKEN=
19. Add this there as well PASS=
20. Go to ge.tt and create a account, then go to http://ge.tt/developers/create and create a app respectivly a api key
21. Add the credentials to the environment variables as well:
password=
email=
registerpass=
apikey=

22. Add java -jar Autoupload.jar "build/libs" "" "< link to add.php>" this at the end of the release-managment.sh
23. (Optional) Open the drone.io settings go to repository and then enter master into the branch filter, then only commits to master trigger a build

This is a long instruction and I dont know if I explained everything correctly, if you have any problems ask me.

Example Mod: https://github.com/maxanier/MinecraftSecondScreenMod
Drone.io: https://drone.io/github.com/maxanier/MinecraftSecondScreenModDownload site: http://maxgb.de/minecraftsecondscreen/files/index.php

Would be happy to see your implementations or modifications or suggestions.

Maxanier

Can you send me a pastbin of the log at drone.io?

Two things:

1. I think you have to create a tag/release on git/github first, otherwise you get an error, don't know if I mentioned that somewhere

2. Apparently I have updated my release managment script without updating the link here.

Try adding this at the end of your release.sh: java -jar Autoupload.jar "build/libs" "MinecraftSecondScreen" "http://maxgb.de/minecraftsecondscreen/files/add.php" (MinecraftSecondScreen should be replaced by the github repository name, the link at the end by your add.php)

Also adjust the last line from your drone.io script to this:
bash Release.sh maxanier MinecraftSecondScreenMod http://maxgb.de/minecraftsecondscreen/files/addchangelog.php (replace maxanier by your github username, MinecraftSec... by your repository name and the link to your addchangelog.php, or leave it away if dont have one