Jump to content

calbzam

Administrators
  • Posts

    3,118
  • Joined

  • Last visited

  • Days Won

    115

Posts posted by calbzam

  1. Hi,

    - Have you recently upgraded any security policy in your machine? I guess you were using Plastic with no issues until now (and no recent Plastic version upgrades), right?

    Maybe a recent Windows upgrade?


    - Can you temporary disable the antivirus/Windows defender... Some external tool (or security policy) seems to be preventing the Plastic client to start.

    - Do you have installed any of the following tools?

    MSI Afterburner

    RivaTuner

    Regards,

    Caros.

  2. Hi,

    We are already handling this via support ticket, but just let me post the answer also here:
     

    Quote

     

    Plastic-global-config should already be available for Cloud Edition.
    Have you tried? 
    Are there any issues?
    We are not aware of any problem with it, so if you can't configure it, please tell us as it should be working.

    However, even if there is not still a GUI panel to configure the issue tracker, you can still do it via a configuration file. Please check our guide:
    https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#JIRAintegration

    Hope this helps you.

    Best regards,

    Héber.

     

     

  3. Hi @jwkdwuvrt, what specific integration do you miss in the cloud? Plastic hosted servers doesn't neither have a a specific slack integration apart from the one mentioned in previous link and it should be also valid if you are using cloud repos.

    The only limitation is the Plastic cloud still doesn't have support for mergebots (not sure if this is what you mean). 

    https://www.plasticscm.com/mergebot-devops

    But the note that Plastic cloud isfully  compatible with all of our CI and issue tracker plugins/integrations (Jenkins, Teamcity, Bamboo, JIRA...).

    Your feedback is welcome.

    Regards,

    Carlos.

  4. Hello,

    Just replicating the branches that you actually need doesn't help to reduce the size? I'm afraid that the hydration feature is not configurable to some specific changesets.

    It's on our roadmap to provide a solution to reduce the Jet databases removing the old history of a repo. I guess this feature would be also useful in your scenario.

    Regards,

    Carlos.

     

  5. If you use two server (for work and personal projects), you can replace the cloud edition license by your personal license. This way, you will be able to run the replica and configure both servers based on your needs.

    The Plastic cloud edition license is designed only for hosting local repos and push/pull to the cloud. You cannot create new users or even run the web admin panel to configure the local server.

    Regards,

    Carlos.

  6. Hi,

    I would use your current Plastic edtion installation. If I properly, understand it, your are using it for your work but you also want to create some local repos for personal projects.

    Plastic cloud edition installs by default a local Plastic server (to host your local repos) and I would use this same local server for your personal projects.

    By default, Plastic Cloud edition includes a Plastic license for 1 user (the local machine user). If I properly understand you don't want to use this same local user for your personal projects?

    If you replace the default "plasticd.lic" by the Personal license, you will be able to re-configure your local server and create a custom user. But at the end of the day, your local server (doesn´t matter if using cloud edition or a Personal license) will only support one user. More than one user, requires a Team license.

    As you mentioned, you can install a second server, using a docker container... but I think this complicates too much the setup.

    http://blog.plasticscm.com/2015/01/plastic-meets-docker.html

    I would use the same local user for my personal projects (local repos) in order to make the setup as simple as possible.

    Regards,

    Carlos.

  7. Hello,

    I'm afraid we still don't have a feature to support this kind of workflow to easily remove the old changesets (repo history). Not sure if you are refering to the "cm archive" commnad, but I think it won't be useful in this scenario as it won't release the space used by the databases. 

    I'm sharing your feedback with the team because we have in mind to support and provide a solution for these kind of workflow. I will let you know if we shedule something in the near future.

    Sorry for the inconveniences,

    Carlos.

  8. Hi again,

    - If you manually remove the " C:\Users\me\AppData\Local\plastic4\issuetrackers" folder and re-configure the values from scratch, does the issue persist, right?

    - If you have a "plastic-global-config" repo, you should have a local "C:\Users\me\AppData\Local\plastic4\globalconfig" folder. Even if it doesn't contain nothing related to the issue tracker but just a "ignore.conf".

     

    Quote

     Error when performing background operation: The remote name could not be resolved: 'local'

    - If you are using Plastic cloud edition installer, no sure why the "local" server cannot be resolved. Anyway, it doesn't seem to be related to the issue tracker problem.

    - If you reach us at support@codicesoftware.com, we can even arrange a GoToMeeting session to debug what could be your problem.

    Regards,

    Carlos.

  9. Hi,

    We have tracked this request also from other customers. We initially designed the Plastic SCM Cloud to work as a pull/push service, more and more users demanded a centralized workflow with the rest of operations such us, checkin, create branch, update, switch...

    The shelve operation didn't get much traction and was left in the backlog. I will share it again with the team.

    Regards,

    Carlos.

  10. If you are using GitSync, you should be using the same client (the one where the original mappings were created to perform the future syncs). Also the Gitsync operation is performed between one specifc Plastic repo and a git repo. 

    If you want to involve a totally new repo in the sync, it needs to be empty so at the same time it's populated, the local mappings are also generated in your client.

    I'm gessing if you are replicating a repo in a client where you don't have the original GitSync mappings and this is duplicating all the repo history. We need to be careful with this workflow because it could break the repo history.

    Regards,

    Carlos.

     

  11. It seems like a temporary network issue and the client is not able to download the requested revisions. Is the network you are using fast and stable enough?

    The error message is not very clear. Leaving Plastic open for a long time should be any problem.

    Is it Windows or macOS? If you attach the client logs, we will review them in detail.

    Regards,

    Carlos.

×
×
  • Create New...