You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For common integrations, it's handy to refer to the table below to know what configuration manager to choose. Most of the implementations below are written and managed by the companies behind the product. These implementations are typically open source and each part could be added by community contributions for those familiar with the code implementations. If you are unable to provide code implementations for adding necessary functionality to the integrations, we find it best if you create issues/tickets with those organizations if you are a customer as you will have more leverage into getting them implemented.
8
+
For common integrations, it's handy to refer to the table below to know what configuration manager to choose. Most of these implementations are written and managed by the organizations behind the product and are typically open source. Each part could be added by community contributions for those familiar with the code implementations. If you are unable to provide code implementations for adding necessary functionality to the integrations, we find it best if you create issues/tickets with those organizations if you are a customer as you will have more leverage in getting them implemented.
9
9
10
10
<Callouttype="info">
11
11
If you are a configuration manager company identified in the table and you have implemented anything in the below or you find our information is incorrect, please let us know so we can get it fixed.
Each *x* is linked to the specific feature documentation.
26
26
</Callout>
27
27
28
28
For most of these, those configuration managers have some sort of exec you could use to manage those additional aspects, but it would be best if they supported all aspects of configuration of Chocolatey as part of the provider implementations.
Chocolatey integrates with several infrastructure automation tools!
12
+
## Summary
13
13
14
-
With most of these tools, the interface you would interact with Chocolatey would be through the tool or through the interfaces of the tool, like in scripts.
14
+
Chocolatey can be used with almost every mainstream infrastructure automation tool! Some of the more popular ones are listed below.
15
15
16
-
## Summary
16
+
With most of these tools, the interface you would interact with Chocolatey would be through the tool or through the interfaces of the tool, like in scripts.
17
17
18
18
### Chocolatey Integration Implementation with Common Configuration Managers
Octopus is a friendly deployment automation tool for .NET developers. It integrates with lots of utilities, and they have a template for installing Chocolatey packages: https://library.octopusdeploy.com/step-template/actiontemplate-chocolatey-install-package
Otter has an [open source Chocolatey extension](https://github.com/Inedo/inedox-chocolatey) that allows installing and uninstalling packages, specifying package versions, chocolatey sources, chocolatey features, and installing chocolatey itself.
102
+
Inedo has an [open source Chocolatey extension](https://github.com/Inedo/inedox-chocolatey) that allows installing and uninstalling packages, specifying package versions, Chocolatey sources, Chocolatey features, and installing Chocolatey itself.
103
103
104
-
Otter also keeps an inventory of Chocolatey packages installed on any or all servers.
104
+
BuildMaster/Otter also keeps an inventory of Chocolatey packages installed on any or all servers.
Copy file name to clipboardExpand all lines: src/content/docs/en-us/guides/organizations/proxying-ccr.mdx
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,13 +59,6 @@ For more information, visit Inedo ProGet's documentation on [HOWTO: Proxy Packag
59
59
60
60
#### JFrog Artifactory
61
61
62
-
<divclass="callout callout-warning">
63
-
<divclass="callout-header">WARNING</div>
64
-
<p>
65
-
This does not work with the self-hosted version of Artifactory and may result in blocks for excessive usage. However, this may work in the Cloud/SaaS version. JFrog is aware that this does not work with the self-hosted version and once this has been resolved, this warning will be removed. [More information can be found here](https://jfrog.atlassian.net/browse/RTFACT-31207).
0 commit comments