Topics created by philippe.camelio_3885

@rhessinger

Hi @stevedennis I was just looking to configure Proget as good as possible. This part was a little bit fogus for me I thought this was a bug ... Thanks for your reply Best regards PhilippeC.

@dean-houston About the missing files (FileNotFoundException), I made a mistake in my docker-compose file, so the packages volume wasn't persistent. Noob error , sorry about that. Best regards PhilippeC.

Hi Dean Thanks for your reply. It was just a question, finally useless. And Thanks you for your time Best regards Philippe

@dean-houston

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 @rhessinger Pb solved, Thanks for your fast correction

@gdivis Thank you

I added this to our Otter 2023 list of items to review/consider :) Please stay tuned

@philippe-camelio_3885 oh wow, great find. Hmmm..... so I guess that must be some kind of UI bug with not trimming the newlines variable.ListValues = variable.Type == VariableTemplateType.List ? txtListValues.Value?.Split(new[] { Environment.NewLine }, StringSplitOptions.RemoveEmptyEntries) : null; I'm sure this should be fixed eleswhere too, but for now I'll just add | StringSplitOptions.TrimEntries and I guess that will at least fix the UI bug

@atripp said in BM - Help needed for Git checkout: shexec echo hello world; I have no issue to run a shexec. This is just the git-checkout. The server is also configured thru Otter without any problems ... I am using artifact captured from localhost so it is OK for me I will make other tests later

@atripp Good to know Thanks

@apxltd I'll wait for v2024

Hi @atripp Oups, After your reply, I checked the ssh config on the target server and I forgot I allowed ssh root connection only from the Otter / BM server. Match Address XXX.XXX.XXX.XXX PermitRootLogin prohibit-password Changing the address solved the error My bad Thank you for your time

Hi @philippe-camelio_3885, Good catch! I created a ticket, OT-494, to track the fix. We should have this released in the next two versions of Otter (2022.12 or 2022.13). Thanks, Rich

Hi @atripp Thanks for the tips. Best regards Philippe

Hi @philippe-camelio_3885 , thanks for reproting this; definitely looks like a regression of some kind. We'll get it fixed ASAP via BM-3860 -- but sounds like you found a temporary work-around for now :)

@apxltd said in OT - SSH Secure Credentials Private Key ed25519: Thanks for clarifying @philippe-camelio_3885. I see the issue in the code now. I think it's been this way for quite a while Thanks for your reply

I thought I was wrong