Jump to content

KVs

Members
  • Posts

    5
  • Joined

  • Last visited

KVs's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi Carlos, We are writing program to sync the changeset deletion in servers. GUID is common between the servers. So we retrieve the GUID with before-rmchange set trigger and delete the changeset in remote server with after-rmchangeset trigger. The issue is we get null value for PLASTIC_FULL_BRANCH_NAME environment variable. Sample code is below echo %PLASTIC_CHANGESET_NUMBER% >> C:\trigger\log.txt echo %PLASTIC_CHANGESET_OWNER% >> C:\trigger\log.txt echo %PLASTIC_BRANCH_NAME% >> C:\trigger\log.txt echo %PLASTIC_REPOSITORY_ID% >> C:\trigger\log.txt echo %PLASTIC_REPOSITORY_NAME% >> C:\trigger\log.txt echo %PLASTIC_COMMENT% >> C:\trigger\log.txt echo %PLASTIC_FULL_BRANCH_NAME% >> C:\trigger\log.txt echo %PLASTIC_CLIENTMACHINE% >> C:\trigger\log.txt Please let me know is there any other way to sync the changeset deletion. Br, KVS
  2. Hello Carlos, Moved the the syncservertrigger to production servers. But after-replicationwrite trigger is removed. My only issue now is delete changeset is not replicated between servers. Any idea on how to resolve this issue. Thanks
  3. Hello Carlos, Moved the the syncservertrigger to production servers. But after-replicationwrite trigger is removed. My only issue now is delete changeset is not replicated between servers. Any idea on how to resolve this issue. Thanks
  4. Dear Carlos, Thanks for the synctrigger tool. Tried the tool on the test setup with 2 windows servers. Changed the Plastic Server service account to run as Administrator user to make it work. During network outage if there are checkins to the same Repository on both servers , the changeset number is same on both servers. But the Changeset content is different. When the network resumes, the sync stops with error and requires user intervention to sort out the sync issues. Is it possible to avoid user intervention by deploying cloud extension. Another issue is the tool is installed on both Plastic servers. The after-replicationwrite trigger goes on endless loop. Attached is the log file. Should we remove after-replicationwrite trigger in one of the server? Warnemails does not work does not work. I think we can correct this issue ourselves. Thanks Saravanan 2020-10-09.log.txt
  5. We have 2 Plastic Enterprise servers in Bangalore and London. Both servers act as Master. Currently using triggers to replicate the Repositories between 2 servers. Issue here is the replication starts only on trigger. Is there any better way to auto sync all the repositories between 2 servers at server level instead of repository level? Will deploying Cloud extension on these servers help to achieve auto syncing of all Repos on daily basis? Thanks
×
×
  • Create New...