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 ORIGINAL_TRIGGER link type to ActT/TCT/TSS #355
Conversation
Note that this PR branch is based on the #354 PR branch. You'll want to filter the PR diff view to only show the last commit. I deliberately haven't added new versions of TCT and TSS since you might have opinions about the wording of the ORIGINAL_TRIGGER documentation. |
This new link type is useful to describe the relationship between the original attempt to complete a task (e.g. a build) and subsequent activities that retry the first one.
The PR branch has been rebased and it now based on the master branch instead of the (now merged) PR. |
Here's a diff between newly added event versions and their predecessors:
|
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 current state of this PR is good enough, so I will not request changes to be made (in order to not hinder it being merged if I'm off later). But I have some wishes for improvements that could be considered if you agree.
Co-authored-by: Emil Bäckmark <emil.backmark@ericsson.com>
Co-authored-by: Emil Bäckmark <emil.backmark@ericsson.com>
New diff that includes new TCT and TSS versions:
|
Ha, the newly added test for history table existence caught me. Sorry for not catching this before pushing this and requesting your reviews. |
Applicable Issues
Fixes #246
Description of the Change
Add a new ORIGINAL_TRIGGER link type to ActT, TCT, and TSS to be able to describe the retry/retrigger/rebuild relationship of subsequent activities and the original activity.
Alternate Designs
We've quibbled over the name of the link type (see linked issue) but implementation-wise there aren't that many options.
Benefits
Retries can be modeled with Eiffel.
Possible Drawbacks
Introducing another relationship for activities could make it harder to understand.
Sign-off
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
Signed-off-by: Magnus Bäck <magnus.back@axis.com>