It's supported using the Legacy Action, which isn't ideal obviously. This will be replaced with a function in v5/OtterScript: # reads at most 250 characters from the file set $hdarfs = $FileContents(c:\hdarfs\info.txt, 250); Log-Information $hdarfs; However, this function is only available in 5.3 (which is shipping this week).

Yep, all of these are things that people use BuildMaster for on a regular basis. Note that, the terminology you're using ("pipelines") is more generalized than the BuildMaster construct (there are Pipelines and Deployment Plans that do a mix of the things you describe), but the general idea is the same.

Alana, I knew they are in the legacy side but I couldn't find a easy way to find/use them if I'm creating a new plan but I didn't think of creating a new legacy one then converting it later (firm smack to my forehead!) Thanks!

Done... ticket #EDO-1612.... hope it helps, and thanks in advance for all your efforts and attention.

Thank you for the report, it appears to be a regression with that event listener that will be fixed in the next version. A patch is also available for download here, simply extract the zip file and execute the contained SQL file against the BuildMaster database. Note: This patch may only be used for versions of BuildMaster between v5.0.0 and v5.2.3 (inclusive) and will be already included in v5.2.4 and later.

Yes, it's posible, and that's a common workflow; there are operations to do all of these things. I would try to follow the [BuildMaster tutorials])(/support/tutorials), some of them have some workflow similar to what you're doing. The other things (like SEnd Email, Execute SQL Scripts) are just differnet types of operations you can run during a plan.

I'm migrating all our "workflows 4.9.7" to pipelines 5... then converting our legacy plans to the new plans...maybe in the future will not so often than now...but actually I have that situation almost every time, and sometimes the errors appears after 10 or 20 minutes of an execution...

This is only available as a legacy action as of 5.2.1; there is no corresponding Operation built for it yet, but we will get one going soon.

The "Generate Release Notes Action" in those release notes was referring to the same action as 4.9.7, which was not implemented in 5.0.0. The Generate Release Notes Operation for v5 plans is available as of v5.2.3.

Hello, I was not able to reproduce this. Here is what I did. Create a new PowerShell Asset... Name: Test Script Parameters: none One ambient variable: MyEnvVar ==> $EnvVar Contents : Write-Host My var is $MyEnvVar; Create a variable on MYSERVER: $EnvVar = my server var Create a new application with a deployment plan that has a single action (targeting MYSERVER) that calls Test Script Output is My var is my server var, as expected I also deleted $EnvVar from the server, and then created it on an environment the server is associated with, and it works as expected. When I deleted $EnvVar from the environments, it produced the literal output (My var is $MyEnvVar) upon running. So, my guess is there's a typo somewhere... best, Alana

It looks like this was caused by a packaging issue with installation; this impacts some upgrades and certain Linux-based querying from the web app (i.e. if you just save, and don't validate, it should work).. You can manually fix by going to the BuildMaster installation directory and: Delete the libssh2.dll file from the Web\bin directory Copy the Service\lib directory to the Web\bin directory (so Web\bin also contains the lib directory) We will of course get an updated installer built as well, but this should get things working for you until then.

Alright, v5.1.2 was released and it should be correct now :)

It looks like the Legacy Plan Importer currently does not support the ExecutionStatusPredicate and ReleaseStatusPredicate, which is throwing the error; we will fix this in a maintenace release, but as a work-around you can delete the predicate before converting.

Hi, Version number for the Windows agent shows 34.0.0.1 in add/remove programs. '#justsaying' David

Well, we are closer at least. Yes, that does appear to be a regression - fortunately all it really does is wrap the "zip" CLI tool, so as you've discovered you can work around with Exec pretty easily. Regardless, we'll be sure to have the zip operations fixed for Linux in the next update.

Aha! That's the ticket -- setting ErrorOutputLogLevel to "Warning" is just what I was looking for. For some reason I had thought the option would do the inverse (e.g. elevate warnings to errors). Thanks a ton for the help, -J

BuildMaster is licensed by users, so you can have as many servers as you'd like.

Hi, DOH! Yes, thanks, that's it. I'm blaming the person that wrote the original script I copied :-) Thanks again for your help. David

Thank you very much! The 'Imported Deployables" functionality worked like a charm :-) Regards, Francesc

Thanks for your response, Alana. Can you elaborate a little bit on the API commands you would leverage in this instance? I had considered that before, but I'd be curious to know how you'd approach this.