Skip to content

Commit 2d7731d

Browse files
zigarnzigarn
authored
[semver:patch] Bootstrap Orb (#1)
1 parent 7dc4f82 commit 2d7731d

File tree

17 files changed

+382
-0
lines changed

17 files changed

+382
-0
lines changed

‎.circleci/README.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Orb Development Pipeline
2+
3+
This configuration file uses [orb-tools orb]() version 10 to automatically _pack_, _test_, and _publish_ CircleCI orbs using this project structure. View the comments within the config file for a full break down
4+
5+
## Overview:
6+
7+
**Imported Orbs**
8+
9+
Both orb-tools and a development version of your orb will be imported into the config. On the first run, a `dev:alpha` development tag _must_ exist on your orb, but will be handled automatically from there on.
10+
11+
**Jobs**
12+
13+
In the _jobs_ key, you will define _integration tests_. These jobs will utilize the functionality of your orb at run-time and attempt to validate their usage with live examples. Integration tests can be an excellent way of determining issues with parameters and run-time execution.
14+
15+
### Workflows
16+
17+
There are two workflows which automate the pack, test, and publishing process.
18+
19+
**test-pack**
20+
21+
This is the first of the two workflows run. This workflow is responsible for any testing or prepping prior to integration tests. This is where linting occurs, shellchecking, BATS tests, or anything else that can be be tested without the need for further credentials.
22+
23+
This Workflow will be placed on _hold_ prior to publishing a new development version of the orb (based on this commit), as this step requires access to specific publishing credentials.
24+
25+
This allows users to fork the orb repository and begin the pipeline, while the code-owners review that the code is safe to test in an environment where publishing keys will be present.
26+
27+
Once approved, the development version of the orb will publish and the _trigger-integration-tests-workflow_ job will run, kicking off the next workflow
28+
29+
**integration-test_deploy**
30+
31+
The second and final workflow is manually triggered by the _trigger-integration-tests-workflow_ job. In this run, the development version of the orb that was just published will be imported, and the integration tests will run.
32+
33+
When running on the `master` branch (after merging to `master`), the workflow will additionally publish your new production orb.

‎.circleci/config.yml‎

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
version: 2.1
2+
3+
orbs:
4+
ztraining2strigo: zenika-training/ztraining2strigo@<<pipeline.parameters.dev-orb-version>>
5+
orb-tools: circleci/orb-tools@10.0
6+
7+
# Pipeline Parameters
8+
## These parameters are used internally by orb-tools. Skip to the Jobs section.
9+
parameters:
10+
run-integration-tests:
11+
description: An internal flag to prevent integration test from running before a development version has been created.
12+
type: boolean
13+
default: false
14+
dev-orb-version:
15+
description: >
16+
The development version of the orb to test.
17+
This value is automatically adjusted by the "trigger-integration-tests-workflow" job to correspond with the specific version created by the commit and should not be edited.
18+
A "dev:alpha" version must exist for the initial pipeline run.
19+
type: string
20+
default: "dev:alpha"
21+
22+
workflows:
23+
# Prior to producing a development orb (which requires credentials) basic validation, linting, and even unit testing can be performed.
24+
# This workflow will run on every commit
25+
test-pack:
26+
unless: << pipeline.parameters.run-integration-tests >>
27+
jobs:
28+
- orb-tools/lint # Lint Yaml files
29+
- orb-tools/pack # Pack orb source
30+
# Publish development version(s) of the orb.
31+
- orb-tools/publish-dev:
32+
orb-name: zenika-training/ztraining2strigo
33+
context: orb-publishing # A restricted context containing your private publishing credentials. Will only execute if approved by an authorized user.
34+
requires:
35+
- orb-tools/lint
36+
- orb-tools/pack
37+
# Trigger an integration workflow to test the
38+
# dev:${CIRCLE_SHA1:0:7} version of your orb
39+
- orb-tools/trigger-integration-tests-workflow:
40+
name: trigger-integration-dev
41+
context: orb-publishing
42+
requires:
43+
- orb-tools/publish-dev
44+
filters:
45+
branches:
46+
only:
47+
- main
48+
49+
# This `integration-test_deploy` workflow will only run
50+
# when the run-integration-tests pipeline parameter is set to true.
51+
# It is meant to be triggered by the "trigger-integration-tests-workflow"
52+
# job, and run tests on <your orb>@dev:${CIRCLE_SHA1:0:7}.
53+
integration-test_deploy:
54+
when: << pipeline.parameters.run-integration-tests >>
55+
jobs:
56+
# Publish a semver version of the orb. relies on
57+
# the commit subject containing the text "[semver:patch|minor|major|skip]"
58+
# as that will determine whether a patch, minor or major
59+
# version will be published or if publishing should
60+
# be skipped.
61+
# e.g. [semver:patch] will cause a patch version to be published.
62+
- orb-tools/dev-promote-prod-from-commit-subject:
63+
orb-name: zenika-training/ztraining2strigo
64+
context: orb-publishing
65+
add-pr-comment: false
66+
fail-if-semver-not-indicated: true
67+
publish-version-tag: false
68+
filters:
69+
branches:
70+
only:
71+
- main

‎.editorconfig‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# EditorConfig helps developers define and maintain consistent
2+
# coding styles between different editors and IDEs
3+
# editorconfig.org
4+
5+
root = true
6+
7+
8+
[*]
9+
# Change these settings to your own preference
10+
indent_style = space
11+
indent_size = 4
12+
13+
# We recommend you to keep these unchanged
14+
end_of_line = lf
15+
charset = utf-8
16+
trim_trailing_whitespace = true
17+
insert_final_newline = true
18+
19+
[*.md]
20+
trim_trailing_whitespace = false
21+
indent_size = 2
22+
23+
[*.yml]
24+
indent_size = 2

‎.github/ISSUE_TEMPLATE/BUG.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: "\U0001F41E Bug report"
3+
about: Report any bugs encountered while using this orb.
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
## Orb version:
11+
12+
<!---
13+
e.g., 1.0.0
14+
find this information in your config.yml file;
15+
if the version is @volatile, check the top of your CircleCI-generated,
16+
expanded configuration file, viewable from the "Configuration" tab of
17+
any job page, for the orb's specific semantic version number
18+
-->
19+
20+
## What happened:
21+
22+
<!---
23+
please include any relevant links to CircleCI workflows or jobs
24+
where you saw this behavior
25+
-->
26+
27+
## Expected behavior:
28+
29+
<!--- what should happen, ideally? -->
30+
31+
## Additional Information:
32+
33+
<!--- Provide any additional context possible. -->

‎.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
name: "\U0001F680 Feature Request"
3+
about: Propose changes to the orb.
4+
title: ''
5+
labels: feature_request
6+
assignees: ''
7+
---
8+
9+
## Describe Request:
10+
11+
## Examples:
12+
13+
## Supporting Documentation Links:

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: false

‎.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
2+
**SEMVER Update Type:**
3+
- [ ] Major
4+
- [ ] Minor
5+
- [ ] Patch
6+
7+
## Description:
8+
9+
<!---
10+
Describe your changes in detail, preferably in an imperative mood,
11+
i.e., "add `commandA` to `jobB`"
12+
-->
13+
14+
## Motivation:
15+
16+
<!---
17+
Share any open issues this PR references or otherwise describe the motivation to submit this pull request.
18+
-->
19+
20+
**Closes Issues:**
21+
- ISSUE URL
22+
23+
## Checklist:
24+
25+
<!--
26+
Thank you for contributing to CircleCI Orbs!
27+
before submitting your a request, please go through the following
28+
items and place an x in the [ ] if they have been completed
29+
-->
30+
31+
- [ ] All new jobs, commands, executors, parameters have descriptions.
32+
- [ ] Usage Example version numbers have been updated.

‎.gitignore‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# orb.yml is "packed" from source, and not published directly from the repository.
2+
orb.yml

‎.yamllint‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
extends: relaxed
2+
3+
rules:
4+
line-length:
5+
max: 200
6+
allow-non-breakable-inline-mappings: true

‎LICENSE‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2021 Zenika SAS
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

0 commit comments

Comments
 (0)