Jump to content

Most Liked Content

#6531 P4VS hangs Visual Studio 2012 for several minutes frequently

Posted solidstore on 08 November 2012 - 11:42 AM

I would love to use the Visual Studio plugin for perforce however in our solution we have found that it hangs the entire IDE for atleast 5 minutes every so often and its extremely frustrating. The problem disappears when the Perforce plugin is disabled. I'm not sure what causes it, it seems to happen randomly but quite frequently.

Does this happen to anyone else? Or is there a workaround?

#11440 New Releases of Git Fusion, P4VS and P4API.NET, Commons and P4Java

Posted Perforce Software on 13 November 2013 - 07:02 PM

Here's what’s new from Perforce this month. All the product releases
listed below are now available for download from perforce.com/downloads.

Git Fusion 2013.2: Enterprise Git Management
Git Fusion enables Git and Perforce developers to work side by side
using their preferred tools without compromise. The latest release
makes the experience better still with support for Git tags, the
option of using HTTP instead of SSH as your transport protocol, and a
pre-flight commit hook that allows custom policy enforcement similar
to Perforce change-submit or form-in triggers to ensure both your
Perforce depot and Git repo are in a consistent state.
Download Git Fusion | Release Notes

P4VS: Perforce Plugin for Visual Studio 2013.3 and P4API.NET 2013.3
P4VS, the Perforce Plugin for Visual Studio, embeds the power of
Perforce's version management features into the Microsoft Visual
Studio IDE. If you're working in Perforce Streams, P4VS now has a
Streams tool window that enables a much cleaner workflow with merges
and copies, which can be started directly from the tool window.
Additionally, all Streams in a particular depot can be filtered by
several criteria, and the status of pending work can be seen at a glance.
This release of P4VS includes the latest bug fixes and performance
improvements, and supports Visual Studio 2013. Please note P4VS 2013.3
is the last supported version for Visual Studio 2008.
Download P4VS | Release Notes
Download P4API.NET | Release Notes

Perforce Commons 2013.5: Document Collaboration
If you're using Perforce Commons for document collaboration, get this
latest release for better folder management—namely the ability to
delete, rename and move folders.
Download Commons 2013.5 On-Premise | Release Notes
Activate a Commons Cloud Account—Free for Teams of 20 Users

P4Java 2013.2: Perforce Java API
P4Java is a Java-native API for accessing Perforce SCM services from
within Java applications, servlets, plugins, and other Java contexts.
Get four new P4Java API methods in the 2013.2 release, and the latest
bug fixes.
Download P4Java 2013.2 | Release Notes

Sign Up for Monthly Product Updates
You can sign up to receive monthly product updates by email in the
Communication Center.

Did you miss last month’s product updates? No problem. Visit the
monthly product updates archive to see what was made available for
downloading in previous months:

#17239 Allow user to set whitespace preferences globally

Posted matthauck on 22 April 2015 - 06:40 PM

Currently you can only ignore whitespace on a per-file setting even within a given review. It would be great to be able to set it per review, and have that default to a users' preference.

#15255 Feature Request: Syntax highlighting in diff view

Posted dominik on 16 September 2014 - 11:47 AM

I would like to have the color coded syntax highlighting that I have in the file view also in the diff view. It would be tremendous helpful when doing the review and writing comments.


#18087 Setup Swarm projects via Active Directory groups?

Posted Andrew DeFaria on 11 July 2015 - 01:11 AM

Is it possible to utilize Active Directory groups to setup Swarm projects instead of having to input each and every project member into each project?

#16883 Feature Requests

Posted jerome on 18 March 2015 - 01:15 PM

Hi, we are also evaluating swarm and gathering feature requests from our developers.

Here's a list so far, I hope that it will help
  • Preventing approval of code review when a task is still opened, also re-open the review when a task is re-opened or created.
  • Reporting feature. This is critical for us, we are in a regulated environment and we are required to regularly produce a code review report of all submitted code (for a given job, for example) with all associated tasks.
    • Retrieve comments and tasks details through the REST API. Related to the above request, we started to work on a reporting tool and the REST API does not provide any hook to comments / tasks. Querying directly the perforce server appears to be kind of wrong for that.
  • Allow the developer to set a deadline for his review. When the deadline date approaches and the code review is still opened, a notification is sent.
  • Official support of Windows for swarm server. P4D is compatible with windows, we expect to have all the P4 ecosystem compatible as well.
  • Detach a changelist from a review. We have developers preferring post-commit reviews and they use the add-commit button to associate task-fixing changelists to the original review. When the wrong commit is select and added to a review, they are stuck.
  • Aggregate notifications. When a reviewer makes three comments in a row on the same file, three emails are sent out. That would be better to aggregate them by using a two-step comment creation (batch save) or some kind of periodic notification.
  • Delete and edit of comments, already mentioned in this thread
  • Syntax highlighting in diffs. The syntax highlighting is available when browsing files but disappears in diffs, can that be enabled ? That could be an option
  • Flag a review as important and be able to filter important reviews
  • The add commit button adds the submitted changelist as a new dot in the review timeline. This is quite confusing because it is different from a file update (re-shelving). That would be easier to spot if it was, for example another icon.
  • Clarify the voting feature. Developers approve or reject reviews, why would they need to up-vote or down-vote as well? This adds complexity and people are reluctant to have multiple required reviewers because they have trouble understanding it. Maybe having a configuration option to either go all up-vote (majority and required up-vote = approve) or all approve button would make it simpler.
  • A real TODO list so the user knows what is expected from him. Already mentioned in this thread. We can partially get that from the review tab by playing on filters but that ought to be more convenient and that does not take into account tasks.
  • Review comments not aligned with the code when a file is updated. Can the review comment or task be shown on the left pane of the diff to reduce this occurrence?
  • Threaded comments
And cosmetics or less important in our eyes:
  • Possibility to select multiple lines of code for a comment
  • Group review. Being able to assign a group of people to a review
  • Analytics reports. For example have knowledge of how many tasks are still open by project, review load by user or changelists that are not reviewed.
  • Ping a reviewer, similar to the deadline feature request.
  • We would love code navigation in swarm....
  • [Added 05/22] Attach files of documentation to a review, there is a documented way to do that but that doesn't seem to be doable from the web client
  • [Added 05/22] Diff between two non consecutive shelves, we can achieve that with /reviews/{id}/v{x},{y} but that it is not intuitive at all

#15853 Feature Requests

Posted adrianstone on 17 November 2014 - 11:03 PM

We've been evaluating Swarm for about a month now and it is a great product but we have a few requests for how it could be improved:
  • In the reviews screen, there are many filters available, but it lacks the one filter that we'd find most useful.  There is no way to see only reviews that you are part of that you haven't voted up.  We often have lots of reviews in progress, and what people want to see is all the reviews they are part of that they haven't yet completed.  Even without the filter, there is no way to scan the list and see without clicking on each review whether it is still awaiting a vote from you.
  • It would be nice to have filters on the comments view.  We'd like filters for comments with unverified tasks, comments by the reviewer, and comments by the reviewee.
  • It would be nice to edit comments.  It drives people mad when they mistype a comment and can't correct it.
  • For post-commit reviews, it would be nice if adding committed changelists to the review expanded the list of files in the review rather than replacing it.  If you check in 3 files and start a post-commit review, then fix one of those files in response to comments and check that in, the review should show the modifications to the one file but not lose the changes to the other two files.


#11690 Checkpoint replay to PostgreSQL database for Insight

Posted Punith on 24 November 2013 - 08:57 AM


We have a p4d checkpoint of size 40Gig, while replaying it to PostgresSQL database, its taking days to complete. With 30% of progress it consumed 500Gig of space.

Do you guys recommend any configuration for PostgresSQL to improve the checkpoint replay time?
Also wondering when will Insight start supporting database other than PostgresSQL?


#11602 Issues With Logging In

Posted spectre1989 on 22 November 2013 - 05:37 PM

One of my colleagues is having some issues with logging in. He commits stuff to his sandbox, but when he comes to copy up, he gets error messages saying that he isn't logged in. He's not prompted with a log in box or anything, the only way we've found to authenticate him is to fire up p4admin have him log in to the remote depot from there.

On a similar note, I have a similar problem - I'm prompted with a log in box when I copy up. It doesn't matter how many times I put my password in, it won't accept it. I have to fire up p4admin (for which I'm not prompted to log in for some reason), I then have to choose to change my password, where I actually keep it the same, but the process of doing it seems to authenticate me.

Help with either of these problems would be awesome :D


#11566 GitHub to Perforce migraton - Help requested

Posted ckenkare on 21 November 2013 - 07:17 PM


As part of merging projects, We have a requirement to import files from GITHub to Perforce (details below).

Also, please note that P4D is currently integrated with bugzilla via p4dti.
P4D: Server
P4D/LINUX26X86_64/2008.2/179173 (2008/12/05)- Broadview Netwokrs 24 Users
P4V: Visual Client
P4/NTX86/2008.2/179173 (2008/12/05)
I have never done this kind of migration before.  Kindly suggest me how it can easily achieved. Also, some suggested "GIT Fusion" - But I'm not sure how it's going to work with defect tracking component (bugzilla/p4dti with versions mentioned above).  Thanks in advance..

#11510 Unexpected "all revision already integrated" from p4 integrate using...

Posted Oskar Senft on 20 November 2013 - 04:29 PM

Hi everyone

I'm using a branchspec that maps two different source folders to the same target folder. What happened is that the files in the two folders have been moved manually into the same folder and then just added to P4 without maintaining integration history.

Here's the branchspec:
//source/MDMTests/PCK24_FileLoader/... //target/SystemTests/PCK24_FileLoader/...
"//source/MDMTests/Product Maintenance Tests/..." //target/SystemTests/...

There are changes in the //source/MDMTests/PCK24_FileLoader/... location that have not yet been integrated to the target. However, there are now changes in "//source/MDMTests/Product Maintenance Tests/..." that need integrating.

If I run
p4 integrate -b branchspec
I'm getting
All revision(s) already integrated

However, if I remove the second line from the branchspec, it does integrate the files as expected.

As far as I can tell, since the second mapping from the branchspec yields no files that need integration, P4 seems to discard the first mapping from the branchspec.

Is this correct behavior? Did anyone come across that?


#10706 Interested in installing Perforce products from RPM or deb packages? Quick su...

Posted Don Marti on 15 August 2013 - 09:53 PM

We're in the process of creating RPM and deb packages for installing Perforce products. IMHO this is going to be a time saver, especially when installing something with dependencies such as Git Fusion or Swarm.

If you're interested in installing Perforce products using your system package manager (doing something like "yum install perforce-git-fusion") could you please take a minute to answer a brief survey on how you work with packages? All questions optional, all feedback appreciated.


#22582 Slack invite?

Posted BrianH on 27 October 2017 - 05:38 PM

View PostP4Jen, on 27 October 2017 - 02:21 PM, said:

The decision was taken to shut down the community slack channels, as they were not getting very much use.

Not being used much by who? Perforce employees?

Let this be my official request to keep a chat channel somewhere open.

#21834 Automating Permission changes through command line

Posted Sambwise on 18 May 2017 - 10:27 PM


p4 protect -i < yourfile.txt


cat yourfile.txt | p4 protect -i

or whatever.

For this to work yourfile.txt must be a valid protections spec (same as what you'd get in the editor when you run "p4 protect" normally) -- usually the easiest way to do this in an automated way is to start with "p4 protect -o", do stuff to the result, and then feed the modified result to "p4 protect -i".

You can also use the --field flags to do simple munging of the spec fields:

p4 --field "Protections=super user Me * //..." --field "Protections+=open group SomeGroup * //..." protect -o | p4 protect -i

#19997 How to differentiate email notifications based on Required Reviewer/Optional...

Posted Daniel D'Cotta on 17 May 2016 - 08:36 AM

I get quite a lot of email notifications from Swarm and would like a way to categorize them based on my role:
  • Required Reviewer
  • Optional Reviewer
  • Author

I would love if there was some role information included in each email so that I could used Microsoft Outlook's Rules to move them to different folders.

This is so that I can prioritized which notification I deal with first.

#19921 P4VS NuGet support

Posted pditterline on 27 April 2016 - 02:17 PM

Are there any plans to implement this change?  Our team is regularly bitten by packages.config failing to get checked out as well.

#19753 command that does both "change" and "describe"

Posted P4Matt on 15 March 2016 - 10:01 PM

Just for grins and giggles, here is a version of Nicole's one liner using the upcoming 16.1 p4 aliases feature:

full-changes $(rev) = -ztag -F %change% changes $(rev) > $(changes) && -x - describe -s < $(changes)

#19696 Changing case for filenames / folders

Posted Domenic on 07 March 2016 - 06:57 PM

http://answers.perfo...rticles/KB/3448 (Changing the Case of a Filename) should also be helpful :)

#18804 p4 command to determine the depot source path of file marked for integrate

Posted P4Sam on 13 October 2015 - 08:50 PM

View Postgsb, on 13 October 2015 - 08:29 PM, said:

I'm working on a p4 change-submit trigger where I need to determine the source depot path for files marked as "integrate"  and reject the submit if the source is coming from a certain branch.

Use "p4 resolved" -- make sure to use the submitting client to run the command, since "resolved" shows you resolve information for the current client, not across all clients.

#18593 "p4 reconcile -n" with lots of spurious diffs?

Posted P4Sam on 17 September 2015 - 08:20 PM

View Postjchowdown, on 17 September 2015 - 08:06 PM, said:

Art.meta is a text file. Our Line endings are set to Shared in my workspace.

That's a pretty big clue.  What if you change your LineEnd to "unix" and try the reconcile again?  Or open the file for edit, submit, and reconcile again?