OPEN - The integration tests are executed in Zowe Jenkins

[plavjanik]

Issue by varma09
Monday Oct 01, 2018 at 07:30 GMT
Originally opened as https://github.com/gizafoundation/api-layer/issues/140

---

As a Zowe engineer, I would like to have the integration tests executed as part of the Zowe build so I know that my changes have not broken them.

Not a must for open-sourcing

Acceptance Criteria (accepted by the architect):

The integration tests are executed as part of Zowe Jenkins (can be in Docker on Jenkins without z/OS)
Their results and logs are available by clicking on a link in the GitHub PR
Notes:

does it need to be run on mf only? no!
need docker container, run all integration tests, posts results to Git.
run on branch and master? yes
need to check if we can change zowe and if not find out who can do it for us - probably Mark
jenkins plugin for publishing results
need to come up with a procedure for reviewing external pull requests
how to support integration tests/build issues
might Mark/Dan/Petr help with this

[balhar-jakub]

We are moving with this and there is a new story created by Elliot that should precisely reflect the current state.
#627

[balhar-jakub]

The integration tests that doesn't depened on MF Environment are now run as a part of the Zowe Jenkins pipeline.

[balhar-jakub]

@plavjanik I would like to close this issue as all the tests that doesn't directly depend on MF environment are now running on the external Jenkins.

As for testing of the integration on MF there is another story where we move the smoke tests to Marist environment here:
#627

Related PRs:
#631
#657

[plavjanik]

I am great to see that :) It has been very helpful for the REST API SDK when integration tests in the CI run for few seconds and find the troubles before doing z/OS deployment and testing that takes minutes. Marist environment should improve stability and speed. I am closing it.

[zowe-robot]

The changes to the error code documentation are available in this PR: zowe/docs-site#3231