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

@Srinidhi-Patwari_0272 here is the api for healthcheck: https://docs.inedo.com/docs/proget-reference-api-health the url would be /health

Hi @paul_6112 , That's really peculiar; what must be happening is that PowerShell is returning multiple results, so the variable is automatically being being created as a list: https://github.com/Inedo/inedox-scripting/blob/master/Scripting/InedoExtension/Functions/PsEvalVariableFunction.cs#L52 Digging further, it's like related to some issue with value detection/conversion: https://github.com/Inedo/inedox-scripting/blob/master/Scripting/InedoExtension/PowerShell/PSUtil.cs#L205 Unfortunately it's a bit of rabbit hole from here; it's just as likely a bug in .NET6 powershell libraries as it is our code. But hopefully you can play around and find a work around? I'm at a loss, and we're pretty heads-down in ProGet 2024 planning at the moment, so hard to find the likely half-a-day to explore this further. I'll add this to our BuildMaster 2024 roadmap, but if anyone else experiences this (or we get a ticket) we'll investigate it further. Cheers, Alana

@dima-tinte_1260 @rob-leadbeater_2457 @sdohle_3924 Debian (Apt) Connectors are here! Check out this blog article to learn more: https://blog.inedo.com/inedo/new-debian-feeds/

@shfunke_1795 @jrottmann_6111 @sdohle_3924 @bahues_9728 @appplat_4310 Thanks for insight into this! I'm happy to report that starting in ProGet 2023.22, you can create Alpine (APK) feeds with connectors :)

Hi Alana, Well.... technically none of your software is supported since you are a free user https://inedo.com/buildmaster/pricing [image: 1699460452895-62c1fb23-5230-49bf-b126-880475ae9bd3-image.png] I'm currently getting my money's worth on this forum after an upgrade to v2023 Thanks, Paul

Hi Rich, Brilliant, thank you for the update. Regards, Paul

Hi Rich, Super, thank you. Regards, Paul

Hi @paul_6112 , we could definitely be more consistent here. The listing is generally called "Deployments & Executions" , which we shorten to "Deploys". I'll make a note in our roadmap to review this!

Hi @paul_6112 thanks for the report -- this is a known issue/regression in our internal UI library with focus- it only impacts a very few number of pages, but it's on our list to eventually address

@paul_6112 said in Do you plan to upgrade JQuery in a future ProGet release?: This was picked up by nessus on BuildMaster v7 Lol wow - that's ridiculous As I mentioned before, it's a forked library thus not vulnerable. So I suppose you can continue reporting it as a "false positive" to whoever seems to care, and perhaps we'll also just edit the version number out to appease that the security tool

@atripp Thanks

Have you had any success deleting these after retagging? We haven't been able to reproduce this so far.

what if we try it on a sub website i mean a subdomain? it will work or not?

Hi @A-Schoder_7166 , It sounds like your installation is somehow corrupt?? I can't imagine what would cause that error but it's basically saying that the upack.json file within the extension file (xxx.upack) is corrupt. Maybe some antivirus tool went and "quarantined" zip files on disk that contained executable code? Really hard to guess. The file sare loaded , typically in c:\Program Files\ProGet\Extensions, and they are part of the installation. I would uninstall and reinstall, and hopefully that will fix the issue. Thanks, Alana

Thank you for your help! I am hoping that this is enough to lock down nuget restores: API Keys for Pulling/Listing Packages Most clients will not send the API key for operations like listing or pulling packages. In this case, ProGet will issue an authentication challenge, and the client will respond by prompting for a username and password. In this case, you can supply api for the username, and your API key for the password. I'll test that.

Hi @devopsdude3113, What scopes do you have configured for your personal access token? When I tested this, I created a personal access token and added only the read:packages scope. Also, do you see any error in your ProGet diagnostic center? Thanks, Rich

Hi @rhessinger Pb solved, Thanks for your fast correction

Hi @jw , Thanks for reporting these! We'll get the fixed in hopefully the next upcoming maintenance release via PG-2520 and PG-2521 Cheers, Alana

Hi @gunmaden, Thanks for reporting this! I've filed it for investigation as PG-2519.