[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.
by Bob Davis (JIRA)
[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ]
Bob Davis commented on JBDS-3871:
---------------------------------
Would it not make sense to just copy the text as written on the developers.redhat.com login page?
https://developers.redhat.com/auth/realms/rhd/protocol/openid-connect/aut...
"You can use your existing Red Hat Developer Program, Red Hat Customer Portal, OpenShift Online, or other Red Hat account to log in."
Bob
> installer credentials misleading/incomplete information.
> --------------------------------------------------------
>
> Key: JBDS-3871
> URL: https://issues.jboss.org/browse/JBDS-3871
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Win 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 11.2.0.AM3
>
>
> There are several problems a with the information on the platform installer's login screen:
> # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process.
> # The register link points to the login page, not the register page.
> # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed."
> # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription.
> The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access."
> Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials".
> During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet.
> Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account.
> Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software.
> Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer..
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
by Bob Davis (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Bob Davis commented on JBIDE-24897:
-----------------------------------
If we get confirmation that it does not work, then we should not include it.
However, in light of your earlier comments, [~psrna], if it does work, then it should be an optional installation in DevStudio (since it's in tech preview) and once it's GA, it should be in the default package.
The status as an optional install in JBT still stands - assuming it works.
I thought we had confirmation that it was working yesterday, is that not right?
> 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
[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 edited comment on JBIDE-24897 at 1/17/18 9:32 AM:
-------------------------------------------------------------
{quote}
Regarding the Jenkins job not running UI tests... not sure why.
{quote}
I see a commit disabling unit tests. Plugin API has changed and the tests were not adjusted, but instead disabled to pass the build. This should not happen again.
I've had a recent chat with [~gbatra] and there are several blocking issues to be fixed: e.g: (LSP not working: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i..., many URL's used are to be changed, etc.)
I want to point out, that bugs not fixed until Today probably won't get into Devstudio 11.2.GA, because devstudio code freeze is Today and we are building Tomorrow.
I'm concerned that this plugin does not meet Devstudio QE release criteria even to be release as a Tech Preview, because it just won't work properly.
[~rpdavis] can you please clarify how we proceed with this one? Thx.
was (Author: psrna):
{quote}
Regarding the Jenkins job not running UI tests... not sure why.
{quote}
I see a commit disabling unit tests. Plugin API has changed and the tests were not adjusted, but instead disabled to pass the build. This should not happen again.
I've had a recent chat with [~gbatra] and there are several blocking issues to be fixed: e.g: (LSP not working: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i..., many URL's used are to be changed, etc.)
I want to point out, that bugs not fixed until Today probably won't get into Devstudio 11.2.GA, because devstudio code freeze is Today and we are building Tomorrow.
I'm concerned that this plugin does not meet Devstudio QE release criteria even to be release as a Tech Preview, because it just won't work properly.
[~rpdavis] can we please clarify how we proceed with this one? Thx.
> 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