-
Notifications
You must be signed in to change notification settings - Fork 37
🐛 Fix seed dup target labels #776
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
Conversation
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
| target.Provider = t.Provider | ||
| target.Choice = t.Choice | ||
| target.ImageID = f.ID | ||
| target.Labels = []model.TargetLabel{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hint: This is the main fix ^.
aufi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix looks good to me, git command in container-build scripts setting hub-build probably needs some update.
83.41 git describe --match "v[0-9]*" --tags HEAD > bin/.build
83.41 fatal: No names found, cannot describe anything.
I think it just needs --always flag. |
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
mansam
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes an issue with duplicate target labels. Also, add support for a hub build version needed to detect upgrades. The git _tag-hash_ is written to `/etc/hub-build`. The _abbreviated_ commit hash is appended when HEAD is a commit added to the latest label. Examples: ``` v0.6.0-beta.1-1-e161635 # tag+hash v0.6.0-beta.1-1 # tag only e161635 # hash only ``` After seeded, the build is stored in settings: `.hub.db.seed.build`. This is compared with current build to detect when the build has changed. Seeding is _skipped_ when both the build (version) and the seed data have not changed. --- The go.mod update was to bump go-utils for better logging of objects. Included here for better logging of the _Settings_. --------- Signed-off-by: Jeff Ortel <[email protected]> Signed-off-by: Cherry Picker <[email protected]>
Fixes an issue with duplicate target labels. Also, add support for a hub build version needed to detect upgrades. The git _tag-hash_ is written to `/etc/hub-build`. The _abbreviated_ commit hash is appended when HEAD is a commit added to the latest label. Examples: ``` v0.6.0-beta.1-1-e161635 # tag+hash v0.6.0-beta.1-1 # tag only e161635 # hash only ``` After seeded, the build is stored in settings: `.hub.db.seed.build`. This is compared with current build to detect when the build has changed. Seeding is _skipped_ when both the build (version) and the seed data have not changed. --- The go.mod update was to bump go-utils for better logging of objects. Included here for better logging of the _Settings_. --------- Signed-off-by: Jeff Ortel <[email protected]> Signed-off-by: Cherry Picker <[email protected]> Signed-off-by: Jeff Ortel <[email protected]> Signed-off-by: Cherry Picker <[email protected]> Co-authored-by: Jeff Ortel <[email protected]>
Fixes an issue with duplicate target labels.
Also, add support for a hub build version needed to detect upgrades.
The git tag-hash is written to
/etc/hub-build. The abbreviated commit hash is appended when HEAD is a commit added to the latest label.Examples:
After seeded, the build is stored in settings:
.hub.db.seed.build. This is compared with current build to detect when the build has changed. Seeding is skipped when both the build (version) and the seed data have not changed.The go.mod update was to bump go-utils for better logging of objects. Included here for better logging of the Settings.