-
Notifications
You must be signed in to change notification settings - Fork 16.4k
[AIRFLOW-4061] Remove incubator in CI process #4896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AIRFLOW-4061] Remove incubator in CI process #4896
Conversation
|
This PR can't be merged as |
|
Sorry missed your description above @zhongjiajie . Yes, change must be made for |
|
@XD-DENG Never mind, I thought you had seen it 😄. just let comment for other committer/PMC member? |
|
Maybe we can wait with it a bit as I am working now on #4543 which effectively removes the need for this external airflowci image - also something discussed in |
|
I think we should get this in for now. We should get rid of all incubator references. I've also requested to remove the old repository: https://jira.apache.org/jira/browse/INFRA-18084 Did the CI run with this PR? |
|
@zhongjiajie Please |
|
@Fokko I already add |
|
Sorry, I was a bit too quick with the enter button there. I think we should run the CI to check if the image works. |
Remove incubator as Airflow is Top-Level project.
5b6526c to
73c0d08
Compare
|
@Fokko I remove "skip" and start test. but I could not find any release in https://hub.docker.com/r/airflowci/airflow-ci and I don't think CI will pass |
|
So it died: Lets see if we can do a new release of the image. AIP-3 is pending until Sunday. Lets wait until 1.10.3 to make @ashb 's life easier ❤️ and then make a new release of the CI image. |
|
@kaxil Can you elaborate on what's going on here. I see that the current repository points to |
|
@Fokko where exactly is that? Sorry, I am not able to get this |
|
No, I'm confused. I thought the old incubator repo was pointing to your repository. |
|
Hey @Fokko @kaxil . Not sure if you are aware of it but the problem is that you need to update DockerHub account rather than GitHub repo. The URL in docker-compose is link to this dockerhub repository : https://cloud.docker.com/repository/docker/airflowci/incubator-airflow-ci and it takes the name of the image from repository name in DockerHub. In order to make it works, you'd have to create a new repository for 'airflowci' DockerHub user ( airflow-ci). I don't think you can rename incubator-airflow-ci repository (I have not found such option)- yoy need to copy configuration for automated build from incubator to the new repository (and eventually delete the old Dockerhub incubator-airflow-ci repository). No change in https://github.com/apache/airflow-ci github is needed. BTW. I am rather close to fixing all errors in the multi-stage docker #4938 and once this is merged, we won't need this dual-account/dual repos drama ;). All of this will be happening (automatically) via 'airflow' github repo and 'airflow' dockerhub user. |
|
@potiuk I was thinking the same, in the end, we would like to use the same image. Having two repositories and trying to keep them in sync is painful, and distracts us from the actual work :-) |
|
@Fokko Are we going to point to airflowci/airflow-ci:latest right now? |
|
@zhongjiajie Not yet, |
|
Get it. |
Remove incubator as Airflow is Top-Level project.
[ci skip]
Make sure you have checked all steps below.
Jira
Description
We still use
airflowci/incubator-airflow-ci:latestin our ci docker-compose, should change it toairflowci/airflow-ci:latest, in this case we have to change airflow-ci setting in docker-hub, letairflowci/airflow-ci:latestwork.