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

Store version number in DB after successful sql remote #2111

Closed
metas-ts opened this issue Aug 4, 2017 · 1 comment
Closed

Store version number in DB after successful sql remote #2111

metas-ts opened this issue Aug 4, 2017 · 1 comment
Assignees
@metas-lc
Labels
branch:release bug_please_use_type:bug_instead type:enhancement

Comments

@metas-ts
Copy link
Member

metas-ts commented Aug 4, 2017 •
edited
Loading

Is this a bug or feature request?

Feature

Description

Results

  • the rollout package's version is now stored in a file build-info.properties in the dist folder of both the sql-only-tar.gz and dist-tar.gz artifact
  • the rollout tool tha sql_remote.sh invokes checks the version and only runs if the package's version is higher
    • this is the default; call the tool with -h to learn more

Example: two consecutive rollouts with the same version:

First run with the special case that the DB column + initial value had to be created oin the fly:
image

Second run:
image
@metas-ts metas-ts self-assigned this Aug 4, 2017
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
solved bugs around the rollout tool; add AD_System.DBVersion to DB
28fc8cc 
Store version number in DB after successful sql remote
#2111
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
Solve problem that the tool would ignore ~/local_settings.properties
bae7360 
Store version number in DB after successful sql remote
#2111
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
minor logging improvements
b6ce724 
Store version number in DB after successful sql remote
#2111
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
fix: the version check needs to be done on the template DB
e1a1f7e 
also logging improvements
Store version number in DB after successful sql remote
#2111
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
solve stupid mistage
463681a 
#2111 Store version number in DB after successful sql remote
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
make sure to close a connection after having selected the DBVersion
21329ff 
#2111 Store version number in DB after successful sql remote
@metas-ts metas-ts mentioned this issue Aug 8, 2017
Merged
metas-ts added a commit that referenced this issue Aug 8, 2017
@metas-ts
Update ReleaseNotes.md
5572655 
[#2110](#2110) make version/build infos more transparent
[#2111](#2111) Store version number in DB after successful sql remote
@metas-ts metas-ts removed their assignment Aug 8, 2017
metas-ts added a commit to metasfresh/metasfresh-dist-orgs that referenced this issue Aug 9, 2017
@metas-ts
fix jenkins build label
a7ce16b 
Store version number in DB after successful sql remote
metasfresh/metasfresh#2111
This was referenced Aug 9, 2017
Merged
Closed
metas-ts added a commit that referenced this issue Aug 14, 2017
@metas-ts
Fix and refactoring
42cce2c 
* Fix adding the "updateInProgress" string during the migration
  * it's now more "SemVer"
  * the version is only set to the packages version (without
"inProgress") after the successfull rollout
* refactored RolloutMigrate to be more testable
* add a new Main class whic configures and calls RolloutMigrate (also to
achieve testability)
* add tests for RolloutMigrate.run0() for different (but not all!)
scenarios
* also code cleanup

#2111 Store version number in DB after successful sql remote
@metas-lc metas-lc self-assigned this Oct 17, 2017
@metas-lc
Copy link
Contributor

can be moved to done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@metas-lc metas-lc

Labels
branch:release bug_please_use_type:bug_instead type:enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@metas-ts @metas-lc