You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following situation currently requires manual intervention.
A modification is made to MPS that contains an incompatible change (fixing a mistake)
MSG generates a schema and pushes to MPS
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.
The text was updated successfully, but these errors were encountered:
The following situation currently requires manual intervention.
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.The text was updated successfully, but these errors were encountered: