June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3918) Latest DevStudio build starts without splash screen

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3918: ----------------------------------- Summary: Latest DevStudio build starts without splash screen Key: JBDS-3918 URL: https://issues.jboss.org/browse/JBDS-3918 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: p2-product Affects Versions: 10.0.0.Alpha3 Environment: OS: Windows 10 Devstudio: Version: 10.0.0.Alpha3 Build id: Alpha3-v20160601-0425-B5485 Build date: 20160601-0425 Reporter: Denis Golovin Latest nightly build downloaded bu Development Suite installer starts without splash screen -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19506 at 6/1/16 4:08 AM: ------------------------------------------------------------------ quite a few more tests added in [#1199|https://github.com/jbosstools/jbosstools-openshift/pull/1199] even though the coverage is still not where I expect it to be in this very crucial part of the tooling. I thus would merge and postpone to add further tests was (Author: adietish): quite a few more tests added in [#1199h|ttps://github.com/jbosstools/jbosstools-openshift/pull/1199] even though the coverage is still not where I expect it to be in this very crucial part of the tooling. I thus would merge and postpone to add further tests > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-216) Running image, which has shell form of CMD needs to be enclosed in quotes [EBZ#494555]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-216?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-216. ------------------------------- Assignee: Roland Grunberg Resolution: Done Patch reviewed and merged > Running image, which has shell form of CMD needs to be enclosed in quotes [EBZ#494555] > -------------------------------------------------------------------------------------- > > Key: ERT-216 > URL: https://issues.jboss.org/browse/ERT-216 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > > Running image, which was build using dockerfile with CMD in shell form (for example greyltc/lamp) needs to be enclosed in quotes. > Steps to reproduce: > * Pull image which was build using dockerfile with CMD in shell form (for example greyltc/lamp from docker hub) > * In Docker Explorer right click that image -> Run > * Assert: command should be the same as running that image from command line > * FAIL: command is `/bin/sh -c start-servers; sleep infinity` instead of `/bin/sh -c 'start-servers; sleep infinity'` > Those missing quotes causes that container to stop right after it was started (which is not desired) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- Ok, so the rdevelopers-ci account for GtHub Pull Request Builder plugin on https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/credential-s... has a token with only status:repo permission. [~maxandersen] Then can you please add the rhdevelopers-ci user as a collaborator on all jbosstools-* and devstudio-* repos? > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22470) Integration tests not published to snapshots update site

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22470?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22470: ---------------------------------- Description: For some reason the update site here is outdated (from March 9): http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... We consume it here: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... The build is building just fine: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... And the result is here: http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... But for some reason it's not propagated to the standard url. Can you please check why that is? I checked the config but could not understand what's wrong. was: For some reason the update site here is outdated (from March 9): http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... We consume it here: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... The build is building just fine: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... And the result is here: http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... But for some reason it's not propagated to the standard url. Can you please check why is that? I checked the config but could not understand what's wrong. > Integration tests not published to snapshots update site > -------------------------------------------------------- > > Key: JBIDE-22470 > URL: https://issues.jboss.org/browse/JBIDE-22470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha3 > Reporter: Martin Malina > Assignee: Nick Boldt > > For some reason the update site here is outdated (from March 9): > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We consume it here: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > The build is building just fine: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > And the result is here: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > But for some reason it's not propagated to the standard url. > Can you please check why that is? I checked the config but could not understand what's wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22470) Integration tests not published to snapshots update site

by Martin Malina (JIRA)

Martin Malina created JBIDE-22470: ------------------------------------- Summary: Integration tests not published to snapshots update site Key: JBIDE-22470 URL: https://issues.jboss.org/browse/JBIDE-22470 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.0.Alpha3 Reporter: Martin Malina Assignee: Nick Boldt For some reason the update site here is outdated (from March 9): http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... We consume it here: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... The build is building just fine: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... And the result is here: http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... But for some reason it's not propagated to the standard url. Can you please check why is that? I checked the config but could not understand what's wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3881) Pass user password to devstudio as environment variable

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3881?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3881. ----------------------------- Verified in B161. > Pass user password to devstudio as environment variable > ------------------------------------------------------- > > Key: JBDS-3881 > URL: https://issues.jboss.org/browse/JBDS-3881 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha2 > > > To avoid re-prompting password during vagrant-up configure env variable rhel.subscription.password with user password when launching DevStudio form installer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3889) Remove JBoss from Platform Installer full name

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3889?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3889. ----------------------------- Verified in B161. > Remove JBoss from Platform Installer full name > ---------------------------------------------- > > Key: JBDS-3889 > URL: https://issues.jboss.org/browse/JBDS-3889 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha2 > > > Platform installer full name is "Red Hat Developer Studio Platform Installer" and it should be updated in many places throughout Plafrom Installer: > 1. Banner > 2. Window title > 3. Confirmation page Dev Studio name > 4. Start up page Dev Studio name > 5. Exec file "Details" tab info > 6. Target install folder name (see JBDS-3874) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3666) Back off and retry if download fails

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3666?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3666. ----------------------------- There have been some issues with this, but since they have their own jiras, I'm going to close this one. For more info, refer to JBDS-3906 and JBDS-3912. > Back off and retry if download fails > ------------------------------------ > > Key: JBDS-3666 > URL: https://issues.jboss.org/browse/JBDS-3666 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Story > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Critical > Labels: Havoc, new_and_noteworthy, user-docs > Fix For: 10.0.0.Alpha2 > > Attachments: download-again.png > > > We should back off and retry downloads when they fail, automatically. We should also off a manual retry button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-295) utilize the tycho testing support for test bundles on JBTIS

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-295?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-295: ----------------------------------------- Actually, the "fast" suite of smoke tests for Fuse tooling is in progress. Our plan is to run such smoke tests for each PR (just with JBTIS dependencies as a verification job). Moreover, every night we execute some subset of tests for the latest build of Fuse tooling with the latest version of JBDS (corrently only with 9.x). Something similar we plan for the Teiid Designer but not for the other components (there are no changes or only small changes). I'm not sure what's the exact goal of this issue. All work mentioned above will be done on Fuse (resp. TD) side so that developers can immediately see what's wrong. > utilize the tycho testing support for test bundles on JBTIS > ----------------------------------------------------------- > > Key: JBTIS-295 > URL: https://issues.jboss.org/browse/JBTIS-295 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: testing > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > > Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse. > [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution > [~rcernich] would this cover you intended use case ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

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 June 2016