March 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4746) GPG key for code signing

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4746: ------------------------------------- [~nickboldt] [~mat.booth] Do you still need some support of GPG signing on snapshots? I would close this issue or migrate it somewhere else if needed. > GPG key for code signing > ------------------------ > > Key: JBDS-4746 > URL: https://issues.jboss.org/browse/JBDS-4746 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: build > Reporter: Mat Booth > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.x > > > Hi, this is related to JBDS-4740 -- allow building of flatpak applications. > I will need to GPG sign flatpak applications before users can install them. > Does jenkins know about any GPG keys for code signing? And if so, where does the keyring live? > When I ran "{{gpg --list-keys}}" during a build, to list all the keys in the default keyring location (the default location is ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26453) Adapters/vscode-openshift tooling onboarding

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26453?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-26453 at 3/20/19 7:59 AM: ---------------------------------------------------------------- I have made a couple of PRs: https://github.com/redhat-developer/rsp-server/pull/275, https://github.com/redhat-developer/rsp-server/pull/251, https://github.com/redhat-developer/rsp-server/pull/223, https://github.com/redhat-developer/rsp-server/pull/225, https://github.com/redhat-developer/rsp-server/pull/236, https://github.com/redhat-developer/rsp-server/pull/266. Covering unit and integration tests fixes, updating jenkinsfile, improving pipeline, etc. I would consider this issue to be done, and I will continue working on adapters. was (Author: odockal): I have made a couple of PRs. > Adapters/vscode-openshift tooling onboarding > -------------------------------------------- > > Key: JBIDE-26453 > URL: https://issues.jboss.org/browse/JBIDE-26453 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: integration-test, quality > Fix For: 4.11.0.Final > > > Jump in adapters stuff: > * go through repos, get familiar with plugins > * start exploring locally, build it, run it > * pick up github issues and start implementing in typescript/java > * increase unit tests coverage > * get familiar with infrastructure -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH - proxy requirements definition

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26452: ---------------------------------- Sprint: devex #157 November 2019, devex #159 December 2018, devex #164 April 2019 (was: devex #157 November 2019, devex #159 December 2018) > Explore existing proxy server set up solutions outside RH - proxy requirements definition > ----------------------------------------------------------------------------------------- > > Key: JBIDE-26452 > URL: https://issues.jboss.org/browse/JBIDE-26452 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.Final > > > Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge. > Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code? > Requirements for proxy solution: > * Supports HTTP and HTTPS protocols > * Clear and configurable logging and other tools > * runs on linux > * Open Source solution > * License usable "in house" (can be use for profit = in enterprise environment) > * Project is alive/maintained - or we would must maintain our own fork? > * Community > * Code on github - preferably > * uses issue tracking system > Requirements for putting proxy into action: > * easy to deploy solution > * does not require user knowledge of proxy configuration - minimalist config > * can be updated at place > * RH certificate can be used -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4746) GPG key for code signing

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4746: -------------------------------- Summary: GPG key for code signing (was: GPG key for code siging) > GPG key for code signing > ------------------------ > > Key: JBDS-4746 > URL: https://issues.jboss.org/browse/JBDS-4746 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: build > Reporter: Mat Booth > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.x > > > Hi, this is related to JBDS-4740 -- allow building of flatpak applications. > I will need to GPG sign flatpak applications before users can install them. > Does jenkins know about any GPG keys for code signing? And if so, where does the keyring live? > When I ran "{{gpg --list-keys}}" during a build, to list all the keys in the default keyring location (the default location is ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26456) Provision Rhel 8 image with JBDS labels and add it to jenkins

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26456?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-26456: ------------------------------------- Assignee: Zbyněk Červinka (was: Ondrej Dockal) > Provision Rhel 8 image with JBDS labels and add it to jenkins > ------------------------------------------------------------- > > Key: JBIDE-26456 > URL: https://issues.jboss.org/browse/JBIDE-26456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Zbyněk Červinka > Priority: Major > Labels: jenkins, openstack > Fix For: 4.11.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26456) Provision Rhel 8 image with JBDS labels and add it to jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26456?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26456: ---------------------------------- Sprint: devex #157 November 2019, devex #159 December 2018, devex #164 April 2019 (was: devex #157 November 2019, devex #159 December 2018) > Provision Rhel 8 image with JBDS labels and add it to jenkins > ------------------------------------------------------------- > > Key: JBIDE-26456 > URL: https://issues.jboss.org/browse/JBIDE-26456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Zbyněk Červinka > Priority: Major > Labels: jenkins, openstack > Fix For: 4.11.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26579) Add Sonar in integration tests repo

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26579?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26579: ---------------------------------- Story Points: 8 > Add Sonar in integration tests repo > ----------------------------------- > > Key: JBIDE-26579 > URL: https://issues.jboss.org/browse/JBIDE-26579 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.11.0.Final > Environment: Jenkins > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26454) Proxy usage within QE teams, needs and requirements for deploying

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26454?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26454: ---------------------------------- Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #164 April 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019) > Proxy usage within QE teams, needs and requirements for deploying > ----------------------------------------------------------------- > > Key: JBIDE-26454 > URL: https://issues.jboss.org/browse/JBIDE-26454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.Final > > > Find out: > * existing solutions within RH > * needs of other teams > * usability of open source proxy technologies/solutions > * usage among different OS -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4756: -------------------------------- Sprint: devex #164 April 2019 (was: devex #163 March 2019) > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.11.0.GA > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26557) Update WildFly from version 11 to version 15 in maven.itests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26557?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26557: ---------------------------------- Sprint: devex #164 April 2019 > Update WildFly from version 11 to version 15 in maven.itests > ------------------------------------------------------------ > > Key: JBIDE-26557 > URL: https://issues.jboss.org/browse/JBIDE-26557 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.11.0.AM1 > Environment: All environments. > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > WildFly needs to be updated from version 11 to version 15. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2019