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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,22 @@ All notable changes to this project will be documented in this file.
7
7
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
8
8
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
9
9
10
+
## [1.4.2] - 2025-03-07
11
+
12
+
### Added
13
+
14
+
- Content placements to add to storage (no support of containered runs at this moment).
15
+
- Support of crates inside workspaces (content example - `rust-crate-ver.py`; to know crate version of the package inside some workspace, just specify package's `Cargo.toml` path; works only with no `{ workspace = true }` versions).
16
+
17
+
### Fixed
18
+
19
+
-`auto_version_rule` deserialization from YAML/TOML (see the `MIGRATIONS.md`).
20
+
10
21
## [1.4.1] - 2025-03-05
11
22
12
-
### Changed
23
+
### Added
13
24
14
-
-Added support of `daemon_wait_seconds` field in `CustomCommand`.
25
+
-Support of `daemon_wait_seconds` field in `CustomCommand`.
Copy file name to clipboardExpand all lines: DOCS.en.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -386,14 +386,44 @@ Time after time, you will start to notice that some projects are overused in oth
386
386
"type": "add_to_storage",
387
387
"short_name": "my-project",
388
388
"auto_version_rule": {
389
-
"plain_file": "file-with-current-version.txt"
389
+
"type": "plain_file",
390
+
"path": "file-with-current-version.txt"
390
391
}
391
392
}
392
393
}
393
394
```
394
395
395
396
-`short_name` - string designation of the content, which will be used to place it in the storage and each time it is used
396
-
-`auto_version_rule` - a way to automatically determine the version of the content (either `plain_file` - a file that will contain only the version and nothing else, or `cmd_stdout` - a command that will display only the version and nothing else)
397
+
-`auto_version_rule` - a way to automatically determine the version of the content (either `plain_file` with `path` field - a file that will contain only the version and nothing else, or `cmd_stdout` with `cmd` field - a command that will display only the version and nothing else)
398
+
-`content` - you may not specify it in case when you need to push all your artifacts in the storage, or you can write this way:
399
+
400
+
```json
401
+
{
402
+
"title": "Add content",
403
+
"desc": "",
404
+
"info": "content-add@0.1.0",
405
+
"tags": [],
406
+
"action": {
407
+
"type": "add_to_storage",
408
+
"short_name": "my-project",
409
+
"auto_version_rule": {
410
+
"type": "plain_file",
411
+
"path": "file-with-current-version.txt"
412
+
},
413
+
"content": {
414
+
"type": "fixed_files",
415
+
"placements": [
416
+
{
417
+
"from": "target/release/my-project",
418
+
"to": "my-project"
419
+
}
420
+
]
421
+
}
422
+
}
423
+
}
424
+
```
425
+
426
+
In this example you may see that you can specify only needed to you files from Deployer's run directory (relative `from` path) to push at content's folder (relative `to` path).
397
427
398
428
However, sometimes the file needs to be edited in some way - and not so much even the added content from the Deployer repository, but, for example, various files in the build dependencies, e.g. manually forking Python libraries to add the desired functionality, etc., etc. And, as a rule, you want to do it without creating forks and synchronizing changes with the main repository! You can't do it with `git` patches alone.
Copy file name to clipboardExpand all lines: DOCS.ru.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -386,14 +386,44 @@ deployer new content
386
386
"type": "add_to_storage",
387
387
"short_name": "my-project",
388
388
"auto_version_rule": {
389
-
"plain_file": "file-with-current-version.txt"
389
+
"type": "plain_file",
390
+
"path": "file-with-current-version.txt"
390
391
}
391
392
}
392
393
}
393
394
```
394
395
395
396
-`short_name` - строковое обозначение контента, которое будет использовано для размещения в хранилище и каждый раз при использовании
396
-
-`auto_version_rule` - способ автоматического определения версии контента (либо `plain_file` - файл, в котором будет указана только версия и больше ничего, либо `cmd_stdout` - команда, которая выведет на экран только версию и больше ничего)
397
+
-`auto_version_rule` - способ автоматического определения версии контента (либо `plain_file` с полем `path` - файл, в котором будет указана только версия и больше ничего, либо `cmd_stdout` c полем `cmd` - команда, которая выведет на экран только версию и больше ничего)
398
+
-`content` - вы можете ничего не указывать в случае, если вам нужно поместить в хранилище все ваши артефакты, иначе вы можете написать следующим образом:
399
+
400
+
```json
401
+
{
402
+
"title": "Add content",
403
+
"desc": "",
404
+
"info": "content-add@0.1.0",
405
+
"tags": [],
406
+
"action": {
407
+
"type": "add_to_storage",
408
+
"short_name": "my-project",
409
+
"auto_version_rule": {
410
+
"type": "plain_file",
411
+
"path": "file-with-current-version.txt"
412
+
},
413
+
"content": {
414
+
"type": "fixed_files",
415
+
"placements": [
416
+
{
417
+
"from": "target/release/my-project",
418
+
"to": "my-project"
419
+
}
420
+
]
421
+
}
422
+
}
423
+
}
424
+
```
425
+
426
+
В этом примере видно, что вы можете указать только нужные вам файлы из папки запусков Деплойера (относительный путь `from`), чтобы поместить их в папку с контентом (относительный путь `to`).
397
427
398
428
Однако иногда файл нужно каким-то образом редактировать - и не столько даже добавляемый контент из хранилища Деплойера, сколько, например, различные файлы в зависимостях сборки, например, вручную делать форки библиотек Python для добавления нужной функциональности и т.д. и т.п. Причём, как правило, хочется делать это без создания форков и синхронизации изменений с `main`-репозиторием! Одними патчами `git`'а не обойтись.
Copy file name to clipboardExpand all lines: MIGRATIONS.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,33 @@
2
2
3
3
> Actual configs' version: `4`.
4
4
5
+
## From `1.4.1` to `1.4.2`
6
+
7
+
1. Manually check all your `add_to_storage` Actions (`AutoVersionExtractFromRule`): them now look like this:
8
+
9
+
```json
10
+
[
11
+
{
12
+
"type": "add_to_storage",
13
+
"short_name": "my-project",
14
+
"auto_version_rule": {
15
+
"type": "plain_file",
16
+
"path": "file-with-current-version.txt"
17
+
}
18
+
},
19
+
{
20
+
"type": "add_to_storage",
21
+
"short_name": "my-project-2",
22
+
"auto_version_rule": {
23
+
"type": "cmd_stdout",
24
+
"cmd": <!-- {custom command} -->
25
+
}
26
+
}
27
+
]
28
+
```
29
+
30
+
Formally, you should now specify `type` field of `auto_version_rule` object.
31
+
5
32
## From `1.4.0-beta-3` to `1.4.0-beta-4`
6
33
7
34
1. Manually check all your configuration files for programming languages and targets' OSes. Replace `null` values with strings in the lower register (for example, `"rust"`, `"linux"`, etc.).
0 commit comments