|
1 | | -# Orb Template |
| 1 | +# Cloudsmith CircleCI Orb |
2 | 2 |
|
3 | | -<!--- |
4 | | -[](https://circleci.com/gh/<organization>/<project-name>) [](https://circleci.com/developer/orbs/orb/<namespace>/<orb-name>) [](https://raw.githubusercontent.com/<organization>/<project-name>/master/LICENSE) [](https://discuss.circleci.com/c/ecosystem/orbs) |
| 3 | +[](https://dl.circleci.com/status-badge/redirect/gh/ft-circleci-orbs/cloudsmith-circleci-orb/tree/main) [](https://raw.githubusercontent.com/ft-circleci-orbs/cloudsmith-circleci-orb/master/LICENSE) |
5 | 4 |
|
6 | | ----> |
| 5 | +A CircleCI orb to assist with downloading from and publishing packages to Cloudsmith. |
7 | 6 |
|
8 | | -A project template for Orbs. |
| 7 | +--- |
| 8 | + |
| 9 | +## Getting started |
| 10 | + |
| 11 | +The orb commands need the following parameters: |
| 12 | + |
| 13 | +* `repository_identifier` : The identity/slug of the Cloudsmith repository |
9 | 14 |
|
10 | | -This repository is designed to be automatically ingested and modified by the CircleCI CLI's `orb init` command. |
11 | 15 |
|
12 | | -_**Edit this area to include a custom title and description.**_ |
| 16 | +* `service_identifier` : The identity/slug of the Cloudsmith service account to use when authenticating with OIDC |
| 17 | + |
| 18 | +This can be found in the [Cloudsmith UI](https://cloudsmith.io/orgs/financial-times/). |
| 19 | + |
| 20 | +The orb provides commands to set environment variables for various package managment tools (e.g. pip). |
13 | 21 |
|
14 | 22 | --- |
15 | 23 |
|
16 | | -## Resources |
| 24 | +## Documentation |
17 | 25 |
|
18 | | -[CircleCI Orb Registry Page](https://circleci.com/developer/orbs/orb/<namespace>/<orb-name>) - The official registry page of this orb for all versions, executors, commands, and jobs described. |
| 26 | +Please see the [documention on the CircleCI orb registry](https://circleci.com/developer/orbs/orb/ft-circleci-orbs/cloudsmith-circleci). |
19 | 27 |
|
20 | | -[CircleCI Orb Docs](https://circleci.com/docs/orb-intro/#section=configuration) - Docs for using, creating, and publishing CircleCI Orbs. |
21 | 28 |
|
22 | | -### How to Contribute |
| 29 | +### Supported Package Management Tools |
23 | 30 |
|
24 | | -We welcome [issues](https://github.com/<organization>/<project-name>/issues) to and [pull requests](https://github.com/<organization>/<project-name>/pulls) against this repository! |
| 31 | +**Python:** pip |
| 32 | + |
| 33 | +--- |
25 | 34 |
|
26 | | -### How to Publish An Update |
27 | | -1. Merge pull requests with desired changes to the main branch. |
28 | | - - For the best experience, squash-and-merge and use [Conventional Commit Messages](https://conventionalcommits.org/). |
29 | | -2. Find the current version of the orb. |
30 | | - - You can run `circleci orb info <namespace>/<orb-name> | grep "Latest"` to see the current version. |
31 | | -3. Create a [new Release](https://github.com/<organization>/<project-name>/releases/new) on GitHub. |
32 | | - - Click "Choose a tag" and _create_ a new [semantically versioned](http://semver.org/) tag. (ex: v1.0.0) |
33 | | - - We will have an opportunity to change this before we publish if needed after the next step. |
34 | | -4. Click _"+ Auto-generate release notes"_. |
35 | | - - This will create a summary of all of the merged pull requests since the previous release. |
36 | | - - If you have used _[Conventional Commit Messages](https://conventionalcommits.org/)_ it will be easy to determine what types of changes were made, allowing you to ensure the correct version tag is being published. |
37 | | -5. Now ensure the version tag selected is semantically accurate based on the changes included. |
38 | | -6. Click _"Publish Release"_. |
39 | | - - This will push a new tag and trigger your publishing pipeline on CircleCI. |
0 commit comments