Impacts whem accessing Bare repositories from outside (of SCM-Manager)

[Matthias.Sc...@materna.de]

Hello,

we are currently discussing a use case where we would allow access to
selected Bare Repositories which are registered to SCM-Manager e.g. via SSH.

It's clear that accessing the Repositories via other ways than SCM-Manager
bypasses the authentication mechanism configured within SCM-Manager and the
functionality of the plugins. This would be no problem in our use case.

But are there any other constraints? Does SCM-Manager have any difficulties
with repositories which suddenly e.g. have additional commits?

Regards,
Matthias


Mit freundlichen Grüßen

i. A.
Matthias Schwellenberg

Manager
Shared Delivery Services

Phone: +49 231 5599-8244
Mobile: +49 1570 112-8244
Matthias.Sc...@Materna.de
www.materna.de
________________________________________________

Materna GmbH | Voßkuhle 37 | D-44141 Dortmund | Germany
Geschäftsführer: Helmut Binder, Michael Knopp
Amtsgericht Dortmund HRB 5839

[Sebastian Sdorra]

Hi,

Yes this could lead to problems, because scm-manager make intensive use of caches to be more performant. Those caches are updated or cleared, when the repository changes. If you bypass scm-manager on a push, scm-manager could not update the caches. If this happens, you see probably stale data in the ui or other services which are using the scm-manager api. As a workaround you could clear the caches with the script plugin after each non http push, but this could lead to a performance degrease. 

Sebastian

2017-05-19 13:29 GMT+02:00 <Matthias.Sc...@materna.de>:

Hello,

we are currently discussing a use case where we would allow access to
selected Bare Repositories which are registered to SCM-Manager e.g. via SSH.

It's clear that accessing the Repositories via other ways than SCM-Manager
bypasses the authentication mechanism configured within SCM-Manager and the
functionality of the plugins. This would be no problem in our use case.

But are there any other constraints? Does SCM-Manager have any difficulties
with repositories which suddenly e.g. have additional commits?

Regards,
Matthias


Mit freundlichen Grüßen

i. A.
Matthias Schwellenberg

Manager
Shared Delivery Services

Phone: +49 231 5599-8244
Mobile: +49 1570 112-8244

Matthias.Schwellenberg@Materna.de

www.materna.de
________________________________________________

Materna GmbH | Voßkuhle 37 | D-44141 Dortmund | Germany
Geschäftsführer: Helmut Binder, Michael Knopp
Amtsgericht Dortmund HRB 5839

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matthias.Sc...@materna.de]

Hi Sebastian,

thank you for your feedback. We'll test the performance impacts when rebuilding the caches regularly on demand.

Regards,
Matthias

-----Ursprüngliche Nachricht-----
Von: scmma...@googlegroups.com [mailto:scmma...@googlegroups.com] Im Auftrag von Sebastian Sdorra
Gesendet: Mittwoch, 24. Mai 2017 14:02
An: scmma...@googlegroups.com
Betreff: Re: Impacts whem accessing Bare repositories from outside (of SCM-Manager)

Hi,
Yes this could lead to problems, because scm-manager make intensive use of caches to be more performant. Those caches are updated or cleared, when the repository changes. If you bypass scm-manager on a push, scm-manager could not update the caches. If this happens, you see probably stale data in the ui or other services which are using the scm-manager api. As a workaround you could clear the caches with the script plugin after each non http push, but this could lead to a performance degrease.

Sebastian

2017-05-19 13:29 GMT+02:00 <Matthias.Sc...@materna.de <mailto:Matthias.Sc...@materna.de> >:

Hello,

we are currently discussing a use case where we would allow access to
selected Bare Repositories which are registered to SCM-Manager e.g. via SSH.

It's clear that accessing the Repositories via other ways than SCM-Manager
bypasses the authentication mechanism configured within SCM-Manager and the
functionality of the plugins. This would be no problem in our use case.

But are there any other constraints? Does SCM-Manager have any difficulties
with repositories which suddenly e.g. have additional commits?

Regards,
Matthias


Mit freundlichen Grüßen

i. A.
Matthias Schwellenberg

Manager
Shared Delivery Services

Phone: +49 231 5599-8244 <tel:%2B49%20231%205599-8244>
Mobile: +49 1570 112-8244 <tel:%2B49%201570%20112-8244>
Matthias.Sc...@Materna.de
www.materna.de <http://www.materna.de>

________________________________________________

Materna GmbH | Voßkuhle 37 | D-44141 Dortmund | Germany
Geschäftsführer: Helmut Binder, Michael Knopp
Amtsgericht Dortmund HRB 5839


--
You received this message because you are subscribed to the Google Groups "scmmanager" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com <mailto:scmmanager%2Bunsu...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout> .

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.