At 09:37 25.08.2017, Fabian Cenedese wrote:
>Hi
>
>We've updated out mantis from 1.2.x to the latest 1.3. Previously
>we used the scripts/checkin.php script to add notes or close issues
>by svn commit messages. This script called the internal function
>custom_function_default_checkin. Now with 1.3 both the file and
>the function are gone. Is there a recipe on how to adjust the used
>checkin script to work with 1.3? How can notes be added and issues
>be closed via script in 1.3?

It seems that this possibility has been removed for good:
https://github.com/mantisbt/mantisbt/commit/9527e0ef9c84b87d3d01ec646d55ff56ba85c9ac

The recommeded way to do it is to use the source integration plugins:
https://github.com/mantisbt-plugins/source-integration

That seems to work but there are some things that I don't find too good.

Now every repository has to be added in mantis. With the older checkin
script that was not necessary, all the needed information was given from
svn to the hook to mantis. So this demands more work than the older
solution, especially with many repositories. Or is there a way to create
and configure all repositories via scripts?

The authentication information for every repository has to be stored in the
mantis configuration.

The recommended link updates all information:
curl 
"http://host.domain.tld/mantisbt/plugin.php?page=Source/import&id=all&api_key=<YOUR_API_KEY>"

Can this be adjusted to only get the informationen of the used repository,
and only import the latest data? I guess the id= can determine the repository,
but I couldn't find documentation about it. I'd like to keep the server load
as low as possible.

Thank you

bye  Fabi


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help

Reply via email to