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