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
@@ -133,7 +153,11 @@ You first need to create a service account (client ID), download its json key an
133
153
134
154
```yaml
135
155
in:
136
-
type: gcs
156
+
type:
157
+
source: maven
158
+
group: org.embulk
159
+
name: gcs
160
+
verison: "0.5.0"
137
161
auth_method: json_key
138
162
json_keyfile: /path/to/json_keyfile.json
139
163
```
@@ -142,7 +166,11 @@ You can also embed contents of json_keyfile at config.yml.
142
166
143
167
```yaml
144
168
in:
145
-
type: gcs
169
+
type:
170
+
source: maven
171
+
group: org.embulk
172
+
name: gcs
173
+
verison: "0.5.0"
146
174
auth_method: json_key
147
175
json_keyfile:
148
176
content: |
@@ -164,24 +192,32 @@ Compute Engine VM instance, then you can configure embulk like this.
164
192
165
193
```yaml
166
194
in:
167
-
type: gcs
195
+
type:
196
+
source: maven
197
+
group: org.embulk
198
+
name: gcs
199
+
verison: "0.5.0"
168
200
auth_method: compute_engine
169
201
```
170
202
171
-
## Eventually Consistency
203
+
Eventually Consistency
204
+
-----------------------
172
205
173
206
An operation listing objects is eventually consistent although getting objects is strongly consistent, see https://cloud.google.com/storage/docs/consistency.
174
207
175
208
`path_prefix` uses the objects list API, therefore it would miss some of objects.
176
209
If you want to avoid such situations, you should use `paths` option which directly specifies object paths without the objects list API.
177
210
178
-
## Build
211
+
For Maintainers
212
+
----------------
213
+
214
+
### Build
179
215
180
216
```
181
-
./gradlew gem
217
+
./gradlew jar
182
218
```
183
219
184
-
## Test
220
+
### Test
185
221
186
222
To run unit tests, we need to configure the following environment variables.
187
223
@@ -230,3 +266,42 @@ $ launchctl getenv GCP_EMAIL //try to get value.
230
266
231
267
Then start your applications.
232
268
```
269
+
270
+
### Release
271
+
272
+
Modify `version` in `build.gradle` at a detached commit, and then tag the commit with an annotation.
273
+
274
+
```
275
+
git checkout --detach master
276
+
277
+
(Edit: Remove "-SNAPSHOT" in "version" in build.gradle.)
278
+
279
+
git add build.gradle
280
+
281
+
git commit -m "Release vX.Y.Z"
282
+
283
+
git tag -a vX.Y.Z
284
+
285
+
(Edit: Write a tag annotation in the changelog format.)
286
+
```
287
+
288
+
See [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) for the changelog format. We adopt a part of it for Git's tag annotation like below.
289
+
290
+
```
291
+
## [X.Y.Z] - YYYY-MM-DD
292
+
293
+
### Added
294
+
- Added a feature.
295
+
296
+
### Changed
297
+
- Changed something.
298
+
299
+
### Fixed
300
+
- Fixed a bug.
301
+
```
302
+
303
+
Push the annotated tag, then. It triggers a release operation on GitHub Actions after approval.
0 commit comments