[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23017:
-------------------------------
Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016, devex #120 September 2016)
> use sshfs to speed up publishing process
> -----------------------------------------
>
> Key: JBIDE-23017
> URL: https://issues.jboss.org/browse/JBIDE-23017
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM1
>
>
> Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org.
> If we could simply copy bits over sshfs, the process might be a lot faster than these times:
> {code}
> JBT coretests 1.1G: 59m20
> JBT core 1.2G: 64m23
> devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13
> devstudio (copy from local to www.qa) 3.1G: 6mins(?)
> {code}
> To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3903:
-----------------------------
Fix Version/s: 10.2.0.AM1
(was: 10.1.0.GA)
> Platform Installer does not Setup Docker Env-Vars
> -------------------------------------------------
>
> Key: JBDS-3903
> URL: https://issues.jboss.org/browse/JBDS-3903
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 10.0.0.Alpha1
> Environment: Windows
> Reporter: Thomas Mäder
> Assignee: Xavier Coulon
> Fix For: 10.2.0.AM1
>
>
> I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection.
> Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection.
> As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3879:
-----------------------------
Fix Version/s: 10.2.0.AM1
(was: 10.1.0.GA)
> AERI - Closing the 'configure projects' dialog disables enabled projects
> ------------------------------------------------------------------------
>
> Key: JBDS-3879
> URL: https://issues.jboss.org/browse/JBDS-3879
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: aeri, target-platform
> Affects Versions: 10.0.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160430-1625-B5264
> Build date: 20160430-1625
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: 10.2.0.AM1
>
> Attachments: after.png, before.png
>
>
> To recreate:
> * Navigate to: Preferences->General->Error Reporting
> * Open 'configure projects' dialog
> * Enable one or more projects, click on "Enable"
> * Open 'configure projects' dialog
> * Close the dialog (select the 'x' at upper right)
> * Open 'configure projects' dialog
> * Observe that the selections are now disabled
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23005:
---------------------------------------
Raised to critical because it is happening to me more often and I have to hard reset IDE (via terminal) and try again bcs even if I click on stop button, it does not stop for minutes.
> Server Adapter: Stuck on creating/publishing
> --------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM1
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23005:
----------------------------------
Priority: Critical (was: Major)
> Server Adapter: Stuck on creating/publishing
> --------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM1
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-900) Skip more drools tests when jira describing issue is not fixed
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/JBTIS-900?page=com.atlassian.jira.plugin.... ]
Tomas David updated JBTIS-900:
------------------------------
Description: Use the mechanism for skipping test when jira describing issue is not fixed for improve stability of drools test suite. (was: Use the mechanism for skipping test when jira describing issue is not fixed for better stability of drools test suite.)
> Skip more drools tests when jira describing issue is not fixed
> --------------------------------------------------------------
>
> Key: JBTIS-900
> URL: https://issues.jboss.org/browse/JBTIS-900
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: drools/ jBPM, QE
> Affects Versions: 4.4.0.Alpha1
> Reporter: Tomas David
> Assignee: Tomas David
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> Use the mechanism for skipping test when jira describing issue is not fixed for improve stability of drools test suite.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-900) Skip more drools tests when jira describing issue is not fixed
by Tomas David (JIRA)
Tomas David created JBTIS-900:
---------------------------------
Summary: Skip more drools tests when jira describing issue is not fixed
Key: JBTIS-900
URL: https://issues.jboss.org/browse/JBTIS-900
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: drools/ jBPM, QE
Affects Versions: 4.4.0.Alpha1
Reporter: Tomas David
Assignee: Tomas David
Priority: Minor
Fix For: 4.4.0.Alpha1
Use the mechanism for skipping test when jira describing issue is not fixed for better stability of drools test suite.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months