djl-serving icon indicating copy to clipboard operation
djl-serving copied to clipboard

[CI] Integrates temp into build, integration, publishing pipeline

Open zachgk opened this issue 7 months ago • 0 comments

This PR contains a renovated Actions setup for DJL Serving as promised in https://github.com/deepjavalibrary/djl-serving/pull/1264. The major change is to create a new nightly orchestration action that will call the build, integration, and publish actions. Note that the lmic performance and PySDK integration tests were not included and will run as usual.

The build was changed to always push to the temp repo. It does still take a nightly/release to determine the version used during build. All of the publishing to both docker hub and ECR are done in the publish pipeline. It will pull the images from the temp repo and then retag and upload them to both docker hub (nightly or release) and ECR.

The integration tests are changed to run off only the temp builds. Each of them will pull and use the instances from the temp repo.

In summary, her are the major workflows you will need:

  • Nightly - The nightly action runs almost everything by a cron job like usual. It will not publish a bad release failing the tests. The list of actions to monitor consists of nightly and the two integration tests not included in it.
  • Release - The release can be done by running the nightly action. Only the single action needs to be run and it will complete the full verification up to ECR.
  • Development - For development with integration tests, you should begin by making a branch on upstream. Then, run the build for your branch. Once it is built, you can run any integration test on your branch

zachgk avatar Nov 04 '23 00:11 zachgk