Compare commits

...

17 commits
1.9.0 ... main

Author SHA1 Message Date
ansgarz
0f6c2a5dcc bump version to: 4.0.1-dev 2024-02-02 11:27:05 +01:00
ansgarz
f0b0fb958d release: 4.0.0 2024-02-02 11:27:05 +01:00
ansgarz
def5427840 release: 3.0.0 2024-02-02 11:15:19 +01:00
ansgarz
1e5c4d236d bump version to: 2.1.1-dev 2024-02-02 11:15:07 +01:00
ansgarz
8f84454a84 release: 2.1.0 2024-02-02 11:15:07 +01:00
ansgarz
67ed50a36f release: 2.0.0 2024-02-02 11:14:51 +01:00
ansgarz
3860531bd4 update README.md 2024-02-02 11:11:20 +01:00
ansgarz
52c65b54c2 update README.md 2024-02-02 10:29:57 +01:00
ansgarz
e403015a30 bump version to: 1.10.1-dev 2024-02-02 09:26:40 +01:00
ansgarz
60c5efe19b release: 1.10.0 2024-02-02 09:26:40 +01:00
ansgarz
a7fbf02d7e chg layout 2024-02-02 08:38:54 +01:00
ansgarz
82016d213b bump version to: 1.9.3-dev 2024-02-01 22:53:36 +01:00
ansgarz
db0dde6251 release: 1.9.2 2024-02-01 22:53:36 +01:00
ansgarz
b08e201a03 prompt for gopass only if certain environment is set 2024-02-01 22:53:24 +01:00
ansgarz
32ae618fd6 bump version to: 1.9.2-dev 2024-01-26 14:39:23 +01:00
ansgarz
d48206f88c release: 1.9.1 2024-01-26 14:39:23 +01:00
ansgarz
c356ddf7e3 bump version to: 1.9.1-dev 2024-01-26 14:34:51 +01:00
5 changed files with 59 additions and 8 deletions

View file

@ -1,3 +1,45 @@
This repo shows examples how dda-devops-build (https://repo.prod.meissa.de/meissa/dda-devops-build) can be used.
As a starting point, you may want to have a look at file [build.py](build.py) in this repo
and the tasks which are defined in this file.
# Usage
## Examples
### Build
You can trigger the build-task by
```
pyb dev
```
### Releases
With task `patch` you can create a patch-level release with one command, i.e. perform the following actions:
* create a commit for a patch-leve release version
* e.g. if current project version is 1.1.1-dev, the update version will be the release version 1.1.1
* the commit contains all build files specified in the build.py (primary as well as secondary build files),
where the primary build file contains the version number to be used for all build files
* create a tag for the release commit (e.g. tag 1.1.1 for the corresponding commit)
* a second commit for the next snapshot version (1.1.2-dev)
* push both commits and the tag to the remote git repo
```
pyb patch
```
Similarly you can create a minor or major version with:
```
pyb minor
```
resp.
```
pyb major
```
# Release Testing
## NoRelease

View file

@ -3,7 +3,7 @@ plugins {
}
version = "1.9.0"
version = "4.0.1-SNAPSHOT"
group = "org.domaindrivenarchitecture.buildtest"

View file

@ -7,18 +7,27 @@ name = "buildtest"
MODULE = "release"
PROJECT_ROOT_PATH = "."
version = "1.9.0"
version = "4.0.1-dev"
@init(environments=["local"])
def initialize1(project):
@init
def initialize0(project):
"""
to avoid prompt for gopass; ONLY to be used for local tasks
usage: with option "-E local" , e.g. "pyb -E local patch_local"
to avoid prompt for gopass if no artifacts need to be uploaded
usage: with option "-E ng" , e.g. "pyb -E artifacts patch_local"
"""
os.environ["RELEASE_ARTIFACT_TOKEN"] = "dummy" # avoids prompt for RELEASE_ARTIFACT_TOKEN
@init(environments=["artifacts"])
def initialize1(project):
"""
prompt for gopass if no artifacts need to be uploaded
usage: with option "-E artifacts" , e.g. "pyb -E artifacts patch_local"
"""
del os.environ["RELEASE_ARTIFACT_TOKEN"]
@init
def initialize2(project):
input = {

View file

@ -33,7 +33,7 @@ default_task = "dev"
name = "ddadevops"
MODULE = "not-used"
PROJECT_ROOT_PATH = "."
version = "1.9.0"
version = "4.0.1-dev"
summary = "tools to support builds combining gopass, terraform, dda-pallet, aws & hetzner-cloud"
description = __doc__
authors = [Author("meissa GmbH", "buero@meissa-gmbh.de")]

View file

@ -2,7 +2,7 @@
"name": "c4k-jira",
"description": "Generate c4k yaml for a jira deployment.",
"author": "meissa GmbH",
"version": "1.9.0",
"version": "4.0.1-SNAPSHOT",
"homepage": "https://gitlab.com/domaindrivenarchitecture/c4k-jira#readme",
"repository": "https://www.npmjs.com/package/c4k-jira",
"license": "APACHE2",