[jira] [Commented] (AIRFLOW-116) Surface Airflow Version On Webservers

2016-05-16 Thread Siddharth Anand (JIRA)

[ 
https://issues.apache.org/jira/browse/AIRFLOW-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285002#comment-15285002
 ] 

Siddharth Anand commented on AIRFLOW-116:
-

[this|http://stackoverflow.com/a/7071358/1110993] seems like a good way to 
specify versions. We currently have it specified (and duplicated in 2 places : 
both setup.py and init.py

> Surface Airflow Version On Webservers
> -
>
> Key: AIRFLOW-116
> URL: https://issues.apache.org/jira/browse/AIRFLOW-116
> Project: Apache Airflow
>  Issue Type: Task
>  Components: webserver
>Reporter: Dan Davydov
>Assignee: Siddharth Anand
>Priority: Minor
>
> Surface Airflow Version On Webservers
> Why?
> Figuring out what version webservers are running requires sshing to the 
> webservers which isn't very sane (and not everyone has permissions to do 
> this).
> Success:
> Surface the current airflow version in the webserver (bonus points if the git 
> sha of the airflow code is shown too although this could be hacky), either on 
> every page as a static element or on a dedicated settings page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (AIRFLOW-116) Surface Airflow Version On Webservers

2016-05-16 Thread Siddharth Anand (JIRA)

[ 
https://issues.apache.org/jira/browse/AIRFLOW-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284978#comment-15284978
 ] 

Siddharth Anand commented on AIRFLOW-116:
-

I looked for places where __version__ is referenced. I saw the not in setup.py 
that we manually keep the airflow.__version__ in sync, which I'm not sure how 
to interpret. 

{quote}
(venv) sid-as-mbp:airflow siddharth$ grep -ri __version__ . | grep -v Binary | 
grep airflow
grep: ./airflow/www/static/docs: No such file or directory
./airflow/__init__.py:__version__ = "1.7.0"
./airflow/bin/cli.py:print(settings.HEADER + "  v" + airflow.__version__)
./airflow/www/views.py:pre_subtitle=settings.HEADER + "  v" + 
airflow.__version__,
./setup.py:# Kept manually in sync with airflow.__version__
{quote}

> Surface Airflow Version On Webservers
> -
>
> Key: AIRFLOW-116
> URL: https://issues.apache.org/jira/browse/AIRFLOW-116
> Project: Apache Airflow
>  Issue Type: Task
>  Components: webserver
>Reporter: Dan Davydov
>Assignee: Siddharth Anand
>Priority: Minor
>
> Surface Airflow Version On Webservers
> Why?
> Figuring out what version webservers are running requires sshing to the 
> webservers which isn't very sane (and not everyone has permissions to do 
> this).
> Success:
> Surface the current airflow version in the webserver (bonus points if the git 
> sha of the airflow code is shown too although this could be hacky), either on 
> every page as a static element or on a dedicated settings page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (AIRFLOW-116) Surface Airflow Version On Webservers

2016-05-16 Thread Chris Riccomini (JIRA)

[ 
https://issues.apache.org/jira/browse/AIRFLOW-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284648#comment-15284648
 ] 

Chris Riccomini commented on AIRFLOW-116:
-

[This|http://stackoverflow.com/questions/2058802/how-can-i-get-the-version-defined-in-setup-py-setuptools-in-my-package]
 looks like a better solution. Uses the {{__version__}} variable in 
{{__init__.py}}.

> Surface Airflow Version On Webservers
> -
>
> Key: AIRFLOW-116
> URL: https://issues.apache.org/jira/browse/AIRFLOW-116
> Project: Apache Airflow
>  Issue Type: Task
>  Components: webserver
>Reporter: Dan Davydov
>Assignee: Siddharth Anand
>Priority: Minor
>
> Surface Airflow Version On Webservers
> Why?
> Figuring out what version webservers are running requires sshing to the 
> webservers which isn't very sane (and not everyone has permissions to do 
> this).
> Success:
> Surface the current airflow version in the webserver (bonus points if the git 
> sha of the airflow code is shown too although this could be hacky), either on 
> every page as a static element or on a dedicated settings page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)