CODEWITHSUNDEEP
rtc
user3302323
user3302323

Reputation: 423

Purpose of a public repository workspace in rtc

In RTC what is the purpose of using public repository workspace in rtc.

1) will all the users be able to check in the data to the public repository workspace.

2) will all the users be able to deliver the code to the connected stream.

3) How to get the incoming changes from another user.?

Upvotes: 1

Views: 276

Answers (2)

user3302323
user3302323

Reputation: 423

Sand box code :

sysout("sand box");

Code in repo workspace : sysout("repo code");

code in stream : sysout("stream code");

How it will reflect in pending changes view ?

Upvotes: 0

VonC
VonC

Reputation: 1325966

As mentioned in this thread:

The idea of using a public repository workspace is to provide an up and running development environment for the team.
I do not want a developer to spend 2-3 hours with the support of somebody else to setup his workspaces, to run a web application with the J2EE artifacts.
Currently we are using MAVEN to build are applications and setting up the development environment and we are struggling with it. To much knowledge required by the developer and way to much money trying to automagically configure the RAD 7.5 workspace with MAVEN and are own scripts.

The idea is to setup pre-configured public repository workspace with all the necessary RAD 7.5 artifacts (server, EAR configuration, web configuration, link between projects and link to MAVEN repository for component that you don't want to load in your workspace.

I prefer my repos workspace to be scoped (never private though, or only the admin can access it and deliver changeset that might not have been delivered to the stream)

The help page mentions:

On the New Repository Workspace panel, enter a number for the level of the visibility for the workspace, which determines who can see the workspace.

    • Public
      Everyone with access to the repository is able to see the files and change sets in all public components in this workspace.
    • Private
      The owner is the only person with read access to the repository workspace. However, change sets in the public components are visible to others.
    • Scoped
      Everyone with read access in the connected project area can see the files and contents in public components in this workspace.

So:

1) will all the users be able to check in the data to the public repository workspace.

No, only the owner can add changesets

2) will all the users be able to deliver the code to the connected stream.

Yes

3) How to get the incoming changes from another user.?

You can change the flow target of that workspace in order to reference the workspace of another user.

Upvotes: 0

Related Questions