P4 Plugin - By Perforce Software. Jenkins plugin for a Perforce Helix Versioning Engine. Is this a Matrix Project? What Axes do you have and do you use any variables in the workspace view? Jenkins polls on the master and I rely on the SyncID to track changes. As a temporary fix we are periodically removing all *.txt files created by the. Perforce has specific issues when projects within a depot exist in different local locations that don't map directly to the depot. Added support for managing Perforce workspaces with multiple mappings in the view spec (JENKINS-3745) Perforce user's password is. Where can I file a request for the Perforce plugin to provide a way to.

The existing 'perforce' plugin is used by many of our customers and I was concerned that effectively replacing it with the new plugin may upset some users. Whilst the new plugin provides all the basic SCM functions, it is not yet as feature rich. We plan to add features over the next few months and are keen to involve the community as much as possible.

We would obviously like to use the 'Perforce' name space; perhaps there is a way to branch (fork) the old codebase into a legacy area? Paul > -- > You received this message because you are subscribed to the Google Groups 'Jenkins Developers' group. > To unsubscribe from this group and stop receiving emails from it, send an email to. > For more options, visit. -------------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.

Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Perforce Software. Finally, the recipient should check this email and any attachments for the presence of viruses. Perforce Software accepts no liability for any damage caused by any virus transmitted by this email.

Perforce Software UK Ltd is registered in England and Wales as company no. 3816019 at the following address: West Forest Gate, Wellington Road, Wokingham, RG40 2AT, UK -------------------------------------------------------------------------------- Jesse Glick 17/4/2014, 8:59 น. On Thu, Apr 17, 2014 at 11:51 AM, Paul Allen wrote: > Whilst the new plugin provides all the basic SCM functions, it is not yet as feature rich.

We plan to add features [] > > [] perhaps there is a way to branch (fork) the old codebase into a legacy area? A bit more work, but arguably better for users, would be to include the new refactored implementation inside the existing plugin (in trunk versions). For a time, users of the plugin would see two SCM options—Perforce (v1) and Perforce (v2)—with somewhat different configuration UIs and functionality. Silent hunter commanders edition.

They could experiment with switching to v2, or go back for a while, on a project-by-project basis. You could even decide that v1 configurations restricted to a certain set of commonly used features would be safe to automatically upgrade (i.e., readResolve) to a v2 configuration. Eventually the v1 implementation could be dropped, or rather exist only as a class with a readResolve method. This is of course assuming that the current maintainer(s) of perforce-plugin are aware of your effort and on board with it. Pallen 17/4/2014, 9:52 น. Hi Rob, The refactoring effort would be so wide spread there would be very little, if anything, left.

By removing the underlying p4 command wrapper (Tek42) and replacing it with the p4-java api would require a re-write of all the functions. In addition the behavioural changes to the use of Perforce workspaces and authentication would change most of the user interface. I suggest that we either create a new plugin 'p4' or fork/rename the existing plugin. A new plugin would be less disruptive to the existing user base and give the opportunity for a clean start. Paul Stephen Connolly 18/4/2014, 2:42 น.