Hi Christopher, I am not able to recreate this issue locally, can you confirm that your license key is valid, current, and activated. It looks like you were issued a new license key last month 4/16/2019 for ProGet Basic. An invalid or expired key will force the retention policy to execute in dry-run mode so I want to rule that out first. Thanks, Jason

That is great news! feel free to reach out if you have any other issues.

The error message you are getting (There must be exactly one package.) is essentially saying the file that you are trying to push doesn't exist. And since I can see that the file is created in the previous pack command, My thought is that file creation is not fully complete or the file is still in use by the pack command. I am thinking it might be useful to add a Start-Sleep -s 5 command between the pack and push commands.

I'm sorry for the difficulty; I can't say I've ever heard of "the server crashes and the only option to recover is to reinstall", but I'm thinking it's something unrelated. All that page does is change a setting in the database that instructs the connector code reads to determine how to configure the proxy. Instead of re-installing, can you investigate the windows event logs and see what errors are happening? Can you give more details about "only option to recover" means? I'm guessing the service crashes, but you can simply start up the service or reboot if that happens.

I would try to reboot the server; sometimes the windows service manager caches information that makes it hard to detect. Next, it could be that you don't have permission to view the service. You can use a tool like sc.exe to unregister the service. Then, it should work

Thank you very much for your precision. I realy appreciate it. I personaly work with non conterize Postgres database in order to avoid data corruption issue; but I understand your make this decision. Hava a good day, Mathieu HOFERT

You are right, the PipelinestageName Variable is correctly set at the build level.. But, it is assigned with the last Pipeline used and it is a little confusing for what I am looking for (for each pipeline step correspond a DB string) Never mind, I will make the DB connection by hand Thank you for the spending time

Hi Vijay, please refer to this documentation to better understand file masks in our tools. hope this helps! Thanks, Jason

Didn't get the answer quite right the first time. The error occurs if the version is postfixed with som text. In my case, I postfixed the branch name to the version number - e.g. 1.0.0.0-master.

Hello Ali, The agent version is not shown in BuildMaster 5.x's server overview page, but you can view it by going to /administration/service-status and forcing a run of the AgentUpdater executer and then checking the log for something like Connected to localhost:46336 (v39.0.0.2); checking status... (in this case, the agent on localhost is v39.0.0.2, the version of InedoAgent distributed with BuildMaster 5.8.3)

FYI this has been added (in Subversion extension v1.1.0) and the available variables are documented here: https://inedo.com/support/documentation/buildmaster/builds/continuous-integration/source-control/svn#automatic-builds-continuous-integration-with-subversion

Hi Sergey, It's not built in but you can integrate it with custom directories. Please see https://inedo.com/support/questions/3991 for a related discussion.

Hi Anup, Here is some documentation regarding active directory configuration across all of the Inedo tools: Using LDAP & Active Directory

Hi Bret, A tutorial for TeamCity is here: https://inedo.com/support/tutorials/buildmaster/teamcity/choosing-specific-artifact-from-teamcity Future note, the TeamCity tutorial may be moved to https://github.com/inedo/inedox-teamcity/wiki as part of a docs re-organization. As for controlling Apache, this is done through the httpd command, which can be executed with an Exec operation in your deployment plans, e.g.: # Deploy to Apache { Exec httpd -k stop; # deploy artifacts... Exec httpd -k start; }

Hi Anderson , Of course, a lot of our customers host ProGet in the cloud, and just install it on their own server in the cloud. But, we found it wasn't so popular to pay us to do that. The pricing was basically hosting costs + license costs + overhead, so something like $150/mo, depending. We stopped offering it, because we found most customers were either looking for a cheap, multi-tenant service (like $20 to $50/mo), or for really advanced infrastructure far beyond our capabilities (like dozens of servers globally linked, at like $10k/mo+). We are planning to launch “bring your own license” VM/Container in the cloud services at some point, and may leverage that as a hosted option. Any datapoints or insights you might have are always welcome, and I’ll share those to our leadership!

I did try that and it works outside Docker where it just uses the user that is running it. Within Docker though I can't get it to work. I tried giving it creds or api key and it just won't validate. On proget it never shows an attempt when it's the api key either. Anyway, this work around is working so now i'm progressing. I'll pass on the details once I have it working. Thanks.

Hi Alex , Thank you for your feedback . I understand better now . Of Course , I will share with you and the community , the way I'm doing when they are correctly setup , tested and approved . Best Regards , Andry

ProGet is licensed per server, so you need a separate license per server. We do permit temporary using the same key in the case of moving servers, etc., but only if they're used in a temporary state and decommissioned soon.

Eventually, but we haven't had too many requests for it :) If this is something you're interested in, we'd love to partner with a customer or two to help get this developed.

Hi Dean - apologies, other priorities came up and I lost track of this. I see your point regarding those extensions. I would be interested in getting our custom extension running if possible, so yes if you can contact me directly that would be great