April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23598) Integration tests global refactoring: org.jboss.tools.perf.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23598?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23598: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration tests global refactoring: org.jboss.tools.perf.test > --------------------------------------------------------------- > > Key: JBIDE-23598 > URL: https://issues.jboss.org/browse/JBIDE-23598 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests, performance > Fix For: 4.6.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.perf.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23595) Integration tests global refactoring: org.jboss.tools.vpe.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23595?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23595: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration tests global refactoring: org.jboss.tools.vpe.bot.test > ------------------------------------------------------------------ > > Key: JBIDE-23595 > URL: https://issues.jboss.org/browse/JBIDE-23595 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests, vpe > Fix For: 4.6.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.vpe.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23592) Integration tests global refactoring: org.jboss.tools.seam.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23592?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23592: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration tests global refactoring: org.jboss.tools.seam.ui.bot.test > ---------------------------------------------------------------------- > > Key: JBIDE-23592 > URL: https://issues.jboss.org/browse/JBIDE-23592 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: seam2 > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests, seam > Fix For: 4.6.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.seam.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24146: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Support pipeline deployment style > --------------------------------- > > Key: JBIDE-24146 > URL: https://issues.jboss.org/browse/JBIDE-24146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: application_wizard, openshift, openshift_v3 > Fix For: 4.6.x > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png, webui-edit-pipeline-file.png > > > In the web-console jenkins pipelines are supported in the following way: > * when opening up an empty project you get a special template: > !jenkins-pipeline-template.png! > * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline): > !jenkins-variants.png! > * once executed you get a special build type *pipeline* > !pipeline-build.png! > * the full example template is using the following build config with the strategy type *JenkinsPipeline*: > {code} > apiVersion: v1 > kind: BuildConfig > metadata: > name: sample-pipeline > namespace: gulu > selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline > uid: 12dec3c8-1948-11e7-a217-0251082287a6 > resourceVersion: '3757' > creationTimestamp: '2017-04-04T15:05:00Z' > labels: > app: jenkins-pipeline-example > name: sample-pipeline > template: application-template-sample-pipeline > annotations: > pipeline.alpha.openshift.io/uses: >- > [{"name": "nodejs-mongodb-example", "namespace": "", "kind": > "DeploymentConfig"}] > spec: > triggers: > - type: GitHub > github: > secret: secret101 > - type: Generic > generic: > secret: secret101 > runPolicy: Serial > source: > type: None > strategy: > type: JenkinsPipeline > jenkinsPipelineStrategy: > jenkinsfile: >- > node('nodejs') { > stage 'build' > openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs: > 'true') > stage 'deploy' > openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example') > } > output: {} > resources: {} > postCommit: {} > nodeSelector: null > status: > lastVersion: 1 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24144) When deploying user should be able to tune the memory requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24144?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24144: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > When deploying user should be able to tune the memory requirements > ------------------------------------------------------------------ > > Key: JBIDE-24144 > URL: https://issues.jboss.org/browse/JBIDE-24144 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, wizard > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24135: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Clean up old vscode builds and establish file retention / cleanup policy > ------------------------------------------------------------------------ > > Key: JBIDE-24135 > URL: https://issues.jboss.org/browse/JBIDE-24135 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Fix For: 4.6.x > > > Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts. > * java-server 1.0.x > * java-server 0.1.x > * jdt-language-server 0.1 older than 4 weeks ago > Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as: > /neon/snapshots/vscode > /neon/integration/vscode > etc. > Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created. > Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24046) Move jst.itests to jbosstools-jst

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24046?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24046: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Move jst.itests to jbosstools-jst > --------------------------------- > > Key: JBIDE-24046 > URL: https://issues.jboss.org/browse/JBIDE-24046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24019) test failures in webservices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24019?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24019: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > test failures in webservices > ---------------------------- > > Key: JBIDE-24019 > URL: https://issues.jboss.org/browse/JBIDE-24019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.x > > Attachments: .log, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt > > > See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. > See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt] > Running again now with {code}mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} \ > -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}{code} > See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt] and [^.log] > Could the problem be this? > {code}!ENTRY org.eclipse.wst.common.project.facet.core 4 0 2017-02-28 11:14:37.082 > !MESSAGE Project facet wst.jsdt.web has not been defined. It is used in plugin org.eclipse.jst.server.core. > {code} > (Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT? see JBIDE-24020) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23993) Reverse engineering editor generates duplicate ID values

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23993?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23993: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Reverse engineering editor generates duplicate ID values > -------------------------------------------------------- > > Key: JBIDE-23993 > URL: https://issues.jboss.org/browse/JBIDE-23993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.3.Final > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM (headless)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23882: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Automate test of installation of software from Red Hat Central into devstudio RPM (headless) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Vojtech Prusa > Fix For: 4.6.x > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018