[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23889:
------------------------------------
If it's failing repeatedly, then you should look in the console to see WHY and maybe help fix it ... it's most likely a TP problem.
{code}
[p2.dir] Cannot complete the install because one or more required items could not be found.
[p2.dir] Software being installed: JBoss Tools Apache Cordova Simulator Tests Developer Resources 3.8.3.v20161201-1914 (org.jboss.tools.cordovasim.test.feature.source.feature.group 3.8.3.v20161201-1914)
[p2.dir] Missing requirement: BrowserSim 3.8.3.v20161201-1732 (org.jboss.tools.browsersim.ui 3.8.3.v20161201-1732) requires 'bundle org.eclipse.jetty.server [9.3.9,9.4.0)' but it could not be found
{code}
> 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
> Affects Versions: 4.4.3.AM2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.4.AM1
>
>
> 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23889:
------------------------------------
Yes, that's because this is the job that aggregates all the upstream changes from the jbosstools-* projects to determine if we need to rebuild the JBT and devstudio aggregates/products.
It's supposed to run frequently. Or as frequently as it sees changes in github upstream repos.
> 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
> Affects Versions: 4.4.3.AM2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.4.AM1
>
>
> 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-20529) Master JIRA for XML Validation Problems
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20529:
-------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.4.3.Final)
> Master JIRA for XML Validation Problems
> ---------------------------------------
>
> Key: JBIDE-20529
> URL: https://issues.jboss.org/browse/JBIDE-20529
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples, server
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: xtriage
> Fix For: 4.4.4.Final
>
>
> This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21593:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.3.Final)
> Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21593
> URL: https://issues.jboss.org/browse/JBIDE-21593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22, GTK 3.
> Reporter: Marián Labuda
> Labels: application_wizard, explorer, openshift_v3
> Fix For: 4.4.4.AM2
>
> Attachments: empty_project.png
>
>
> When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot
> !empty_project.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22375:
-------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.4.3.Final)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: jmx, openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.4.Final
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22075:
-------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> Confusing error message when trying to attach remote debugger to OS app run in debug mode
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: debugging, openshift_v3
> Fix For: 4.4.4.AM1
>
> Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png
>
>
> If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically.
> If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message
> When I am trying to run remote debugging of an application on OpenShift I get following error
> !!error-in-launching-remote-debugger.png! !
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *Steps to reproduce:*
> ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace.
> EXEC: Select "Restart in Debug" in context menu of server adapter.
> ASSERT: Server adapter is in state debugging ("[Debugging, Started]").
> EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging.
> RESULT: Error is shown.
> EXPECTED RESULT: The error message should tell you that there already is an instance running.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month