307 results found
-
Add CLI command to replace existing checkin-comment
Via GUI it's possible to edit existing checkin-comments and save them.
In the CLI (cm command line) there is no equivalent to this action. There should be a command to replace the comment of a specified changeset.
That way we could apply batch pattern-replacement in checkin comments, similar to "git filter-branch --msg-filter". This is not about rewriting history, as only the comments will be modified.
An example of where this is useful: after import from SVN via Git each changeset has got an appended formatted string, starting with "git-svn-id:" and containing info about the corresponding branch and revision in the…
10 votes -
Provide a setting to disable drag&drop in Pending changes view inside Visual Studio
I'm using the Visual Studio extension of Plastic SCM. In the "Pending changes in workspace" view dragging and dropping changed files is possible, which opens that file directly in Visual Studio.
This feature might have been a good idea, but I'm starting to hate it. Every time when I try to select/click on of those files, I move my mouse a few pixels and drag&drop kicks in and opens that file, but my intention was to check/uncheck that file, not opening it.
Either there should be an option to disable drag&dop, or the sensitivity of the drag&drop operation should be…
9 votes -
Put also item revision number on history view
I would like you to add also additional column in "Item History View" with revision number.
Currently in "History view" there are changset numbers.
In "History 2d tree view" there are item revision numbers.
It is very difficult to connect entries in "History view" with points in "History 2D tree".4 votes‘History’ & ‘History 2D tree’ views already use changeset numbers. Checked in the 5.4.16.738 release.
-
Bug: Edit changes in Visual Studio Plugin loses changes
After editing a checkedout file in Visual Studio, open "Diff with previous". The changes can be edited. I found the "Save" button on top (hard to see...), but if you close the window before saving all changes are lost with no warning. I think that is a serious bug.
8 votesDone! Available in the 695 release.
-
maintain selection on update of changeset list
When updating the list of changesets the current selection is lost. I suggest always maintaining the selection state. This is important for persons reviewing the history of a branch or repository respectively. They need to track which changeset they are currently investigating.
13 votes -
Jenkins selector text should support build parameters
The Plastic SCM Jenkins plugin currently does not process build parameters for the selector text.
If this was supported, one application of this is would be to parametrize a Jenkins build such that a branch can be selected as a parameter.
3 votes -
add support for creating plugins / third party integrations on Mac Plastic
Third party integrations and the ability to make our own plugins is great on Windows, but don't seem to be supported on Mac Plastic. If there was some way to use the same code for both platforms, that would be even better!
3 votesHi Eric,
Thank you for your interest in improving Plastic SCM!
We’re really happy to say that both GTK Plastic and MacPlastic are fully compatible with existing and custom issue tracker extension libraries. However, the only supported functionality at the moment is the checkin log when working in Task on Branch mode.
Since the issue tracker extensions are implemented using C# and the .Net framework, you can absolutely use the same libraries available for Windows, even your custom ones!
Please follow these steps to enable your extension:
1. Edit your client.conf file (located at ${HOME}/.plastic4/client.conf by default) and add the following lines inside the ClientConfigData tag:1.1. You’ll need to set the AssemblyFile attribute value with your own, of course.
2. If you start MacPlastic right away, your extension won’t work because it lacks the appropriate configuration values. However, the configuration file itself should have been created now. You… -
Create repo during first sync of that repo to local PC (for DVCS)
To make DVCS easier, allow for a local PC repo to be created during the first sync (or perhaps better during the setup of the sync pair). Default to creating the local repo with the same name as the central repo you are settting up a sync with.
It seems natural to me, that I be able to have the setting up of a sync for the purpose of DVCS be able to create the local PC repo for me, rather than having to create it first, then setup the sync.3 votesHi! I’m glad to say this have been implemented for some time now. Sorry for not keeping you updated on this!
Now, while creating a Sync View from the Repositories View (Repositories > Right click on a repository > Create new Sync View (push/pull)), or from the Cloud View (same steps as before), you can create the local or remote repositories with a single click (depending on which of them doesn’t exist).
For example, let’s suppose that you are browsing your local repositories, and you want to create a sync view using your local repository as the source, and the remote as the destination. If there is no repository in the destination server (your Cloud organization, by default) with the same name as the source one, you can create it with a single click.
If what you are browsing are the repositories in a remote server, it works the same…
-
Auto-comment fields values in pending changes shall be refreshed after clicking refresh
There is great feature which allows to put automatically time, date or branch name into check-in comment.
But I have one observation - formating syntax variables are evaluated only ones when Pending Chanegs tab is opened first time.
If in meantime branch will be switched and refresh button clicked it still remains the same. So it leads to situation when both {1} (Data) and {3} (Branch name) can be complately out of sync with real check-in operation.
I propose that refresh shall also re-evaluate auto-comment string and update Check-in comment accordingly.
3 votesReleased in BL693
-
Allow changing branch parent
Allow some way to restructure branch parentage. CLI or or other power-user way would suffice...
If it's true that child branches and top-level branches are identical types and the hierarchy is only for display purposes, I would want to have some way of changing the parentage of a branch (at least from the CLI).
Make child branch from top-level branch, and vice-versa.
There may have to be restrictions on this, like "parent can only be set to root or creation point"?
The practical use-case for us is that we have imported some top-level branches from SVN that logically should be…
3 votesClosed thanks to Göran answer. It is a hacker way to do it but probably it is fine right now.
-
spell checker
i think it is mandatory for all textual input fields.
3 votesDone. 6.0 added speelchecker to the checkin when you write comments.
-
allow selection of multiple directory conflicts and resolve at once on macplastic
Currently, I have to go through one-by-one for directory conflicts and resolve them individually. This is painful when I have 144 evil twin conflicts.
3 votes -
trigger on merge
In order to be able to implement a condition on merge, such as requiring a peer review before merge, or a test build completing, I would like to see the ability to have a trigger on a merge operation. Today we can trigger on the check-in after starting a merge, but then if the condition is not met we are left with having to undo the merge (remove the pending changes). It would be much easier to implement this sort of "merge gate condition" if the trigger could be on the actual merge operation.
6 votes[New] Release 6.0.16.1471
Added a new before-merge trigger. This trigger could be used to deny the merge of some branches if certain conditions are not met.
The trigger can be register using the following command:
[code]cm maketrigger before-merge merge_gate “/path/to/script” —server=myserver:8084[/code]Check the [link] https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide.shtml#Chapter5:Detailedtriggerreference triggers reference[/link] to check all the available info on the merge trigger.
Remarks: the client and the server should be updated to use this functionality
-
TeamCity plugin: support agent-side VCS checkout mode
Currently, the Plastic plugin for TeamCity (Continuous Integration) only supports server-side checkout mode.
This means the workspace resides on the server and after updating the workspace its contents are copied to the build agent(s). Thus, the agent does not have a complete workspace, only a copy, which means that Plastic commands can not be run in this copy on the agent.
More specifically, it is not possible to ask questions about the current changeset or workspace status on the agent. (Our build process assumes that the build is done inside a Plastic workspace.)
Could you please considere supporting the TeamCity…
6 votesDone in 5.4.16.712
-
Items view: allow diff of two different files (Diff selected files)
In the Items view, it would be very useful to select two different files in the tree and compare them against each other.
As it is, I can't use Plastic's excellent Diff window for this purpose (at least not from inside the Plastic GUI). Instead I have to configure a Diff tool separately with a shell extension and use it from Windows explorer.
1 vote -
'cm find revision' command shall properly display files in case of merge from other branch
Currently command 'cmd find revision' for changsets which are result of merging does not display files which were included in them.
This leads to situation that if 'branch per task' approach is applied Jenkins plugin is not able to properly present modified elements in Changes chapter.
If from any reason 'cm find revision' behaviour shall be preserved than other command shall be used in Jenkins plugin (e.g. "cm diff cs:XY" and the "cm log cs:XY") as suggested on PlasticSCM forum
3 votes -
When applying a shelve, append shelve comment to pending checkin-comment
It would be very useful to have the shelve comment transferred to the comment box in the Pending Changes view. Usually the shelve comment is related to the changes made anyway so it makes for a good starting comment. It should be appended, so as not to lose any previously entered comment (that goes for the list of remembered comments, by the way).
A second-best alternative would be to add the shelve comment to the list of remembered comments...
5 votesAvailable at release 694: https://www.plasticscm.com/download/releasenotes/5.4.16.694
-
Save button in Diff view should have standard Ctrl+S keyboard shortcut
(I believe this one is already on the roadmap...)
6 votesHappily merged into https://www.plasticscm.com/download/releasenotes/5.4.16.691
-
Extend "global configuration" to cover cloaked, ignored, filetypes etc
For integration with issue trackers there is a "Global extension configuration" feature, implemented through a special repository "plastic-global-config". This could be extended as a way to offer server-global configuration of cloaked / ignored items, revision filetypes etc.
This would be an alternative to adding .conf files for all workspaces locally on each machine, under %LocalAppData%\plastic4.
(I was told this is already on the roadmap...)
3 votes -
Workspace-relative paths should work in cloaked.conf when put in LocalAppData
As it is now, to be able to cloak stuff on initial update we need to put a cloaked.conf file in "%LocalAppData%\plastic4\" on my local machine. This file is then applied to all workspaces.
However, workspace-relative rules (like "/product/install/redist") do not seem to work in this case, they only work in a cloaked.conf put inside the workspace.
This is inconvenient, since you will then need to apply a less-specific rule (like "redist") to the less-specific target of "all workspaces", running the risk of matching things you did not intend...
3 votes
- Don't see your idea?