#193 Added example workflow for the AUTOSAR-UML Bridge action#194
#193 Added example workflow for the AUTOSAR-UML Bridge action#194
Conversation
…LieberLieber/LemonTree.Automation.Workflows into 193-incquery-autosar-uml-bridge
|
✔️ Model is identical! |
2 similar comments
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
@kkadosa all good - but why is the action.yml not in a seperate repo? or integrated into the main.yml? |
|
@danielsiegl the repo with the aruml action wasn't public when @kkadosa started the work. We will change it to reference https://github.com/IncQueryLabs/incquery-suite-bridge-autosar-uml-action/ |
|
|
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
2 similar comments
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
dandrid
changed the title
|
✔️ Model is identical! |
6 similar comments
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
kkadosa
force-pushed
the
193-incquery-autosar-uml-bridge
branch
from
610a671 to
3be2ca0
Compare
|
✔️ Model is identical! |
1 similar comment
|
✔️ Model is identical! |
kkadosa
force-pushed
the
193-incquery-autosar-uml-bridge
branch
from
12d1036 to
a35b341
Compare
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
✔️ Model is identical! |
|
@danielsiegl we have finished with the implementation, once you have time, please review it. We have a PR for demonstration of how this workflow works (but that PR will not get merged, we will close it once this PR gets merged): If a user modifies the ARXML file: 134fd50 |
4 participants
Closes #193
Add a workflow that executes on each (re-)opening of and on each new commit in a pull-request. Firstly, it runs the IncQuery AUTOSAR-UML Bridge using its action. Then, it pushes the updated EA model back to the originating branch, automatically keeping the two manifestations of the model in synch.
Finally, it generates a review-session file, uploads it to artifactory and post a message in the pull request containing conflict status and a link to the review session.