Jump to content

Héber

Administrators
  • Posts

    175
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by Héber

  1. Hi, 

    I'm not sure I'm understanding what you are trying to achieve here. 

    If it is only the find thing, then you can also add the entry to check the attribute and attribute value, but I'm not sure if this is what you are looking for or not.

    Could you give us more details? What is the final goal?

     

    Best,

    Héber.

  2. Hi,
     
    First of all, what we would need is to run a "cm iostats yourorganization@cloud" to check the actual speed that you are getting.
     
    Based on those results we can try to ascertain why it is being that slow. Could you share that information?
     
    Best,
    Héber.
  3. Hi Stephen,

    I understand your frustration with this. 

    The problem is that branches are an entity by themselves in Plastic, and operations can be run against them. In fact, a workspace can be pointing to an empty branch (although it will be loading the content of the parent changeset) thus the need to show in the selector the branch without the changeset. I agree that the usability here could be improved, but there is no way at the moment to get all the information with one command.

    I'm sorry for the inconvenience.

     

    Best,

    Héber.

  4. Hey!

    This is Héber. 

    Can you try creating a "plastic.selector" file in that location with the following content replacing the repo and organization name with yours?

    rep "repponame@organizationname@cloud"
      path "/"
        smartbranch "/main" changeset "0"           

    Once that is sorted out, could you run an update operation?

     

    Best,

    Héber.

  5. HI,

    Can you check that your workspace is pointing to the cloud server's repo? My guess is that at least one of you is working distributed without pushing the changes, so they are not being sent to the server. here you have more information on how to work centralized:

    https://www.plasticscm.com/documentation/cloud-edition/plastic-scm-version-control-cloud-edition-guide#WorkcentralizedwithPlastic

     

    Best,

    Héber.

  6. Hi,
     

    Yes, it is supported. 
    Let's try this:

    • Open the regular PlasticSCM GUI.
    • Go to "other actions" and then "sync repositories".
    • Create a new sync view and set the local repo as the source one and the cloud one as the destination one.
    • Push the branches with the "push visible" option.
    • Go to the repositories view.
    • Set the cloud server in the top bar and then search for the cloud repo you just synced.
    • Right-click on the latest changeset.
    • Select the "switch workspace to this changeset" option.

    With that, your content should be in the cloud now and your workspace pointing to that repo, so you don't need to run the sync operations anymore.
     

    Best,

    Héber.

  7. Hi,

    For the recent Ubuntu version where the libgnome2 library was deprecated, we recommended users grab the packages from the Ubuntu18 - Bionicle repos. That one should be the one you need to install.

    Regarding PlasticX, it is in Alfa, so if you want to use it, that's perfectly fine. Most of the team uses it, but we end up lacking some functionalities. It should give no particular errors, but keep in mind that it is not even a Beta yet, expect missing features and bugs. Aside from that, I can't tell you whether to use it or not.

    Best,

    Héber.

  8. Hi,

    If you are working centralized then you need access to the server in order to check the file out, as it would try to get a lock on it. If you don't have access to it, I'm afraid you can't checkout the file. 

    If you are working distributed, make sure that the workspace is pointing to the local server.

     

    Best,

    Héber.

  9. Hi Peter,

    Using the jet.conf file is the way to go. With it, you can specify where the repositories should be created. A new "jet" folder will be there with the repos inside. If you create a new repo, a new folder inside the jet one should be created named "rep_X" where the X stands for the number of the repo.

    Keep in mind that it will start creating them there, not move the old ones. 

    What version are you using? I guess this is a cloud edition, right? Can you share your jet.conf file?

     

    Best,

    Héber.

     

×
×
  • Create New...