152 results found
-
[issue] Replication does NOT replicate changed comments on history changeset
How to reproduce:
Take 1:
1. Setup replication between 2 repo(A and B) and synchronize.
2. Change the comment of one changeset in A.Expected behavior:
* A and B should be considered different for now and allow user to synchronize them through replication again.Current behavior:
* The replication view shows A and B is identical and nothing to synchronize.Take 2:
* Manually push/pull between A and BExpected behavior:
* The comment in B should be updated.Current behavior:
* The comment in B still remains the old one.1 voteWhile I understand it is not the most intuitive behavior, it works the way we expect it to do.
Let me explain: only new changesets are replicated, so whatever you changed on an older changeset that doesn’t need to be replicated, will be ignored. This is like this due to performance issues, otherwise every single replica would require to walk back all the changesets.
-
Implement integration to Flowdock
Would be great to see repository changes in inbox. Integration should be relatively easy to do as Flowdock has really easy API.
1 voteGood idea! Why don’t you take a look at this blogpost we written for Slack? (code included).
http://codicesoftware.blogspot.com/2015/01/integrating-plastic-scm-with-slack.html
I think it will be easy for you to write your own integration, and count on us to help you if you have questions! :-)
Thanks!
-
put a 'download' gitsync in gitsync page
I cannot find a download or any action that can be taken in gitsync page other than viewing what gitsync can do. The page is:
https://www.plasticscm.com/gitsync/index.html
Maybe just me that cannot find how to download gitsync?
1 voteActually GitSync is just a feature inside Plastic. Just download Plastic :-)
-
Add cm command to list deleted repositories
When using for instance compactsql it's very hard to get a list of deleted repositories (so they can be removed).
It would help if you had a cm command that takes a database filename and returns status (attached/detached).
Also re-attaching removed databases is a pain (as you cannot retrieve the name of the repository easily).
Yes I know I should notify the db admin (me too) to deleted the database right away (problem is it's easy to remove a repo but not to get it's associated table name afterwards).
Newer request than my previous:
http://plasticscm.uservoice.com/forums/15467-general/suggestions/2775133-keep-info-on-deleted-databases3 votesAs we said in the comment, deleted repos are outside the control of plastic… so there’s no good way to list them
-
Add path permission to prevent viewing of files
If you could set the visibility of files/paths in the permissions system to prevent them from being visible (checked out) by users who have been denied that permission.
1 voteNever heard back from the user :-S
-
highlighting of un-merged branches
I wanted to be able to quickly see (within the branch explorer) branches that have changesets after the last merge in the branch.
An enhancement could be to do this only for child branches of a specific branch.As I described here:
http://www.plasticscm.net/index.php?/topic/876-highlighting-un-merged-branches/page__fromsearch__133 votesThere’s a rule in branch explorer specifically created to do that :-)
-
Is it possible to view and create code review content from a command line?
It's even impossible to list all code reviews. And it's so pity :(
3 votesYou can use:
cm codereview —help
This command allows users to manage code reviews: create, edit and delete
code reviews for changesets or branches. -
Merge into
Apple's XCode has a nice feature I miss in PlasticSCM.
It allows you to merge your current branch into another (for instance /main) and after the merge switch to it.
In PlasticSCM the workflow is switch to /main and merge the other branch into the current (/main) branch.
XCode's added merge into feels a bit more natural if you're in a branch you want to close with a merge.
3 votesNo answer from the submitter :-S
-
Code review diff shows custom changes separately from merged lines
When creating a code review with files that have been merged into the branch it (sometimes) properly categorizes them as CC "Changed in merge source and destination). However, the diff does not show which lines came from the source and which were change in the destination. It would be great to have those separated out for easier code review.
12 votesAnswered. No implementation needed.
-
Support shared hosting / Remote MySQL installations
Shared Web hosts like Bluehost have Remote MySQL access but they don't give you access to opening ports like 8088 without giving them more money and upgrading to a business class. Would be nice to have a tool to support having remote databases without having to run PlasticSCM on that server (or at least making it function without requiring port 8088.)
1 voteNot a real issue but looks more like a question that was answered in the thread.
-
Allow date limited git sync
We have 4 years of history in our Plastic history. We do automated syncing to a git server for CI and analysis. Currently, every git sync goes through every checkin in the Plastic history and compares it to the git history. It would be nice to tell Plastic that the history is mostly sync'd, and to only check the last 30 days of checkins.
3 votesGitSync doesn’t walk the entire history. We asked for more data but it wasn’t provided :S
-
add a Secondary Active Directory Server Option
Most windows server programs will let you set a secondary server option, where you can add a second IP for the backup and if the first one is overloaded or completely down, it will use the backup. This is very helpful as our AD server is not only for plastic, and apparently gets overloaded often, but the backup controls all the overflow. I feel this would not be the most difficult update and would be very helpful for atleast my situation.
3 votesDidn’t receive answer from customer requesting it.
-
Global Encoding Setting
I would like to ask for a global configuration in the client for the encoding which diffs should be displayed.
For example, if you set the encoding in the settings to UTF-8, all diffs you display will have UTF-8 selected as default. Perhaps an individual option could be added for the encoding of the left and right diff panes.
3 votesYou can select a default encoding at: Preferences —> Diff and Merge —> Default encoding
-
Xlinks break when their target repository is renamed
Repository A has an xlink to repository B. Repository B is renamed to C. When downloading the content of repository A to a workspace, there is an error, because the xlink points to a repository B that is no longer accessible under that name, even though it still exists.
I know you rarely change repository name, but it happens. You can of course fix all xlinks after you do that, but you won't fix the history. So if you attempt to download a historical changeset of repo A, you won't get its whole content.
Don't you think it would be…
3 votesAs Mario pointed, we’ll close the suggestion. Maybe we can relive it in the future :-)
-
Provide Baseline DB Scripts with Install Files
Provide Baseline DB Scripts with Install Files. I didn't install Firebird and it wasn't installed for me. As a result, there was no original database following a fresh install. The result was that, when I did the backend change to a SQL Server, there were no initialized databases for the dbs repositories and rep_1.
1 voteNever heard back from this.
-
Display file version in the pending changes view
What do you think about adding an extra column to the pending changes view, to display file version? When we merge a branch into the main one, we always start the check-in comment with the exe/dll file version. We do that to be able to find historic revisions of our projects based on file version.
And if it isn't too time consuming to implement, such column would also be useful in the file history view.
0 votesDiscarded as pointed by the submitter :)
-
Stop storing information in Visual Studio Solutions
Many companies (mine included) don't store our projects and solutions within source control. There are many reasons for this, but in a nutshell, the VS formats don't play nicely when it comes to large, complex merges. Instead, we use things like Premake and CMake to generate our projects and solutions on developer machines. This is fundamentally incompatible with your VS integrations. Could there possibly be an option to store the information your tool needs in another format?
3 votesWe don’t actually store any info other than the standard stored by Visual Studio when it plugs a version control system to the project.
-
support global branch explorer colour prefs
The conditional format and changeset colours are currently per workspace. It would be nice if all my workspaces were consistent and I didn't need to configure them all manually.
11 votes -
Hide old branches
We have some very old branches, which don't fit in our current branching concept. These where created when we first started using plastic scm and didn't know how to structure them.
We do have a very clean structure for our branches - finally. In the "Branches" view all branches are displayed, no date filter is applied by default. We use the tree view, as it supports our branch structure very well. The only problem is: There are these old branches, which destroy the clean look and feel of our sturctur and also confuse some users.
It would be nice to…
3 votesJust use the permissions to hide the old branches you do not want to see anymore
-
list parent revision in item history
It doesn't seem possible to find the parent revision of an item on the command line. It would be useful if 'cm hst' listed the parent revision of each revision listed.
It would also be useful for the GUI history table to have a similar column.
3 votesQuestion answered
- Don't see your idea?