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.?
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.
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 ?
Related
we are developing some private libraries and are wondering how do we get them shared between different users of the team?
Same as a git repository (I guess) but do we need to have them stored in Codesys store as a private repository or we can have them stored on our local server and different user to sync to that backend?
Default settings for the Managed Libraries are in the local drive C:/ProgramData, which works for a single user but not very well where a team need to access the library.
It would be great if you could help me with one thing.
I'm using Fossil as my version manager. Using this on my PC is not a problem but when I try to push it to remote repository I can't.
Here's the thing:
When inside folder with my repository I type
fossil push https://chiselapp.com/user/sebatbg/repository/nres
I get info that:
Error: Wrong project
When I type
fossil push https://sebatbg#chiselapp.com/user/sebatbg/repository/nres
It asks for my password but when I enter it fossil says that Login failed
I tried both my pass to chisel app and for specific repository but result is the same.
Could anyone tell me step by step how to do the push?
Thank you
Fossil assigns a unique ID, called the "project ID", to each new repository. The error message "Wrong project" means that you've got different repositories locally and remotely, that their project-IDs don't match.
The only way I know to publish an existing local repository on Chisel is to upload said repository, and then set the remote-url of your local repository to the Chisel URL, either explicitly or by pulling from the URL.
I had a similar problem. I had cloned a remote repository, but could not push to it.
I could solve it by adding the username to the remote url
remote-url https://{username}#chiselapp.com/user/{chiselab-user}/repository/{repository-name}
you are then prompted for the password of the remote repository.
If you have an existing local repository that you would like to upload to the chiselapp hosting service, the process can be a bit awkward. If your repository is smaller than 8M, chiselapp provides a command Upload repository that may suit your purposes. Otherwise, this is what you need to do:
Navigate to a source tree for the local repository.
Issue the fossil info command and copy the project-code of the local
repository. This is a SHA1 hash.
Log in to chiselapp.com website and click on the Create Repository
link in the header of the home page.
Paste the previously copied project-code into the Override Project Code
field of the resulting form.
Fill the remaining fields as appropriate and click the Create Repository
button at the bottom of the page.
Record the password that is then assigned to you.
Navigate to the chiselapp dashboard and click on the name of the newly
created repository. This should bring you to the fossil web interface of this repository.
Login to the new repository using your local username and the recorded
password. This should be the only user so far and should have setup user permissions.
Navigate to the Admin/Stats page and check that the Project ID of the new
remote repository matches the project-code of the local repository.
Back in the local repository's source tree issue the command
fossil push https://<username>:<recorded-password>#chiselapp.com/user/<username>/repository/<repository-name> -R <local-repository-file>
Can someone please suggest me how to centrally store DB connections and jobs in DI repository
I installed s/w on 2 machines. On one machine I have enabled the Kettle DI repository but when I try to access the same from the other m/c, I am not able to access
Can someone suggest me any good tutorial or video etc ?
Thanks
Repository connection definitions are stored in your .kettle file. This is by default in your user profile directory. To share the same definitions among a group of users on the same machine, move the kettle home directory to a shared location and set the KETTLE_HOME environment variable to reflect that location.
Then copy that .kettle file to all installations that need to share the repositories.
I've a very simple application built in MVC4. This application allow the users to upload a file, and the application generates an output.
This app works great locally, but when I publish to azure (by right click -> publish), I get a less descriptive error. I've figured out that the error was because in the code, we accessed to a server relative path, and that is not possible in azure. So I've found a way to solve that in this link, that says that I should use LocalResource, rather than Server.MapPath. That make sense for me, but so far, I'm struggling with the suggested line.
LocalResource localResource = RoleEnvironment.GetLocalResource("DownloadedTemplates");
I'm not able to get it working, and also can't get a proper error. BTW I'm not sure how to enable the error log in azure :(
So, after going deeper in MSDN, I've seen that I should configure the Local Storage Resources, but as I've created a local MVC4 project, I can't find where I should configure this.
I need to be able to store a temporary file in the application (hosted in azure).
Did someone faced with this problem?
Anybody knows how to enable the Local Storage Resource in a project like that?
TIA!
Milton RodrÃguez
Well, after struggling a while, I've ended up using Windows Azure Tools.
The steps:
Add a new project
Under Cloud category, select Windows Azure Cloud Service.Note that if you don't have this option, an option to install the needed SDK will be shown. Install it first.
Name it properly :)
New Windows Azure Cloud Service window will appear, select the role that fits your needs. In my case, I choose ASP.Net MVC4, and then removed it.Note that you can edit the name of the created role at the right.
In the Roles folder of your new project, select Add, and then Web Role Project in solution. Your project will be an option to add.
You can remove the other role in the folder, the web project created in step 4, and also the folder ending in Content (ie. WebRole1Content). Basically, you can remove the created assets, but the Azure Service, and link the service to your project.
You're almost done. Follow this link to configurate your local storage :)
Now you're done!
Is it possible to have publicly available read-access maven repository on cloudbees?
I did found a wiki entry on private maven repository http://wiki.cloudbees.com/bin/view/DEV/CloudBees+Private+Maven+Repository but it clearly states that access to maven repo is only for users wired to cloudbees account.
Looking at the description of the project at https://github.com/arey/hibernate-hydrate which is build by Dev#Cloud and then deployed to cloudbees maven repo, it seems it is possible.
In my case every time i enter https://repository-<cloudbees-account>.forge.cloudbees.com i am prompted for a password. Can anyone help me on this?
Assuming i have 2 cloudbees accounts: A and B, is it possible to have public accessible maven repo for account A and at the same time password protected repo for account B?
UPDATE: I finally got it, on repository page you can define if one of repositories (svn/git/maven repo) is to be public or account access
So regarding Jesse advice i am posting a response to my own questions:
on cloudbees repository page you can define if give repository (of type maven,svn, git) is accessible (in read only mode) for public access. Originally i was fooled by "maven private repository" name used by cloudbees - it is indeed private (defined specially for your cloudbees account) but it can be publicly accessible.