Yes, definitely; BuildMaster supports any type of file, such as Java .properties as well. You could set up with a simple replacement syntax, or just have a separate .ini instance file for each environment.

This will be added as an Operation in the next release; look for [BM-2218]. IUn the mean time, the legacy action is a good work-around.

It's scheduled for release later today. in the mean time, you can use PowerShell or not set that particular property that requires a timespan.

In v5.4, we will have a "Custom Setter" for template variables which would allow for this scenario. Our primary use case is to allow for a searchable list of packages from ProGet, or builds from teamCity/Jenkins/etc to be populated.

This does involve a bit of refactoring... but we should be able to get this into 5.6, shipping on the 18th.

This isn't currently supported, but we can add an endpoint for that. Sounds like it would fit in the Package Deployment API (see roadmap). Of course, we can always ship these in earlier maintence releases, they just won't be documented and may change before final releases.

Please ignore this question. It works now.

Yes, that would do it; the $WorkingDirectory() function will always ends return a slash. So, you'll want to definitely trim it; you can do this with a $PSEval, but we will have built-ins soon - https://github.com/Inedo/inedox-inedocore/issues/9

David, great to hear! Aris, would you mind opening a new thread, or submitting a ticket (maybe easier to back and forth on email); I think I understand what you're suggesting. We'll definitely have to re-engineer something to support this sort of usecase, so any more details on how it should behave (from the UI, pipeline JSON, etc) would be helpful!

Thanks; I can see the issue, it appears if the environment is the same, then this may occur, depending on which one fails first. We will investigate.

Thanks for the quick response. Yes, sooner would be great. I will start using the new feature as soon as you can release it, with or without documentation.

If I use this string it returns me: System.ArgumentException: 'server' is not a connection attribute valid. What should I use instead?

Check out KB#1039 - The Inedo Agent and Legacy BuildMaster Agents for more information on this.

That's generally the idea of the arguments: those are the required variables. template MyTemplate<$var1,$var2,$var3> { ... } It's generally a good practice to use these instead of external or configuration variables. But you can always use the $IsVariableDefined function as well. if !$IsVariableDefined(my_var_name) { error; }

ignore my previous post. I had modified a second action and had left the first one with spaces, the semi-colons worked fine. Thanks

Yes I do see it there. I think the message on the key generation page implies that the key should be visible immediately after generating the key and is perhaps misleading. Thanks for the info.

You are not going wrong :) Support for XSL as the template and data as the instance will be added in v5.3.4 as a separate template type so it doesn't break existing deployments. We'll release this within the next day or so.

Just a heads up, that we've updated the docs with our proposed specifications, always open to feedback! Formal Grammar Formal Specification Strings and Literals We don't have an ETA; the changes aren't really that difficult, but once we implement them we're stuck with them.

Alana, thanks. Just getting into using the script and didn't realize I could create a var with no value like that. Thanks!

I actually am at fault for not being thorough here; I jumped in without being diligent. I am not using Integrated, but using LDAP provider via forms in Buildmaster and it was this that was failing. My apologies! Our custom OAUTH API gateway validates against ADFS prior to providing tokens, think of it as a custom Oauth2 token provider to provide SSO with Windows Auth. The whys and hows can be discussed offline if you want, though there are a few sites which explain this and the reasonings. This custom OAUTH Api/gateway worked at the time of Buildmaster not working. Hence my confusion about why one was working and not the other. With that said, I will still continue to monitor. I will assume this was a "fluke" on the system side that is not worth troubleshooting.