Skip to content
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

Stabilize e2e - Closes #2063 #2064

merged 5 commits into from May 27, 2019


3 participants
Copy link

commented May 23, 2019

What issue have I solved?


How have I implemented/fixed it?

How has this been tested?

Review checklist

Efefefef added some commits May 23, 2019

@Efefefef Efefefef self-assigned this May 23, 2019

@Efefefef Efefefef force-pushed the 2063-stabilize-e2e branch from b6ff5ac to 0cca4d5 May 24, 2019

@Efefefef Efefefef requested a review from massao May 24, 2019

@Efefefef Efefefef force-pushed the 2063-stabilize-e2e branch from 1bdccd7 to 6aed3ea May 24, 2019


massao approved these changes May 27, 2019

Copy link

left a comment


@reyraa reyraa added this to Pull Requests in Version 1.18.0 via automation May 27, 2019

@Efefefef Efefefef merged commit 7888cb1 into development May 27, 2019

3 checks passed

Jenkins e2e tests e2e tests passed
Jenkins test deployment Commit was deployed to test
continuous-integration/jenkins/pr-merge This commit looks good

Version 1.18.0 automation moved this from Pull Requests to Merged Pull Requests May 27, 2019

@Efefefef Efefefef deleted the 2063-stabilize-e2e branch May 27, 2019

@reyraa reyraa added the ready label Jun 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.