Hi David,

From looking at the code that error/message is occurring because it is not finding any pertinent repository monitor records in the [RepositoryMonitorStates] It is looking for any records with branches named default or master... This is leading me to believe that there is a configuration issue that doesn't generate an exception when monitoring or no changes were found. Additional logging might be something worth looking into. Without any additional information it would be hard to determine on our end.

Thanks,
Jason

Hi Simon,

I am unable to recreate this issue. Please check to make sure the path exists at run-time and that the buildmaster agent has permissions to it. You can try to test this with a different path like c:\Buildmaster\rpt\

Brent,

This our public Q&A forum, which is used for software technical support; as such, I've edited your message to remove your company and contact information.

That said, we help organizations with compliance-related questionnaires on our products all the time, both sales and post-sales. Please reach out to your Inedo account manager or use our contact form, and send whatever security compliance forms/documentation you are trying to fill out, and we will do our best to advise and help.

Hi Simon,

Thank you for this information, I am going to try and replicate this issue and see where to go from there.

Thanks,
Jason

Hi,

We are still discussing this issue internally. I am wondering if the issue could be with the endpoint.. can you change to /nuget/default instead of /feeds/default/nuget

Thanks,
Jason

Hello,

I'd like to get a little more information regarding this ticket. Can you provide me some screen shots of your feed settings and other relevant screens.

Thanks,
Jason

Jon,

I haven't found too much on this besides what we already recommended. I did find this option specifically for Import-module : https://stackoverflow.com/a/28512164

Hi Simon,

I need a bit more information. Can you send the portion of your OtterScript plan that is causing the exception? (You can obfuscate any sensitive urls).. My initial thought is that the remote server has directory browsing disabled.. But we can look further into this.

Thanks,
Jason

Hi Bret,

For question #1 - We have just published this documentation for TeamCity: https://inedo.com/support/documentation/buildmaster/builds/external-systems/teamcity
This may give you a little more guidance on that subject.

For question #2- all of our tutorials are here: https://inedo.com/support/tutorials
but this one might be what you are looking for https://inedo.com/support/tutorials/buildmaster/continuous-integration/manage-pipelines-git

Thanks,
Jason

Yes. that is correct. I believe there is a plan to add security into the API.

Groups_XML is basically 2 nodes. groups and group.

<groups>
      <group>Administrators</group>
</groups>

Jon,

Did using the Out-Null help to limit the logging?

After looking into this issue further we have determined that sequentially ordering the parameters will resolve the issue.

Thanks,
Jason

Was the -verbose attribute specified in the script? I don't know of any way to suppress this off-hand, perhaps you can try -Verbose:$false or pipe to Out-Null

Taras,

try encrypting without the brackets {}

so encrypt this first:

api:FHGDSFREG-3FrF

your command should exclude {} as well

npm config set _auth=YXBpOntGSEdEU0ZSRUctM0ZyRn0g__newtoken

Hi Andrey,

Generally a feature is included in the Free Edition unless otherwise stated. For LDAP authentication you will need to install the InedoCore extension.

Here are more docs to review
https://inedo.com/support/documentation/various/ldap/ldap-active-directory

Let me know if further help is needed.

Thanks,
Jason

Please refer to this topic for help uninstalling the product.

Hi Garry,
have you looked into adding retention rules to the feed?

Hi Taras,

This has been tested in ProGet, in order to publish with Token authentication:

• You need to create a user in proget
• give that user the Add Package role
• create a new token that impersonates that user.
• encrypt the token to base64

Hi Fabrizio,
It appears that the ProGet source code is fine but the issue is with NuGet symbol & source server.