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

Hi Luke, you'll want to put the connection string in quotes: bmdbupdate UPDATE /conn="Data Source=DB1;Initial Catalog=ProGet;Integrated Security=SSPI;User ID=Account;Password=Password;" We'll try to add that to a new version of the database updater! Cheers!

This isn't specific to ProGet at all, but HTTPS/SSL in general. It's not possible to bypass or address this from the server software (ProGet) side at all. You'll need to either trust the self-signed certificate on the client (Jenkins), install a certificate from a trusted root (server), or bypass that warning in the client (Jenkins).

We'll be fixing some of the bugs in the visual editor with regards to template arguments in a future maintenance release (hopefully 1.1.3); we've already made the changes in BuildMaster v5's editor, just need to bring them over.

What do you think of something like this? Of course it's not implemented, but just an idea... if $IsCollectRun || !$IsAutomaticallyTriggered { Ensure-Something-That-Requires-Reboot(); } So this way, the block would run during the collection run of the plan (which is where drift is detected/reported), and would only run if the job is manually triggered.

I'm afraid the Ensure operations are a bit trickier to write, mostly because they require the definition of a configuration template... The EnsureOperation<TConfig> class is designed to help make it simpler to write these... but we don't have a tutorial for those just yet. In the mean time, I've emailed you the source code of all of the built-in Operations and Configurations, so I hope that might be of some assistance.

It sounds like ProGet is working fine, but that the CHOCOLATEGUI doesn't support Windows Integrated Authentication. I would submit a ticket/bug request on their github and ask them to support it. It's generally a relatively easy change to make, depending on how they implemented querying.