I've reread the documentation for Execution Modes. I believe I have a better understanding of executionPolicy's purpose now.

George, thank you so much for pointing me in the right direction, that's exactly what I was looking for!

Thank you for the report; it looks like the extension was migrated correctly but never officially released to our extension feed... I'll have someone release it ASAP

There must be some confusion here (and that is understandable since it's a legacy feature that I am in the process of reworking to support the "provider-less" model). An SCM Trigger cannot create a release, only a release package. If there are no releases (or the specific selected release doesn't exist) nothing will happen. Can you share the example pipeline, and the plan associated with its first stage's target?

I totally agree! Thanks for pointing this out. I've filed this is a bug report (OT-254), so it will get fixed in a future maintenance release

Ok, recursive search enabled, it still doesn't assign the rights based on my group membership. I'll create a ticket with a few screenshots, I'd rather not post names of our internal groups on the wider internet :)

A 401 means that npm requires authentication which was not supplied, visit Feeds > Connectors > [edit/create npm connector] and enter a username/password to connect to the external registry.

This was resolved in the latest release of Otter (v2.0.12 at the time of posting).

Thanks for the update; due to its severity we put out an emergency maintenance release to fix this.

These are available on the All Versions page: https://inedo.com/proget/versions

So between running the 'ProGetInstaller.exe' after deleting keys and directories... didn't realize the unpack directory gets recreated each time. So once I knew I deleted the 'unpack' directory... I never checked again for it. Now that I removed that directory and ran 'ProGetInstaller.exe'... looks like I can now install the application. Yes something simple and stupid. Thank you all for you help!

Please review KB#1161 for instructions on how to update this.

There are no changes in ProGet that would cause this. Most likely the package file is invalid, something is cached, you're using the wrong URL, etc. If you can provide a very specific reproduction case using a new (empty) feed, and a specific set of packages that, when uploaded in a specific order, cause this behavior, we can investigate it further.

I'm not sure if I totally understand the question, but packages are designed to be immutable, and as such you really can't "update" them. You can delete or overwrite a package if you have permissions, but it's inadvisable and you should not make this part of your workflow. In addition to being against the fundamental package workflow/design guidelines, packages are cached by clients like Visual Studio, and won't see a "new version" of a "version" of a package.

Hi Philippe, This is due to a packaging error on our part. That extension is actually the 1.0.7 (and 1.0.4) release, but reports its version incorrectly to Otter. This will be resolved in the next extension update.

Hi Alana, Thanks so much for the update and the workaround solution. I'll be sure to upvote the linked issue. Best, Michael

Hi Alana More or less it is what I am looking for. a configuration variable from a dependency role of the current role is available at runtime I will try to explain it in a better way for a request feature Thank you :)

This original post is really old and refers to an old version of BUildMaster (v4); I'm not sure what version you're using, etc. Can you submit this as a new question so we can more easily try to address / reproduce / investigate it?

As far as I'm aware, the original issue in this thread has been resolved long ago. If there is a new issue with pulling connector packages, please post a new question.