The SVN, nightly builds and biweekly betas

[Chris H.]

I think I know what the issue is. You are using svn from the command line (its called from Maven command line). Your SVN creds are not stored unless you have been using it from the command line.

From your Forge checkout working directory type:

Code: Select all

svn ls


This will try to list the root directory of the svn repo. If your creds are not set up, it will prompt you for username and password. These creds are for the SVN repo, not the cardforge ftp. You will have to put your username in quotes if your username has a space.

`
OK, I relaunched terminal.app and used the cd from my command file. I then pasted in

Code: Select all

svn ls

and it listed the root directory of the svn repo. I was not prompted for a password:

Code: Select all

Last login: Fri Aug 19 11:31:19 on ttys000
Macintosh:~ chrish$ cd /Users/chrish/Workspace_SVN/ForgeSVN/
Macintosh:ForgeSVN chrish$ svn ls
.checkstyle
.classpath
.fbprefs
.project
.settings/
CHANGES.txt
LICENSE.txt
README.txt
forge.properties
pom.xml
res/
src/
Macintosh:ForgeSVN chrish$

[jendave]

Ok. Can you do a 'svn update' from the command line? Also try to modify a file and do a 'svn commit -m "test commit" <filename>'

[Chris H.]

Ok. Can you do a 'svn update' from the command line? Also try to modify a file and do a 'svn commit -m "test commit" <filename>'

`
Will do, just need to reboot into Snow Leopard.

(I hope to figure out how to get a VirtualBox Snow Leopard VM running inside of Lion. )

[Chris H.]

Ok. Can you do a 'svn update' from the command line? Also try to modify a file and do a 'svn commit -m "test commit" <filename>'

`

Code: Select all

svn update

`
gives me:

Code: Select all

Macintosh:ForgeSVN chrish$ svn update
A    res/cardsfolder/d/dawnfluke.txt
A    res/cardsfolder/e/ego_erasure.txt
Updated to revision 9815.
Macintosh:ForgeSVN chrish$


`
I then did a"

Code: Select all

svn commit -m "test commit" ForgeSVN

`
and got:

Code: Select all

Macintosh:ForgeSVN chrish$ svn commit -m "test commit" ForgeSVNsvn: Commit failed (details follow):
svn: '/Users/chrish/Workspace_SVN/ForgeSVN/ForgeSVN' is not under version control
Macintosh:ForgeSVN chrish$


`
Hmm, let me try:

Code: Select all

svn commit -m "test commit"

`

Code: Select all

Macintosh:ForgeSVN chrish$ svn commit -m "test commit"
Macintosh:ForgeSVN chrish$


[Chris H.]

Oh, I just realized that I needed to change a file before doing the test commit. So I did just that and re-tried the test commit.

This time I got a dialog asking me if I wanted to give access to my keys (creds) and I choose always allow. I guess that my keychain should now be good to go.


EDIT 1

Launched Keychain Access and selected the login for slightlymagic and checked out the Access Control tab and I now see:

Code: Select all

svn
Eclipse

`

EDIT 2

I am now retrying the Bi-Weekly build and release Maven command.

[Chris H.]

EDIT 2

I am now retrying the Bi-Weekly build and release Maven command.

`

Code: Select all

[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/chrish/Workspace_SVN/ForgeSVN && svn --username releases@cardforge.org --password '*****' --no-auth-cache --non-interactive commit --file /var/folders/0V/0Vuo2rLY2Rmm2k+BYpeWKU+++TI/-Tmp-/maven-scm-1167136479.commit --targets /var/folders/0V/0Vuo2rLY2Rmm2k+BYpeWKU+++TI/-Tmp-/maven-scm-1782240742987296963-targets
[INFO] Working directory: /Users/chrish/Workspace_SVN/ForgeSVN
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:02.547s
[INFO] Finished at: Fri Aug 19 13:11:06 EDT 2011
[INFO] Final Memory: 47M/376M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project forge: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: Commit failed (details follow):
[ERROR] svn: MKACTIVITY of '/forge/!svn/act/81eb6173-b447-46dd-8bed-29d5b5ff604f': authorization failed: Could not authenticate to server: rejected Basic challenge (http://svn.slightlymagic.net)
[ERROR] -> [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/MojoFailureException
logout

[Process completed]

[jendave]

Try it without the '--username' and '--password' and without '-Dusrname -Dpassword'

[Chris H.]

Try it without the '--username' and '--password' and without '-Dusrname -Dpassword'

`
I started this awhile ago and it is now uploading the files, so I think we fixed it.

Code: Select all

[INFO] Reply received: 226-File successfully transferred
[INFO] 226 0.237 seconds (measured here), 30.18 Kbytes per second
[INFO]
[INFO] completed = /Users/chrish/Workspace_SVN/ForgeSVN/target/checkout/target/site/team-list.html
[INFO] Command sent: CDUP
[INFO]
[INFO] Reply received: 250 OK. Current directory is /
[INFO]
[INFO] completed = /Users/chrish/Workspace_SVN/ForgeSVN/target/checkout/target/site
[INFO] ftp.cardforge.org/site/ - Session: Disconnecting 
[INFO] ftp.cardforge.org/site/ - Session: Disconnected
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD SUCCESS
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 31:15.380s
[INFO] [INFO] Finished at: Fri Aug 19 15:03:19 EDT 2011
[INFO] [INFO] Final Memory: 41M/356M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] Cleaning up after release...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 43:26.659s
[INFO] Finished at: Fri Aug 19 15:03:19 EDT 2011
[INFO] Final Memory: 47M/356M
[INFO] ------------------------------------------------------------------------
logout

[Process completed]


[Braids]

Try it without the '--username' and '--password' and without '-Dusrname -Dpassword'

`
I started this awhile ago and it is now uploading the files, so I think we fixed it.
. . .

Dave will make a command line jockey of you yet, Chris.

[Chris H.]

Thank you for your help today Dave.

[Chris H.]

I moved my Nightly Build script over to my HD with the Lion OS and followed the instructions in this topic. I finally got it to work.

The forge-1.1.3-20110821 files were done from within Lion. Another step forward.

[Braids]

I moved my Nightly Build script over to my HD with the Lion OS and followed the instructions in this topic. I finally got it to work.

The forge-1.1.3-20110821 files were done from within Lion. Another step forward.

edit: congratulations, Chris!

should we use one or two digit numbers for the third part of the version string? Mantis has been using two, like <<1.1.03>>.

[Chris H.]

should we use one or two digit numbers for the third part of the version string? Mantis has been using two, like <<1.1.03>>.

`
We will have to wait to see if Dave can edit the pom in this fashion. It would be a nice feature.

[Braids]

should we use one or two digit numbers for the third part of the version string? Mantis has been using two, like <<1.1.03>>.

`
We will have to wait to see if Dave can edit the pom in this fashion. It would be a nice feature.

now that i think about it, i prefer the single digit format. @Dave, please don't change anything. mantis sorts versions by date, not alphabetically, so it's easy for 1.1.10 to show up higher in the list than 1.1.9.

why do i prefer the single digit format? {edit: because the following questions don't have good answers.} if we use leading zeroes, how many are enough? should we put them in the first and second numbers of the version string?

@Rob (edit: and anyone else who cares): do you mind if we switch to 1.1.1 format instead of 1.1.01? i can change the versions in Mantis without messing up any existing issues. and, as i said previously, mantis sorts these by date, not alphabetically. so i don't think we have anything to lose by going this route.

[Rob Cashwalker]

I guess it doesn't make a difference to me...