Docker Private Registry Integration (Deprecated)
Deprecation Note
This integration has been deprecated. A new integration called Docker Registry has been introduced which can be used instead. It aims to simplify and unify existing Docker Hub, Docker Private/Trusted Registry functionalities.
If you have any existing Docker Private Registry integrations, you can continue to use them.
The Docker Private Registry Integration is used to connect Shippable DevOps Assembly Lines platform to a privately hosted Docker Hub so that you can pull and push Docker images.
Creating an Integration
Since this integration has been deprecated, you cannot create new integrations for this, you can only edit/delete the exisiting Docker Private Registry integrations. You can use the new Docker Registry instead.
Usage in CI
Usage in Assembly Lines
The Docker Private Registry integration can be used in the following resources:
Default Environment Variables
When you create a resource with this integration, and use it as an IN or OUT for a runSh or runCI job, a set of environment variables is automatically made available that you can use in your scripts.
<NAME> is the the friendly name of the resource with all letters capitalized and all characters that are not letters, numbers or underscores removed. Any numbers at the beginning of the name are also removed to create a valid variable. For example, my-key-1 will be converted to MYKEY1, and my_key_1 will be converted to MY_KEY_1.
| Environment variable | Description |
|---|---|
<NAME>_INTEGRATION_URL |
URL supplied in the integration |
<NAME>_INTEGRATION_USERNAME |
Username supplied in the integration |
<NAME>_INTEGRATION_PASSWORD |
Password supplied in the integration |
<NAME>_INTEGRATION_EMAIL |
Email supplied in the integration |
Shippable Utility Functions
To make it easy to use these environment variables, the platform provides a command line utility that can be used to work with these values.
How to use these utility functions is documented here.