[jira] [Commented] (AIRFLOW-6344) CI builds with TAG fail with "unknown revision or path not in the working tree"
[ https://issues.apache.org/jira/browse/AIRFLOW-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036312#comment-17036312 ] ASF subversion and git services commented on AIRFLOW-6344: -- Commit 413f9613755bd3ab54c317e73b488d51fa23c30a in airflow's branch refs/heads/v1-10-test from Ash Berlin-Taylor [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=413f961 ] [AIRFLOW-6344] Fix travis CI for tag builds (#7411) Don't try to find changed files unless we are building a pull request. This only caused a problem on build of tags, but we were also doing this for master/branch builds, but it was always saying finding no files changed. By checking this early we can make the other conditions in this function simpler. (cherry picked from commit 67463c3d8e5fe1618117244364d8a49f80536820) > CI builds with TAG fail with "unknown revision or path not in the working > tree" > --- > > Key: AIRFLOW-6344 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6344 > Project: Apache Airflow > Issue Type: Improvement > Components: ci >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Assignee: Ash Berlin-Taylor >Priority: Major > Fix For: 1.10.10 > > > See for example here: unknown revision or path not in the working tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6344) CI builds with TAG fail with "unknown revision or path not in the working tree"
[ https://issues.apache.org/jira/browse/AIRFLOW-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036308#comment-17036308 ] ASF subversion and git services commented on AIRFLOW-6344: -- Commit 67463c3d8e5fe1618117244364d8a49f80536820 in airflow's branch refs/heads/master from Ash Berlin-Taylor [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=67463c3 ] [AIRFLOW-6344] Fix travis CI for tag builds (#7411) Don't try to find changed files unless we are building a pull request. This only caused a problem on build of tags, but we were also doing this for master/branch builds, but it was always saying finding no files changed. By checking this early we can make the other conditions in this function simpler. > CI builds with TAG fail with "unknown revision or path not in the working > tree" > --- > > Key: AIRFLOW-6344 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6344 > Project: Apache Airflow > Issue Type: Improvement > Components: ci >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Assignee: Ash Berlin-Taylor >Priority: Major > > See for example here: unknown revision or path not in the working tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6344) CI builds with TAG fail with "unknown revision or path not in the working tree"
[ https://issues.apache.org/jira/browse/AIRFLOW-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036307#comment-17036307 ] ASF GitHub Bot commented on AIRFLOW-6344: - ashb commented on pull request #7411: [AIRFLOW-6344] Fix travis CI for tag builds URL: https://github.com/apache/airflow/pull/7411 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 > CI builds with TAG fail with "unknown revision or path not in the working > tree" > --- > > Key: AIRFLOW-6344 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6344 > Project: Apache Airflow > Issue Type: Improvement > Components: ci >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Assignee: Ash Berlin-Taylor >Priority: Major > > See for example here: unknown revision or path not in the working tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6344) CI builds with TAG fail with "unknown revision or path not in the working tree"
[ https://issues.apache.org/jira/browse/AIRFLOW-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036201#comment-17036201 ] ASF GitHub Bot commented on AIRFLOW-6344: - ashb commented on pull request #7411: [AIRFLOW-6344] Fix travis CI for tag builds URL: https://github.com/apache/airflow/pull/7411 Don't try to find changed files unless we are building a pull request. This only caused a problem on build of tags, but we were also doing this for master/branch builds, but it was always saying finding no files changed. By checking this early we can make the other conditions in this function simpler. --- 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 > CI builds with TAG fail with "unknown revision or path not in the working > tree" > --- > > Key: AIRFLOW-6344 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6344 > Project: Apache Airflow > Issue Type: Improvement > Components: ci >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Assignee: Ash Berlin-Taylor >Priority: Major > > See for example here: unknown revision or path not in the working tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
