100: Importing repository via cron fails

(096)
John Reese (administrator)
2010-02-18 12:35

If are running the curl command from a machine other than the server, you will need to add the other machine's IP address or IP range to the Source Integration configuration page. Click on Repositories -> Configuration, and add the IP address to the section labelled Allow Remote Imports. Sometimes depending on server configuration or network routing, you may need to add the server's IP address as well.

(097)
Jürgen (reporter)
2010-02-18 12:40

Very good, that's the trick.

I'm now getting a full HTML page and that looks as if curl is calling a proper MantisBT page.

However, looking in the content the output says "APPLICATION ERROR 200" and something about a back button in the browser to go back and correct the problem. But it doesn't say more about what the problem might be.

(098)
James Keir (reporter)
2010-02-18 13:09

Hey,
Just my 2c but wouldn't it be better to use a SVN post commit hook to import changeset into MantisBT? I setup mine that way and it works wonderfully :)

(099)
Jürgen (reporter)
2010-02-18 13:12

Sounds promissing, could you shed some more light to it? I imagine it's the same curl command but issued by a SVN hook instead of the cron?

Have you got an example for this and how would I get rid of that 200 application error?

(129)
John Reese (administrator)
2010-03-26 14:17

Can you try this again with the latest git master? I've made some changes to the way the repository import page works, which should solve some of these types of problems.

(131)
Jürgen (reporter)
2010-03-27 01:24

My problem had already been solved by adding a script to the crontab and the scriptfile contains lines like

curl "http://my.domain.de/plugin.php?page=Source/repo_import_latest&id=3" [^] > /dev/null 2>&1

Issue History
Date Modified	Username	Field	Change
2010-02-18 12:21	Jürgen	New Issue
2010-02-18 12:35	John Reese	Note Added: 096
2010-02-18 12:35	John Reese	Assigned To	=> John Reese
2010-02-18 12:35	John Reese	Status	new => feedback
2010-02-18 12:40	Jürgen	Note Added: 097
2010-02-18 12:40	Jürgen	Status	feedback => assigned
2010-02-18 13:09	James Keir	Note Added: 098
2010-02-18 13:12	Jürgen	Note Added: 099
2010-03-26 14:17	John Reese	Note Added: 129
2010-03-26 14:17	John Reese	Status	assigned => feedback
2010-03-27 01:24	Jürgen	Note Added: 131
2010-03-27 01:24	Jürgen	Status	feedback => assigned
2010-03-27 17:26	John Reese	Status	assigned => resolved
2010-03-27 17:26	John Reese	Resolution	open => no change required

Notes
(096) John Reese (administrator) 2010-02-18 12:35	If are running the curl command from a machine other than the server, you will need to add the other machine's IP address or IP range to the Source Integration configuration page. Click on Repositories -> Configuration, and add the IP address to the section labelled Allow Remote Imports. Sometimes depending on server configuration or network routing, you may need to add the server's IP address as well.

(097) Jürgen (reporter) 2010-02-18 12:40	Very good, that's the trick. I'm now getting a full HTML page and that looks as if curl is calling a proper MantisBT page. However, looking in the content the output says "APPLICATION ERROR 200" and something about a back button in the browser to go back and correct the problem. But it doesn't say more about what the problem might be.

(098) James Keir (reporter) 2010-02-18 13:09	Hey, Just my 2c but wouldn't it be better to use a SVN post commit hook to import changeset into MantisBT? I setup mine that way and it works wonderfully :)

(099) Jürgen (reporter) 2010-02-18 13:12	Sounds promissing, could you shed some more light to it? I imagine it's the same curl command but issued by a SVN hook instead of the cron? Have you got an example for this and how would I get rid of that 200 application error?

(129) John Reese (administrator) 2010-03-26 14:17	Can you try this again with the latest git master? I've made some changes to the way the repository import page works, which should solve some of these types of problems.

(131) Jürgen (reporter) 2010-03-27 01:24	My problem had already been solved by adding a script to the crontab and the scriptfile contains lines like curl "http://my.domain.de/plugin.php?page=Source/repo_import_latest&id=3" [^] > /dev/null 2>&1

Relationships