June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24554) Fix maven integration tests for Oxygen

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24554?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-24554: --------------------------------------- PR is merged > Fix maven integration tests for Oxygen > -------------------------------------- > > Key: JBIDE-24554 > URL: https://issues.jboss.org/browse/JBIDE-24554 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24554) Fix maven integration tests for Oxygen

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24554?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24554. --------------------------------- > Fix maven integration tests for Oxygen > -------------------------------------- > > Key: JBIDE-24554 > URL: https://issues.jboss.org/browse/JBIDE-24554 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24002) CDK 3 integration with Devstudio - CI preparation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24002?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24002 at 6/20/17 3:32 AM: ---------------------------------------------------------------- After resolving the last related issue JBIDE-24005 this one can be resolved as well, since the testing pipeline process for CDK into devstudio is done. was (Author: odockal): After resolving last related issue JBIDE-24005 this one can be resolved as well, since the testing pipeline process for CDK into devstudio is done. > CDK 3 integration with Devstudio - CI preparation > ------------------------------------------------- > > Key: JBIDE-24002 > URL: https://issues.jboss.org/browse/JBIDE-24002 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk, integration_tests, jenkins > Fix For: 4.5.0.AM1 > > > Top jira covering jiras that include complete CI structure for CDK3 integration to devstudio testing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24002) CDK 3 integration with Devstudio - CI preparation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24002?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24002: ---------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > CDK 3 integration with Devstudio - CI preparation > ------------------------------------------------- > > Key: JBIDE-24002 > URL: https://issues.jboss.org/browse/JBIDE-24002 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk, integration_tests, jenkins > Fix For: 4.5.0.AM1 > > > Top jira covering jiras that include complete CI structure for CDK3 integration to devstudio testing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4440. ------------------------------ Verified, TP includes sources. > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1073) Add versions for devstudio-is components in a standalone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1073?page=com.atlassian.jira.plugin... ] Paul Leacu closed JBTIS-1073. ----------------------------- Resolution: Won't Do This listed components to install are really just the product categories. The installer is not exposed to sub-component version numbers. We don't want to promote a product category component over the product category itself as it could get confusing for the user. > Add versions for devstudio-is components in a standalone installer > ------------------------------------------------------------------ > > Key: JBTIS-1073 > URL: https://issues.jboss.org/browse/JBTIS-1073 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.3.0.GA > > Attachments: devstudio-is-installer-components.png > > > Add versions for devstudio-is components in a standalone installer on 'Summary Information' page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24561 at 6/19/17 3:44 PM: ------------------------------------------------------------- Problem could in fact be the text-finder plugin. I've removed that config to see if the 80 mins are still needed. {code} - <hudson.plugins.textfinder.TextFinderPublisher plugin="text-finder(a)1.10"> - <regexp>.+(BUILD FAILED|Cannot complete the install|conflicting dependency|Connection refused|exec returned: 13).+</regexp> - <succeedIfFound>false</succeedIfFound> - <unstableIfFound>true</unstableIfFound> - <alsoCheckConsoleOutput>true</alsoCheckConsoleOutput> - </hudson.plugins.textfinder.TextFinderPublisher> {code} After removing this, jobs are 80 mins faster. was (Author: nickboldt): Problem could in fact be the text-finder plugin. I've removed that config to see if the 80 mins are still needed. {code} - <hudson.plugins.textfinder.TextFinderPublisher plugin="text-finder(a)1.10"> - <regexp>.+(BUILD FAILED|Cannot complete the install|conflicting dependency|Connection refused|exec returned: 13).+</regexp> - <succeedIfFound>false</succeedIfFound> - <unstableIfFound>true</unstableIfFound> - <alsoCheckConsoleOutput>true</alsoCheckConsoleOutput> - </hudson.plugins.textfinder.TextFinderPublisher> {code} > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24561: ------------------------------------ If this is the problem, then perhaps we could experiment with this plugin? https://plugins.jenkins.io/log-parser > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24561: ------------------------------------ Problem could in fact be the text-finder plugin. I've removed that config to see if the 80 mins are still needed. {code} - <hudson.plugins.textfinder.TextFinderPublisher plugin="text-finder(a)1.10"> - <regexp>.+(BUILD FAILED|Cannot complete the install|conflicting dependency|Connection refused|exec returned: 13).+</regexp> - <succeedIfFound>false</succeedIfFound> - <unstableIfFound>true</unstableIfFound> - <alsoCheckConsoleOutput>true</alsoCheckConsoleOutput> - </hudson.plugins.textfinder.TextFinderPublisher> {code} > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24561: ---------------------------------- Assignee: Nick Boldt > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017