-
Notifications
You must be signed in to change notification settings - Fork 3
/
step.yml
107 lines (90 loc) · 3.48 KB
/
step.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/
title: |-
Features and epics list for release notes
summary: |
Creates a list of features and epics gathered from git commits and tags using given pattern.
description: |
Feature descriptions are derived from commit messages. List of the features is based on previous commits messages.
The regex pattern to look for features is "<project_prefix>[0-9]{1,5}"
Epics are derived from tags.
The regex pattern to look for epics is "<project_prefix>[0-9]{1,5}_"
An alternative use, would be to create links to appropriate features and epics in the backlog system using the <default_backlog_url> variable.
website: https://github.com/DroidsOnRoids/bitrise_set_jira_features
source_code_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features
support_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features/issues
host_os_tags:
- osx-10.10
- ubuntu-16.04
# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
# project_type_tags:
# - ios
# - macos
# - android
# - xamarin
# - react-native
# - cordova
# - ionic
# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
- utility
is_requires_admin_user: false
is_always_run: false
is_skippable: false
run_if: ""
deps:
brew:
- name: git
apt_get:
- name: git
toolkit:
bash:
entry_file: step.sh
inputs:
- backlog_default_url:
opts:
title: "Default URL for the backlog system"
description: |
Base URL for prefixing the features and epics.
e.g. "https://example.com/"
Can be empty.
is_expand: true
is_required: true
- project_prefix:
opts:
title: "Project prefix"
description: |
Project prefix to search for features and epics.
e.g. "PROJ-"
Can be empty.
is_expand: true
is_required: true
outputs:
- FEATURES_FROM_COMMITS:
opts:
title: "List of features derived from commits"
description: |
If the backlog_default_url is specified, each element is prefixed with the given URL
e.g. https://example.com/PROJ-1
- EPICS_FROM_TAGS:
opts:
title: "List of epics with titles derived from tags"
description: |
If the backlog_default_url is specified, each element is prefixed with the given URL
e.g. https://example.com/PROJ-1