koobas.hobune.stream
Asset Server: Deleting a Commit
Is there a way to delete a commit in the Asset Server? Because No one in my office now has the ability to update due to a large commit that seems to be "Compiling Scripts" as it updates and ends up crashing the computers. We've tried Updating multiple times on the same computer with no results. Is there a way to remove this update? This is a big problem for us.
If you go on server and the update tab, you can right click and DISCARD. But I'm not sure about what it does...
It would be better to contact the Unity Support in this case, than the user base. But as far as I've seen in the Unity Trial, there is no way to delete commits. Actually I can't remember one single versioning system which has delete option. You typically "undo" change by commiting an old revision.
i.e. if you had revision 1234, then push 1235 which is wrong or broke something you typically checkout 1234 and commit it as 1236. That's how every version software works I've seen and I don't see a reason why Asset Server should be an exception.
Deleting commits from version software would lead to a lose of integrity, so it's not desirable. Imagine you push 1234, then 1235. Then someone downloads 1235 on his PC. Now you delete the 1235 version and push a new commit, which also gets 1235. If the other guy gets an checkout, he shouldn't get anything because he already has 1235 and when then when someone pushs 1236 you would merge the 1236 changes with your old 1235 (the one who got deleted) and if you commit this, you're in pretty big trouble, because you destroyed the integrity and pushed the old, bugged (and deleted) commit again into the system.
It's incredibly easy to remove a commit with git, and fairly easy with SVN. I don't know what source control you have been using... I need this functionality due to a bad commit breaking everything, and no way of undoing it. By bad commit I mean the asset server breaking for no reason.
I would imagine in that example, if the version created is 1235 after the previous 1235 would of been deleted that, they would definitely pose big problems. But I'd imagine that the software ought to keep count of the revisions and create 1236 instead.
I vaguely remember perforce and svn may have allowed us to remove commits from the server as an admin. But I think I may be completely and utterly wrong 8 r and be a different feature altogether. So you could be right and no other source control would even need this feature, if updates were flawless. But since unity tends to do various things other than just straight download, (very very rarely) sometimes updates may not work. And I'm thinking you're right and only unity support may solve this. Unless we find a work-around, which we may be able to find. But if anything, Unity may in fact need this feature, or a feature that would aleviate failed updates.
Well, SVN have a revert to revision function, but it's basically the same as if you check out 1234 and commit it as 1236 in aboves case. The stuff you added with 1235 will still remain on the version server and can be obtained when you checkout 1235. But if you previously had 1234 then go to 1236, nothing will be changed (other than the last checkout revision)
Make a backup copy.
Install pgAdmin III 1.10 (latest version wont work since it no longer supports Asset Server's Psql 8.3.7)
Using pgAdmin configure and connect to your Asset Server's database (port 10733)
Tables you're looking for are located in /Databases//Schemas/public/tables/
