Ah ha, ok got it! I've identified the bug, and we will fix this in [BM-2003], shipping ASAP!

Thanks; I've logged this as a bug (BM-1999), and we will fix it in the next maintenance release.

Hello; you can request a key from my.inedo.com, and then enter that in the installer. Once installed, there will be activation instructions (because the software can't auto-activate). No internet access is required to install or use BuildMaster.

BM-1997 - FIX: Transfer-Files operation can create files with \ characters on Linux Thanks very much. Works as expected :-)

The feedCleanup makes sure the files on disk and metadata files in sync. It'd be fine to run weekly or disable. There are no additional settings available, but we may add something to mitigate this in the future; it's extremely rare, and it's quite complex to handle properly.

We have identified and fixed the bug responsible for this, and will have it fixed in the next maintenance release (Otter 1.1.5). Thanks for the bug report!

I cheated and did it in SQL, been digging a little bit into your database anyways. DECLARE @DefaultRaftId INT SELECT TOP 1 @DefaultRaftId = Raft_Id FROM Rafts WHERE Raft_Name = 'Default' UPDATE [Servers] SET Raft_Id = @DefaultRaftId UPDATE [ServerRoles] SET Raft_Id = @DefaultRaftId

Thank you Alana, this makes sense. I was trying to use a NuGet feed type. This answers my question.

In case you didn't see the email, we were able to reproduce this with your repository and will be fixing this in the next maintenance release! Thanks

This is, unfortunately, a new glitch related to the call template statement in the visual editor. We'll be fixing it in next maintenance release. FWIW - we're also looking to add a "undo" mechanic that should, at the very least, allow for recovery to previous states when the visual editor creates an invalid model of a plan/OtterScript.

Aha! Thank you! I didn't realize the feed wasn't at the root, since normal 'nuget push' and 'nuget install' commands worked with just the root URL as the '-Source' parameter. Only the 'nuget restore' failed.

Thanks- we'll have both of these added in the next release, 4.1.1.

Hi Chris, If you haven't already, make sure to check out KB#1118: Legacy Plans in BuildMaster 5.0 to see how to import plans and how the concepts differ. The technique for handling this scenario would be.. foreach deployable in @DeployablesInRelease { «operation1» «operation2» «operationN» } That being said, the @DeployablesInRelease function is not available in v5.0.4, and this specific translation is not handled by the importer, which is a bug in v5.0.4. We will fix this in 5.0.5 and will ship this quite soon (by end of week).

Awesome! I downloaded and verified this is fixed in 4.1 beta.

Just a quick update -- we also fixed this in BuildMaster 5.0.4.

Thanks, we've identified this as a bug with template variable processing, and will have this fixed in the next version of Otter (coming in a day or two).

I have renamed the roles just incase, but as soon as I upgrade to 4 it appears I get knocked out of the necessary task groups. Your user account does not have the Admin_ConfigureProGet task. I also get the same message if I don't change the role names.

Please note the privilege changes in v4: Upgrade Notes for ProGet 4.0