Jump to content

calbzam

Administrators
  • Posts

    3,118
  • Joined

  • Last visited

  • Days Won

    115

Posts posted by calbzam

  1. Hi,

     

    Yes,

     

    If you have a wXlink pointing to Lib repo and you perform a change, a new changeset will be created in both repositories. 

    Even if you create a new branch, this new branch will be autoexpanded as well to the Xlinked repository.

     

    Please, check this guide for more information: https://www.plasticscm.com/documentation/xlinks/plastic-scm-version-control-xlinks-guide.shtml#Chapter3:XlinkExpansionRules

     

    Regards,

    Carlos.

  2. Hi,

     

    You will be happy to know that we are implementing the support to point subdirectories instead of just the root of the repository when using readonly Xlinks.

     

    Other possibilities are:

     

    - Adding to the "Cloaked list" the items you don´t want to download from the shared repositopry. Cloaked items are items that the update operation won't download by default from the repository to the workspace. http://plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide.shtml

     

    - You can also think on splitting the shared repository in different repositiories.

     

    Regards,

    Carlos.

  3. Hi,


     


    I´m able to reproduce the issue when using the sync view. We are going to review it and fix it asap, but anayway using the Branch explorer or the command line, it should properly work:


     


     


    - Command line:  cm replicate br:/main@default@localhost:8087 repoRemote@ssl://remoteServer:8088

     

    - Branch explorer --> right-click --> replicate:  Remenber that you should enter something like:"ssl://serverName:8088" in the replication dialog  of the remote server (If don´t enter the protocol, you will not ble a to perform the replication).

     

     

    Regards,

    Carlos

  4. Hi,

     

    If you configure the sync view using a hostname that is not getting the "WARNING" message (running "cm lrep"), are you still getting the error?

     

    Could you try running the "cm replicate" command instead?  If a command works, the rest of the commands should also work.

     

    The client GUI is is not probably showing the warning dialogs, just the "authentication or decryption has failed" error.

     

    Regards,

    Carlos

  5. Hi,

     

    I´m able to configure the same scenario. Let me guess what could be happening:

     

    - If I run a "cm lrep" using the remote IP, I get this message

    C:\Program Files\PlasticSCM5\client>cm lrep ssl://192.168.1.56:8088
    WARNING: the secure connection hostname provided in the server
    certificate doesn't match the server's hostname. This means that the
    certificate was not issued to this hostname or that there is a network
    configuration problem with this host.
    
    
    - Certificate hostname: CN=triskelion
    - Server hostname: CN=192.168.1.56
    If I re-run the command, the WARNING is appearing again and again.
     
     

    - If I run a "cm lrep" using the hostname, I don´t get this message because the certificate was issued for this hostname.

    C:\Program Files\PlasticSCM5\client>cm lrep ssl://triskelion:8088
     1 default ssl://triskelion:8088
     
    The same happens when configuring the sync view. You need to enter the same hostname that is stored in the certificate. If you use the IP or a different server alias, the SSL connection will not work.
     
    Summary:
    - Step 1: Run the "cm lrep" command and check that the WARNING message is not being shown.
    - Step 2: Configure the sync view using the same server name as the previous command.
     
    Regards,
    Carlos
     
  6. Hi dist,

     

    If a Plastic SCM client tries to connect to a Plastic SCM server using SSL, a message will pop up
    asking to accept or reject the server certificate. If the client accepts the certificate, it will be
    stored in the machine for further operations. Once the certificate is accepted, communication
    will flow, but what happens when a server needs to talk with another SSL server?
     
     
    If a Plastic SCM client tries to connect to a Plastic SCM server using SSL, a message will pop up
    asking to accept or reject the server certificate. If the client accepts the certificate, it will be
    stored in the machine for further operations. Once the certificate is accepted, communication
    will flow, but what happens when a server needs to talk with another SSL server?
     
    Installing the certificate on server machines
    As the server does not have any interface to interact with the user and accept the remote server certificates, we have to manually install the remote certificates on the server machine.
    If the Server machine is a Windows machine you can use the “certmgr.msc” tool to import the remote server certificate. It needs to be imported into the “Plastic Client” store:
     
    If the Plastic SCM server is installed in a Linux machine the “cer” file must be copied to the "~/.config/.mono/certs/Plastic client/" directory.
    Both Windows and Linux steps must be carried out by the user that is running the Plastic SCM server. So the “certmgr.msc” tool must be executed by the right user and the "~/.config/.” path must be for the correct user.
     

    Regards,

    Carlos

  7. Hi,

     

    - If you are using VS2013, I recommend you to test out integration package. It will help you to perform the SCM operations.

    - In the "Pending changes" view, there is an "Options" button where you can select "Show private items".  This way you can check the private items you have in the workspace and add them to source control in a single checkin.

    - Plastic allows to store private files in the workspace, but as I explained, it´s very easy to review the private files and add them to Plastic in a single step.

     

    Regards,

    Carlos 

  8. Hi,

     

    We try to support the official IntelliJ IDEA IDE, and as far as I know some of the "descendatns" were also compatible.

     

    Do you mean that after the upgrade from  IntelliJ IDEA 13.0.2 Community Edition to 13.1.1 the plugin stopeed working? In that case, I will check if there are new API changes that may have broken the integration.

     

    What Plastic version are you using?

     

    Best regards,

    Carlos

  9. Hi,

     

    When you perform the cherry pick operation, it doesn´t keep traceability as merge does. When you try to merge the task branch in the main branch, there is not a common ancestor and you get the loaded twice conflict (Plastic always does a 3 way merge)

     

    We have a task to improve this kind of scenarios. Actually, this is a variation of the linked user voice request (based on the same concept). It´s in our roadmap to improve these scenarios, but voting in the user voice page is appreciated.

     

    Regards,

    Carlos

×
×
  • Create New...