Release template values are currently only used by the user interface, as a means of assisting users enter key/value pairs (variables) for a release or package. They API does not reference these, but you can pass variables into the APi quite easily.

Thanks for the clarification; I was able to repro this and logged a bug report (BM-2371). It will be addressed in a future maintence release.

Hello Alana, Thank you for reply. Adding "Delete Files" step before "Get Git Source" worked for me. Deleted files don't appear in newly created artifacts anymore. cheers, Milan

By default, all you need is the name. The following operations are equivalent: Deploy-Artifact my-artifact-name; # and... Deploy-Artifact my-artifact-name ( To: $WorkingDirectory, Application: $ApplicationName, Release: $ReleaseNumber, Package: $PackageNumber, Deployable: $DeployableName, DeployAsZipFile: false, TransferAll: false, DoNotClearTarget: false, Verbose: false ); This should be mentioned in the auto-generated docs but since it is not, I'll put in a note to do that :)

I tried to use the docker API, however I'm having problems accessing it For example, according to the API documentation: GET /v2/<name>/manifests/<reference> Should get the signature, however using this call: curl -H "Accept: application/vnd.docker.distribution.manifest.v2+json" -X GET -vvv -k https://<host>/<repository>/v2/<image>/manifests/latest Returns not found. What is the correct way to call v2 API from a proget docker repository ? I couldn't find any documentation about it. Thanks Francisco

Figured it out. It's not the user running the installation that needs db_owner membership. It's the SQL user (i.e. progetuser) created in the original setup that needs temporary db_owner membership for the upgrade process. Thanks.

Thanks for the bug report. This will be fixed in v4.7.2, which should be released today. To upgrade, see the "Upgrading to a new version" section of this KB article: http://inedo.com/support/kb/1100/getting-started-with-proget-for-linux Basically though, when the container starts up it makes sure the database schema version is current, so all you really need to do is run the new container and point to the same data.

Yes that is a bug then. I'll submit a bug report.

Just a quick update... Upon researching it further, it seems that modifying PSCall in this manner might be quite a bit complicated; not so much technically, but we'd have to balance with how PSExec works as well. Definitely something for us to consider as we work towards getting closer with PowerShell/DSC in the coming versions. The current thought is to add a new variatic variable function: PSEvalAsset(OptionalRaftName::AssetName[, arg.1..n]) This could return a scalar ($), vector (@), or map (@). Unfortunately there are no named arguments in OtterScript variable functions (unlike operations), but I think that's OK... hopefully assets will be very simple and not have a lot of arguments.

This is exactly what I was looking for, thank you!

We will implement this eventually once we have the specs nailed down. The plan is to offer a per-variable setting (in the same vein as the "sensitive" option) so it shouldn't break backwards compatibility.

You could look at the event log under Admin > Events and possibly see when/who deleted it, but there's no way to know "why" it was deleted. ProGet will not automatically delete package versions unless you specify that in a retention policy, or if they're removed from disk or database.

That makes much more sense! Thank you for the clarification. So I effectively do not need to specify targets in any of the Buildmaster actions that would require that information. Thanks for your help Tod

i'm afraid we won't be able to help with that; please consult with the BizTalk ESB team or forums.

I'll put a note in to add this to the next maintenance release this week.

Glad that worked! I created an issue for this; we should get this behavior a little more intuitive in an upcoming maintenance release.

Please note that this (or any multi-node) installation requires a ProGet Enterprise or ProGet Load Balanced License to be purchased. ProGet Basic and ProGet Free only permit a single server to be used in a single installation. That said, we recommend IIS because it's the easiest to support (by your own network admin team) and has many configuration options. In theory, you could probably use the integrated server. A HA configuration ought to use a SQL Cluster, otherwise you have a single point of failure.

Please see the ProGet feature comparison. There are no limits to the number of feeds.a

OK, I will upgrade to the latest version. It turns out the ProGet service wasn't running. I hadn't even realized it because the Web site and NuGet/NPM feeds were working normally. Starting the service was all that was needed to get those tasks running. Thanks