jwvanderbeck

This is happening again!

Also to clarify here, yes I have it working but it doesn't explain why the original query didn't work. Seems like there is a bug in how the query works, or I specified it wrong. Some clarity there would be appreciate.

Yes, working, except for the issue of having to refresh the entire branch explorer view every time an attribute is added/changed/removed.

The idea is to track the windows AND mac build # on Unity Cloud Build so both attributes are needed. Wanting to check if either value is present is just a way to see if either build was done without having to have a third flag attribute. Thanks for pointing out the "hidden" button though for seeing previous values. I was going to suggest the ability to preset values to choose form so human errors don't occur. Not sure why that button is LITERALLY hidden as it is super useful!

Yeah the problem I have with attributes, or the Jira properties panel, is the same. You have to click on the branch or changeset to see that information. Where as things like Labels, Colors, and Branch Names you can see ALL of them at once, at a glance, without having to click on any of them.

Same user, same system. I don't know about the first panel asking for user login credentials, but the second one asking to make a workspace is the one I discovered I could cancel, which would exit Plastic, but then restart it and I would be resumed back into my normal settings which is how I know the setting FILES are still there.

I know this is kind of against the "best practice" as seen in the blogs, but I find it a bit odd that I don't have the option to do this. Knowing if a task is a bug fix, versus new feature, versus changes to existing features, is information I find very useful when it comes to integration ahead of a build as well as building release notes. I've been looking into the more advanced features of Plastic such as attributes and conditional formatting to try and better visualize my branch information but I'm still struggling with the best way to have this information readily available at a glance. I essentially have two different pieces of information that I want to visualize for a BRANCH and no easy way that I can see to do it with the tools available. For a given branch I want to know 1) What is its status? In progress, Review and Merge, or Done and 2) What type of task was this work? Bug fix, new feature, or changed feature. The problem is coloring the branch only lets me visualize one piece of information. Anything else I have to click on the branch and open its attributes. While this isn't the end of the world, it does mean I can't just look at the big picture and get an overview. However, if I could change the branch prefix to be representative of the task type, that would give me two pieces of information in an overview. Now, all that said, if there is a better way to manage this please let me know. I'm open to suggestions.

To follow on with this, it also doesn't appear that these are "dynamic". In otherwords, once a changeset has a color assigned, changing its attributes won't give it a new color if the changes would result in a new color being assigned. To get the new color I have to disable one of the rules, then re-enable it, which will then make the "Apply" button active again. Then clicking in Apply will update the colors. It would be really nice if these were more dynamic, so that changing an attribute automatically refreshes the colors. If this is not doable, can we at least have a button to easily refresh rather than dancing with the formatting rules? EDIT: Just realized I can refresh the Branch Explorer view to update. Still it would be nice if changing a branch or changeset's attributes would just refresh the formatting for that item rather than having to wait for the entire view to be recalculated.

I'm still trying to find the best workflow here so suggestions are welcome, but here is where I am now. When we want to do a build, using Unity Cloud Build, then we will GitSync the branch to Gitlab which in turn connects to UCB and does a build for Mac and Windows. Previously I would then add a Label to the changeset indicating the build # on UCB to keep a connection there. This was ok but got a bit cluttered when we added Mac builds, so now two labels, and possibly more in the future. So instead I decided to move to putting the build #s in attributes instead. This works fine but there is no clear way to tell a changeset was sent to UCB. So what I tried to do was add a custom changeset color something like this: attribute='Windows Alpha Build' or attribute='MacAlpha Build' I don't care what value the attribute has, just asking if it has either of these attributes, color it. Doesn't work though. Is there a way to do this? For now I've added a third attribute that I just set to "yes" when a build was sent, but this feels clumsy and the fact that an attribute HAS to have a value makes it a little more clumsy. EDIT: Ok I got this working. Seems I think a bug in how the conditional formatting is set parsed. After posting this I saw that I had a typo in the second attribute, where it was put as 'MacAlpha Build' when it should have been 'Mac Alpha Build'. When I fixed the missing space suddenly the coloring worked. However, as that is an OR condition, it seems it shoudl have worked even with the typo which makes me suspect my conditional isn't working the way I expect.

Actually to clarify a bit here, the ACTUAL settings don't appear to be lost. In other words the configuration files in appdata/local/plastic4 are intact. But when the PlastkicGUI starts up after an update it seems to ignore those and make me go through the new user wizard again. First asking for the login credentials, and then asking me to set up a workspace. When what it should be doing is just launching straight into the app using the previous settings.

Bear in mind I'm coming from a Git background so it might be we should change our way of thinking, but it is currently as such. Tasks are done in branches off develop (eg /master/developer/scm10), and this lets us do integration in /master/develop. Alpha (and probably beta) releases can can then be cut from /master/develop by doing a GitSync which then kicks off a Unity Cloud Build. Then, certain alpha/beta builds will be "promoted" to the /main branch as full releases. So for us /main/develop is sort of like a fast ring, and /main a slow ring. This works well with Unity Cloud Build as well because I can have different build configurations for /master and /master/develop so for example all builds coming from /master/develop are build as development builds with extra debugging, whereas those coming from /master are not. Right now we are just starting the project and in early prototyping, so all builds are getting integerated back to /master/develop and built as alpha builds. The red is /master and the blue is /master/develop

Windows 10. I can't think of anything special about my setup.

I changed nothing. I just went to bed and it worked in the morning. Well I did close the Plastic GUI when I went to bed and re-opened it in the morning.

I'm still evaluating Plastic. Been only I think two weeks so far and in that time 3 or 4 new versions of Plastic have been released. And each time I update all my settings are lost! First I thought it was a fluke, but then it just keeps happening and it did it again just now. After installing the new version and starting Plastic GUI on Windows it is now asking for all my login information again. I put my cloud credentials in, and then it gives me the wizard to set up a new workspace. WHY!? Why can't an upgrade just leave things alone? Oh an even better after pointing it to my existing workspace thinking it would just reconnect, it instead errors saying workspace already exists. Seriously. I like what I've seen mostly of Plastic but I'm now essentially unable to continue working. This is just unacceptable. I need source control I can rely on EDIT OK after struggling with that Workspace screen I just killed the app and restarted it and this time it reconnected to my existing workspace. I'm glad I tried that rather than wringing my hands all night long and getting no work done. You guys seriously need to improve the update process.

Is this new system hardcoded to consider main the trunk? All our development at this time pretty much treats develop as the trunk until later in the product cycle.

Ok somehow in this process I completely broke something, and the only error that pops up in the GUI is a blank box with the words PlasticSCM. Not very helpful I THINK I finally fixed it, at least the error went away. The problem is referencing the DLL in the client.conf file. The instructions aren't very good here as they seem geared towards Linux where Mac is different. Best I can tell from browsing around, the jirextension.dll is located in /Applications/PlasticSCM.app/Contents/MonoBundle/extensions/jira/jiraextension.dll After setting that the error went away so I think its working. However in the branch explorer I don't see any way to view jira issue properties like I do on Windows. EDIT: Ok it is working because I can when I go to create a new branch it does show the issues list from Jira as expected. So I guess I just don't know how to view the Jira properties from the Branch Explorer like in Windows. Overall those docs could really be improved for the Mac side, as it isn't really the same as Linux. And the GUI is completely different from Windows so some docs there on how to find the same features would be nice.

It is just me, and the changeset was even created on this very computer earlier in the day. I have not enabled encryption, so unless it was enabled by default ot strangely enabled itself, that should not be a problem. Looking through the UI right now I don't even see where that would be enabled. In any case that was last night and this morning it appears to be working again. Which is good but disconcerting. Most likely it was a problem on the cloud server which concerns me a bit given we appear to be on different time zones, so if something like that was blocking my work I would be stuck.

Suddenly I am unable to review any diffs with cloud changesets. I am still able to push and pull changes and create branches just fine (or at least without error. I hope there isn't some subtle issue I'm not seeing!) but if I try to view diffs on changes, I get an error similar to the following: "Cannot download revision 29141 from server. Data cannot read/write to Plastic Cloud. There was an authentication issue. Your local date (client or server) is probably wrong. Change it to fix the issue" My local computer's date and time is correct.

Oh my bad!

I just work directly with the cloud rather than a local server and syncing. Seems much simpler to me, but I know it depends on your workflow and preferences.

Those instructions indicate to make a file in a location containing the server name, but my Jira server is the cloud Jira and I can't put a web address into a directory name.

I can get that to you in about 8 hours. I left most of the settings as default, only setting the server address and user information. Seems odd that it works after I first start the client, and then again after "refreshing" the connection with the Test button, but then stops in between.

I have Jira integration setup in my client on Windows, but on mac I don't see any options for integrations at all. Are integrations not available on Mac?

Any update on this? It is pretty infuriating to be honest.

Yeah I do mark the branch as open, but have to assign the user manually.