Jump to content

Search the Community

Showing results for tags 'cloud'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. Hello. We are using Plastic SCM Cloud with Unity for 1,5 years now and database size is growing up by time, although our Repository size doesn't increase at all. This happens because the database (and cloud storage) keeps multiple versions of all assets. For example we have 50+ versions of our scene assets and they are really big. And we almost never need the older versions of scenes. We no longer need the histories of most assets from 1 year ago. We currently have 600 changesets but the changesets 1 to 400 aren't required anymore. As I know there was a trim command to delete old changesets from the database, but I couldn't find any info about this in the documentation. In example, to delete all changesets from 1 to 400 and database would look like it started in changeset 401, keeping all changesets to 600. And I guess we can backup and locally keep the original database from our disk. And if we ever need a file from those early changesets, we can access it with plastic using those backups. (From this directory: C:\Program Files\PlasticSCM5\server\jet) Am I correct with these? And if there is such an operation available, whats it called? Are there some best practices on what to do with such scene files that are changed often, but old versions aren't important? What should we do to avoid them growing the database size so fast? Thank you,
  2. I'm evaluating Plastic Cloud Edition using Gluon as the front end. I've tried searching the web and forums to see if it is possible to manage access to individual cloud repositories but haven't been able to find any clear information. I'm interested specifically in the following: - Can you grant people access to specific repositories and not others? - Can access be restricted to read-only? - and if so how is this managed?
  3. Hi, In trying out Plastic Cloud, I created a repository which I no longer need. I deleted this repo yesterday, but it still shows up in my Organization's usage details. Is there another step I need to take in order to reclaim the space? I'm currently on the 5GB plan so those 400MB are actually quite substantial.
  4. Hi! I'm new to PlasticSCM and am setting up a new repository on the cloud service. I'm a developer using the PlasticSCM client proper, which is working fine... but when I set up Gluon for our artist, I'm getting weird errors. Several hundred files appear to be locked and checked out to the artist. The Check In option isn't available. And when we try Check Out, there's an error message saying "These items are exclusively checked out by [artist name]." Is there anyway to reset the checkouts on these files? Thanks, Brian
  5. Hello everyone, I'm having a bit of a bother with Plastic when it comes to creating a new local workspace. I have created a cloud repo with no issues whatsoever. When I try to create a new local workspace, Plastic tells me that the 'workspace already' exists.. but for my existing workspace and not the new one. Plastic happily creates a new local folder and the same issue occurs if I choose an already existing local source folder. I've only got a single pre-existing workspace also linked to a cloud repo. The new one has nothing to do with the existing one. Perhaps someone could advise me as to a solution? Thanks Dan.
×
×
  • Create New...