October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24835) Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24835?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-24835: ------------------------------------ Yes, there is nothing for base, because jbosstools-base does not contain any itests (only test-framework). Correct link to openshift itests is (dot instead of dash): https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... The above links for server and archives itests seem correct. We probably will rename it to *.itests to stay consistent with all other jobs. I believe work on this jira is done. Please reopen if you feel otherwise. Thx! > Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24835 > URL: https://issues.jboss.org/browse/JBIDE-24835 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4569) Update kompose to 1.3.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4569?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-4569. --------------------------------- Resolution: Duplicate Issue Being tracked on github here https://github.com/redhat-developer-tooling/developer-platform-install/is... > Update kompose to 1.3.0 > ------------------------ > > Key: JBDS-4569 > URL: https://issues.jboss.org/browse/JBDS-4569 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.1.0.GA > > > Kompose 1.3.0 is out and should be included into DevSuite installer across all supported platforms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4569) Update kompose to 1.3.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4569?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4569: -------------------------------- Description: Kompose 1.3.0 is out and should be included into DevSuite installer across all supported platforms. (was: Kompose 1.4.0 is out on Oct 30th and should be included into DevSuite installer across all supported platforms.) > Update kompose to 1.3.0 > ------------------------ > > Key: JBDS-4569 > URL: https://issues.jboss.org/browse/JBDS-4569 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.1.0.GA > > > Kompose 1.3.0 is out and should be included into DevSuite installer across all supported platforms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4569) Update kompose to 1.3.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4569?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4569: -------------------------------- Summary: Update kompose to 1.3.0 (was: Update kompose to 1.4.0 ) > Update kompose to 1.3.0 > ------------------------ > > Key: JBDS-4569 > URL: https://issues.jboss.org/browse/JBDS-4569 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.1.0.GA > > > Kompose 1.4.0 is out on Oct 30th and should be included into DevSuite installer across all supported platforms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25284) Use default plugin classpath in 'org.jboss.tools.hibernate.search'

by Koen Aers (JIRA)

Koen Aers created JBIDE-25284: --------------------------------- Summary: Use default plugin classpath in 'org.jboss.tools.hibernate.search' Key: JBIDE-25284 URL: https://issues.jboss.org/browse/JBIDE-25284 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25284) Use default plugin classpath in 'org.jboss.tools.hibernate.search'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25284?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-25284: --------------------------------- Assignee: Koen Aers > Use default plugin classpath in 'org.jboss.tools.hibernate.search' > ------------------------------------------------------------------ > > Key: JBIDE-25284 > URL: https://issues.jboss.org/browse/JBIDE-25284 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25284) Use default plugin classpath in 'org.jboss.tools.hibernate.search'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25284?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-25284: ------------------------------ Fix Version/s: 4.5.1.Final > Use default plugin classpath in 'org.jboss.tools.hibernate.search' > ------------------------------------------------------------------ > > Key: JBIDE-25284 > URL: https://issues.jboss.org/browse/JBIDE-25284 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25282) IT: tests should be able to run individually and reuse resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25282?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25282: ------------------------------------- Description: * integration tests should reuse OpenShift resources, not start from scratch in each test. Creating OpenShift applications for instance can easily take up to several minutes. Multiply this by ex. 100 tests and we're easily at a runtime of several hours for the whole suite. The Requirements that we have in reddeer OpenShift were create with re-using resources in mind. ** Ex. annotating a test class with {code} @RequiredProject( name = DatastoreOS3.TEST_PROJECT) {code} makes sure that there's a project "test-project" that exists in the OpenShift server that's being used. If it exists, the annotation would do nothing. It creates it if it doesnt exist. The required project (either pre-existing the test or created upfront if it didnt) is injected into the test via {code} @InjectRequirement protected static OpenShiftProjectRequirement requiredProject; {code} ** Ex. annotating a test class with {code} @RequiredService( project = DatastoreOS3.TEST_PROJECT, service = OpenShiftResources.NODEJS_SERVICE, template = OpenShiftResources.NODEJS_TEMPLATE) {code} makes sure that the test has a service called "nodejs-example" available. If it exists it wont do anything. If it doesn't, it'll create it using the NODEJS_TEMPLATE provided in the annotation. * All tests should be able to run indivdiually. When developing integration tests for a new feature, running the whole suite gets a big impediment. We should therefore allow all tests to be run individually was: * integration tests should reuse OpenShift resources, not start from scratch in each test. Creating OpenShift applications for instance can easily take up to several minutes. Multiply this by ex. 100 tests and we're easily at a runtime of several hours for the whole suite. The Requirements that we have in reddeer OpenShift were create with re-using resources in mind. ** Ex. annotating a test class with {code} @RequiredProject( name = DatastoreOS3.TEST_PROJECT) {code} makes sure that there's a project "test-project" that exists in the OpenShift server that's being used. If it exists, the annotation would do nothing. It creates it if it doesnt exist. ** Ex. annotating a test class with {code} @RequiredService( project = DatastoreOS3.TEST_PROJECT, service = OpenShiftResources.NODEJS_SERVICE, template = OpenShiftResources.NODEJS_TEMPLATE) {code} makes sure that the test has a service called "nodejs-example" available. If it exists it wont do anything. If it doesn't, it'll create it using the NODEJS_TEMPLATE provided in the annotation. * All tests should be able to run indivdiually. When developing integration tests for a new feature, running the whole suite gets a big impediment. We should therefore allow all tests to be run individually > IT: tests should be able to run individually and reuse resources > ---------------------------------------------------------------- > > Key: JBIDE-25282 > URL: https://issues.jboss.org/browse/JBIDE-25282 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Fix For: 4.5.x > > > * integration tests should reuse OpenShift resources, not start from scratch in each test. Creating OpenShift applications for instance can easily take up to several minutes. Multiply this by ex. 100 tests and we're easily at a runtime of several hours for the whole suite. > The Requirements that we have in reddeer OpenShift were create with re-using resources in mind. > ** Ex. annotating a test class with > {code} > @RequiredProject( > name = DatastoreOS3.TEST_PROJECT) > {code} > makes sure that there's a project "test-project" that exists in the OpenShift server that's being used. If it exists, the annotation would do nothing. It creates it if it doesnt exist. > The required project (either pre-existing the test or created upfront if it didnt) is injected into the test via > {code} > @InjectRequirement > protected static OpenShiftProjectRequirement requiredProject; > {code} > ** Ex. annotating a test class with > {code} > @RequiredService( > project = DatastoreOS3.TEST_PROJECT, > service = OpenShiftResources.NODEJS_SERVICE, > template = OpenShiftResources.NODEJS_TEMPLATE) > {code} > makes sure that the test has a service called "nodejs-example" available. If it exists it wont do anything. If it doesn't, it'll create it using the NODEJS_TEMPLATE provided in the annotation. > * All tests should be able to run indivdiually. When developing integration tests for a new feature, running the whole suite gets a big impediment. We should therefore allow all tests to be run individually -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25283) IT: ImportApplicationWizardTest needs to reuse an existing connection and existing resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25283?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25283: ------------------------------------- Summary: IT: ImportApplicationWizardTest needs to reuse an existing connection and existing resources (was: IT: ImportApplicationWizardTest needs to reuse resource) > IT: ImportApplicationWizardTest needs to reuse an existing connection and existing resources > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25283 > URL: https://issues.jboss.org/browse/JBIDE-25283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > > ImportApplicationWizardTest is using (via the super class ImportApplicationBase) > {code} > @CleanConnection > {code} > which kills all projects that exist in the OpenShift server that the given/default connection points to. We need to get rid of this annotation and make sure that the test is re-using the service that it's requiring via the service requirement annotation: > {code} > @RequiredService( > project = DatastoreOS3.TEST_PROJECT, > service = OpenShiftResources.NODEJS_SERVICE, > template = OpenShiftResources.NODEJS_TEMPLATE) > {code} > The very same is true about the following annotation that it's currently using: > {code} > @CleanOpenShiftExplorer > {code} > This annotation is clearing all connections that exists in the explorer. We should simply reuse the (existing) connection that the test is annotated with: > {code} > @RequiredBasicConnection > {code} > This annotation is referring to the server that is given via the system properties (in cmd-line with -D) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25283) IT: ImportApplicationWizardTest needs to reuse resource

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25283: ---------------------------------------- Summary: IT: ImportApplicationWizardTest needs to reuse resource Key: JBIDE-25283 URL: https://issues.jboss.org/browse/JBIDE-25283 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.1.AM3 Reporter: Andre Dietisheim Fix For: 4.5.x ImportApplicationWizardTest is using (via the super class ImportApplicationBase) {code} @CleanConnection {code} which kills all projects that exist in the OpenShift server that the given/default connection points to. We need to get rid of this annotation and make sure that the test is re-using the service that it's requiring via the service requirement annotation: {code} @RequiredService( project = DatastoreOS3.TEST_PROJECT, service = OpenShiftResources.NODEJS_SERVICE, template = OpenShiftResources.NODEJS_TEMPLATE) {code} The very same is true about the following annotation that it's currently using: {code} @CleanOpenShiftExplorer {code} This annotation is clearing all connections that exists in the explorer. We should simply reuse the (existing) connection that the test is annotated with: {code} @RequiredBasicConnection {code} This annotation is referring to the server that is given via the system properties (in cmd-line with -D) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017