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
Polish travis.yml to run integration tests #3654
Labels
Milestone
Comments
6 tasks
6 tasks
@RongtongJin Try to start a new journey with GitHub workflow, Travis traffic is very heavy now. |
Looking forward to seeing our chaos module in the new CI/CD architecture:-) |
duhenglucky
pushed a commit
that referenced
this issue
Dec 17, 2021
devfat
pushed a commit
to devfat/rocketmq
that referenced
this issue
Mar 3, 2022
…e#3655) * 1.Make travis to run integration tests 2.Fix running testSynSendNullMessage failed * Remove run 'mvn clean install -Pit-test' after success * Change package to install when running UT
GenerousMan
pushed a commit
to GenerousMan/rocketmq
that referenced
this issue
Aug 12, 2022
…e#3655) * 1.Make travis to run integration tests 2.Fix running testSynSendNullMessage failed * Remove run 'mvn clean install -Pit-test' after success * Change package to install when running UT
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The issue tracker is ONLY used for bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
FEATURE REQUEST
Polish travis.yml to run integration tests
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
The text was updated successfully, but these errors were encountered: