Can you allow import or synchronization of software artifacts from production to test but restrict from it going from test to production?
Topic:
CRRTC5036W Distributed SCM is disabled for this server – admin can enable this on JTS Advanced Properties page
Question:
Can you enable outgoing synchronization on one server (i.e. import project artifacts from a different repository on a different server) but restrict incoming synchronization (protect the server sending the artifacts from receiving artifacts)
This is because we have many builds and dependencies set up in our development environment and don’t want to recreate them in our training environment, we just want to be able to import them. But we don’t want changes to be able to be delivered back to the dev environment in case we mess something up in training.
Marco Covi
Source Code Analyst
Operations Branch
Children Youth and Social Services Cluster
CRRTC5036W Distributed SCM is disabled for this server – admin can enable this on JTS Advanced Properties page
Question:
Can you enable outgoing synchronization on one server (i.e. import project artifacts from a different repository on a different server) but restrict incoming synchronization (protect the server sending the artifacts from receiving artifacts)
This is because we have many builds and dependencies set up in our development environment and don’t want to recreate them in our training environment, we just want to be able to import them. But we don’t want changes to be able to be delivered back to the dev environment in case we mess something up in training.
Marco Covi
Source Code Analyst
Operations Branch
Children Youth and Social Services Cluster
One answer
First note that calling it "synchronization" is likely to cause confusion.
What is supported by distributed SCM is deliver and accept between streams/workspaces that belong to different RTC repositories.
Whether or not a given user can deliver to a particular stream is determined by the write-access control on that stream.
But I do not believe there is a way to say "user X is allowed to deliver to a stream, but is not allowed to do a cross-repository (distributed) deliver to that stream".
What is supported by distributed SCM is deliver and accept between streams/workspaces that belong to different RTC repositories.
Whether or not a given user can deliver to a particular stream is determined by the write-access control on that stream.
But I do not believe there is a way to say "user X is allowed to deliver to a stream, but is not allowed to do a cross-repository (distributed) deliver to that stream".