Collectible Card Game Headquarters

yay! i just fixed the version numbers in Mantis. there is no need to change the release numbering now.

Argh!
I had been checking http://cardforge.org/releases/snapshots ... -SNAPSHOT/ for build updates and I was not finding anything.
I finally hit the Parent Directory link and saw what I was missing.

Braids wrote:yay! i just fixed the version numbers in Mantis. there is no need to change the release numbering now.

Thanks Braids.

Is it easy to get one of these daily builds and use it to play Forge? Or is it best to just wait until betas are released?

timmermac wrote:Is it easy to get one of these daily builds and use it to play Forge? Or is it best to just wait until betas are released?

it's not too hard. go to http://cardforge.org/releases/snapshots/forge/forge/, click the latest SNAPSHOT link, then scroll to the bottom. download the latest .tar.bz2 file (for Linux and Windows) or the latest -osx.tar.bz2 (for Mac). those files install like the beta releases.

edit: the SVN Rev number will automatically be populated in any bug reports you file from within Forge, courtesy of Rob Cashwalker and myself.

Braids wrote:

timmermac wrote:Is it easy to get one of these daily builds and use it to play Forge? Or is it best to just wait until betas are released?

it's not too hard. go to http://cardforge.org/releases/snapshots/forge/forge/, click the latest SNAPSHOT link, then scroll to the bottom. download the latest .tar.bz2 file (for Linux and Windows) or the latest -osx.tar.bz2 (for Mac). those files install like the beta releases.

edit: the SVN Rev number will automatically be populated in any bug reports you file from within Forge, courtesy of Rob Cashwalker and myself.

Cool... Next question... Is there a list of changes made to the SVN like there was at the Google site?

timmermac wrote:Cool... Next question... Is there a list of changes made to the SVN like there was at the Google site?

Yep.

http://svn.slightlymagic.net/websvn/log.php?repname=forge&path=%2F

-slapshot5

Before I run the Nightly Build Maven script I try to not only update to the latest head version on the SVN, I also paste in the commit logs from the previous 24 hours.

I received an error while running the nightly build script. It looks like the project was built in my target folder and during the upload to cardforge an error developed. The error report mentions a broken pipe.

Code: Select all

Uploading: ftp.cardforge.org/snapshots/forge/forge/maven-metadata.xml
Uploaded: ftp.cardforge.org/snapshots/forge/forge/maven-metadata.xml (310 B at 0.2 KB/sec)
Uploading: ftp.cardforge.org/snapshots/forge/forge/1.1.3-SNAPSHOT/forge-1.1.3-20110906.103846-20-jar-with-dependencies.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19:05.258s
[INFO] Finished at: Tue Sep 06 06:48:04 EDT 2011
[INFO] Final Memory: 55M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project forge: Failed to deploy artifacts: Could not transfer artifact forge:forge:jar:jar-with-dependencies:1.1.3-20110906.103846-20 from/to cardforge-snapshot-repo (ftp.cardforge.org/snapshots): PUT request to: forge/forge/1.1.3-SNAPSHOT/forge-1.1.3-20110906.103846-20-jar-with-dependencies.jar in cardforge-snapshot-repo failed: Broken pipe -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
logout

`
It looks like the upload process aborted before the two local archives for the forge app could be uploaded. We got the 3 pom and the 3 jar files uploaded. The process aborted on the 3 jar-with-dependencies file upload.

My terminal log states that the forge apps were uploaded but they do not appear in the snapshot listing on cardforge.

`

Chris. That looks like a problem with FTP. You'll have to run the process again.

I am now having an issues extracting the new file.

| Open

! C:\Documents and Settings\cduncan\Desktop\Forge2\forge-1.1.3-20110906.152905-21.tar.bz2: Read error in the file C:\Documents and Settings\cduncan\Desktop\Forge2\forge-1.1.3-20110906.152905-21.tar.bz2

edit.
I re downloaded and could not duplicate the error.

jendave wrote:Chris. That looks like a problem with FTP. You'll have to run the process again.

`
I reran the script and it appears that we have a successful build and release this time.

Whatever interrupted the file transfer the first time was temporary.

Oh, on the files at card forge the naming appears to be

Code: Select all

"forge-" + version + "-" + date + "." time + "-" a number ...

`
so, what is the number after the time? Is this a build and release number? It appears to increase by one every time that I run the nightly build script.

Corwin72 wrote:I am now having an issues extracting the new file.

| Open

! C:\Documents and Settings\cduncan\Desktop\Forge2\forge-1.1.3-20110906.152905-21.tar.bz2: Read error in the file C:\Documents and Settings\cduncan\Desktop\Forge2\forge-1.1.3-20110906.152905-21.tar.bz2

edit.
I re downloaded and could not duplicate the error.

`
I downloaded both of the file archives and was able to extract both of them.

I think revision number is missing in build filenames. It might be even better than date+time, because SVN holds a log for every commit

Max mtg wrote:I think revision number is missing in build filenames. It might be even better than date+time, because SVN holds a log for every commit

Unfortunately the Maven snapshot builds naming convention cannot be easily modified. I started looking at adding the rev number as a "classifier", but I will test it out. I don't want to make the naming convention logic too complex. It may end up messing up the release builds.