June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24340: ---------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > CDK3 tools works behind proxy - Test case > ----------------------------------------- > > Key: JBIDE-24340 > URL: https://issues.jboss.org/browse/JBIDE-24340 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, docker, integration-tests, openshift > Affects Versions: 4.4.4.Final > Environment: Linux (Fedora), Mac OS, Windows > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.0.AM2 > > Attachments: create_proxy-test_env.sh > > > It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines. > Steps to follow: > 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] ) > 2. Download/install devstudio > 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk) > 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli > 4. Set env. variable MINISHIFT_HTTP(S)_PROXY > 5. Start devstudio, add new Container Development Environement server > 6. Start server adapter > 7. ASSERT: CDK tools are working properly - CDK started successfully > * rhel-image was subscribed > * docker image pulled > * log into openshift -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24517) Provision windows on bare metal machine

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24517?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24517: ---------------------------------- Story Points: 40 > Provision windows on bare metal machine > --------------------------------------- > > Key: JBIDE-24517 > URL: https://issues.jboss.org/browse/JBIDE-24517 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci, devsuite > > * Configure foreman for provisioning machines in the same subnet > * Prepare image for provisioning > * Provision basic image to local machine -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-511) com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-511?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny updated ERT-511: -------------------------------- Sprint: devex #133 Jun 2017 > com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659] > --------------------------------------------------------------------------------------------------------- > > Key: ERT-511 > URL: https://issues.jboss.org/browse/ERT-511 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.9_RC3, General, bzira > Fix For: Oxygen (4.7) RC3 > > > com.google.javascript and com.google.guava plugins are required by org.eclipse.wst.jsdt.core plugin but not added to org.eclipse.wst.jsdt.feature. > The unsatisfied p2 requirements result in p2 install error. This should be fixed in WTP 3.9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-511) com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-511?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny updated ERT-511: -------------------------------- Story Points: 2 > com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659] > --------------------------------------------------------------------------------------------------------- > > Key: ERT-511 > URL: https://issues.jboss.org/browse/ERT-511 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.9_RC3, General, bzira > Fix For: Oxygen (4.7) RC3 > > > com.google.javascript and com.google.guava plugins are required by org.eclipse.wst.jsdt.core plugin but not added to org.eclipse.wst.jsdt.feature. > The unsatisfied p2 requirements result in p2 install error. This should be fixed in WTP 3.9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-511) com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-511?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-511: ----------------------------------- Assignee: Victor Rubezhny > com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659] > --------------------------------------------------------------------------------------------------------- > > Key: ERT-511 > URL: https://issues.jboss.org/browse/ERT-511 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.9_RC3, General, bzira > Fix For: Oxygen (4.7) RC3 > > > com.google.javascript and com.google.guava plugins are required by org.eclipse.wst.jsdt.core plugin but not added to org.eclipse.wst.jsdt.feature. > The unsatisfied p2 requirements result in p2 install error. This should be fixed in WTP 3.9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23732) Implement new batch integration ui tests for content assist features in job.xml file.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23732?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23732: ------------------------------- Sprint: (was: devex #133 Jun 2017) > Implement new batch integration ui tests for content assist features in job.xml file. > -------------------------------------------------------------------------------------- > > Key: JBIDE-23732 > URL: https://issues.jboss.org/browse/JBIDE-23732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.4.x > > > These tests covers both view tabs where content assist feature is used (design and source view). Test: > 1. Offered batch artifacts in content assist menu for ref attribute > 2. Offered element's id for id attribute with correct level of context > 3. Fully qualified names of exceptions used in class attribute of include/exclude tag > 4. Properties from both property definition in job.xml and from batch artifact with @BatchProperty annotation > 5. Proper list of element's id referred from next, to attributes and/or restart attributes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24543) Get rid of AbstractCreateApplicationTest in selected classes

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24543?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-24543: ------------------------------- Story Points: 20 > Get rid of AbstractCreateApplicationTest in selected classes > ------------------------------------------------------------ > > Key: JBIDE-24543 > URL: https://issues.jboss.org/browse/JBIDE-24543 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > > Functionality of AbstractCreateApplicationTest should be implemented by requirements using openshift API isntead of UI. > The selected classes are: > CreateServerAdapterTest > DebuggingEAPAppTest > DeleteResourcesTest > DeploymentTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24539: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.0.AM2) > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM1 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24543) Get rid of AbstractCreateApplicationTest in selected classes

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24543?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-24543: ------------------------------- Description: Functionality of AbstractCreateApplicationTest should be implemented by requirements using openshift API isntead of UI. The selected classes are: CreateServerAdapterTest DebuggingEAPAppTest DeleteResourcesTest DeploymentTest was:Functionality of AbstractCreateApplicationTest should be implemented by requirements using openshift API isntead of UI. > Get rid of AbstractCreateApplicationTest in selected classes > ------------------------------------------------------------ > > Key: JBIDE-24543 > URL: https://issues.jboss.org/browse/JBIDE-24543 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > > Functionality of AbstractCreateApplicationTest should be implemented by requirements using openshift API isntead of UI. > The selected classes are: > CreateServerAdapterTest > DebuggingEAPAppTest > DeleteResourcesTest > DeploymentTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-22680: ---------------------------------- Sprint: devex #133 Jun 2017 Assignee: Radim Hopp (was: Nick Boldt) > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Radim Hopp > Fix For: 4.5.0.AM1 > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017