Jump to content


P4Jen

Member Since 11 Apr 2014
Offline Last Active Sep 18 2020 05:18 PM
-----

Posts I've Made

In Topic: Implementing a linter as a change-content trigger

16 September 2020 - 04:39 PM

Hi,

There are some change-content trigger examples In the Helix Server admin guide:
  https://www.perforce...ts.content.html

Some example triggers are also located here:
  https://swarm.worksh...ham-p4triggers/

Kind regards,
Jen.

In Topic: Workspace doesn't sync to ChangeView of virtual stream after changing it

11 September 2020 - 04:46 PM

Hi,
It sounds like Epic Games would need to change the way they currently do things with streams, to enable you to achieve what you went.

I suggest you raise this with them.

If there is a problem that can not be resolved by tweaking the stream specs or creating a new virtual stream, they can open a support case with us to discuss the issue further.

Kind regards,
Jen.

In Topic: Where to Get Perforce at Price Within my Budget?

11 August 2020 - 05:01 PM

Hi,

To find out about licensing and pricing, you will need to contact our sales team.

We don't give out any discounts via the forums.

Kind regards,
Jen.

In Topic: Lost all data besides archives folder

27 July 2020 - 11:40 AM

Hi Adam,

If you no longer have the database files (db.* files) then all the metadata the Helix Core server created about your files is gone.
It sounds like your files were stored as binary, so each revision is stored within a 'gz' file.

You can extract these and re-add them to a fresh Helix Core server, but all the metadata about them will be new.

If some of your files are RCS, they will be stored as text files and the deltas of each revision will be stored.

On Linux or Mac OS you can use the tool 'co' to extract some information from the RCS files, but this is no substitute for the
metadata you would get from the 'db.*' files.

For future reference, information about Helix Core backup and recovery is here:
  https://www.perforce...ter.backup.html

Regards,
Jen.

In Topic: Errors upgrading a Ubuntu P4 server

27 July 2020 - 11:24 AM

Hi,
For future reference, this KB article provides details about what you can expect to see when upgrading packages, and also links to
the documentation in the Helix Core admin guide:
  https://community.pe...s/article/16525

Before trying anything else I suggest you first backup your depot files, and take a checkpoint.
To take a checkpoint, run:
  p4d -r <P4Root> -jc

Also, this forum post may provide some hints about the 'temporary failure in name resolution" error:
  https://forums.perfo...ilure-on-linux/

Once you have a checkpoint and backup of archive files, you can reinstall the packages if necessary, then restore your checkpoint
and archive files.

If you would like more assistance from technical support and don't have a support contract, please contact our sales team to discuss this further.

In the mean time I hope this helps,
Jen.