[JBoss JIRA] (JBIDE-22105) Update AERI Server to 2.0
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22105?page=com.atlassian.jira.plugi... ]
Marcel Bruch resolved JBIDE-22105.
----------------------------------
Fix Version/s: 4.3.x
Resolution: Done
The server was rolled out. Reviewers base URL is https://redhat.ctrlflow.com/reviewers/#!/
Tested that the server still receives error reports from Eclipse clients.
> Update AERI Server to 2.0
> -------------------------
>
> Key: JBIDE-22105
> URL: https://issues.jboss.org/browse/JBIDE-22105
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aeri
> Reporter: Marcel Bruch
> Priority: Minor
> Fix For: 4.3.x
>
>
> I'd like to roll out an update of the aeri server.
> Notable changes on for Eclipse clients:
> This update changes the sever responses send back to clients on submission of a problem report. The response format is compatible with the Eclipse AERI integration 1.100+
> No breaking changes.
> Most notable changes on the server's web-site:
> * The UI changed from AngularJS to Vaadin
> * Improved JIRA integration.
> * Improved customization of email digests and bug creation templates
> * Fine-grained control over server-responses
> * Auto-Actions for automated problem state transitions on problem state changes (e.g., _number-of-reporters > 100 && status=open --> Set Severity to major._ or _If new error reports arrived in with bundle.version > 1.2.3 --> set status=reopen.
> Details will be announced separately.
> In this bug I'm looking for a process *how* to perform an server-update for JBoss Tools.
> I'd like to know who needs to be involved in case of major/minor updates? Is some testing / approval from QE required before an update can go live?
> My proposed way of doing a major update:
> * Copy the current database.
> * Set up a sandbox instance running on the copied database
> * Create a JIRA issue for the planned update.
> * After approval by QE switch testing instance to production
> FWIW, I don't plan to announce minor bugfixes and minor improvements (e.g., to duplicate detection) as long as they do have user-observable impact or lead to significant changes in the UI and workflows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22148:
------------------------------------
To quickly get tests passing again, I've applied this fix for now.
https://github.com/jbosstools/jbosstools-discovery/pull/330
We'll need to do the same for the other branches, unless we want to use a specific release (eg., 6.4.0.RELEASE).
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
> Affected jobs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22148:
-------------------------------
Description:
{code}
09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
{code}
So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
And we need to verify that the features we include in Central are still available on the new site.
Affected jobs:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
was:
{code}
09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
{code}
So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
And we need to verify that the features we include in Central are still available on the new site.
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
> Affected jobs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22148:
-------------------------------
Affects Version/s: 4.2.3.Final
4.1.2.Final
4.4.0.Alpha1
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-22148:
----------------------------------
Assignee: Nick Boldt
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22148:
------------------------------------
Looks like the current site [1] contains the three (3) features we need {code}
org.zeroturnaround.eclipse.feature.feature.jar 6.4.2.SR1
org.zeroturnaround.eclipse.m2e.feature.feature.jar 6.4.2.SR1
org.zeroturnaround.eclipse.wtp.feature.feature.jar 6.4.2.SR1
{code}
Affected releases:
https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/...
https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.2.x/...
https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.1.x/...
https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.0.x/... (not affected, uses different URL)
(and the same again for JBDS, too.)
We could also use an older RELEASE site [2], eg., 6.4.0.RELEASE [3].
[2] http://update.zeroturnaround.com/update-site-archive/
[3] http://update.zeroturnaround.com/update-site-archive/update-site-6.4.0.RE...
We could also report this upstream to Zeroturnaround to get them to set up a URL redirect:
* from http://update.zeroturnaround.com/update-site-jboss/
* to http://update.zeroturnaround.com/update-site/
> Zeroturnaround JRebel update site no longer exists; automated Central install broken
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.3.0.Final, 4.3.1.CR1
> Reporter: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3710) use brackets logo in icon for Developer Platform installer .exe
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3710.
---------------------------------
Resolution: Done
> use brackets logo in icon for Developer Platform installer .exe
> ---------------------------------------------------------------
>
> Key: JBDS-3710
> URL: https://issues.jboss.org/browse/JBDS-3710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: dpinstaller-new-icon-and-properties-2.png, dpinstaller-new-icon-and-properties.png, icons.png, RedHatDeveloperStudio_Logo_Installer.ico
>
>
> Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years