set up continuous delivery in Github Actions about test-runner HOT 11 CLOSED

Hello,

Currently, we deploy a SNAPSHOT on maven central at each commit: see mvn-deploy-action.yml.

Should we replace this chore with another to make a stable release at each commit? If so, we will lose control over the releases on GitHub.

from test-runner.

First attempt #133

from test-runner.

from test-runner.

Hi,

It works but the version number is wrong. 😅

from test-runner.

It deployed test-runner 1.4

In test-runner, we have 3 levels of versionning, e.g. 3.1.3.

What I propose is:

1. perform a new deployment of test-runner-4.0, to have a "fresh" start of versionning. This new version, i.e. test-runner 4 will be the first official one that has automatic increment at each commit.
2. Then, since we reduce the numbering to two levels of version, we now increment the last digit at each commit.

WDYT?

from test-runner.

👍

from test-runner.

Looking at the badge, we are now at version 4.4 :)

https://search.maven.org/artifact/eu.stamp-project/test-runner/

that's cool!

but expected?

from test-runner.

Actually, no.

The automatization has been out of control.

The new version number has been built from 3.1.3 and not from 4.0 hence, the 4.4.

I think that I went too fast between the commits.

However, it should be now stable. The next commit should release 4.5.

from test-runner.

ack. let's do a documentation commit to try?

from test-runner.

I added a new option and the new version of test-runner is 4.6.

it seems to work properly.

from test-runner.

great!

from test-runner.