[GoCD support]

Hi,

This is now resolved for me. I add my notes below.

The GoCD plugin jar is available in Plastic SCM plugins directory. I did not know about the existance of this folder, just saw it in another thread in the forum. 

C:\Program Files\PlasticSCM5\client\plugins\gocd

GoCD works correctly with this jar file. One catch; the client.conf needs to be copied to the Plastic SCM program files directory. I found this solution in the forum as well by searching the specific error message.

Fyi..

[GoCD support]

Hi,

Is there a Plastic SCM plugin available for GoCD? There is some old information below, but the GoCD web site does not seem to list a Plastic SCM plugin (https://www.gocd.org/plugins/#scm). Googling did not help either, but I just wanted to check.

Quote

GoCD plugin: A new Plastic SCM plugin is available for GoCD. It allows Plastic SCM to be set up as a pipeline material.

https://www.plasticscm.com/download/releasenotes/6.0.16.947

[Any caveats to using many levels of repositories?]

Hi Pablo,

I agree with your point. It's not likely that we will actually go deeper than 2 or 3 levels, the question is more about being aware of any limits.

Also thanks for the information, I didn't know about the possibility to have a session with experts. We will keep that in mind.

Regards,

Engin

[Any caveats to using many levels of repositories?]

Hi Carlos,

Thank you for all the information.

Kind regards,

Engin

[Any caveats to using many levels of repositories?]

Thank you! That's exactly the answer I needed, and it's funny even some of the wording matches with the question.

 

14 hours ago, calbzam said:

All the submodules inside a given repository are stored inside the same database as the repository, actually using different table name prefixes or schemas in the case of SQL Server.

As an additional thought on this, how would having many submodules in a single database perform compared to making each one a separate (top-level) repository?

For instance, should we take that into account for a few thousands of submodules?

 

Kind regards,

Engin

[Any caveats to using many levels of repositories?]

Hello,

Having a large number of repositories we intend to create many 'levels' by using the '/' character in repository names to take advantage of the tree view in Repositories screen, such as:

AAA

-- AAA/BBB

---- AAA/BBB/CCC

---- AAA/BBB/CCC/DDD

-- AAA/XXX

...

 

I haven't been able to find a specification of this feature in the documentation -sorry if I missed. Before setting up our repos like this, I would like to find out if there are any points to watch out for in such design. For example:

- Is there a limit to the number of levels (i.e. depth)?

- Are there any 'gotcha's with renaming a repo in this structure?

For example, renaming a repo  that has sub-repos? as in AAA/BBB/CCC --> AAA/BBB/CCCX

Or moving a sub-repo one level up? AAA/BBB/CCC/R1 --> AAA/BBB/R1

The reason for this question is that I found out the "Root repositories cannot be converted into modules" restriction by experiment (discussed here).

 

Briefly, could you please let me know if there would be any other restrictions on freely re-structuring this hierarchy if the need arises later?

I hope that makes sense.

 

Thank you for any feedback.

Kind regards,

Engin.