January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24897: ------------------------------------ FWIW, if we don't get this completed before (or slightly after code freeze), the next window for GA delivery is in April 24, via the next train, in 12 weeks. But if you want to include it earlier as part of a JBoss Tools milestone release, those are released to the public every 3 weeks. Calendar as always is here: http://bitly.com/rhdtrain > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24897 at 1/17/18 10:23 AM: -------------------------------------------------------------- "The hard part is that we cannot say if it works at least partially or not, because the backend is down. So we cannot confirm for sure." Options: a) the back end server returns miraculously before 8:30am EST on Thursday (time of the the 5x5 call), QE confirms it works, and I pull a Hail Mary and do all the work to add this into JBT/devstudio/central a day after code freeze. Staging build for QE review is a few hours late, but DOES include the fabric8 analytics. QE signoff planned for next Tuesday may be delayed to Wed, but we still have 2-3 days to complete the release after that. b) the above stars (in option a) do not align, and fabric8 analytics feature is not included in JBT/devstudio/Central c) even without confirming if it's broken or working, we include it *today* as a Tech Preview and cross fingers that when the back end comes back up, things DO work as intended. If not, well, it's a Tech Preview so it's allowed to set your computer on fire. It's not like we're releasing an Intel CPU *<cough>* Spectre *</cough>*. was (Author: nickboldt): "The hard part is that we cannot say if it works at least partially or not, because the backend is down. So we cannot confirm for sure." Options: a) the back end server returns miraculously before 8:30am EST on Thursday (time of the the 5x5 call), QE confirms it works, and I pull a Hail Mary and do all the work to add this into JBT/devstudio/central a day after code freeze. Staging build for QE review is a few hours late, but DOES include the fabric8 analytics. QE signoff planned for next Tuesday may be delayed to Wed, but we still have 2-3 days to complete the release after that. b) the above stars (in option a) do not align, and fabric8 analytics feature is not included in JBT/devstudio/Central c) even without confirming if it's broken or working, we include it *today* as a Tech Preview and cross fingers that when the back end comes back up, things DO work as intended. If not, well, it's a Tech Preview so it's allowed to set your computer on fire. It's not like we're releasing an Intel CPU *cough* Spectre */cough*. > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25559) Add itests to cover wrong credentials passed into cdk via server adapter

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25559?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25559: ---------------------------------- Issue Type: Feature Request (was: Enhancement) > Add itests to cover wrong credentials passed into cdk via server adapter > ------------------------------------------------------------------------ > > Key: JBIDE-25559 > URL: https://issues.jboss.org/browse/JBIDE-25559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.2.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-24897: ------------------------------------ [~nickboldt] c) is the worst option we should even not consider doing (maybe less work). I do not believe in miracles and we should avoid surprises. I would rather see proper planning and execution in the next release train. I think there is a lot of to be improved in the process. > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4665) Enable m2e logging

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4665?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4665: ---------------------------------- So, you're asking that we include *m2e - slf4j over logback logging (Optional) 1.8.1.20170728-1531* in the list of pre-installed, out-of-the-box features that come with a devstudio installation? We could consider this for 11.3. [~jeffmaury] WDYT? > Enable m2e logging > ------------------ > > Key: JBDS-4665 > URL: https://issues.jboss.org/browse/JBDS-4665 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Affects Versions: 11.1.0.GA > Reporter: Vsevolod Golovanov > Fix For: 11.x > > > I used to enable it manually, by installing m2e - slf4j over logback logging (Optional). (For some reason, this doesn't work with JBDS 11.1: https://stackoverflow.com/questions/48276549/enable-m2e-logging-in-jboss-... ) > It would be much more convenient if m2e logging came bundled with JBDS. It does with Eclipse for Java EE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4665) Enable m2e logging

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4665?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4665: -------------------------------- Assignee: Nick Boldt > Enable m2e logging > ------------------ > > Key: JBDS-4665 > URL: https://issues.jboss.org/browse/JBDS-4665 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Affects Versions: 11.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Nick Boldt > Fix For: 11.x > > > I used to enable it manually, by installing m2e - slf4j over logback logging (Optional). (For some reason, this doesn't work with JBDS 11.1: https://stackoverflow.com/questions/48276549/enable-m2e-logging-in-jboss-... ) > It would be much more convenient if m2e logging came bundled with JBDS. It does with Eclipse for Java EE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4665) Enable m2e logging

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4665?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4665: ----------------------------- Fix Version/s: 11.x > Enable m2e logging > ------------------ > > Key: JBDS-4665 > URL: https://issues.jboss.org/browse/JBDS-4665 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Affects Versions: 11.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Nick Boldt > Fix For: 11.x > > > I used to enable it manually, by installing m2e - slf4j over logback logging (Optional). (For some reason, this doesn't work with JBDS 11.1: https://stackoverflow.com/questions/48276549/enable-m2e-logging-in-jboss-... ) > It would be much more convenient if m2e logging came bundled with JBDS. It does with Eclipse for Java EE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25588) CDK server adapter timeouts during starting with JDK9

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25588?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25588: ---------------------------------- Priority: Blocker (was: Critical) > CDK server adapter timeouts during starting with JDK9 > ----------------------------------------------------- > > Key: JBIDE-25588 > URL: https://issues.jboss.org/browse/JBIDE-25588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.2.Final > Environment: Fedora 26 > java-9-openjdk-9.0.1.11-4.fc26.x86_64 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.x > > > CDK server adapter remains in state starting after CDK is started properly (in console you can see all steps passed without problem), one can connect to openshift via browser. Also, SSL untrusted certificate was accepted. There is running job: Starting Container Developer Environment 3.2+ Preparing launch delegate...: Launching delegate... > Adapter will just timeout eventually. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25588) CDK server adapter timeouts during starting with JDK9

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25588?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25588: ---------------------------------- Priority: Critical (was: Blocker) > CDK server adapter timeouts during starting with JDK9 > ----------------------------------------------------- > > Key: JBIDE-25588 > URL: https://issues.jboss.org/browse/JBIDE-25588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.2.Final > Environment: Fedora 26 > java-9-openjdk-9.0.1.11-4.fc26.x86_64 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.x > > > CDK server adapter remains in state starting after CDK is started properly (in console you can see all steps passed without problem), one can connect to openshift via browser. Also, SSL untrusted certificate was accepted. There is running job: Starting Container Developer Environment 3.2+ Preparing launch delegate...: Launching delegate... > Adapter will just timeout eventually. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24897: ------------------------------------ "The hard part is that we cannot say if it works at least partially or not, because the backend is down. So we cannot confirm for sure." Options: a) the back end server returns miraculously before 8:30am EST on Thursday (time of the the 5x5 call), QE confirms it works, and I pull a Hail Mary and do all the work to add this into JBT/devstudio/central a day after code freeze. Staging build for QE review is a few hours late, but DOES include the fabric8 analytics. QE signoff planned for next Tuesday may be delayed to Wed, but we still have 2-3 days to complete the release after that. b) the above stars (in option a) do not align, and fabric8 analytics feature is not included in JBT/devstudio/Central c) even without confirming if it's broken or working, we include it *today* as a Tech Preview and cross fingers that when the back end comes back up, things DO work as intended. If not, well, it's a Tech Preview so it's allowed to set your computer on fire. It's not like we're releasing an Intel CPU *cough* Spectre */cough*. > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 January 2018