Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create a tag when new code to master is pushed #117

Closed
vaadin-miki opened this issue May 12, 2020 · 0 comments · Fixed by #118
Closed

Create a tag when new code to master is pushed #117

vaadin-miki opened this issue May 12, 2020 · 0 comments · Fixed by #118
Assignees
@vaadin-miki
Projects
CI, docs, management
Milestone
0.6.1 - Release p...

Comments

@vaadin-miki
Copy link
Owner

It should be possible to automatically create a tag when a new push to master is made. That commit has version already set, so the tag should correspond to that version.

It seems to be difficult to achieve with maven, but one way seems to be mvn help:evaluate -Dexpression=project.version -q -DforceStdout.
@vaadin-miki vaadin-miki self-assigned this May 12, 2020
@vaadin-miki vaadin-miki added this to To Do in CI, docs, management via automation May 12, 2020
vaadin-miki added a commit that referenced this issue May 13, 2020
@vaadin-miki
#117 testing multiline properties
e52fa46
vaadin-miki added a commit that referenced this issue May 13, 2020
@vaadin-miki
#117 testing multiline properties, trying escaping
b909237
vaadin-miki added a commit that referenced this issue May 13, 2020
@vaadin-miki
#117 testing multiline properties
4eca758 
fixed incorrect "
vaadin-miki added a commit that referenced this issue May 13, 2020
@vaadin-miki
#117 done, hopefully
8932b75 
uses a different action that default create-release, as the official one lacks support for branch to create the tag to
vaadin-miki added a commit that referenced this issue May 13, 2020
@vaadin-miki
#117 done, hopefully
0e37f18 
removed .test from tag name
@vaadin-miki vaadin-miki mentioned this issue May 13, 2020
Merged
CI, docs, management automation moved this from To Do to Done May 13, 2020
vaadin-miki added a commit that referenced this issue May 13, 2020
@vaadin-miki
#117 done
b62bf69 
workflow should in theory figure out version number (used for tag), release title and release notes from release-notes.md
vaadin-miki added a commit that referenced this issue May 29, 2020
@vaadin-miki
Release 0.6.2 ready (#130)
511d16e 
done #100 #105 #108 #110 #107 #111 #113 #115 #117 #119 #22 #124 #126 #127 #129
vaadin-miki added a commit that referenced this issue Jun 22, 2020
@vaadin-miki
Release 0.7.0 ready (#169)
be67db6 
done #100 #105 #108 #107 #111 #113 #115 #117 #119 #22 #124 #126 #127 #129 #132 #122 #136 #137 #123 #141 #139 #143 #135 #146 #147 #152 #154 #131 #171
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vaadin-miki vaadin-miki

Labels
None yet
Projects
CI, docs, management
  
Done
Milestone
0.6.1 - Release process improvement
Development

Successfully merging a pull request may close this issue.

117 auto release vaadin-miki/super-fields
1 participant
@vaadin-miki