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
* Sync with DataMiner docs changes
* Syncing the Getting Started more to be in line with the docs
* Apply suggestions from code review
Co-authored-by: Marieke Goethals <94605575+MariekeGO@users.noreply.github.com>
* Applying other CR remarks on other places
* Update GettingStarted.md
---------
Co-authored-by: Marieke Goethals <94605575+MariekeGO@users.noreply.github.com>
(cherry picked from commit 5f19658)
Copy file name to clipboardexpand all lines: working/templates/SharedItems/.github/workflows/basic.yml
+1-1
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ jobs:
29
29
if [[ -z "${{ secrets.DATAMINER_TOKEN }}" ]]; then
30
30
echo "Error: DATAMINER_TOKEN is not set. Release not possible!"
31
31
echo "Please create or re-use an admin.dataminer.services token by visiting: https://admin.dataminer.services/."
32
-
echo "Navigate to the right Organization then go to Keys and create/find a key with permissions to Register catalog items, Download catalog versions and Read catalog items."
32
+
echo "Navigate to the right organization, then go to Keys and create or find a key with permissions Register catalog items, Download catalog versions, and Read catalog items."
Welcome to the Skyline DataMiner DevOps environment!
4
-
This quick-start guide will help you get up and running. It was auto-generated based on the initial project setup during creation.
3
+
Welcome to the Skyline DataMiner DevOps environment!
4
+
This quick-start guide will help you get up and running. It was auto-generated based on the initial project setup during creation.
5
5
For more details and comprehensive instructions, please visit [DataMiner Docs](https://docs.dataminer.services/).
6
6
7
7
<!--#if (CreateDataMinerPackage)-->
8
-
## Creating a DataMiner Application Package
8
+
## Creating a DataMiner application package
9
9
10
-
This project was configured to create a `.dmapp` file every time you build the project.
11
-
When you compile or build the project, you will find the generated `.dmapp` in the standard output folder, typically the `bin` folder of your project.
10
+
This project is configured to create a .dmapp file every time you build the project.
12
11
13
-
When you publish the project (see Publishing topic below), a corresponding item will be created in the online DataMiner Catalog.
12
+
When you compile or build the project, you will find the generated .dmapp in the standard output folder, typically the *bin* folder of your project.
13
+
14
+
When you publish the project, a corresponding item will be created in the online DataMiner Catalog.
14
15
15
16
<!--#else-->
16
-
## Enabling the Creation of a DataMiner Application Package
17
+
## Enabling the creation of a DataMiner application package
17
18
18
-
This project was not configured to generate a `.dmapp` file.
19
-
To enable `.dmapp` generation, consider migrating to a multi-artifact DataMiner Application Package as described below.
19
+
This project was not configured to generate a .dmapp file.
20
+
To enable .dmapp generation, consider migrating to a multi-artifact DataMiner Application Package as described below.
20
21
21
22
<!--#endif-->
22
-
## Migrating to a Multi-Artifact DataMiner Application Package
23
+
## Migrating to a multi-artifact DataMiner application package
23
24
24
-
If you need to combine additional components in your `.dmapp` file, you should:
25
+
If you need to combine additional components in your .dmapp file, you should:
25
26
26
27
1. Open the `$SCRIPTNAME$.csproj` file and ensure the `<GenerateDataminerPackage>` property is set to `False`.
27
28
28
-
2. Right-click your solution and select **Add > New Project**.
29
+
1. Right-click your solution and select *Add* > *New Project*.
29
30
30
-
3. Select the **Skyline DataMiner Package Project** template.
31
+
1. Select the *Skyline DataMiner Package Project* template.
31
32
32
33
Follow the provided **Getting Started** guide in the new project for further instructions.
33
34
34
35
<!--#if (CreateDataMinerPackage)-->
35
36
## Publishing to the Catalog
36
37
37
-
This project was created with support for publishing to the DataMiner Catalog.
38
+
This project was created with support for publishing to the DataMiner Catalog.
38
39
You can publish your artifact either manually via the Visual Studio IDE or by setting up a CI/CD workflow.
39
40
<!--#endif-->
40
41
<!--#if (IsCatalogNoCICD)-->
41
42
42
-
### Manual Publishing
43
+
### Publishing manually
44
+
45
+
1. Obtain an **organization key** from [admin.dataminer.services](https://admin.dataminer.services/) with the following scopes:
43
46
44
-
1. Obtain an **Organization Key** from [admin.dataminer.services](https://admin.dataminer.services/) with the following scopes:
45
-
-**Register catalog items**
46
-
-**Read catalog items**
47
-
-**Download catalog versions**
47
+
-*Register catalog items*
48
+
-*Read catalog items*
49
+
-*Download catalog versions*
48
50
49
51
1. Securely store the key using Visual Studio User Secrets:
50
52
51
-
1. Right-click the project and select **Manage User Secrets**.
53
+
1. Right-click the project and select *Manage User Secrets*.
52
54
53
55
1. Add the key in the following format:
54
56
@@ -62,70 +64,77 @@ You can publish your artifact either manually via the Visual Studio IDE or by se
62
64
}
63
65
```
64
66
65
-
1. Publish the package by right-clicking your project in Visual Studio and then selecting the **Publish** option.
67
+
1. Publish the package by right-clicking your project in Visual Studio and then selecting the *Publish* option.
68
+
69
+
This will open a new window, where you will find a Publish button and a link where your item will eventually be registered.
66
70
67
-
This will open a new window, where you will find a *Publish* button and a link where your item will eventually be registered.
71
+
> [!NOTE]
72
+
> To safeguard the quality of your product, consider using a CI/CD setup to run *dotnet publish* only after passing quality checks.
68
73
69
-
**Recommendation:** To safeguard the quality of your product, consider using a CI/CD setup to run **dotnet publish** only after passing quality checks.
74
+
### Changing the version of a package
70
75
71
-
### Changing the Version
76
+
There are two ways to change the version of a package:
72
77
73
-
1. Navigate to your project in Visual Studio, right-click, and select Properties.
78
+
- By adjusting the package version property:
74
79
75
-
1. Search for Package Version.
80
+
1. Navigate to your project in Visual Studio, right-click, and select *Properties*.
76
81
77
-
1. Adjust the value as needed.
82
+
1. Search for *Package Version*.
78
83
79
-
### Changing the Version - Alternative
84
+
1. Adjust the value as needed.
80
85
81
-
1. Navigate to your project in Visual Studio and double-click it.
86
+
- By adjusting the *Version* XML tag:
82
87
83
-
1. Adjust the "Version" XML tag to the version you want to register.
88
+
1. Navigate to your project in Visual Studio and double-click it.
84
89
85
-
```xml
86
-
<Version>1.0.1</Version>
87
-
```
90
+
1. Adjust the *Version* XML tag to the version you want to register.
91
+
92
+
```xml
93
+
<Version>1.0.1</Version>
94
+
```
88
95
89
96
<!--#elseif (IsCatalogBasicCICD)-->
90
-
## Publishing to the Catalog with Basic CI/CD Workflow
97
+
## Publishing to the Catalog with basic CI/CD workflow
98
+
99
+
This project includes a basic GitHub workflow for Catalog publishing.
91
100
92
-
This project includes a basic GitHub workflow for Catalog publishing.
93
101
Follow these steps to set it up:
94
102
95
-
1. Create a GitHub repository by going to **Git > Create Git Repository**, selecting GitHub, and filling in the wizard before clicking **Create and Push**.
103
+
1. Create a GitHub repository by going to *Git* > *Create Git Repository* in Visual Studio, selecting GitHub, and filling in the wizard before clicking *Create and Push*.
96
104
97
105
1. In GitHub, go to the *Actions* tab.
98
106
99
107
1. Click the workflow run that failed (usually called *Add project files*).
100
108
101
-
1. Click the "build" step that failed and read the failing error.
109
+
1. Click the "build" step that failed and read the error.
102
110
103
111
``` text
104
112
Error: DATAMINER_TOKEN is not set. Release not possible!
105
113
Please create or re-use an admin.dataminer.services token by visiting: https://admin.dataminer.services/.
106
-
Navigate to the right Organization then go to Keys and create/find a key with permissions to Register Catalog Items.
114
+
Navigate to the right organization, then go to Keys and create or find a key with permissions Register catalog items, Download catalog versions, and Read catalog items.
107
115
Copy the value of the token.
108
116
Then set a DATAMINER_TOKEN secret in your repository settings: **Dynamic Link**
109
117
```
110
118
111
119
You can use the links from the actual error to better address the next couple of steps.
112
120
113
-
1. Obtain an **Organization Key** from [admin.dataminer.services](https://admin.dataminer.services/) with the following scopes:
114
-
-**Register catalog items**
115
-
-**Read catalog items**
116
-
-**Download catalog versions**
121
+
1. Obtain an **organization key** from [admin.dataminer.services](https://admin.dataminer.services/) with the following scopes:
122
+
123
+
-*Register catalog items*
124
+
-*Read catalog items*
125
+
-*Download catalog versions*
117
126
118
-
1. Add the key as a secret in your GitHub repository, by navigating to **Settings > Secrets and variables > Actions** and creating a secret named `DATAMINER_TOKEN`.
127
+
1. Add the key as a secret in your GitHub repository, by navigating to *Settings* > *Secrets and variables* > *Actions* and creating a secret named `DATAMINER_TOKEN`.
119
128
120
129
1. Re-run the workflow.
121
130
122
131
With this setup, any push with new content (including the initial creation) to the main/master branch will generate a new pre-release version, using the latest commit message as the version description.
123
132
124
-
### Releasing a Specific Version
133
+
### Releasing a specific version
125
134
126
-
1. Navigate to the **<> Code** tab in your GitHub repository.
135
+
1. Navigate to the *<> Code* tab in your GitHub repository.
127
136
128
-
1. In the menu on the right, select **Releases**.
137
+
1. In the menu on the right, select *Releases*.
129
138
130
139
1. Create a new release, select the desired version as a **tag**, and provide a title and description.
131
140
@@ -134,17 +143,15 @@ With this setup, any push with new content (including the initial creation) to t
134
143
135
144
<!--#elseif (IsCatalogCompleteCICD)-->
136
145
137
-
## Publishing to the Catalog with Complete CI/CD Workflow
146
+
## Publishing to the Catalog with complete CI/CD workflow
138
147
139
148
This project includes a comprehensive GitHub workflow that adheres to Skyline Communications' quality standards, including static code analysis, custom validation, and unit testing.
140
149
141
-
### Prerequisite
150
+
1. Make sure you have a **SonarCloud organization**.
142
151
143
-
You need a **SonarCloud Organization**. If you don’t have one, you can create it [here](https://sonarcloud.io/create-organization).
152
+
If you do not have one yet, you can create it on [sonarcloud.io](https://sonarcloud.io/create-organization).
144
153
145
-
### Steps
146
-
147
-
1. Create a GitHub repository by going to **Git > Create Git Repository**, selecting GitHub, and filling in the wizard before clicking **Create and Push**.
154
+
1. Create a GitHub repository by going to *Git* > *Create Git Repository* in Visual Studio, selecting GitHub, and filling in the wizard before clicking *Create and Push*.
148
155
149
156
1. In GitHub, go to the *Actions* tab.
150
157
@@ -155,19 +162,20 @@ You need a **SonarCloud Organization**. If you don’t have one, you can create
155
162
```text
156
163
Error: DATAMINER_TOKEN is not set. Release not possible!
157
164
Please create or re-use an admin.dataminer.services token by visiting: https://admin.dataminer.services/.
158
-
Navigate to the right Organization then go to Keys and create/find a key with permissions to Register catalog items, Download catalog versions and Read catalog items.
165
+
Navigate to the right organization, then go to Keys and create or find a key with permissions Register catalog items, Download catalog versions, and Read catalog items.
159
166
Copy the value of the token.
160
167
Then set a DATAMINER_TOKEN secret in your repository settings: **Dynamic Link**
161
168
```
162
169
163
170
You can use the links from the actual error to better address the next couple of steps.
164
171
165
-
1. Obtain an **Organization Key** from [admin.dataminer.services](https://admin.dataminer.services/) with the following scopes:
166
-
-**Register catalog items**
167
-
-**Read catalog items**
168
-
-**Download catalog versions**
172
+
1. Obtain an **organization key** from [admin.dataminer.services](https://admin.dataminer.services/) with the following scopes:
173
+
174
+
-*Register catalog items*
175
+
-*Read catalog items*
176
+
-*Download catalog versions*
169
177
170
-
1. Add the key as a secret in your GitHub repository, by navigating to **Settings > Secrets and variables > Actions** and creating secrets or variables with the required names.
178
+
1. Add the key as a secret in your GitHub repository, by navigating to *Settings* > *Secrets and variables* > *Actions* and creating secrets or variables with the required names.
171
179
172
180
1. Re-run the workflow.
173
181
@@ -179,21 +187,21 @@ The following secrets and variables will have been added to your repository afte
179
187
|`SONAR_TOKEN`| Secret | Token for SonarCloud authentication | Obtain from [SonarCloud Security](https://sonarcloud.io/account/security) and add it as a secret. |
180
188
|`SONAR_NAME`| Variable | SonarCloud project ID | Visit [SonarCloud](https://sonarcloud.io/projects/create), copy the project ID, and add it as a variable. |
181
189
182
-
### Releasing a Version
190
+
### Releasing a version
183
191
184
-
1. Navigate to the **<> Code** tab in your GitHub repository.
192
+
1. Navigate to the *<> Code* tab in your GitHub repository.
185
193
186
-
1. In the menu on the right, select **Releases**.
194
+
1. In the menu on the right, select *Releases*.
187
195
188
196
1. Create a new release, select the desired version as a **tag**, and provide a title and description.
189
197
190
198
> [!NOTE]
191
199
> The description will be visible in the DataMiner Catalog.
192
200
193
201
<!--#else-->
194
-
## Enabling Publishing to the Catalog
202
+
## Enabling publishing to the Catalog
195
203
196
-
This project was created without support for publishing to the DataMiner Catalog.
197
-
To enable this, add a **Skyline DataMiner Package Project** to your solution and follow the **Getting Started** guide provided in that project.
204
+
This project was created without support for publishing to the DataMiner Catalog.
205
+
To enable this, add a *Skyline DataMiner Package Project* to your solution and follow the **Getting Started** guide provided in that project.
0 commit comments