@atripp Thanks for the fast reply and the bypass. Best regards PhilippeC.

I finally found how to handle properly (I guess) the variable The Dockerfile looks like: ARG SOME_VAR=default_var FROM some_image:some_version WORKDIR /usr/src/app RUN .... and the Deploy script like : Git::Checkout-Code(); Docker::Build-Image ( DockerfileVariables: %(SOME_VAR:myvar), Tag: $ReleaseNumber-pre.$BuildNumber, RemoveAfterPush: true ); bur I have signing problem to push container in proget. => I start a new thread

Hi @philippe-camelio_3885 , We haven't investigated or changed this code in very many years (especially within the last year), so I wouldn't expect a changed result. Can you try the same troubleshooting steps as above? To find out where the invalid JSON is? Maybe it's comma again? FYI - we use Newtonsoft.Json for both serializing and deserializing (as you can see from error). It's really odd to be generating invalid JSON, but that's what the message is It could be related to an obscure bug, etc. We just have no idea and haven't investigated in past year. Thanks, Alana

Thanks

Thanks you Rich it is working !.

@rhessinger said in buildmaster linux docker install: sa login failures: @mcascone slope game said in buildmaster linux docker install: sa login failures: docker exec -it inedo-sql /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P 'redacted' -Q 'CREATE DATABASE [ProGet] COLLATE SQL_Latin1_General_CP1_CI_AS' Hi @mcascone, This line has the issue. You created a database named [ProGet] instead of a database name [BuildMaster] as you stated in the connection string on the third command. Thanks, Rich Thank you very much for the explanation. It works now.

@ashah_4271 can you share your OtterScript? and show specifically what you'd like to do? Happy to help if we can!

@rhessinger Thanks a lot. I will try it.

In my opinion, using $ApplicationName is not possible, at least for Gitlab Indeed from GitLab ref, we read : The URL a badge points to, as well as the image URL, can contain placeholders which will be evaluated when displaying the badge. The following placeholders are available: * %{project_path}: Path of a project including the parent groups * %{project_id}: Database ID associated with a project * %{default_branch}: Default branch name configured for a project’s repository * %{commit_sha}: ID of the most recent commit to the default branch of a project’s repository As %{project_path} is different from $ApplicationName if the project is defined in a group, the only link between the gitlab project and the builmaster application is the commit_sha var. I think you just need to add stage as querystring and make the search for the result of the pipeline named stage for which exists an active build variable ($commitId in my example) with a value of commit_sha. and $commitId has to be unique over all BuidMaster. Actually, it is not possible to get more variables (ideally %{project_path} at the GitLab::Get-source step. The filter would be then better (Filter for project_path+ commitid + stage), but this is still a build variable and not an implicit variable like $ApplicationName I don't know if there a better way because I have just started to use Gitlab.

@atripp Thanks

@atripp Thank you Just one small quesiton: When do you plan to make the UPack raft available for both BuildMaster and Otter ?

Hello @atripp You were right. In Otter Define the agent's temp directory as it should be by default /tmp/otter. In BuildMaster Force a sync Infrastructure The pb is gone I will now implant my ansible function on buildMaster Best Regards PhilippeC.

@rhessinger Good news thank you

We don't have a bug bounty program, but please submit a ticket if you find anything and we will immediately address it.

Warn will still automatically advance. I was able to utilize the Set-ReleaseVariable as you suggested. Thanks!

Nice password ;) Did you try restarting the agent service? (inedo.agent.exe)? I looked again (feel free to request access as well), and compared this against the messaging protocol that we use. The error is happening during the handshake. Now I'm starting to think that Otter isn't actually connecting to the Inedo Agent... but that other thing is sending back a different response? Normally the other thing would just disconnect, but I guess maybe not? Anyways Wireshark should tell you... Here's the full handshake, where you can see that Otter assumes the first byte received is a valid encryption mode (0,1,2). internal async Task SendHandshakeAsync(AgentEndpoint endpoint) { if (this.disposed) throw new ObjectDisposedException(nameof(ServerConnection)); var buffer = new MemoryStream(); var writer = new BinaryWriter(buffer); writer.Write(ProtocolGuid.ToByteArray()); writer.Write(AgentProtocolVerisons.Agent1); writer.Write(AgentProtocolVerisons.Agent2); try { var initialIV = new byte[16]; using (var cts = new CancellationTokenSource(30 * 1000)) { await this.Stream.WriteAsync(buffer.GetBuffer(), 0, (int)buffer.Length, cts.Token).ConfigureAwait(false); await this.Stream.FlushAsync(cts.Token).ConfigureAwait(false); var mode = (AgentEncryptionMode)this.Stream.ReadByte(); if (mode == AgentEncryptionMode.Ssl) { var stream = new SslStream(this.Stream, false); try { await stream.AuthenticateAsClientAsync(endpoint.HostName).ConfigureAwait(false); } catch (Exception ex) { throw new AgentConnectionException(AgentConnectionError.BadCertificate, ex.Message, ex); } this.Stream = stream; } else if (mode == AgentEncryptionMode.Aes) { if (endpoint.EncryptionKey == null) throw new AgentConnectionException(AgentConnectionError.BadEncryptionKey, "The server requires an encryption key, but a key has not been configured."); int count = await this.Stream.ReadBlockAsync(initialIV, 0, 16).ConfigureAwait(false); if (count != 16) throw new AgentConnectionException(AgentConnectionError.BadHandshake); this.messageFormatter = new MessageFormatter.AesMessageFormatter(endpoint.EncryptionKey, initialIV); } else if (mode != AgentEncryptionMode.None) { throw new AgentConnectionException(AgentConnectionError.BadHandshake, "The server requires an encryption mode that is not supported by this client."); }

Hi Tigran, We currently do not support pytest but will take this into advisement and treat this ticket as a feature request Thanks, Jason

Hi David, It appears that only the start of a statement block shows in the execution log.. # Visible in execution log # This is not bisible in execution log { } # Visible in execution log # This is not visible in execution log { # This is not visible in execution log } # not showing in execution log Let me know if you have any specific examples that aren't working as expected. Here is the full documentation for OtterScript comments https://inedo.com/support/documentation/executionengine/otterscript/comments-and-descriptions Thanks, Jason