July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3981) Build a new update site that includes only the content in devstudio, not including dependencies in common with RHSCL and devstudio

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3981: -------------------------------- Summary: Build a new update site that includes only the content in devstudio, not including dependencies in common with RHSCL and devstudio Key: JBDS-3981 URL: https://issues.jboss.org/browse/JBDS-3981 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build, updatesite Affects Versions: 10.1.0.AM2 Reporter: Nick Boldt Assignee: Nick Boldt update site will be called something like devstudio-{version}-updatesite-javaee.zip, assuming we call the rpm something like devstudio-javaee -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22847: ------------------------------------ Option 1: fix the problem Option 2: have the job throw a warning, not an error/failure when it can't find the bz link, and simply move on. > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22847: ------------------------------------ So, https://issues.jboss.org/browse/ERT-362 is created fine, but has no link back to http://bugs.eclipse.org/498440 Could be JIRA api changed? > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22847: ------------------------------- Description: 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... was:it looks like the jiras created after ERT-355 are missing remote link which is causing the job to fail. > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22847: ---------------------------------- Assignee: Nick Boldt > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22847: ------------------------------- Fix Version/s: 4.4.1.AM3 > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22847: ------------------------------- Story Points: 3 Sprint: devex #118 July 2016 > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22825) Forge New and Noteworthy for 4.4.1.AM2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22825?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22825: ----------------------------------------- Thanks Jeff, you're awesome > Forge New and Noteworthy for 4.4.1.AM2 > -------------------------------------- > > Key: JBIDE-22825 > URL: https://issues.jboss.org/browse/JBIDE-22825 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.1.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22849) Update Hibernate Tools dependencies to 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22849?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-22849: ------------------------------ Fix Version/s: 4.4.1.AM3 > Update Hibernate Tools dependencies to 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22849 > URL: https://issues.jboss.org/browse/JBIDE-22849 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM2 > Reporter: Koen Aers > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22849) Update Hibernate Tools dependencies to 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22849?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-22849: --------------------------------- Assignee: Koen Aers > Update Hibernate Tools dependencies to 4.3.5.Final, 5.0.1.Final, 5.1.0.Beta2 and 5.2.0.Alpha3 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22849 > URL: https://issues.jboss.org/browse/JBIDE-22849 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2016