I found the issue, just didn't think about looking at the IIS settings but that clued me in. I needed to use Windows authentication via Powershell. For those that might hit this in the future this is the piece of code that did the trick: $pwd = ConvertTo-SecureString $userPwd -AsPlainText -Force $creds = New-Object System.Management.Automation.PSCredential($userName,$pwd) $Response = Invoke-WebRequest -URI $URL -Credential $creds

thanks, yes I saw that and that is what I am using. I guess the expectation I had was to see the description or synopsis in the dialog when I am adding it a plan. Once it's in the plan is useful, the way it displays now, but it's when it's being added that the person adding it needs the info. I'll just submit a feature request, it's not a major thing just be nice for people who use them later and may not know exactly what they do without opening the full script itself or reading some other doc outside BM

By default, all you need is the name. The following operations are equivalent: Deploy-Artifact my-artifact-name; # and... Deploy-Artifact my-artifact-name ( To: $WorkingDirectory, Application: $ApplicationName, Release: $ReleaseNumber, Package: $PackageNumber, Deployable: $DeployableName, DeployAsZipFile: false, TransferAll: false, DoNotClearTarget: false, Verbose: false ); This should be mentioned in the auto-generated docs but since it is not, I'll put in a note to do that :)

Yes that is a bug then. I'll submit a bug report.

I found the solution. I had tried several different ways but finally found the right way. Just putting folder/job/jobname in the List Source made it work. The list won't auto show the job but you can type it in and it works.

Release template values are currently only used by the user interface, as a means of assisting users enter key/value pairs (variables) for a release or package. They API does not reference these, but you can pass variables into the APi quite easily.

Yes of course, smacking forehead now! Thanks!

Alana, Might I suggest updating the documentation to state that. Currently it is specified for the Upload operation but not the other two.

ah yes, sorry. I setup the creds a couple of months ago and forgot about that option. thanks.

Please disregard now. It's all working fine. Someone changed the issues I was seeing in Jira yesterday and moved them to another release, incorrectly, at about the same time I was viewing them. I got the legacy aspect figured out as well so all of future configs should be non-legacy. Thanks.

Thanks for clarifying that about the Nuget feeds. Awhile back I understood the behavior had been changed so new Nuget feeds did not function the same way. It was a discussion related to Jenkins so I may have misunderstood where the change was.

Discussion should be moved to a new post or followed here: http://inedo.com/support/questions/6554

You can use the Execute-LegacyAction Operation to do this; it inputs the XML-based configuration of the action. The easiest way to get this XML is to create a legacy plan with the desired action, then convert to OtterScript.

Oh ok, I thought it was done by you. I'll pester him about that then. Sorry about that. Thanks, Jon

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.

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

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

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

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!