Executing "fetch changesets" multiple times?

Added by Cory Riddell about 8 years ago

Is there any harm to executing fetch changesets more than once? We are using Subversion and have found that sometimes we get a 404 page when we click on a revision. I was thinking about running the script that collects all the changesets again, but was wondering if I first have to clear out all the old ones. Is there any harm to running it more than once without deleting?

Cory

Replies (5)

RE: Executing "fetch changesets" multiple times? - Added by Ivan Cenov about 8 years ago

You do not have to delete existing revisions before running fetch_changesets. Every time it is run, it adds the revisions created after previous run. Par example I set it to run every hour.

RE: Executing "fetch changesets" multiple times? - Added by Cory Riddell about 8 years ago

Ok, that tells me that we probable do need to wipe out the existing history and start over because the holes in the history are in the past and I'm guessing fetch_changesets only looks for new changes, not ones from 6 months ago that aren't available for some reason.

RE: Executing "fetch changesets" multiple times? - Added by Ivan Cenov about 8 years ago

Hmm, I don't think so. After you assign a repository to a project, first click on Repository entry in the project menu activates procedure to fetch all available revisions from that repository and store them in the Redmine's database. If you don't click on Repository entry, then fetch_changesets will do the same when it is started. Even it is preferable way to fetch revisions for first time. This is because this would be long process and if done via Project repository menu it could lead to timeout in the browser.

RE: Executing "fetch changesets" multiple times? - Added by Cory Riddell about 8 years ago

After you assign a repository to a project, first click on Repository entry in the project menu activates procedure to fetch all available revisions

Right. And for some reason, not all revisions were fetched. I don't know why but now I'm thinking the only way to fix this is to clear the data from the database and do it again in order to fill in the holes.

this would be long process and if done via Project repository menu it could lead to timeout in the browser

Even if it timed out in the browser, the process would finish on the server, right?

RE: Executing "fetch changesets" multiple times? - Added by Ivan Cenov about 8 years ago

Cory Riddell wrote:

After you assign a repository to a project, first click on Repository entry in the project menu activates procedure to fetch all available revisions

Right. And for some reason, not all revisions were fetched. I don't know why but now I'm thinking the only way to fix this is to clear the data from the database and do it again in order to fill in the holes.

I don't know why are these holes ... and why to expect that second try will fill in them.

this would be long process and if done via Project repository menu it could lead to timeout in the browser

Even if it timed out in the browser, the process would finish on the server, right?

I suppose so, right.

(1-5/5)