[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-23889:
--------------------------------------
Assignee: Nick Boldt
> jbosstools-composite-install_master is a spam bomb
> --------------------------------------------------
>
> Key: JBIDE-23889
> URL: https://issues.jboss.org/browse/JBIDE-23889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
>
> jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue.
> I've removed the re-run on failure block of the downstream job trigger as a temporary workaround.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-23889:
--------------------------------------
Summary: jbosstools-composite-install_master is a spam bomb
Key: JBIDE-23889
URL: https://issues.jboss.org/browse/JBIDE-23889
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Mickael Istria
Priority: Critical
jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue.
I've removed the re-run on failure block of the downstream job trigger as a temporary workaround.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBTIS-796) Unify versions of BPMN2 plugins
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-796?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-796:
-----------------------------------------
Also notice that the modeler.core feature is the first feature on the list in the following case
1. Help > Installation Details
2. Type 'bpmn2'
So, users will often report an issue with the wrong version.
> Unify versions of BPMN2 plugins
> -------------------------------
>
> Key: JBTIS-796
> URL: https://issues.jboss.org/browse/JBTIS-796
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: BPMN2
> Affects Versions: 4.3.1.Final
> Environment: JBDSIS 9.0.1.CR1
> Reporter: Tomáš Sedmík
> Assignee: Robert (Bob) Brodt
>
> I noticed there are BPMN2 plugins in two versions. For example:
> - org.eclipse.bpmn2.editor - 1.2.1.Final-v20160218-1950-B212
> - org.eclipse.bpmn2.modeler.core - 1.2.4.Final-v20160330-1625-B110
> [~bbrodt] Is that correct? IMHO all plugins of a single component should be in the same version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBTIS-796) Unify versions of BPMN2 plugins
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-796?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky reassigned JBTIS-796:
---------------------------------------
Resolution: (was: Won't Do)
Assignee: Robert (Bob) Brodt
Hmm... I still don't get it :( If it is completely different then why it is in one project?
Moreover, due to this two version we have to use the following version in the documentation
{code}
BPMN2 1.3.2.Final_1.3.1.Final
{code}
Note that this is also confusing for users.
> Unify versions of BPMN2 plugins
> -------------------------------
>
> Key: JBTIS-796
> URL: https://issues.jboss.org/browse/JBTIS-796
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: BPMN2
> Affects Versions: 4.3.1.Final
> Environment: JBDSIS 9.0.1.CR1
> Reporter: Tomáš Sedmík
> Assignee: Robert (Bob) Brodt
>
> I noticed there are BPMN2 plugins in two versions. For example:
> - org.eclipse.bpmn2.editor - 1.2.1.Final-v20160218-1950-B212
> - org.eclipse.bpmn2.modeler.core - 1.2.4.Final-v20160330-1625-B110
> [~bbrodt] Is that correct? IMHO all plugins of a single component should be in the same version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4253) Show warning for virtualbox component if virtualization is not enabled or cannot be detected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4253?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4253:
--------------------------------
Fix Version/s: 10.3.0.GA
> Show warning for virtualbox component if virtualization is not enabled or cannot be detected
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-4253
> URL: https://issues.jboss.org/browse/JBDS-4253
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.3.0.GA
>
>
> Current implementation shows errors and warning under item selected for installation.
> See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...].
> Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install.
> If Virtualization firmware status cannot be detected (windows 7) message should say:
> * Make sure hardware virtualization is enabled on your platform if supported to improve performance.
> if Hardware Virtualization is Disabled:
> * Please enable hardware virtualization for your platform to improve performance
> If Hardware Virtualization is Enabled, no message is required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month