Hi Clint, Sorry for the slow response. There is no current way to do this at the role level, but we could possibly add this as a feature. If you'd like it, check out our new feature request process, and we can see about assessing it. Thanks!

This is a known issue with the native API. The behavior is certainly not desired, and we are planning to develop a new feed management API in the future, so we will address this issue at that time. in the meantime, please be careful when using the Native API; it's a low-level API and doesn't always validate like you would expect. Note you can also delete the feed using the NativeAPI if you accidentally do that.

Now I did see one version of BuildMaster (v6.0.5... maybe?) having some issue resolving $ServeRName, but it was fixed. Try upgrading to latest v6 as well...

There should be an official v1.0.0 version released with that exception fixed. Before attempting to install it, manually delete Artifactory.* from your Extensions path ({InstallDir}\Extensions) .

Thank you so much, build master now works.

Stoyan -- this is really no way of doing this on Windows. It's simply a limitation of the operation system, and has been for over 10 years. You cannot have something that runs under a service context (BuildMaster and Inedo Agents run as a service) interact with the desktop UI in anyway. You cannot "escape" a service context in any way. So from within a service, you can't launch a program that launches a program that launches a program etc., that launches a WPF application. You would, instead, need to write a desktop application that monitors "something" (a drop folder, pipe, etc), and then reacts when that that changes.

You can just run "ProGet for Linux", it's already in a container.

It sounds like you don't have the extension installed... Go in to your extensions folder, then delete the extensions. restart ProGet website. Then go to reinstall the OSSIndex instead. Then it'll appear :)

After more investigation I discovered the problem was due to lack of permissions on the Storage folder assigned (DOH!). Would be a good idea to improve the ProGet error message as you indicated so it gives a more helpful clue. Thanks for your help. Dwight

We definitely plan to improve the event handling & logging, across the board for our products. I don't have a date on it, but it's in the specification process; we always welcome feedback at this stage, so if you are interested in reviewing once it's ready, we would definitely appreciate it. We don't have an import/export feature for these events. However, they are stored in the database (across a couple tables - EventOccurences and EventOccurenceDetails), so you could extract using this.

You can actually put a full commit ID in the Tag field (which actually supports any refname)... I'll have someone put a note in to change that in the operation.

Understood, thanks for the explanation! So this is an issue on the Jetbrains end. We will definitely contact them and see the course of action that's available. Thanks again!

Thank you Alana. That worked.

I can't seem to find any indication that endpoint is part of official NuGet API, but in ProGet if you want a specific file you can query as per this example: http://proget.company.com/package-files/download?packageId={packageId}&version={packageVersion}&feedName={feedName}&path={packageId}.nuspec A live example: https://proget.inedo.com/package-files/download?packageId=InedoLib&version=528.0.0&feedName=ExternalBuild&path=InedoLib.nuspec

I've come across this too... but I'm pretty certain it's not going to possible. In the visual editor, all properties all text boxes that are blank by default (which means, not specified), and any characters in those boxes are always escaped ("" would become "\"\""). I made a variable function called $Empty that just returns "". Maybe I'll submit as a pull request to InedoCore...

Issue solved. wrong role was applied, target server has no IIS feature installed.

The fix will be part of that (it was actually a regression in the Pipeline picker control which is on both of those pages).

While we don't have a "first class" Quality Center integration, we have a number of customers who have done this. Unfortunately, HPQC automation is not easy, especially to generalize into a plug-in, which is why we don't have built-in support for it. But there are a few general things to keep in mind as you design a process around this, and of course please don't hesitate to reach out for more help :) Of course, BuildMaster can run "anything" with a commandline-interface using the Exec operation. You can create a Powershell Script to surround this, or a OtterScript module to give you a consistent set of arguments. Unfortunately, QC doesn't have a commandline, but it does have a COM-based OTA API that can be used to build a commandline tool that BuildMaster then calls. You could also build an extension using the Inedo SDK that calls this API, but in this case, building your own CLI is typically easier, because you can independently test it, and it offers some isolation against problems with the COM-based API. It does appear that QC has a REST API, but it is a "technical preview" and probably isn't feature complete. You may be able to use it, which would be a lot easier, since you can just use PowerShell or built-in operations to make simple HTTP calls. Hope this helps a little bit!

While we don't have a "first class" Quality Center integration, we have a number of customers who have done this. Unfortunately, HPQC automation is not easy, especially to generalize into a plug-in, which is why we don't have built-in support for it. But there are a few general things to keep in mind as you design a process around this, and of course please don't hesitate to reach out for more help :) Of course, BuildMaster can run "anything" with a commandline-interface using the Exec operation. You can create a Powershell Script to surround this, or a OtterScript module to give you a consistent set of arguments. Unfortunately, QC doesn't have a commandline, but it does have a COM-based OTA API that can be used to build a commandline tool that BuildMaster then calls. You could also build an extension using the Inedo SDK that calls this API, but in this case, building your own CLI is typically easier, because you can independently test it, and it offers some isolation against problems with the COM-based API. It does appear that QC has a REST API, but it is a "technical preview" and probably isn't feature complete. You may be able to use it, which would be a lot easier, since you can just use PowerShell or built-in operations to make simple HTTP calls. Hope this helps a little bit!

We added basic support for this in BM-3197, though anything more complicated needs to be handled with a custom event listener. If you want to create a custom extension for this (and are an enterprise customer) you already have access to the source code at https://my.inedo.com, or you can request direct source access to our GitLab repository as well, just send a note via the contact form.