Story #4687: As a user, I can use either Python or Ruby bindings to interact with Pulp
Test the generated API binds
- Evaluate the best way to test the generated API binds.
One possible solution is to use .json file generated in a certain date, and use to compare with the new one.
- See: generarte-bindings
Add test to compare API bindings
Use the generated OpenAPI schema in json format generated on April/01/2019 as base to compare with generated on the fly API schemas. Main goal is to detect changes in the API schema.
In case of intentional changes, the
stored_open_api.json has to be
Problem: bindings break all the time
Solution: build and test bindings continuosly
This patch adds another job to the Travis build matrix. This new build installs pulpcore and pulp_file and then builds a client library for each. The client libraries are built using pulp-swagger-codegen, a thin wrapper around swagger-codegen-cli. After building the bindings, this job installs them and runs a script that performs the following:
- Create a File Remote
- Create a Repository
- Sync a Repository
- Monitor the sync task
- Create an artifact from a local file
- Create a FileContent from the artifact
- Add the new FileContent to a repository version
- Monitor the repo version creation task
- Create a FilePublisher
- Create a publication from the latest version of the repository
- Monitor the publish task
- Create a distribution pointint to the publication
#9 Updated by kersom about 2 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset pulp_file:ce33164d215e628c23bce3a0b755654d6b5c1f3f.
Please register to edit this issue