Ryxali

Thanks a bunch!

Heya! I'm currently researching how to do Build Automation with Plastic Cloud edition. I've started out trying to integrate it with Jenkins to build a unity game. I'm using the plugin you provided for Jenkins. For simplicity's sake I'm simply testing on my Windows desktop machine. The first issue I encountered was that it seems to look in the wrong place for the client config. It was looking in "C:\WINDOWS\system32\config\systemprofile\AppData\Local\plastic4\client.conf" while my config is in the default generated location in AppData. By copying my client config to the path it was looking in I was able to bypass this. The next issue I encountered was when I attempted to download from the cloud via Jenkins. We use an encrypted cloud, so it got stuck in an infinite loop asking for the encryption key. Is there any way to use your plugin while also providing an encryption key? Currently I've switched to testing with a local repository - and it works fine, but it would be nice to use the repo which is 100% up to date. While on the topic of Cloud & Integration, is there any way to setup hooks/polling so I can setup some responsive build automation? I've attached the Jenkins execution logs from both my failed runs. Thanks in advance! error-config.txt error-encryption.txt

Hello, Took a second look. There was a view trying to reach the removed repo. Closing it allowed us to remove the repo from cloud without the user being further affected. Thanks!

One of my coworkers encountered a strange error when attempting to update a workspace. The error stated that a completely unrealated repository couldn't be found. What had transpired was that my coworker had accidentally created a repository on the cloud named "xxxx xxxx" while attempting to access a repository named "xxxx-xxxx". The name was identical with only the '-' swapped for a space. Realizing his mistake, he then deleted the repository he had created. Then when working in another workspace connected to neither of these repositories, this error started popping up when Updating Workspace. Somehow, recreating repository "xxxx xxxx" got plastic to stop complaining. This occurs on plastic vers. 8.0.16.3177 It's a wierd bug with a wierd fix. I've attached the logs if you want to look into it. error.zip

I think it would be great to be able to optimize for storage, but I think it's also important that the history of a project remains stable. If you remove the data from a changeset, it would be impossible to switch to that changeset and view the project as it was at that point in time. Not all changesets are that useful, though, as evidenced by uploading several alterations of a photoshop document in a single day, so as long as it's done in an orderly fashion, I'm happy. Of course this means you are in single branch, right. How would this work with multiple branches? The "super changeset" can be simply a labelled one. You know, you can label changesets. So the rule would be something like: If you look in the branch explorer and view "only relevant" changesets, all the changesets that disappears I'd say are eligible for removing the data from. So all inbetween-y changesets after some point should have their data deleted can be a general rule.

A convenience suggestion. Could we get the checkout option for context menu for items listed in checkin changes? I find that Changed Items tends to reflect the items I want to checkout, so navigating the explore workspace tab becomes cumbersome in comparison.