The SVN, nightly builds and biweekly betas

[myk]

there are a couple possible problems, it seems. according to the google link above, try using http instead of https. Indeed, when I check my own checkout:

Code: Select all

$ svn info
Path: .
Working Copy Root Path: /Users/myk/src/forge/trunk
URL: http://svn.slightlymagic.net/forge/trunk
...


note the http instead of https. Try this to see if it helps:

Code: Select all

svn switch --relocate https://svn.slightlymagic.net/forge/trunk http://svn.slightlymagic.net/forge/trunk .


[moomarc]

I remember having this issue when cardsfolder was first split into subfolders (at least I think it was then). At the time I just updated one or two folders at a time and if there was another RA layer request failure, I'd run a cleanup and try a smaller section.

[myk]

+1, that was also a suggested solution

[moomarc]

Busy doing that myself at the moment. Eclipse doesn't seem to make life easy for itself. Started with A-C as a tester and B cards flew by, doing all of them in seconds, but now it's jumping between A and C cards and has already taken more than 5 minutes . I tried doing it from command line first (first time trying, but it seems that the Sliksvn client I have for command line is too old. Oh well, I'll stick to what I know and is nice and easy for me...

[Max mtg]

Sharing my personal experience - commit took about 30 minutes. Was commiting the whole folder of 12k+ files with tortoise svn.
Update of secondary working copy took 6 minutes with the same client.

I didn't expect anyone would have troubles updating to latest version.

The internets read that macs have the http://www.zennaware.com/cornerstone/ app to manage svn working copies. The 14-day trial should be sufficient to make a single update.

[moomarc]

Not a problem Max. It's just tedious more than anything else. We'd eventually have to go through the process of removing the deprecated fields anyway if we want to keep the project clean.

[Chris H.]

Try this to see if it helps:

Code: Select all

svn switch --relocate https://svn.slightlymagic.net/forge/trunk http://svn.slightlymagic.net/forge/trunk .


 
Still get the

Code: Select all

svn: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/forge/!svn/vcc/default'

[Chris H.]

OK, got things working finally. Thank you Myk.

With the https to http change I was able to import the project without any errors.

The project name was ForgeLocal rather than ForgeSVN. Used Eclipse's rename command and my various run configs were once again available and my scripts will work as is and do not need to be edited.

So it looks like things are now working OK. Was able to make a commit and am now using my snapshot build and deploy script command file.

[Chris H.]

I have noticed something strange in how the revs are listed for our SVN. We are missing the following revs according to what I can currently see listed.

20181
20180
20179
20176
20173
20172
20171
20170
20169
20166
20164
20156
20152

[timmermac]

They show up on the WebSVN page as belonging to various branches. Could you have a filter set that doesn't show them or something to that effect?

[Agetian]

@ Chris: I can definitely see all the revisions above, it seems like the ones you mention are just parts of branches and not of trunk... Maybe you're only looking at the trunk revisions?

- Agetian

[Chris H.]

Ah, thank you timmermac and Agetian. I had bookmarked the original WebSVN URL and went to that one and can once again see all of the commits.

[myk]

Would it be possible to have a symlink updated that always points to the current snapshot? That way we could permalink to it and people can get the snapshot with a single click instead of going through the list of snapshot builds. A similar symlink that points to the current release would be nice too. I don't see the deploy script checked in -- where is it hiding?

[Chris H.]

Would it be possible to have a symlink updated that always points to the current snapshot? That way we could permalink to it and people can get the snapshot with a single click instead of going through the list of snapshot builds. A similar symlink that points to the current release would be nice too. I don't see the deploy script checked in -- where is it hiding?

 
You ask some good questions and I with wish that I had the expertise to answer them.

Dave created the Maven based build and deploy system. He drops by the CCGH site on rare occasion. But he is not active in our project at this time. He might see this message and reply or you could try to sen him a pm.

[myk]

I might be able to do it myself. Do the ftp passwords also grant shell access? If so, a symlink would be easy enough to create over ssh. There is a maven ssh plugin for integrating it into the deploy sequence. If there is no shell access, there are other ways to get it done, too, but it might take some cooperation from the cardforge.org admin to get the script in place.