September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23016: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22965: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23049) Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23049?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23049: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2 > --------------------------------------------------------------------------------------- > > Key: JBIDE-23049 > URL: https://issues.jboss.org/browse/JBIDE-23049 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 4.4.1.Final > Environment: Eclipse SDK > Version: Neon.1 (4.6.1) > Build id: M20160824-0059 > JBoss Tools from update site: > http://download.jboss.org/jbosstools/neon/snapshots/updates/ > org.jboss.tools.common.mylyn: > 3.8.1.v20160607-2053 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.4.2.AM2 > > > An error is shown in error log after installing JBoss Tools in Eclipse Neon.1 RC2: > {code:java} > Unexpected error while loading repository template extensions > Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'bugzilla' > {code} > Stacktrace: > {code:java} > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23091: ------------------------------- Summary: use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied (was: use #close smart tag in commit messages so JIRAs are closed automatically) > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22728: ---------------------------------- Assignee: Nick Boldt (was: Alexey Kazakov) > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > Attachments: console.log.txt, getProjectRootPomParents.tsk.txt > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in commit messages so JIRAs are closed automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23091: ------------------------------- Parent: (was: JBIDE-22728) Issue Type: Feature Request (was: Sub-task) > use #close smart tag in commit messages so JIRAs are closed automatically > ------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23124) install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23124?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23124. ------------------------------ Resolution: Rejected Rejecting. I'll bug you about this again in future, I'm sure. :D > install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23124 > URL: https://issues.jboss.org/browse/JBIDE-23124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.2.AM1 > > > {code} > 20:18:21 !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2016-09-02 20:18:21.888 > 20:18:21 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > {code} > 20:21:57 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.comhttps://jenkins.mw.lab.eng.bos.r... > and > {code} > 20:32:38 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/releases/neon/201606221000/plugins/or... failed on Connection refused. Retry attempt 0 started > {code} > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Should we be ignoring these failures? Should the install process be using eclipse mirrors? Or should we be installing against TPs under http://download.jboss.org/jbosstools/targetplatforms/ or our mirrors under http://download.jboss.org/jbosstools/updates/requirements/ ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23089) when central tests crash job breaks due to dirty workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23089?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23089. ------------------------------ Resolution: Done Assigning to Fred since he applied the PR, and closing since applied and nothing for QE to do. > when central tests crash job breaks due to dirty workspace > ---------------------------------------------------------- > > Key: JBIDE-23089 > URL: https://issues.jboss.org/browse/JBIDE-23089 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.1.Final, 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.2.AM1 > > > {code} > 15:00:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.26.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.central.test: Working tree is dirty. > 15:00:03 [ERROR] git status central/tests/org.jboss.tools.central.test: > 15:00:03 [ERROR] > 15:00:03 [ERROR] Untracked files: > 15:00:03 [ERROR] central/tests/org.jboss.tools.central.test/hs_err_pid29878.log > 15:00:03 [ERROR] > 15:00:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above). > 15:00:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring > 15:00:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin{code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Workaround: > wipe workspace, try again > Solution: > add hs_err_pid*.log to .gitignore -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23089) when central tests crash job breaks due to dirty workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23089?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23089: ---------------------------------- Assignee: Fred Bricon > when central tests crash job breaks due to dirty workspace > ---------------------------------------------------------- > > Key: JBIDE-23089 > URL: https://issues.jboss.org/browse/JBIDE-23089 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.1.Final, 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.2.AM1 > > > {code} > 15:00:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.26.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.central.test: Working tree is dirty. > 15:00:03 [ERROR] git status central/tests/org.jboss.tools.central.test: > 15:00:03 [ERROR] > 15:00:03 [ERROR] Untracked files: > 15:00:03 [ERROR] central/tests/org.jboss.tools.central.test/hs_err_pid29878.log > 15:00:03 [ERROR] > 15:00:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above). > 15:00:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring > 15:00:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin{code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Workaround: > wipe workspace, try again > Solution: > add hs_err_pid*.log to .gitignore -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4025) Staging process should take advantage of staging download area

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4025?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4025: ---------------------------------- Not sure I understand. Where is this Staging download area? How does one publish there? > Staging process should take advantage of staging download area > -------------------------------------------------------------- > > Key: JBDS-4025 > URL: https://issues.jboss.org/browse/JBDS-4025 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 10.2.0.AM2 > > > Since there is now a Staging download area, we should adapt our staging process to stage bits to this area rather than in our internal directories. QE would then retrieve staged content from this download area, and test a bit more of the full user experience of getting RHDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016