-
Notifications
You must be signed in to change notification settings - Fork 132
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
FAI 658: Add e2e test suite into PR checks #1092
Conversation
The (build) kogito-apps check has failed. Please check the logs. |
Jenkins retest this |
The (build) kogito-apps check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
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.
It ran locally fine for me. Great stuff.
There remains the question of getting it to run under GitHub Actions.
It might also be worth investigating if we can get yarn run build:services
to only compile kogito-apps/explainability
and kogito-apps/trusty
rather than the whole of kogito-apps
.. just an optimisation that would speed-up the e2e quite a lot.
It might also be worth adding kogito-apps/ui-packages/packages/trusty/it-tests/docker-compose/.env
to a .gitignore
file since it is generated. WDYT?
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 the goal here should be to have both jenkins and github actions pipelines executing similarly. Can you also add the new step into jenkins pipeline configuration?
- A few comments inline.
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 have only two very minor comments.
5aeec3e
to
bd583ca
Compare
The (build) kogito-apps check has failed. Please check the logs. |
672fd2b
to
8b647e3
Compare
Jenkins retest this |
The (build) kogito-apps check has failed. Please check the logs. |
Hi @manstis @sjamboro @jiripetrlik , what do you think if we add a new module where we run those tests?
wdyt? |
Kudos, SonarCloud Quality Gate passed! |
The (build) kogito-apps check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
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
It seems that docker-maven-plugin does partially support a network and we need to use just a container name instead of aliases.
It seems that CI adds the --registry option and cypress command does not recognize it. Echo just write the registry option on stdout.
log4j2.xml was removed. The reason is that the config file was upload into container but the log file does not contain more messages aliases of containers is not supported in network by DMP. URL with alias does not work repository of Docker was removed because it is set by CI workflow.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
https://issues.redhat.com/browse/FAI-658
Add E2E Audit UI tests into PR checks.
Related PRs: