Posts made by Anthony

Ok @atripp, thanks for getting back to me. I'll see if I can include the deployment ID and return code as key-value pairs in the build instead.

Have a nice day,
Anthony.

Hi @atripp,

Thank you for your reply.
Using variables for custom properties seems like the logical approach, but the issue is that I cannot set a variable at the deployment level, hence my previous question about the deploymentinfo object.
For instance, the 'Set build variable' operation targets the build itself. Since a single build can involve multiple stages and several deployments, a build-level variable cannot represent a unique deployment execution. Any value set there would be overwritten or shared across all deployments of that build.
My goal is to store a specific value during the execution so the client triggering the deployment can read it back and verify if it completed successfully.
Is there a way to define Deployment-specific variables or Output parameters that persist only for a single execution? I would appreciate any alternative suggestions you might have.

Have a nice day,
Anthony.

Hello to the community.

We use Buildmaster 7.0.23 to enable our customer to deploy artifacts.
The basic flow of a deployment looks like this: An Otterscript is triggered -> SHCall is invoked -> An in-house deployment tool is invoked.
The in-house tool returns a status code, and the SHCall in turn returns this status code to the Otterscript, which then is well known on its level.
The requirement is that this return code be returned to the client. The latter is making the deployment via the /api/releases/builds/deploy API (by submitting: applicationName, releaseNumber, buildNumber, toStage)
The client then checks the status of the deployment by calling /api/releases/builds/deployments, and obtains a DeploymentInfo object as documented in this page : https://docs.inedo.com/docs/buildmaster/reference/api/release-and-build#deploymentinfo-object.
In terms of deployment status, this object doesn’t contain much: just the “status” property, which can only take the values “pending”, “executing”, “succeeded”, ‘warned’, or “failed”.
In the Otterscript, I can control this value, at least between “succeeded,” “warned,” and “failed.” For example, by checking the return code and selecting one of these three values based on the return code.
But that’s not enough, I need to be able to give the client the possibility to get the returned code from the in-house deployment tool, which is known by the Otterscript.
This return code should be scoped at the deployment level.
How can I do this? Is there a way to modify the deploymentinfo object in OtterScript to add custom properties, such as a return code or any other useful information for the client ?

Thank you in advance for your help.
Anthony.

Hello Inedo, the community, everyone,

One of our scripts is running into an issue in buildmaster.
This script is involved in a deployment pipeline that has been used with success for a long time.

Basically, it consists in an Otterscript dealing with a build variable by sending it as an argument to a subsequent Shell script invoked with SHCall.

When this argument exceeds 34632 characters, or when multiple passed arguments exceed together 34632 characters, the execution fails with :

Unable to send channel request
Unhandled exception: Inedo.Agents.Ssh.SshException: Unable to send channel request
   at Inedo.Agents.Ssh.Libssh2.Libssh2Session.HandleError(Int32 res, IntPtr sftp)
   at Inedo.Agents.Ssh.Libssh2.Libssh2Session.WithSocketAsync[T](Func`1 run, Func`2 getError, IntPtr sftp, CancellationToken cancellationToken)
   at Inedo.Agents.Ssh.SshProcess.StartInternalAsync(CancellationToken cancellationToken)
   at Inedo.Agents.Ssh.SshProcess.StartInternalAsync(CancellationToken cancellationToken)
   at Inedo.Extensions.Scripting.Operations.Shell.SHUtil.ExecuteShellScriptAsync(IShellOperation operation, ShellStartInfo startInfo, IOperationExecutionContext context) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E573257\Src\Scripting\InedoExtension\Operations\Shell\SHUtil.cs:line 264
   at Inedo.Extensions.Scripting.Operations.Shell.SHUtil.ExecuteShellScriptAhAsync[TOperation](TOperation operation, IOperationExecutionContext context, String execMode) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E573257\Src\Scripting\InedoExtension\Operations\Shell\SHUtil.cs:line 389
   at Inedo.Extensions.Scripting.Operations.Shell.SHCallOperation.ExecuteAsync(IOperationExecutionContext context) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E573257\Src\Scripting\InedoExtension\Operations\Shell\SHCallOperation.cs:line 81
   at Inedo.BuildMaster.Windows.ServiceApplication.Executions.PlanExecuter.OtterScriptExecuter.Inedo.ExecutionEngine.Executer.IExecutionHostEnvironment.ExecuteActionAsync(ActionStatement actionStatement, IExecuterContext context) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E574178\Src\BuildMasterSolution\BuildMaster.Service\Executions\PlanExecuter\OtterScriptExecuter.cs:line 350

The pipeline looks like :

{
  "Name": "pipeline",
  "Stages": [
    {
      "Name": "test",
      "Targets": [
        {
          "ScriptId": "global::OtterScript",
          "EnvironmentName": "test",
          "ServerNames": [
            "server"
          ],
  [...]

The server which the Shell script is submitted on is Linux like and the used credentials are SSHKeyPair.
I suspect that some SSH agent is implemented by Buildmaster.

The Otterscript looks like :

##AH:UseTextMode

set $arg="<more than 34632 characters>";
# Test Otterscript
{   
        {
        # # SHcall
            {
                SHCall Test_SSH
                (
                Arguments: $arg,

Our instance runs Buildmaster 7.0.23 but I am able to reproduce the issue in Buildmaster 2024.8

Could you please help ?

Thank you.

Thank you for the clarification @dean-houston

Hello team!

From Buildmaster Version 7.0.23, I noticed the entries of access logs associated with api keys usage are limited to 1001 rows in the database.
Are there any settings to customize this limit or do you have any suggestion to increase this ?

Thank you.