Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 02 2016 16:59
    CircleCI success: KaminoCoding build (#86) in https://github.com/KaminoCoding/CommuMod
    • null
      (c0a7eaa41aa52d8098dc43e173379621f6b63360 by null)
  • Feb 02 2016 16:54
    CircleCI success: KaminoCoding build (#85) in https://github.com/KaminoCoding/CommuMod
    • null
      (c0a7eaa41aa52d8098dc43e173379621f6b63360 by null)
  • Feb 02 2016 16:50
    CircleCI success: KaminoCoding build (#84) in https://github.com/KaminoCoding/CommuMod
    • pushing to get out of the way
      (05311ecc58657a5d8fd8e1bb77997e0a9b542bcb by Noah Kovacs)
  • Feb 02 2016 16:35
    CircleCI success: KaminoCoding build (#83) in https://github.com/KaminoCoding/CommuMod
    • null
      (c0a7eaa41aa52d8098dc43e173379621f6b63360 by null)
  • Feb 02 2016 01:37
    Cyb3rWarri0r8 labeled #54
  • Feb 02 2016 01:37
    Cyb3rWarri0r8 labeled #54
  • Feb 02 2016 01:37
    Cyb3rWarri0r8 assigned #54
  • Feb 02 2016 01:37
    Cyb3rWarri0r8 opened #54
  • Feb 02 2016 01:32

    Cyb3rWarri0r8 on develop-1.8

    Fixed #53 "Golems Crash Game" C… (compare)

  • Feb 02 2016 01:26
    Cyb3rWarri0r8 labeled #52
  • Jan 27 2016 21:55
    Cyb3rWarri0r8 labeled #22
  • Jan 27 2016 21:55
    Cyb3rWarri0r8 labeled #24
  • Jan 27 2016 21:53
    Cyb3rWarri0r8 labeled #32
  • Jan 27 2016 21:53
    Cyb3rWarri0r8 unlabeled #32
  • Jan 27 2016 21:53
    Cyb3rWarri0r8 closed #32
  • Jan 27 2016 21:51
    Cyb3rWarri0r8 assigned #53
  • Jan 27 2016 21:51
    Cyb3rWarri0r8 labeled #53
  • Jan 27 2016 21:51
    Cyb3rWarri0r8 labeled #53
  • Jan 27 2016 21:51
    Cyb3rWarri0r8 opened #53
  • Jan 27 2016 21:47

    Cyb3rWarri0r8 on develop-1.8

    Fixes circle.yml Closes #32 Try… (compare)

Noah
@BitForger
testy test test test
Sean
@insuusvenerati
o/
Noah
@BitForger
yo
Sean
@insuusvenerati
How's it goin
Noah
@BitForger
pretty good, you?
Sean
@insuusvenerati
EH can't complain. I was following how you set up your build.gradle for incrementing versions
Noah
@BitForger
ahh yeah
was just about to respond
Sean
@insuusvenerati
And was just wondering how you implement it. Do you just run the tasks?
Cause I use jenkins
Which is mostly automated
Noah
@BitForger
yeah i just ./gradlew setDevVersion build on my build config
Sean
@insuusvenerati
How does that increment the versions? Does it add to the major version every time?
Noah
@BitForger
you can also use gradle build.mustRunAfter setDevVersion build.dependsOn setDevVersion
it increments the number in the config.xml document
it can be setup in a few different ways
based on the versioning style you like.. it's loosely based on semantic versioning right now.. ( http://semver.org )
Sean
@insuusvenerati
Hmm. I guess it would be crazy complicated to get it to set versions based off of git tags. I think that's what I'm ready trying to do. So that way I can increment the major, minor, api or patch version based off of how I do a particular commit
Noah
@BitForger
yeah that would take a lot of using the REST api to pull in that info and then parsing and sending to the config file and build script
Sean
@insuusvenerati
I've been trying to utilize git tags but i'm so inexperienced with git and gradle
Noah
@BitForger
git tags are really only good for milestone releases and you don't want to really make one for different builds.. the purpose of those tasks were to make a way to build nightlies that were stable and if someone wanted to grab the bleeding edge they could
unless your talking about using the version number from a git tag then appending a build number that increments
Sean
@insuusvenerati
I think so?
Lol
I'm still at the beginning stages of development so a lot of this is just framework for the future
Noah
@BitForger
i still wouldn't know how to do that.. it's best to just not use tags until you push a full release artifact out then link that release tag to the time in commit history
here is something that may help with git