[JBoss JIRA] (JBIDE-16720) Allow easier access to openshift operations from jboss servers
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16720:
---------------------------------------------
A) Cool - I'll try it out once I can.
B) okey - good points.
C) Great.
About "openshift will soon allow users to register their downloadable cartridge" ...haven't heard about that ? is that something different than the quickstart/instantapp feature they got already ? (we'll support that too in next revision)
Your writeup is great - it also made me realize my brilliant idea about matching server hostname with the openshift hostname won't work since you are using localhost to do forwarding. That means we will need to somehow "mark" a server as related to a specific openshift application ;/ Was hoping we could avoid that since it would add another set of data to maintain/keep in sync. But the more i think of it we should support this usecase - and in a way that does require a server adapter to actually know about it (so it can work with any server adapter using loalhost as its target)
> Allow easier access to openshift operations from jboss servers
> --------------------------------------------------------------
>
> Key: JBIDE-16720
> URL: https://issues.jboss.org/browse/JBIDE-16720
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.1.Final
> Reporter: Mark Drilling
>
> We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case.
> Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push.
> Currently, we connect to an OpenShift DV instance like this:
> 1) Deploy DV cartridge via OpenShift web console.
> 2) Port forward from command line using rhc port-forward
> 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective
> The issues we observed:
> 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo.
> 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list.
> Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (TOOLSDOC-458) Add info that CordovaSim opens Console tab during startup
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-458?page=com.atlassian.jira.plug... ]
Michelle Murray resolved TOOLSDOC-458.
--------------------------------------
Resolution: Done
> Add info that CordovaSim opens Console tab during startup
> ---------------------------------------------------------
>
> Key: TOOLSDOC-458
> URL: https://issues.jboss.org/browse/TOOLSDOC-458
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: User Guide - Hybrid Mobile Tools and CordovaSim
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 17-01-2014 14:37:43
> Topic ID: 24062-567498 [Specified]
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.1.2
>
> Original Estimate: 30 minutes
> Time Spent: 45 minutes
> Remaining Estimate: 0 minutes
>
> Title: Run a Hybrid Mobile Application on Devices and Simulators
> Describe the issue:
> With the implementation of the fix for JBIDE-15932, the 'Run on CordovaSim' action now brings the Console tab to the forefront when CorodvaSim opens and provides a log of messages including error messages.
> This info should be added to the User Guide, HM+CS chapter. Add a sentence to the section 'Run a Hybrid Mobile Application on Devices and Simulators' stating that the Console tab opens when CordovaSim is launched and shows runtime messages including those relating to errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (TOOLSDOC-458) Add info that CordovaSim opens Console tab during startup
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-458?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-458:
------------------------------------------
See JBIDE-15932 for eng implementation details. At the moment Console view does not auto come to forefront.
> Add info that CordovaSim opens Console tab during startup
> ---------------------------------------------------------
>
> Key: TOOLSDOC-458
> URL: https://issues.jboss.org/browse/TOOLSDOC-458
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: User Guide - Hybrid Mobile Tools and CordovaSim
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 17-01-2014 14:37:43
> Topic ID: 24062-567498 [Specified]
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.1.2
>
> Original Estimate: 30 minutes
> Time Spent: 25 minutes
> Remaining Estimate: 30 minutes
>
> Title: Run a Hybrid Mobile Application on Devices and Simulators
> Describe the issue:
> With the implementation of the fix for JBIDE-15932, the 'Run on CordovaSim' action now brings the Console tab to the forefront when CorodvaSim opens and provides a log of messages including error messages.
> This info should be added to the User Guide, HM+CS chapter. Add a sentence to the section 'Run a Hybrid Mobile Application on Devices and Simulators' stating that the Console tab opens when CordovaSim is launched and shows runtime messages including those relating to errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs especially during startup
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-15932:
-----------------------------------------
Thanks [~ibuziuk].
> CordovaSim needs to display console logs especially during startup
> ------------------------------------------------------------------
>
> Key: JBIDE-15932
> URL: https://issues.jboss.org/browse/JBIDE-15932
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: jbds711
> Fix For: 4.1.2.CR1
>
>
> When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on.
> Just using firebug or similar would not solve this issue since it is not started early enough.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15482:
---------------------------------------------
assigning to Denis so he sees it.
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15482:
----------------------------------------
Assignee: Denis Golovin (was: Nick Boldt)
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16665:
---------------------------------------------
[~nickboldt] anything specific you want QE to test ? This is not an enduser 3rd party plugin. It is a dependency for doing simpler/better xml editors. Sapphire is afaik going to be or is already part of luna release train so its more a matter of getting a PR ready to test this from a dev side rather than QE.
> Add Sapphire to TP
> ------------------
>
> Key: JBIDE-16665
> URL: https://issues.jboss.org/browse/JBIDE-16665
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, testing-tools
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Len DiMaggio
>
> Reason: Required by new feature described in JBIDE-15394
> License and owner: EPL, Eclipse
> Original repository: http://download.eclipse.org/sapphire/0.7/repository
> JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire
> Source: Yes
> Affected projects: arquillian
> Required in devstudio: No
> Type of dependency:
> List of bundles added:
> org.eclipse.sapphire.java
> org.eclipse.sapphire.java.jdt
> org.eclipse.sapphire.java.jdt.ui
> org.eclipse.sapphire.modeling
> org.eclipse.sapphire.modeling.xml
> org.eclipse.sapphire.osgi
> org.eclipse.sapphire.osgi.fragment
> org.eclipse.sapphire.platform
> org.eclipse.sapphire.ui
> org.eclipse.sapphire.ui.swt.gef
> org.eclipse.sapphire.ui.swt.xml.editor
> org.eclipse.sapphire.workspace
> org.eclipse.sapphire.workspace.ui
> org.objectweb.asm
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15482:
------------------------------------
[~dgolovin] Since we now have JBIDE-16309 fixed, I'd like to close this as WONTFIX unless you have more suggestions for how to implement this.
Please provide comments here and in JBIDE-15483, or I'll just close this.
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.x
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months