Oh I see what you mean - I thought you meant that you were able to upload packages using the NuGet client... I was able to reproduce in that way. We'll have a fix for this in maintenance release v3.0.4 (logged as issue PG-210). Apologies for the confusion.

Alana, thanks for the suggestion. I will look at adding this, but do you have any ideas how I can get the execution id for the current execution? There don't seem to be any variables for it. I thought of trying to get it from the BuildMaster API using an HTTP GET request, but I don't see a way to store that to a variable.

In this case, you should install ProGet to IIS (it's an option in the installer), and configure SSL from there.

Can you send a screenshot to support@inedo.com exhibiting this behavior? In a quick smoke test my debug logs disappear when I remove the task from all the roles.

We have released BuildMaster 4.1.3, which addresses this issue: BM-1380 - Hide passwords from clients when UseDpApiForPasswords is enabled So as long as that option is enabled, stored passwords will never be accessible from the UI.

Hi John, I just tested the fix, and it indeed solves the problem. I am impressed how quickly this was handled! Thanks a lot!

Great, many thanks for your support!

The logging isn't disabled; build execution log entries with a debug level are simply not displayed to users who don't have that privilege. By default the "View Only" role does not include the ability to view execution log entries. We have a few tutorials for making a custom action here: http://inedo.com/support/tutorials Alternatively you could store the password on the machine as an environment variable, and have the shell script retrieve it that way.

Hi Tim, You may want to create a role with the task, Builds_PromoteBuild, and then only deny that role to Production. Alex

Are you using IIS or the integrated web server? You may want to try the integrated web server. It's possible an IIS/system-wide setting is overriding some of the configration.

Passing in a username/password is controlled through the API key argument when there is no API key assigned for the feed in ProGet: http://inedo.com/support/documentation/proget/feeds/api-keys

The password being displayed is by design, since the same privilege (Builds_ManageBuildSchedules) is required to both view and edit the build schedules, therefore showing it on one page is essentially the same as showing it on the other. You can disallow users to view the schedule details by denying the Builds_ManageBuildSchedules privilege to whomever you do not want to view the passwords.