[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-20442:
-------------------------------------
Summary: Create SWTBot integration tests for tern related features
Key: JBIDE-20442
URL: https://issues.jboss.org/browse/JBIDE-20442
Project: Tools (JBoss Tools)
Issue Type: Task
Components: jsp/jsf/xml/html-source-editing
Affects Versions: 4.3.0.Beta2
Reporter: Denis Golovin
Priority: Critical
There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20099:
-------------------------------------
Tried it and it worked really well, nice work [~jcantrill]!
So provided the oc binary is present, I could perform the following actions, from OpenShift Explorer, while creating a new eap-basic-sti app:
- Open the Build Log... menu for a build in progress. It streamed the log as expected, in the console.
- After closing the Console, and reopening Build Log..., the console resumed displaying the log
- Opening the log also worked once the build was done
- Opening Pod Log... on the build pod showed the exact same console, if the build log console was already opened
- After the build finished, manually refreshed the Explorer view, so the EAP pod showed up
- Opening Pod Log... on the EAP pod showed the EAP log in a new console.
- EAP logs properly streamed while using the kitchensink app
> enable a logstream for Openshift Pods
> -------------------------------------
>
> Key: JBIDE-20099
> URL: https://issues.jboss.org/browse/JBIDE-20099
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Diógenes Rettori
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
>
> enable the eclipse console to show
> oc get logs <pod>
> oc get build-logs <build>
> You click on the pod, then right-click show logs, or double click go to logs...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20428) Matrix jobs: Unable to report download statistics due to invalid URL
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20428?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20428:
------------------------------------
The WHOLE URL comes from p2StatsURL property.
Thus:
{code}
http://download.jboss.org/jbosstools/usage/installs/
jbosstools-build-sites.aggregate.child-sites_4.3.mars/jdk=jdk1.8,label_exp=(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts,projectName=central/
4.3.0-SNAPSHOT/
Beta2/
Beta2-v20150726-0459-B47/
{code}
is
{code}
http://download.jboss.org/jbosstools/usage/installs/
{JOB_NAME}/
{project.version}/
{BUILD_ALIAS}/
{buildQualifier}/
{code}
Here's the code that does that today, before my PR:
https://github.com/jbosstools/jbosstools-build-sites/pull/201/files#diff-...
The problem is that Jenkins appends the matrix params into the JOB_NAME variable, and Eclipse can't handle a URL of this form without escaping characters.
{code}
jdk=jdk1.8,label_exp=(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts,projectName=central
{code}
So, instead of bothering to include this unneeded metadata, we just use "\{snapshotLocation}-site", which resolves to "core-site" "coretests-site" "earlyaccess-site" and "central-site". Shorter and won't break when using matrix jobs.
> Matrix jobs: Unable to report download statistics due to invalid URL
> --------------------------------------------------------------------
>
> Key: JBIDE-20428
> URL: https://issues.jboss.org/browse/JBIDE-20428
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, usage
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.CR1
>
>
> For matrix job output, we get errors like this when trying to track download stats:
> {code}
> [p2.dir] !MESSAGE Unable to report download statistics due to invalid URL: http://download.jboss.org/jbosstools/usage/installs/jbosstools-build-site... suffix: org.jboss.tools.common.mylyn.feature
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20401:
------------------------------------
I'm willing to help implement this but I have some questions re: how & where...
* Should the URL for OSv3 Getting Started be a link that can change based on values in the ide-config.properties, or hardcoded into some plugin? If dynamic, can you point me at code that does this already, ie., for reading other properties in that file [1] ?
* Would the label ever need to change, based on the link contents changing? eg., we could have a "Getting Started" link now, but in 6mo change it to "User Doc" if the URL changed to include more than just a getting started page.
* Where would this link be in the tooling? In which plugin?
* When will http://tools.jboss.org/documentation/howto/openshift3_getting_started.html be written so that we can link to it?
> OpenShift tooling UI should include a link to user docs
> -------------------------------------------------------
>
> Key: JBIDE-20401
> URL: https://issues.jboss.org/browse/JBIDE-20401
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Len DiMaggio
> Labels: help_wanted
> Fix For: 4.3.0.CR1
>
>
> Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months