[JBoss JIRA] (JBIDE-25315) Include Fuse CI job update for job configuration update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25315?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25315:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.2.Final)
> Include Fuse CI job update for job configuration update
> -------------------------------------------------------
>
> Key: JBIDE-25315
> URL: https://issues.jboss.org/browse/JBIDE-25315
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: fusetools
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
> Attachments: image-2017-11-02-09-23-36-305.png
>
>
> the CI jobs on Fuse Ci are often not synchronized with modifications done on other jboss tools project such as TARGET_PLATFORM version.
> for instance today again:
> !image-2017-11-02-09-23-36-305.png|thumbnail!
> it would be useful to include the update of the FUSE CI jobs in the process to update the jobs
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24897 at 1/16/18 10:06 AM:
--------------------------------------------------------------
[~jeffmaury] The issue building on windows [1] will be solved later today. Geetika needs to rebase her PR [2] to the latest changes in master.
[1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i...
[2] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/p...
Also, I'm seeing itest failures in the latest builds [3]:
[3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too?
Options for inclusion:
* in JBT as an optional install? (if so, which category?)
* in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?)
* in devstudio as optional install? (if so, which category?)
* in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB)
* in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... )
was (Author: nickboldt):
[~jeffmaury] The issue building on windows [1] will be solved later today. Geetika needs to rebase her PR [2] to the latest changes in master.
[1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i...
[2] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/p...
Also, I'm seeing itest failures in the latest builds [3]:
[3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too?
Options for inclusion:
* in JBT as an optional install? (if so, which category?)
* in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?)
* in devstudio as optional install? (if so, which category?)
* in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB)
* in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... )
> 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24897 at 1/16/18 10:05 AM:
--------------------------------------------------------------
[~jeffmaury] The issue building on windows [1] will be solved later today. Geetika needs to rebase her PR [2] to the latest changes in master.
[1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i...
[2] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/p...
Also, I'm seeing itest failures in the latest builds [3]:
[3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too?
Options for inclusion:
* in JBT as an optional install? (if so, which category?)
* in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?)
* in devstudio as optional install? (if so, which category?)
* in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB)
* in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... )
was (Author: nickboldt):
[~jeffmaury] The issue building on windows [1] should now be solved. Can you take another look?
[1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i...
Also, I'm seeing itest failures in the latest builds [2]:
[2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too?
Options for inclusion:
* in JBT as an optional install? (if so, which category?)
* in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?)
* in devstudio as optional install? (if so, which category?)
* in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB)
* in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... )
> 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24897:
------------------------------------
[~jeffmaury] The issue building on windows [1] should now be solved. Can you take another look?
[1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i...
Also, I'm seeing itest failures in the latest builds [2]:
[2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too?
Options for inclusion:
* in JBT as an optional install? (if so, which category?)
* in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?)
* in devstudio as optional install? (if so, which category?)
* in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB)
* in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... )
> 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