-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Clean local tags in tag_providers for network issues with Github #34951
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
Conversation
|
@eladkal @ephraimbuddy handling this like this as per offline discussions. Do let me know what you feel cc @potiuk |
|
LGTM. @eladkal ? |
| git push $remote "${tags[@]}" | ||
| if git push $remote "${tags[@]}"; then | ||
| echo "Tags pushed successfully" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally the script outputs:
➜ airflow git:(main) ./dev/provider_packages/tag_providers.sh
Enumerating objects: 82, done.
Counting objects: 100% (82/82), done.
Delta compression using up to 10 threads
Compressing objects: 100% (82/82), done.
Writing objects: 100% (82/82), 3.33 KiB | 682.00 KiB/s, done.
Total 82 (delta 79), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (79/79), done.
To https://github.com/apache/airflow.git
* [new tag] providers-airbyte/3.4.0rc1 -> providers-airbyte/3.4.0rc1
* [new tag] providers-alibaba/2.6.0rc1 -> providers-alibaba/2.6.0rc1
* [new tag] providers-amazon/8.8.0rc1 -> providers-amazon/8.8.0rc1
* [new tag] providers-apache-beam/5.3.0rc1 -> providers-apache-beam/5.3.0rc1
* [new tag] providers-apache-cassandra/3.3.0rc1 -> providers-apache-cassandra/3.3.0rc1
* [new tag] providers-apache-drill/2.5.0rc1 -> providers-apache-drill/2.5.0rc1
* [new tag] providers-apache-druid/3.6.0rc1 -> providers-apache-druid/3.6.0rc1
* [new tag] providers-apache-flink/1.2.0rc1 -> providers-apache-flink/1.2.0rc1
* [new tag] providers-apache-hdfs/4.2.0rc1 -> providers-apache-hdfs/4.2.0rc1
* [new tag] providers-apache-hive/6.2.0rc1 -> providers-apache-hive/6.2.0rc1
* [new tag] providers-apache-impala/1.2.0rc1 -> providers-apache-impala/1.2.0rc1
* [new tag] providers-apache-kafka/1.2.0rc1 -> providers-apache-kafka/1.2.0rc1
If I read this right now the script will not output this but Tags pushed successfully ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point, the standard output was being compromised. Can you try with the latest commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the original code was correct (and simpler).
if git push $remote "${tags[@]}"; then
would still output the stdout/stderr to terminal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure if the output is present then lets.
I will test it with next release
hussein-awala
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one!
0dd4113 to
464cca4
Compare
) (cherry picked from commit 1e9c807)
As reported on slack, sometimes due to network connectivity issues with Github, our tag_providers.sh script creates tags locally with errors like:
in cases when the tag could not be pushed. This is irritating because now the release team has to manually delete these tags. Adding ability to do this using an env variable. The default behaviour here is that the tags will be cleaned locally.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.