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.

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

Add the ability to update the timestamp of the last commit #40

Open
acmiyaguchi opened this issue Jul 2, 2019 · 0 comments
Open

Add the ability to update the timestamp of the last commit #40

acmiyaguchi opened this issue Jul 2, 2019 · 0 comments

Comments

@acmiyaguchi
Copy link
Contributor

The following situation currently requires manual intervention.

  1. A modification is made to MPS that contains an incompatible change (fixing a mistake)
  2. MSG generates a schema and pushes to MPS
  3. Jenkins picks up on the new schema, enters a failure state

If the table is not dropped between steps 1 and 2, then Jenkins will need to rerun in order to update the table. In order to do this, there needs to be a new commit to the generated-schemas branch.

One solution to this is to allow git commit --amend to the last commit, in order to create a new commit hash with an updated timestamp. Every run of the MSG will then touch the timestamp of the schemas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant