Hello Fabian On 25.08.2017 12:56, Fabian Cenedese wrote: > 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's correct. This method to link to VCS was deprecated in Mantis 1.2 as the plugin framework was rolled out, and the source integration plugin provided a superset of this functionality. > 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? Not out of the box, sorry. > 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. This is generally used for initial import of the repository. The preferred method is to rely on hooks to trigger the import of new changesets as they are committed / pushed. In any case, the full import script stops once it reaches a commit that has already been processed. Cheers Damien ------------------------------------------------------------------------------ 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
