152 results found
-
Integrate with Wrike project management tool
Want to be able to select a wrike task from within the Plastic SCM to link a task to.
Would also be handy to automatically create wrike tasks when a code review is created and for it to assign the the user.
3 votesIt is possible to integrate with any issue tracking system using the API :-)
-
Permiso de borrar changeset propios
En vez de solo permitir/denegar borrar changeset, tener la opción de ser más flexibles, y permitir activar la opción de borrar los changeset propios, un usuario podría borrar sus propios changeset, pero no los de otro
3 votesYou can already do that by assigning the rmchangeset permissions to the special OWNER user.
-
Borrar una rama cuando tiene changeset
Borrar una rama cuando tiene changeset o poder seleccionar varios changeset para borrarlos de una vez
3 votesDeleting changesets is extremely dangerous, and people end up complaining they deleted what they shouldn’t :-) Not the first time it happens.
We have an option to remove csets from command line, which will probably suit your needs :-)
bcm changeset remove —help
Remove a changeset from the repository.Usage:
cm changeset remove | rmOptions:
cset_spec The target changeset to be removed. It must fulfill some specific conditions. See help for further details.Remarks:
- The target changeset must be the last in its branch. - The target changeset cannot be the parent of any other changeset. - The target changeset cannot be neither the source of a merge link nor part of an interval merge as source. - No label must be applied to the target changeset. - The target changeset must not be the root changeset (cs:0)Examples:
cm changeset rm cs:4525@myrepo@myserver cm changeset remove cs:cb11ecdb-1aa9-4f11-8698-dcab14e5885a -
Color
Ability to apply color to branches (simple but usefull tool). All of us works on separate branches and we have as well our "under dev" or task specific branches. We merge from and to only using our main branches. Colorcoding is very intuitive way to differentiate "development/beta" branches from final branches
12 votesAlready there :)
-
Analysis Tool Suggestion
Have you thought about adding analysis tools such as temporal coupling diagrams (https://youtu.be/0oDporwhToQ?t=1502) and fractal figures (https://youtu.be/0oDporwhToQ?t=1819) into your product?
1 voteNever got more feedback or answers to our questions.
-
Allow Jenkins PlasticSCM Plugin to set workspace and directory name to different values
The Jenkins PlasticSCM plugin uses the same setting for workspace name and workspace directory.
This prevents Jenkins from creating multiple workspaces on the same machine in the case below.
e.g.
c:\project-a\mywksp
c:\project-b\mywkspCurrent behaviour is for Jenkins PlasticSCM plugin to create c:\project-a\mywksp with name mywksp. Then when creating c:\project-b\mywksp will use mywksp and overwrite the first workspace.
3 votesHi RichT,
We consider this is a configuration issue, rather than a lack of functionality. The workspace name property can be edited in Jenkins to take advantage of the Jenkins build variables (such as JOB_NAME and NODE_NAME). That way you can have unique workspaces for each project or build agent. You can see this configuration in action on the Plastic SCM Jenkins plugin website: https://wiki.jenkins-ci.org/display/JENKINS/PlasticSCM+Plugin.
Thank you for your feedback!
Regards,
Miguel -
Delete all unversioned files
Basically "git clean" functionality
6 votesHi,
We’ve decided to decline this request since it can be easily performed through the ‘cm status’ command.
As detailed in our forum, you can either use PowerShell:
cm status —private —short $workspacePath | % { rm $_ }
Or one of the two bash alternatives:
cm status —private —short ${WORKSPACE_PATH} | while read FILE; do rm $FILE; done
or
cm status —private —short ${WORKSPACE_PATH} | xargs rm
We’d like to thank you for your feedback! As always, it’s really appreciated.
Regards,
Miguel -
Allow manual selection of which hunks of each file diff will be committed in pending changes view
I would like to be able to select at line level granularity, which hunks of a pending changes diff will be committed to a changeset, so that I may make different commits that split up changes along functional lines / with finer granularity. Any parts of the delta that are not committed should remain as pending changes.
This would make it easier to allow selective merging of specific parts of functionality by cherry picking at changeset level.
Coupled with some functionality to be able to split existing commits along similar lines, this would be a rather nice feature (maybe by…3 votesDuplicate of https://plasticscm.uservoice.com/forums/15467-general/suggestions/15636960-add-git-like-staging-of-parts-of-files
Please vote the original one instead :)
-
Allow branches to be deleted when they have changesets
Currently I get told I can't delete a branch "because it has revisions". I appreciate the warning, but it should allow me to say "ok, delete the revisions too" rather than cancelling the delete. Deleting each changeset manually to allow the branch to be deleted is a pain.
8 votesWe need more feedback to consider it… and it seems nobody answered it in a long time :-(
-
The cm command should be able to do anything the GUI can do
The cm command should be able to do anything the GUI can do.
As near as I can tell, cm is the api for Plastic. The api is incomplete.
This is not the case for Perforce p4 or p4api.
This is especially important for Linux where the gtkplastic GUI does not
provide the same functionality as the Windows GUI3 votesI’m sorry but we need to have specific requests.
We have a REST API and we also can automate the cm as you know. There are few things the cm can’t do (well, it can’t certainly do branch explorer).
-
cm command names should be case insensitive
cm command names should be case insensitive so that they are
more readable in scripts.E.g. getmergeneededbranches vs getMergeNeededBranches
1 voteWe try to always use lowercase, which seems to be a well-known practice.
So: not sure commands should be insensitive as you say, it wouldn’t be super-hard to implement if you really think this is one of the key things you are missing in Plastic :-)
-
1 vote
Nobody else ever asked for it, and there’s a public API to implement
https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide.shtml#WritingPlasticSCMcustomextensions -
lock files with gui
Locking certain files are that common thing to do for every project that this task should have a simple gui. Not everybody likes it to mess with config files.
1 voteNot a bad one, but nobody else asked for it in a year.
We have a plan to create a web-based admin tool, so this would go in the pack.
-
Server dropdown
Recently I have to switch between servers very often. In office it's intranet - at home a vpn. But there is just one input box which allows only a single url which is very inconvenient to use.
Much better would be to have a dropdown with all the server addresses being used.
The checkbox for "ssl" should be obsolete. You can determine if it's ssl connection from the address itself: "ssl://".
1 voteWe will review what we can do to make finding “profiles” chapter in the docu easier.
It is actually documented in the following links:
-
Provide access to the scm context menu in visual studio as a right click on the file tab
This is the same scm context menu you get when right clicking on a file in the solution explorer but means you don't have to navigate to the file to do this operation. You'd just right click on the file tab instead.
6 votesThe same menu can be accessed from the Visual Studio editor context menu, just under the file tab
-
3 votes
Not hard, but we didn’t get enough requests of this :(
-
Extend the idea of (workspacetree) to normal repos.
In the global config (special repo: plastic-global-config) one can put a "<repo>/workspacetree/" sub-directory for keeping the following files:
- ignore.conf
- cloaked.conf
- hidden_changes.conf
- writable.conf / readonly.conf
- filetypes.conf
- semanticexcluded.conf (suggested?)
This idea could be extended to normal repos! Being able to put all these .conf-files under a "workspacetree" directory in the repository (or local workspace) root would reduce the clutter and make it easier to locate these config-files.
NOTE - The semanticexcluded.conf file does not currently work in these scenarios, but there is another uservoice suggesting that it should: https://plasticscm.uservoice.com/forums/15467-general/suggestions/13439505-make-semanticexcluded-conf-file-work-from-wkspace
0 votesNo votes. Out :-)
-
Add quick merge-command "Rebase merge" (merge from parent branch)
A common operation is re-merging (rebasing) from the immediate parent branch into a child branch.
It would be convenient to have a shortcut command for this, in the Branch Explorer and the Branches view.
3 votesNot bad idea, but looks like GUI cluttering to me…
pablo
-
Do not scan files ignore list.
We have a great directory tree is added to the ignor list.
As a result of updating Pending changes lasts a very long time.
Please, do not scan files/folders ignore list.1 voteUser never replied with more info. Couldn’t reproduce.
-
Improve handling of "Merge Links"
Right now, if you get an error like this:
http://i.imgur.com/YzSTTa1.pngYou have to go to .plastic, delete plastic.merges and plastic.mergeschanges files, and then undo all the merged files from a merge link, and then try it again in hopes of it fixing itself. ( which it doesn't )
To get it to cause this error you must:
1) be on a changeset that is not up to date
2) Have 1 .exe or w/e changed
3) Have one of the latest ( newer ) changeset have the same changed .exe or w/e
4) Plastic will ask which file to keep,…3 votes
- Don't see your idea?