November 2017 - jbosstools-issues

[JBoss JIRA] (ERT-533) enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-533: --------------------------------------- Summary: enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533] Key: ERT-533 URL: https://issues.jboss.org/browse/ERT-533 Project: Eclipse Release Train Issue Type: Task Components: WTP Releng Reporter: Friendly Jira Robot As mentioned on https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10522.html WTP uses some sort of versioncheck magic to ensure plugins and features are bumped appropriately. We might want to switch to use the tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata mojos to ensure correct plugin and feature versioning, by settings stable and staging URLs as baselines. For this to work, we need two things: a) all components must build with Tycho 1.0 b) a staging and stable URL must be provided against which to compare versions. The staging site could be the latest I build or else a committers build, such as one of these, built via the current wtp.releng.aggretor build: * http://download.eclipse.org/webtools/downloads/drops/R3.10.0/I-3.10.0-201... * http://build.eclipse.org/webtools/committers/wtp-R3.10.0-I/20171030195222... It should ultimately be a composite or aggregate site built from the collection of WTP subproject builds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25322) Jenkins Job Builder proof of concept

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25322?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25322: ---------------------------------- Description: Jenkins Job Builder https://docs.openstack.org/infra/jenkins-job-builder/ Jenkins Job Wrecker https://github.com/ktdreyer/jenkins-job-wrecker - for converting existing jobs xml config to yaml A good inspiration is this JBDS IS JJB repo: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jbdsis/jbdsis-qe-jenkins... was: Jenkins Job Builder https://docs.openstack.org/infra/jenkins-job-builder/ Jenkins Job Wrecker https://github.com/ktdreyer/jenkins-job-wrecker - for converting existing jobs xml config to yaml > Jenkins Job Builder proof of concept > ------------------------------------- > > Key: JBIDE-25322 > URL: https://issues.jboss.org/browse/JBIDE-25322 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.5.x > > > Jenkins Job Builder > https://docs.openstack.org/infra/jenkins-job-builder/ > Jenkins Job Wrecker > https://github.com/ktdreyer/jenkins-job-wrecker > - for converting existing jobs xml config to yaml > A good inspiration is this JBDS IS JJB repo: > https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jbdsis/jbdsis-qe-jenkins... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25435) Fix intermittent failure in central tests

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25435?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25435: ------------------------------- Sprint: devex #141 December 2017 > Fix intermittent failure in central tests > ----------------------------------------- > > Key: JBIDE-25435 > URL: https://issues.jboss.org/browse/JBIDE-25435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.2.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25435) Fix intermittent failure in central tests

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25435: ---------------------------------- Summary: Fix intermittent failure in central tests Key: JBIDE-25435 URL: https://issues.jboss.org/browse/JBIDE-25435 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.5.2.AM1 Reporter: Jeff MAURY Fix For: 4.5.2.AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25435) Fix intermittent failure in central tests

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25435?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25435: ---------------------------------- Assignee: Jeff MAURY > Fix intermittent failure in central tests > ----------------------------------------- > > Key: JBIDE-25435 > URL: https://issues.jboss.org/browse/JBIDE-25435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.2.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4616) signed rpm fetch job should verify the rpms are signed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4616?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4616: ---------------------------------- Doesn't seem to be working. {code} 11:40:51 ++ rpm -Kv rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.x86_64.rpm 11:40:53 + gpgcheck='rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.x86_64.rpm: 11:40:53 Header V3 RSA/SHA256 Signature, key ID a5787476: NOKEY 11:40:53 Header SHA1 digest: OK (3f968977bc4497273f440edf0520d2517188bb86) 11:40:53 V3 RSA/SHA256 Signature, key ID a5787476: NOKEY 11:40:53 MD5 digest: OK (f4fa9e25e499e519f143d9b0d0074d4d)' {code} - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... But when I do this locally, it works: {code} cd /tmp wget -q http://download-node-02.eng.bos.redhat.com/devel/candidates/jboss/devstud... wget -q http://download-node-02.eng.bos.redhat.com/devel/candidates/jboss/devstud... for theFile in *.rpm; do echo "[DEBUG] Check pgp signature in ${theFile} ..." gpgcheck="$(rpm -Kv ${theFile})" if [[ ! $(echo ${gpgcheck} | grep "key ID a5787476: OK") ]]; then echo "[ERROR] rpm ${theFile} is not signed!" echo "[ERROR] ${gpgcheck}" else echo "[INFO] "$(rpm -K ${theFile}) fi done {code} ... {code} [DEBUG] Check pgp signature in rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.src.rpm ... [INFO] rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.src.rpm: rsa sha1 (md5) pgp md5 OK [DEBUG] Check pgp signature in rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.x86_64.rpm ... [INFO] rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.x86_64.rpm: rsa sha1 (md5) pgp md5 OK {code} Do I need to destroy the slaves and re-create them? > signed rpm fetch job should verify the rpms are signed > ------------------------------------------------------ > > Key: JBDS-4616 > URL: https://issues.jboss.org/browse/JBDS-4616 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 11.1.0.GA > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 11.2.0.AM2 > > > Currently, the job that fetches the signed devstudio rpms can't automatically verify the rpms are signed because the key is not installed on the slaves. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So, we need to fix that so that the job can verify signing has occurred and speed up the release process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Description: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenShift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. Steps: # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) # EXEC: Import project within fuse-on-openshift.zip into your workspace # EXEC: open launch configuration and change: ** -Dkubernetes.master= so that it first your cdk instance ** -Dkubernetes.namespace= to the name of the project that you create in step 1. # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) # ASSERT: server adapter is created and is *[started]* # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end {code} simple-route - >>> 455 simple-route - >>> 695 simple-route - >>> 935 {code} # EXEC: In Project Explorer: open class MyTransformer and change the transform method # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod was: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenShift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. Steps: # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) # EXEC: Import project within fuse-on-openshift.zip into your workspace # EXEC: open launch configuration and change: ** -Dkubernetes.master= so that it first your cdk instance ** -Dkubernetes.namespace= to the name of the project that you create in step 1. # EXEC: run the launch config, so that the project gets deployed to OpenShift (cdk) # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml** # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) # ASSERT: server adapter is created and is [started] # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end {code} simple-route - >>> 455 simple-route - >>> 695 simple-route - >>> 935 {code} # EXEC: In Project Explorer: open class MyTransformer and change the transform method # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM2 > > Attachments: fuse-on-openshift.zip, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24839) Fix OAuth connection in OpenShift tests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24839?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24839: ---------------------------------- Summary: Fix OAuth connection in OpenShift tests (was: Fix Oauth connection in OpenShift tests) > Fix OAuth connection in OpenShift tests > --------------------------------------- > > Key: JBIDE-24839 > URL: https://issues.jboss.org/browse/JBIDE-24839 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4588) update installer to be able to use JDK 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4588?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4588 at 11/23/17 9:16 AM: ------------------------------------------------------------ I think I've fixed the installer to be able to run with JDK 9, and install using JDK 9 too. Tested on Fedora24 using JDK 9 and 9.0.1 (but not 9-ea). Though 9-ea is probably not needed to be supported anymore, we should still ensure it works, I suppose? https://github.com/jbdevstudio/jbdevstudio-product/pull/479/files For more on this issue, see screenshots attached here: https://issues.jboss.org/browse/JBDS-4594?focusedCommentId=13493394&page=... was (Author: nickboldt): I think I've fixed the installer to be able to run with JDK 9, and install using JDK 9 too. Tested on Fedora24 using JDK 9 (not 9.0.1, not 9-ea). We should verify it works for all three versions of the JDK 9, though EA is probably not needed to be supported anymore, and 9 was patched with a security fix to move up to 9.0.1. https://github.com/jbdevstudio/jbdevstudio-product/pull/479/files For more on this issue, see screenshots attached here: https://issues.jboss.org/browse/JBDS-4594?focusedCommentId=13493394&page=... > update installer to be able to use JDK 9 > ---------------------------------------- > > Key: JBDS-4588 > URL: https://issues.jboss.org/browse/JBDS-4588 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM2 > > Attachments: jdk9-ea.png, jdk9.0.1.png > > > Investigate what's needed to support running the installer w/ JDK 9. > May also need to add this to the devstudio.ini, after *-vmargs*: > {code}-Dosgi.requiredJavaVersion=1.8 > --add-modules=ALL-SYSTEM{code} -- https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_f... > cc: [~mmalina] [~jeffmaury] [~dgolovin] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4588) update installer to be able to use JDK 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4588?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4588 at 11/23/17 9:15 AM: ------------------------------------------------------------ I think I've fixed the installer to be able to run with JDK 9, and install using JDK 9 too. Tested on Fedora24 using JDK 9 (not 9.0.1, not 9-ea). We should verify it works for all three versions of the JDK 9, though EA is probably not needed to be supported anymore, and 9 was patched with a security fix to move up to 9.0.1. https://github.com/jbdevstudio/jbdevstudio-product/pull/479/files For more on this issue, see screenshots attached here: https://issues.jboss.org/browse/JBDS-4594?focusedCommentId=13493394&page=... was (Author: nickboldt): I think I've fixed the installer to be able to run with JDK 9, and install using JDK 9 too. Tested on Fedora24 using JDK 9 (not 9.0.1, not 9-ea). We should verify it works for all three versions of the JDK 9, though EA is probably not needed to be supported anymore, and 9 was patched with a security fix to move up to 9.0.1. https://github.com/jbdevstudio/jbdevstudio-product/pull/479/files > update installer to be able to use JDK 9 > ---------------------------------------- > > Key: JBDS-4588 > URL: https://issues.jboss.org/browse/JBDS-4588 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM2 > > Attachments: jdk9-ea.png, jdk9.0.1.png > > > Investigate what's needed to support running the installer w/ JDK 9. > May also need to add this to the devstudio.ini, after *-vmargs*: > {code}-Dosgi.requiredJavaVersion=1.8 > --add-modules=ALL-SYSTEM{code} -- https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_f... > cc: [~mmalina] [~jeffmaury] [~dgolovin] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017