Yes, here is the tracking issue: BM-3165

To be honest, "SCM Triggers" are in a "quasi-legacy" state, because they use the "Legacy Providers". As such, we don't list it as a feature, and we hide the button on installations without SCM Providers configured. This was done slowly over the course of two years, in various v5 versions, to gauge user reaction. So, your inquiry is good feedback. That being said, we have not yet put a lot of effort into properly redesigning this feature. The reason for this, is that the "general direction" has been moving towards post-commit hooks; i.e. triggering the build from the SCM server, once a merge request (or something?) happens. Even on dedicated CI tools, the preference is shifting towards this route. I think this is because the branching logic has been too complicated to follow (even for really advanced CI servers like Jenkins and TC). So I wonder, have you looked into post-commit hooks? Otherwise, we are definitely considering a general-purpose poll/trigger feature: basically, a poll will periodically occur, and if a condition is met, trigger some sort of event. This would be shared across multiple products, and the usecases might vary based on the product. One motivation to develop this feature is that it will allow us to really feature the "BuildMaster is from source to production" story, which is becoming more popular again. Most people didn't want that, but now the pendulum is swinging back to it, now that source code tools (like Git) are integrating (totally inadequate) build/release features. In any case, none of this is all that "immediate", but I wanted to share reasoning to you about this, and solicit your feedback. Of course, if you need to create "legacy components" we can help you do that as well. We don't plan on removing those from BUildMaster, just hiding them so no new users can access them.

Hello Josh, I agree that this would be very useful to have. I've filed IEE-8, which will allow the use of variables in block descriptions if the script contains ##AH:EvaluateStatementDescriptions at the top.

This was introduced into 5.8; so please update to the latest v5. https://inedo.com/buildmaster/5.8

I think you are a looking for a different vendor - Inedo's BuildMaster is a DevOps tool, not accounting software.

Ben, I didn't set it for any particular stage. Based on what you're saying though I think the issue was that didn't have the Listener in place when the app had completed the previous stage. I assumed the email would only go out when the Stage the approval was attached to was initiated for deployment but it sounds like it would do so when the previous stage completes, is that correct?

It's hard to say, because we don't have enough information. The "code" you shared looks like it's part of a PowerShell script, or maybe it's a cmd script, which maybe they're executing from BuildMaster? Or they could be executing the process directly? Where does $targetInstances and $targetDatabase come from? if they're just running a PowerShell script, then I guess they should just edit that powershell script as you suggested? Can you just ask for the deployment plan? Unless it's v4 or earlier, it will be in OtterScript (a text file), and once you see it, it should be fairly clear how to change it.

That doesn't seem right! So, I logged it as a bug BM-3153 We will fix it soon; you may likely be able to work-around it by adding a server by directly going to the URL. In previous versions of Buildmaster, I believe the license would have been disabled.

Sorry, you seem to have the wrong vendor :) Please contact telerik for support.

I'm not really a RegEx expert, but what you're describing should work. Without seeing the input, it's difficult to say. I use http://regexstorm.net/tester to test it every now and then, since we use the .NET RegEx engine, so it might be helpful to make a test case in there first. FYI: you can see exactly how the code uses regex, it's quite simple: https://github.com/Inedo/inedox-inedocore/blob/master/InedoCore/Common/Operations/Files/ReplaceFileTextOperation.cs Can you share something that appears to work on RegExStorm , but not in the OtterScript plan? And then share the OtterScript plan?

That's what I was afraid of. Thanks.

Yes, but we don't provide instructions or support the installation, as behavior of the Mono runtime and Postgres database engine will vary from distro to distro. That said, if you are familiar with Linux commands, you can install it as follows: https://github.com/Inedo/proget-docker/blob/master/Dockerfile If you are not familiar with Linux, you really should use WIndows edition.

Hello Andre, The version number you posted is indeed a valid SemVer2 version number. If you go to the Manage Feed page for the NuGet feed, is there an orange button near the top of the page that says Migrate? If that button is present, the feed is not marked as supporting SemVer2.

Alex, thanks. I don't want to update it via DB I am just going to be changing one and wanted to verify everyplace it's used before I made the change.

It doesn't, but I think we should add it to the Release & Package Deployment .. so I added BM-3149 So, it will come in a future maintenance release, since it's additive and seems to pose minor risk.

I think your best bet is really going to be to use Universal Packages for this. That's what they're designed for, and the operations are much easier to use for it. We very recently updated our documentation to give some guidance on this: https://inedo.com/support/documentation/proget/core-concepts/packages NuGet is designed for .NET library files to be used in developing .NET-based software. Maven is similar, but Java; you should use Maven for packaging up Java code that Java developers will use to build other JAva applications. The applications themselves should be packaged in a universal format.

It does purge the packages and logs, but the artifact files themselves are only purged by a Purge Artifacts policy. This behavior is a little confusing I think - we may change it for v6 (by adding an option). For now you can work around it by adding a purge artifacts policy too, and either creating it before the other policies (they are run in the order they are first created), or checking the option to "purge orphaned artifacts," since an artifact file would become orphaned if its associated release package has been purged from the database.

Unfortunately it's impossible to say. The error message you have provided is in complete, and doesn't give any information about the problem. Scoped packages works in testing, and we haven't heard issues from othere users about it. You'll need to do some further debugging and provide some more information for us to further help you.

Thanks for posting an update! Anecdotally, this used to happen to us "all the time" when rebooting a hypervisor server (i.e. server hosting multiple VMs) because the host/hypervisor server didn't have enough resources to give to each booting virtual machine, and SQL Server couldn't start due to low start-up resources (memory, etc). We've mostly corrected this by staggering start times and increasing VM hardware.

One common way to do this in BuildMaster v4 is to use two pipelines; a "blue" and a "green" pipeline. Another thing is to have a "Blue" and a "Green" environment, and then a pipeline like: Int > Test > Blue > Green Then, basically skip Blue or Green depending on the workflow. You can also have operation groups / action groups with predicates like "if $BlueGreen = Blue". You can certainly use the Set-Release operation (or ACtion in v4) to set configuration variables on a release.