[jira] [Commented] (AIRFLOW-6736) Kubernetes Git test uses always apache/airflow:master as source of files
[ https://issues.apache.org/jira/browse/AIRFLOW-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033575#comment-17033575 ] ASF subversion and git services commented on AIRFLOW-6736: -- Commit c79bd377d6472655304b438eeb8e7682f589ab62 in airflow's branch refs/heads/v1-10-test from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=c79bd37 ] [AIRFLOW-6736] Fix the repo/branch that is used in PRs for git sync (#7368) Kubernetes Git test uses always apache/airflow:master as source of files This made it impossible to test how the Kubernetes GitSync test will behave when merged. The git sync should always be done with the original repo/branch or from the TRAVIS_BRANCH if this is a push build (cherry picked from commit 675cc6a83a3877573f4f4a5afef2d0673be9dfbd) > Kubernetes Git test uses always apache/airflow:master as source of files > > > Key: AIRFLOW-6736 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6736 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Priority: Major > Fix For: 2.0.0 > > > This makes it impossible to test how the Kubernetes GitSync test will behave > when merged. The git sync should always be done with the original repo/branch > or from the TRAVIS_BRANCH if this is a push build -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6736) Kubernetes Git test uses always apache/airflow:master as source of files
[ https://issues.apache.org/jira/browse/AIRFLOW-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030966#comment-17030966 ] ASF subversion and git services commented on AIRFLOW-6736: -- Commit 675cc6a83a3877573f4f4a5afef2d0673be9dfbd in airflow's branch refs/heads/master from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=675cc6a ] [AIRFLOW-6736] Fix the repo/branch that is used in PRs for git sync (#7368) Kubernetes Git test uses always apache/airflow:master as source of files This made it impossible to test how the Kubernetes GitSync test will behave when merged. The git sync should always be done with the original repo/branch or from the TRAVIS_BRANCH if this is a push build > Kubernetes Git test uses always apache/airflow:master as source of files > > > Key: AIRFLOW-6736 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6736 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Priority: Major > Fix For: 2.0.0 > > > This makes it impossible to test how the Kubernetes GitSync test will behave > when merged. The git sync should always be done with the original repo/branch > or from the TRAVIS_BRANCH if this is a push build -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6736) Kubernetes Git test uses always apache/airflow:master as source of files
[ https://issues.apache.org/jira/browse/AIRFLOW-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030964#comment-17030964 ] ASF GitHub Bot commented on AIRFLOW-6736: - potiuk commented on pull request #7368: [AIRFLOW-6736] Fix the repo/branch that is used in PRs for git sync URL: https://github.com/apache/airflow/pull/7368 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: us...@infra.apache.org > Kubernetes Git test uses always apache/airflow:master as source of files > > > Key: AIRFLOW-6736 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6736 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Priority: Major > > This makes it impossible to test how the Kubernetes GitSync test will behave > when merged. The git sync should always be done with the original repo/branch > or from the TRAVIS_BRANCH if this is a push build -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6736) Kubernetes Git test uses always apache/airflow:master as source of files
[ https://issues.apache.org/jira/browse/AIRFLOW-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030730#comment-17030730 ] ASF GitHub Bot commented on AIRFLOW-6736: - potiuk commented on pull request #7368: [AIRFLOW-6736] Fix the repo/branch that is used in PRs for git sync URL: https://github.com/apache/airflow/pull/7368 Kubernetes Git test uses always apache/airflow:master as source of files This made it impossible to test how the Kubernetes GitSync test will behave when merged. The git sync should always be done with the original repo/branch or from the TRAVIS_BRANCH if this is a push build --- Issue link: WILL BE INSERTED BY [boring-cyborg](https://github.com/kaxil/boring-cyborg) Make sure to mark the boxes below before creating PR: [x] - [x] Description above provides context of the change - [x] Commit message/PR title starts with `[AIRFLOW-]`. AIRFLOW- = JIRA ID* - [x] Unit tests coverage for changes (not needed for documentation changes) - [x] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)" - [x] Relevant documentation is updated including usage instructions. - [x] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example). * For document-only changes commit message can start with `[AIRFLOW-]`. --- In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information. 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: us...@infra.apache.org > Kubernetes Git test uses always apache/airflow:master as source of files > > > Key: AIRFLOW-6736 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6736 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Priority: Major > > This makes it impossible to test how the Kubernetes GitSync test will behave > when merged. The git sync should always be done with the original repo/branch > or from the TRAVIS_BRANCH if this is a push build -- This message was sent by Atlassian Jira (v8.3.4#803005)
