I'd like to contribute to jira-python. I cloned the repo and made my changes locally, now I need to install and test. However, every method I've used to install the package from a local directory has failed with the following:
Complete output from command python setup.py egg_info: Traceback (most recent call last): File "<string>", line 1, in <module> File "/Users/davidmcbride/projects/python_jira/jira/setup.py", line 201, in <module> **get_metadata(base_path, NAME, 'package_meta.py') File "/Users/davidmcbride/projects/python_jira/jira/setup.py", line 39, in get_metadata exec(code, scope) File "/Users/davidmcbride/projects/python_jira/jira/jira/package_meta.py", line 103, in <module> __version__ = get_version() File "/Users/davidmcbride/projects/python_jira/jira/jira/package_meta.py", line 38, in get_version version = base_version.base_version AttributeError: 'tuple' object has no attribute 'base_version'
I've tried 'pip install -e', 'easy_install', and 'python setup.py'. I also made sure that 'setuptools' was updated.
Obviously, people are contributing to jira-python, so I guess I just need to understand the workflow better.
Using OS X 10.11.6
I, too, would like to know the best way to do this, but here's what I did.
If anyone has anything better, PLEASE share! Thanks!!
I've gotten a little bit further, but am stuck again . . . the file test.local has this bit of instruction:
# Settings for using the Vagrant VM from atlassian
# (see https://developer.atlassian.com/static/connect/docs/latest/developing/developing-locally.html)
# a user "jira_user" with password "jira" needs to be created manually
The problem now is that the vagrant image is no longer available from Atlassian. They now seem to offer only a temporary cloud instance for testing:
I happen to have the vagrant image, but it seems that the tests have changed and they no longer work with the vagrant image.
Anyone have any insight here? Thanks!!
OK, getting a bit better at this, I think . . .
Would love to hear what @Sorin Sbarnea thinks about this
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs