[AIRFLOW-5886] - fixed a bit too selective Dockerfile copy

[potiuk]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
  • https://issues.apache.org/jira/browse/AIRFLOW-5886

Description

• Here are some details about my PR, including screenshots of any UI changes:

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does
  • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

[potiuk]

It was a bit too selective change - I have to copy the whole CI folder as we also need the CI scripts for DinD Kind operations - i.e. docker builds executed inside the docker container :). I think I must have seen a wrong CI output and merged it hastily yesterday (among 15+ merges I've done yesterday :). I'd fix it without waiting for Travis so that some PRs can be rebased quickly.

[potiuk]

Fun fact for the curious ones - I know the reason it was Green yesterday - because of a the weird Kubernetes test dependency we have.

Currently Kubernetes tests are testing the PREVIOUS MASTER Docker image not the CURRENT SOURCES (not good) so when the PR was run, it was Green as previous Docker file had all the files and the new one did not. So after merge it kind of tripped over its own feet and got broken.

Luckily the permanent fix for the Kubernetes “previous master vs. current” is coming in #6516 which is next in line to merge.

[potiuk]

Thanks @mik-laj !