September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4057) cdk fails, online install

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-4057?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-4057: ---------------------------- Component/s: installer > cdk fails, online install > ------------------------- > > Key: JBDS-4057 > URL: https://issues.jboss.org/browse/JBDS-4057 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Reporter: Misha Ali > > I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue. > I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3838) Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3838: --------------------------------- [~jrichter1] - we need to document the workaround if it is tested and working reliably enough to recommend to users. [~akazakov], do you agree? Jan, can you detail the steps you used in the workaround? I'll try it and document it as well. > Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3838 > URL: https://issues.jboss.org/browse/JBDS-3838 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: install.log, vagrant.log, vbox.log > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23206) build flag for always use current timestamp to assist QE in testing PRs

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23206?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23206: ---------------------------------------- I like the idea. +1 to merge and use it. > build flag for always use current timestamp to assist QE in testing PRs > ----------------------------------------------------------------------- > > Key: JBIDE-23206 > URL: https://issues.jboss.org/browse/JBIDE-23206 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Nick Boldt > > In the case where a PR is not rebased against master constantly, QE is blocked from testing it under two situations: > 1) The PR job has produced a site. QE installs most recent jbt, then tries to install the PR site. This fails because the PR site is older than the nightly build. > 2) The QE rep checks out the PR and tries to build locally. The timestamps match the change date (ie the date the PR was last changed), which is still older than the nightly build. > In both situations, QE cannot install a locally-built or PR-built site on top of a more recent nightly build of JBT. We cannot expect QE to rebase and (if required) merge / change code. > The best bet here is to simply add a flag QE can use when building locally to always use current timestamp, to ensure locally built unit is always 'newest'. > We then document that flag in devdoc for QE and make it part of their standard workflow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23209) Notify PR associated users, when CI build for the PR fails

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23209?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23209: ----------------------------------- Component/s: build > Notify PR associated users, when CI build for the PR fails > ---------------------------------------------------------- > > Key: JBIDE-23209 > URL: https://issues.jboss.org/browse/JBIDE-23209 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Dmitrii Bocharov > Assignee: Nick Boldt > Priority: Minor > > Create Jenkins hook, which will notify people involved in the commits that build is failing and notifying them back when build is back to ok -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23209) Notify PR associated users, when CI build for the PR fails

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23209?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23209: ----------------------------------- Issue Type: Task (was: Feature Request) > Notify PR associated users, when CI build for the PR fails > ---------------------------------------------------------- > > Key: JBIDE-23209 > URL: https://issues.jboss.org/browse/JBIDE-23209 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Dmitrii Bocharov > Assignee: Nick Boldt > Priority: Minor > > Create Jenkins hook, which will notify people involved in the commits that build is failing and notifying them back when build is back to ok -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23209) Notify PR associated users, when CI build for the PR fails

by Dmitrii Bocharov (JIRA)

Dmitrii Bocharov created JBIDE-23209: ---------------------------------------- Summary: Notify PR associated users, when CI build for the PR fails Key: JBIDE-23209 URL: https://issues.jboss.org/browse/JBIDE-23209 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Dmitrii Bocharov Priority: Minor Create Jenkins hook, which will notify people involved in the commits that build is failing and notifying them back when build is back to ok -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23209) Notify PR associated users, when CI build for the PR fails

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23209?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-23209: ---------------------------------------- Assignee: Nick Boldt > Notify PR associated users, when CI build for the PR fails > ---------------------------------------------------------- > > Key: JBIDE-23209 > URL: https://issues.jboss.org/browse/JBIDE-23209 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Dmitrii Bocharov > Assignee: Nick Boldt > Priority: Minor > > Create Jenkins hook, which will notify people involved in the commits that build is failing and notifying them back when build is back to ok -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23029: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/1609, https://github.com/jbosstools/jbosstools-openshift/pull/1325 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1609, https://github.com/jbosstools/jbosstools-openshift/pull/1322) > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.Final > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23206) build flag for always use current timestamp to assist QE in testing PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23206?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23206: ------------------------------------ Discussion w/ wider audience to follow: http://lists.jboss.org/pipermail/jbosstools-dev/2016-September/011660.html > build flag for always use current timestamp to assist QE in testing PRs > ----------------------------------------------------------------------- > > Key: JBIDE-23206 > URL: https://issues.jboss.org/browse/JBIDE-23206 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Nick Boldt > > In the case where a PR is not rebased against master constantly, QE is blocked from testing it under two situations: > 1) The PR job has produced a site. QE installs most recent jbt, then tries to install the PR site. This fails because the PR site is older than the nightly build. > 2) The QE rep checks out the PR and tries to build locally. The timestamps match the change date (ie the date the PR was last changed), which is still older than the nightly build. > In both situations, QE cannot install a locally-built or PR-built site on top of a more recent nightly build of JBT. We cannot expect QE to rebase and (if required) merge / change code. > The best bet here is to simply add a flag QE can use when building locally to always use current timestamp, to ensure locally built unit is always 'newest'. > We then document that flag in devdoc for QE and make it part of their standard workflow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22912: ------------------------------------- If this works, can it be merged in? > Deploy Docker Wizard: Inappropriate project combo size > ------------------------------------------------------ > > Key: JBIDE-22912 > URL: https://issues.jboss.org/browse/JBIDE-22912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Environment: Fedora 24, GTK 3 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: dbocharov_inapproperiateComboSize.webm, dbocharov_inapproperiateComboSize_debug.webm, deploy-to-docker-wizard-fc23.png, project_combo.png > > > In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good. > !project_combo.png! -- 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