-
Notifications
You must be signed in to change notification settings - Fork 51
Conversation
- ".github/workflows/kuksa_val_docker.yml" | ||
- "kuksa-val-server/**" | ||
- "kuksa_certificates/**" | ||
- "proto/**" |
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.
do we need proto here? Server doesn't use it or am I wrong?
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.
Correct, good catch, it uses it's own proto file at https://github.com/eclipse/kuksa.val/blob/master/kuksa-val-server/protos/kuksa.proto. Will update
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.
I think its my bad the comment above. we have a grpc side for server too. Forgot this
But that is not in the Proto folder, it is in https://github.com/eclipse/kuksa.val/blob/master/kuksa-val-server/protos/kuksa.proto |
The databroker failed build is related to #631 |
Pls rebase to master to see it runs through now |
Rationale: Kuksa-val build was triggered too often, But then, should we not trigger when certs and proto files are changed as well (Even if some use symbolic links)
1d88a10
to
c09ba65
Compare
Rationale:
Kuksa-val build was triggered too often due to negative requirement and a spelling error
Clean-images is useless as we do not upload images tagged by PR
But then, should we not trigger when certs and proto files are changed as well (Even if some use symbolic links, do not know if build action is smart enough to follow symbolic links and check if they have been changed))
Note: Not intended for v0.4!