July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24236: -------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Preferences: "automagically" use the oc that's shipped with the cdk3 > -------------------------------------------------------------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.Final > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4105: --------------------------------------- I have no idea when it will be done as there several tasks to be done before by other teams. So 11.1 is fine for me. > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 11.1.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier reassigned JBDS-4105: ------------------------------------- Assignee: (was: Aurélien Pupier) > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.1.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 7/18/17 1:26 PM: ------------------------------------------------------------- Moved to using a parser script local to the workspace so more portable. Here's the script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/jbosst... Iteratively adding more things to watch or ignore, and rolling out changes to more jobs, including base, server, and child-sites (central/EA). https://github.com/jbdevstudio/jbdevstudio-ci/commit/648af4b9c234c2f370ca... was (Author: nickboldt): Rolling out changes to more jobs, including base, server, and child-sites (central/EA). https://github.com/jbdevstudio/jbdevstudio-ci/commit/648af4b9c234c2f370ca... > 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.AM2 > > > 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, 8 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: ------------------------------------ Rolling out changes to more jobs, including base, server, and child-sites (central/EA). https://github.com/jbdevstudio/jbdevstudio-ci/commit/648af4b9c234c2f370ca... > 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.AM2 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24518) change github check frequency for CI builds from 8hrs to 20 mins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24518?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24518: ------------------------------------ Testing this for base and server before rolling out to the rest of the projects / jobs. https://github.com/jbdevstudio/jbdevstudio-ci/commit/648af4b9c234c2f370ca... > change github check frequency for CI builds from 8hrs to 20 mins > ---------------------------------------------------------------- > > Key: JBIDE-24518 > URL: https://issues.jboss.org/browse/JBIDE-24518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Currently the jbosstools-* component project builds run every 8hrs, with a nightly buildflow also triggering a rebuild. But since breaking changes are frequently NOT fixed quickly enough as devs cannot or will not kick their own builds, we need to implement a better strategy to check github for changes more often. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4105: -------------------------------- Assignee: Aurélien Pupier > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 11.1.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4105: ----------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.0.0.AM2) > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.1.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4105: ---------------------------------- Aurelien Pupier said: {quote}it was decided to do nothing short-term but middle-term there is one out of 2 chance to work on it Jeff, Andre and Roland Huss (among other) were in the call during which we decided that{quote} So I'm punting this to 11.1 > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM2 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3587) Uninstalling features from central is misleading if the feature is required in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3587?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3587. ---------------------------- Resolution: Rejected Closing as rejected based on Jan's comments. Jan, please reopen if you change your mind. > Uninstalling features from central is misleading if the feature is required in JBDS > ----------------------------------------------------------------------------------- > > Key: JBDS-3587 > URL: https://issues.jboss.org/browse/JBDS-3587 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Minor > Fix For: 11.0.0.GA > > > Since some features are both in default JBDS installation and in central, you can try uninstalling them from central. The uninstall wizard will show a strange cryptic message saying: > {noformat}"#the selected feature# cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled".{noformat} > That basically means nothing gets uninstalled, but it still requires a restart just for good measure. > The question is - Can it either be more clear that you can't just uninstall those features using central, or just allow it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017