Update .gitlab-ci.yml to avoid downstream qa update
What does this MR do?
In this MR, we are avoiding java-android-apk-qa as this is failing and prevent us from releasing. After this release downstream-qa will be fixed and we will revert this change. There is a circular dependency among different components. This is the initial step to untangle rest for failures in the pipeline.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Edited by Saikat Sarkar