@vadim-k_6062, yes, the latest release fixed quite a few issues. Glad to hear it is working for you now.
Thanks,
Jason
@vadim-k_6062, yes, the latest release fixed quite a few issues. Glad to hear it is working for you now.
Thanks,
Jason
Hi Chris,
This is a common issue that is related to Linux/Mono. ProGet Enterprise doesn't support Linux, is there anyway to use a Windows instance for your solution?
Thanks,
Jason
Hi Martin,
It looks like the stored procedure was using incorrect parameters. We have created an issue for this (PG-1576) and will be prioritizing this. It will likely be included in the release that is scheduled in a few weeks.
Thanks,
Jason
Vadim,
I am unable to recreate this error. Can you tell me what steps to take to reproduce this?
Thanks,
Jason
Hello,
Yes, you are correct this will need to be changed to reflect the curl command line which should be:
http://{proget}/pypi/pypi/upload --user <user>:<password> --upload-file <file-path>
Thanks,
Jason
Frederik,
Are you able to use this credential in a plan to see the full error message?
GitLab::Get-Source
(
Credentials: gitlab-user
);
Hi Frederik,
So you are using a local version of GitLab? I haven't tested with that yet, but have you ever successfully created a credential for GitLab with a non-local instance?
Thanks,
Jason
Hello,
For this functionality we suggest you use the "Unlist" button for any package/version you wish to deprecate.
Thanks,
Jason
Hello,
Are you including a API key with your request? https://docs.inedo.com/docs/proget/administration/security/api-keys#usage
Thanks,
Jason
Hi Vadim,
I understand you have restarted the Otter server. Is this a new error or is this something that has occurred after an upgrade?
Thanks,
Jason
Hi Matthew,
After discussing with our team they think this could be related to Windows Integrated Authentication (if it is enabled) or a configuration issue in your nuget.config file.. Can you try to use fiddler to help pinpoint the issue? Also, have you enabled CEIP in ProGet? That would give us some visibility to you errors.
Thanks,
Jason
Hello,
Sorry for the confusion. For your solution you would need two separate feeds. One for normal package, one for symbols.
Thanks,
Jason
Hi Chris,
I have a feeling what you'll need is the NuGetPackagesV2_SetListed stored procedure which requires two additional parameters, LatestVersion_Text and LatestStableVersion_Text. Currently this is set to internal and we are assessing if we can make this part of the api.
Thanks,
Jason
Hi Chris,
I do not see any issues with your powershell script, and I too am unable to unlist a package with this endpoint. We have created an issue and will be assessing it to determine what release this will go into.
Issue: PG-1549
Thanks,
Jason
Hello,
In ProGet all you just need to modify your baseurl in the advanced settings.
However, for the actual ssl setup we suggest using "letsencrypt" which you can learn more about here: https://blog.georgejose.com/moving-my-http-website-to-https-using-letsencrypt-haproxy-and-docker-deb56ff6be9b
Hope this helps!
Thanks,
Jason
Hello,
I think what you are trying to do can be accomplished by adding a restriction for "View & Download Packages" to "any" feed for "Authenticated" users. Then add whatever permission to the API user. Use the Test Privileges button to verify.
Thanks
Jason
Hi Gordon,
Looking at the code, it should work if the ReleaseNotes element is within PackageManifest under Metadata.
This would be the schema we use:
https://docs.microsoft.com/en-us/visualstudio/extensibility/vsix-extension-schema-2-0-reference?view=vs-2019
Thanks,
Jason
Hi Giorgi,
Are you using Windows Authentication for your instance of ProGet?
Thanks,
Jason
HI Jingesh,
What encryption type are you using on the agent? SSL or AES?
Thanks,
Jason
Alejandro,
My apologies. To be clear, ProGet does not delete the package when promoting. I now see that the documentation isn't very clear on this, so I've made a suggested change.
Thanks,
Jason
Hi Alejandro,
This will function the same way as it does within ProGet.
https://inedo.com/support/documentation/proget/advanced/package-promotion
Thanks,
Jason
Hi Jared,
According to the docs - It’s currently not possible to mirror another private registry. Only the central Hub can be mirrored. However, we do support connectors to another repository and are nearing completion on a project for docker replication between ProGet instances.
Thanks,
Jason
Hi Tigran,
We currently do not support pytest but will take this into advisement and treat this ticket as a feature request
Thanks,
Jason
Hi Steve,
Hopefully this page will clear up any confusion about the free version restrictions.
https://inedo.com/support/documentation/proget/administration/license
Let me know if you need additional information.
Thanks,
Jason
Hi Bohdan,
For the feed migration please refer to this: https://inedo.com/support/kb/1168/migrating-a-proget-feed
As far as Users/Api Keys.. are you using a Built-In user directory only?
Thanks,
Jason
Hi Jared,
I am glad it is fixed. I will make a note of how you were able to get it resolved! If you notice anything else, let us know.
Thanks,
Jason
Hi Jared,
I currently do not have enough information to try and reproduce this.. Has this just recently started? Will this occur when re-indexing every feed or a specific one. Do you have feed replication configured on feeds?
Thanks,
Jason
Hi David,
It appears that only the start of a statement block shows in the execution log..
# Visible in execution log
# This is not bisible in execution log
{
}
# Visible in execution log
# This is not visible in execution log
{
# This is not visible in execution log
}
# not showing in execution log
Let me know if you have any specific examples that aren't working as expected.
Here is the full documentation for OtterScript comments https://inedo.com/support/documentation/executionengine/otterscript/comments-and-descriptions
Thanks,
Jason
Hi Mark,
We have created an issue for this and will be prioritizing this for a future release.
Thanks,
Jason
Mark,
Approval Required listens for Build Promotion Completed events, so the pipeline stage filter should have the name of the stage of the pipeline immediately before the approval gate, not the stage that is blocked by the approval gate.
Will this resolve your issue?
Thanks,
Jason
Hello,
This documentation may help you determine the best approach for your solution: https://inedo.com/support/documentation/proget/feeds/nuget#nuget
Please let me know if you have additional questions.
Thanks,
Jason
AllowFunctionAccess_Indicator is an Y/N indicator to allow access to the credential values if they are encrypted.
Hello,
Thank you for your question. I want to make sure this gets prioritized properly. Can you submit this as a "ticket" instead?
https://inedo.com/support/submit-ticket instead.
Thanks in advance,
Jason.
Hi Adam,
Can you confirm if using false (lowercase) works or not. That is how the sample documentation shows a boolean. I'm also curious if it would convert a zero to false. Let me know what you find out. We may need to make a small change or at least adjust the documentation.
Thanks,
Jason
Hi Adam,
Do you have the latest version of the Windows extension installed? We had a similar issue for integers that was resolved in the latest extension.
Thanks,
Jason
Hi Eyal,
What version of ProGet are you using? This was a known issue that should have been fixed in version 5.1 Let me know if this is not that case.
Thanks!
Jason
Hi Giuseppe,
Unfortunately that is not part of our current API but it is a great idea and I would encourage you to complete our feature request process.
https://inedo.com/open/feature-requests
In the meantime I suggest using the import/export option in buildmaster to clone your applications.
Thanks,
Jason
Hi Frederik,
I wasn't able to recreate this error.. Try deleting the GitLab extension and reinstalling it. Also start with new resource credential. Something may have corrupted the credential record..
Thanks,
Jason
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.