potiuk commented on a change in pull request #8393: Bring back CI optimisations
URL: https://github.com/apache/airflow/pull/8393#discussion_r410101124
 
 

 ##########
 File path: .github/workflows/ci.yml
 ##########
 @@ -80,134 +80,152 @@ jobs:
     name: Build docs
     runs-on: ubuntu-latest
     env:
-      TRAVIS_JOB_NAME: "Build documentation"
       PYTHON_VERSION: 3.6
+      CI_JOB_TYPE: "Documentation"
     steps:
       - uses: actions/checkout@master
-      - name: "Build documentation"
+      - name: "Build CI image"
+        run: ./scripts/ci/ci_prepare_image_on_ci.sh
+      - name: "Build docs"
         run: ./scripts/ci/ci_docs.sh
 
   tests-p36-postgres-integrations:
-    name: "Tests [Postgres9.6][Py3.6][integrations]"
+    name: "[Pg9.6][Py3.6][integrations]"
     runs-on: ubuntu-latest
     needs: [statics, statics-tests]
     env:
-      TRAVIS_JOB_NAME: "Tests [Postgres9.6][Py3.6][integrations]"
       BACKEND: postgres
       PYTHON_VERSION: 3.6
       POSTGRES_VERSION: 9.6
       ENABLED_INTEGRATIONS: "cassandra kerberos mongo openldap rabbitmq redis"
       RUN_INTEGRATION_TESTS: all
+      CI_JOB_TYPE: "Tests"
     steps:
       - uses: actions/checkout@master
-      - name: "Tests [Postgres9.6][Py3.6][integrations]"
+      - name: "Build CI image"
+        run: ./scripts/ci/ci_prepare_image_on_ci.sh
+      - name: "Tests"
         run: ./scripts/ci/ci_run_airflow_testing.sh
 
   tests-p36-postgres-providers:
 
 Review comment:
   Working on it. I will also (I think) incorporate a great idea from 
@turbaszek -> It turns out that (similarly as in GitLab POC I tried before) 
each project has a private GitHub Docker registry that we can use to store the 
images, so for every build we will just build one CI image with latest sources 
and use it for all the jobs. I discussed it with Tomek this morning and I 
thought a bit about it and I can do it very easily now within this CI 
"optimisation" build.
   
   Bear with me. I will finish it today :).

----------------------------------------------------------------
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

Reply via email to