ktmud opened a new pull request #9517: [Build] Add Github workflows
URL: https://github.com/apache/incubator-superset/pull/9517
 
 
   Recreating #9490 after some major refactoring.
   
   ### CATEGORY
   
   - [x] Build / Development Environment
   
   ### SUMMARY
   
   Adding GitHub Actions per discussion in #9481 . This is a pure addition to 
the current build process for now. Nothing changed for Travis CI, except 
Cypress was upgraded from `3.6.1` to `4.3.0`. We could evaluate whether to 
disable Travis CI once these GitHub Actions become more stable. 
   
   Jobs are split into 4 workflows to maximize parallelization:
   
   - **superset-backend.yml:** python lint and unit tests
   - **superset-frontend.yml:** frontend lint and unit tests
   - **superset-e2e.yml:** end to end tests with Cypress
   - **license-check.yml:** check license compatibility
   
   A custom [GitHub Action](https://github.com/ktmud/cached-dependencies) was 
created to generalize the building steps related to caching and dependencies. 
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   
   Once successfully integrated, GitHub PRs should have checks like below:
   
   
![image](https://user-images.githubusercontent.com/335541/79062679-2ef19180-7c51-11ea-9c45-4b85519ae6dc.png)
   
   Meanwhile, use https://github.com/ktmud/incubator-superset/pull/27 to see 
these checks in action.
   
   ### TEST PLAN
   
   Make sure CI passes.
   
   ### ADDITIONAL INFORMATION
   
   N/A
   
   ### REVIEWERS
   
   @john-bodley @dpgaspar @craig-rueda @villebro 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to