[
https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-22847 at 7/28/16 2:14 PM:
-------------------------------------------------------------
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an
outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs
against older versions.
{code}
But I can create JIRAs with links.
So, I update to
https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz{code}
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from
https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from
https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from
https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e...
(from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from
jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages
(from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from
https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737...
(from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from
https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec...
(from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from
https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9...
(from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package
oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt,
oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get the above problem.
Solution: refactored the link creation thing (so it can be done for existing issues as
well as new ones) and fixed the payload expected for the post.
https://github.com/maxandersen/jiralint/commit/b53c03c55a9bd0112561e35731...
was (Author: nickboldt):
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an
outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs
against older versions.
{code}
But I can create JIRAs with links.
So, I update to
https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz{code}
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from
https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from
https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from
https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e...
(from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from
jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages
(from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from
https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737...
(from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from
https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec...
(from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from
https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9...
(from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package
oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt,
oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get:
{code}
[DEBUG] 498440 - Node.js "Relaunch" support - not acting as expected [JSDT,
General, [---]] {20160727T12:40:25} (1 day, 3:37:27.931356) ->
https://bugs.eclipse.org/498440
Query:
https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar...
[INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js
"Relaunch" support - not acting as expected
[DEBUG] {'project': {'key': 'ERT'}, 'priority':
{'name': 'Major'}, 'description': 'When selecting a current
running node process in the debug view.\n\nThere are a few options including
"Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that
relaunch should act any differently than terminate and relaunch, because without first
terminating the process, launching the node process will always result in a type of
"Error: listen EADDRINUSE".', 'components': [{'name':
'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels':
['bzira', 'General'], 'fixVersions': [], 'summary':
'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
[INFO] Created
https://issues.jboss.org/browse/ERT-369
Traceback (most recent call last):
File "bzira.py", line 496, in <module>
process(bug, createdbugs)
File "bzira.py", line 375, in process
jira.add_simple_link(newissue, object=link)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/client.py", line
1129, in add_simple_link
url, data=json.dumps(data))
File
"/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line
152, in post
return self.__verb('POST', url, **kwargs)
File
"/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line
145, in __verb
raise_on_error(response, verb=verb, **kwargs)
File
"/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line
55, in raise_on_error
r.status_code, error, r.url, request=request, response=r, **kwargs)
jira.exceptions.JIRAError: JiraError HTTP 400 url:
https://issues.jboss.org/rest/api/2/issue/ERT-369/remotelink details:
/tmp/jiraerror-EGuiSP.tmp
{code}
jbosstools-jiralint-bzira job fails to create new jiras
-------------------------------------------------------
Key: JBIDE-22847
URL:
https://issues.jboss.org/browse/JBIDE-22847
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Gorkem Ercan
Assignee: Nick Boldt
Fix For: 4.4.1.AM3
it looks like the jiras created after ERT-355 are missing remote link which is causing
the job to fail.
For example:
{code}
11:25:19 [INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org
- Node.js "Relaunch" support - not acting as expected
11:25:19 [DEBUG] {'project': {'key': 'ERT'}, 'priority':
{'name': 'Major'}, 'description': 'When selecting a current
running node process in the debug view.\n\nThere are a few options including
"Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that
relaunch should act any differently than terminate and relaunch, because without first
terminating the process, launching the node process will always result in a type of
"Error: listen EADDRINUSE".', 'components': [{'name':
'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels':
['bzira', 'General'], 'fixVersions': [], 'summary':
'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
11:25:19 [INFO] Created
https://issues.jboss.org/browse/ERT-362
11:25:19 Traceback (most recent call last):
11:25:19 File "bzira.py", line 496, in <module>
11:25:19 process(bug, createdbugs)
11:25:19 File "bzira.py", line 375, in process
11:25:19 jira.add_simple_link(newissue, object=link)
11:25:19 File
"/home/hudson/.local/lib/python2.6/site-packages/jira/client.py", line 1129, in
add_simple_link
11:25:19 url, data=json.dumps(data))
11:25:19 File
"/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line
152, in post
11:25:19 return self.__verb('POST', url, **kwargs)
11:25:19 File
"/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line
145, in __verb
11:25:19 raise_on_error(response, verb=verb, **kwargs)
11:25:19 File
"/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line
55, in raise_on_error
11:25:19 r.status_code, error, r.url, request=request, response=r, **kwargs)
11:25:19 jira.exceptions.JIRAError: JiraError HTTP 400 url:
https://issues.jboss.org/rest/api/2/issue/ERT-362/remotelink details:
/tmp/jiraerror-MrYBu8.tmp
11:25:19 Build step 'Execute shell' marked build as failure
{code}
--
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)