September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3981: ---------------------------------- Testing smart commits and workflow transitions > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3978: -------------------------------- Fix Version/s: 10.1.0.GA (was: 10.2.0.AM1) > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.GA > > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview which redirects to https://access.redhat.com/articles/2255401 > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} - refers to CDK 2.0 and JBoss Developer Studio 9.0 - looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating, especially since the devsuite installer is no longer a Technology Preview. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3978. --------------------------------- Resolution: Done > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.GA > > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview which redirects to https://access.redhat.com/articles/2255401 > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} - refers to CDK 2.0 and JBoss Developer Studio 9.0 - looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating, especially since the devsuite installer is no longer a Technology Preview. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23090) instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23090?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23090. ------------------------------ Resolution: Done > instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23090 > URL: https://issues.jboss.org/browse/JBIDE-23090 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email so that Alexey or Jeff can run it locally in their /tmp folder > 1. script how to fetch jbosstools-build-ci > 2. script how to then run getProjectRootPomParents.sh -w1 /tmp/some-folder/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23090) instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23090?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23090: ------------------------------------ Mr Gorbachev, tear down this JIRA! > instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23090 > URL: https://issues.jboss.org/browse/JBIDE-23090 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email so that Alexey or Jeff can run it locally in their /tmp folder > 1. script how to fetch jbosstools-build-ci > 2. script how to then run getProjectRootPomParents.sh -w1 /tmp/some-folder/ -- 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 edited comment on JBIDE-23091 at 9/21/16 3:48 PM: ------------------------------------------------------------- Seems that currently, despite instructions [1], #close and #resolve don't work to close or resolve an issue in JIRA. [1] https://confluence.atlassian.com/bitbucket/processing-jira-software-issue... Some things I tried: {code:title=https://issues.jboss.org/browse/JBIDE-23090?devStatusDetailDialog=repository} "JBIDE-23090 #time 30m #comment Fixed - this commit comment should cause this JIRA to be auto-closed. #close" "JBIDE-23090 #resolve Issue resolved by smart commit" "JBIDE-23090 #resolve #comment seems that while I can put a comment in a JIRA with smart commit comments, I can't cause an issue to be resolved or closed #resolve #close" "JBIDE-23090 #resolve" "JBIDE-23090 #resolved" "JBIDE-23090 #close #comment Mr Gorbachev, tear down this JIRA! " {code} Only thing that DID work was being able to auto-comment in JIRAs when pushing a commit to github: https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296702&pag... and https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296704&pag... was (Author: nickboldt): Seems that currently, despite instructions [1], #close and #resolve don't work to close or resolve an issue in JIRA. [1] https://confluence.atlassian.com/bitbucket/processing-jira-software-issue... Some things I tried: {code:title=https://issues.jboss.org/browse/JBIDE-23090?devStatusDetailDialog=repository} "JBIDE-23090 #time 30m #comment Fixed - this commit comment should cause this JIRA to be auto-closed. #close" "JBIDE-23090 #resolve Issue resolved by smart commit" "JBIDE-23090 #resolve #comment seems that while I can put a comment in a JIRA with smart commit comments, I can't cause an issue to be resolved or closed #resolve #close" "JBIDE-23090 #resolve" "JBIDE-23090 #resolved" {code} Only thing that DID work was being able to auto-comment in JIRAs when pushing a commit to github: https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296702&pag... and https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296704&pag... > 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: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > 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-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 edited comment on JBIDE-23091 at 9/21/16 3:45 PM: ------------------------------------------------------------- Seems that currently, despite instructions [1], #close and #resolve don't work to close or resolve an issue in JIRA. [1] https://confluence.atlassian.com/bitbucket/processing-jira-software-issue... Some things I tried: {code:title=https://issues.jboss.org/browse/JBIDE-23090?devStatusDetailDialog=repository} "JBIDE-23090 #time 30m #comment Fixed - this commit comment should cause this JIRA to be auto-closed. #close" "JBIDE-23090 #resolve Issue resolved by smart commit" "JBIDE-23090 #resolve #comment seems that while I can put a comment in a JIRA with smart commit comments, I can't cause an issue to be resolved or closed #resolve #close" "JBIDE-23090 #resolve" "JBIDE-23090 #resolved" {code} Only thing that DID work was being able to auto-comment in JIRAs when pushing a commit to github: https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296702&pag... and https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296704&pag... was (Author: nickboldt): Seems that currently, #close and #resolve don't work to close or resolve an issue in JIRA. Examples I tried: {code:title=https://issues.jboss.org/browse/JBIDE-23090?devStatusDetailDialog=repository} "JBIDE-23090 #time 30m #comment Fixed - this commit comment should cause this JIRA to be auto-closed. #close" "JBIDE-23090 #resolve Issue resolved by smart commit" "JBIDE-23090 #resolve #comment seems that while I can put a comment in a JIRA with smart commit comments, I can't cause an issue to be resolved or closed #resolve #close" "JBIDE-23090 #resolve" "JBIDE-23090 #resolved" {code} But we could put a #comment into a JIRA, such as here: https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296702&pag... and https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296704&pag... > 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: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > 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-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 edited comment on JBIDE-23091 at 9/21/16 3:45 PM: ------------------------------------------------------------- For this to work, we will need to be able to run createTaskJIRAs.py 17 times (once per project) and for each one, return the ID of the generated JIRA. Then, we can use that JIRA number when calling getProjectRootPomParents.sh so that commit comments when making changes look like this: {code} git commit -m \"JBIDE-23091 #close #comment bump up to parent pom version = $\{version_parent}\" {code} instead of {code} git commit -m \"bump up to parent pom version = $\{version_parent}\" {code} was (Author: nickboldt): For this to work, we will need to be able to run createTaskJIRAs.py 17 times (once per project) and for each one, return the ID of the generated JIRA. Then, we can use that JIRA number when calling getProjectRootPomParents.sh so that commit comments when making changes look like this: {code} git commit -m \"JBIDE-23091 #close bump up to parent pom version = $\{version_parent}\" {code} instead of {code} git commit -m \"bump up to parent pom version = $\{version_parent}\" {code} > 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: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > 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-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 commented on JBIDE-23091: ------------------------------------ Seems that currently, #close and #resolve don't work to close or resolve an issue in JIRA. Examples I tried: {code:title=https://issues.jboss.org/browse/JBIDE-23090?devStatusDetailDialog=repository} "JBIDE-23090 #time 30m #comment Fixed - this commit comment should cause this JIRA to be auto-closed. #close" "JBIDE-23090 #resolve Issue resolved by smart commit" "JBIDE-23090 #resolve #comment seems that while I can put a comment in a JIRA with smart commit comments, I can't cause an issue to be resolved or closed #resolve #close" "JBIDE-23090 #resolve" "JBIDE-23090 #resolved" {code} But we could put a #comment into a JIRA, such as here: https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296702&pag... and https://issues.jboss.org/browse/JBIDE-23090?focusedCommentId=13296704&pag... > 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: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > 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] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.

by Robert Terzi (JIRA)

[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ] Robert Terzi commented on JBDS-3863: ------------------------------------ See JBDS-4056, created a new ticket to deal with the vagrant box add issue starting with 1.1.0 GA. (leaving this ticket to deal with the issue of how to installer responds to installation failures.) > Platform Installer Hung after CDK install failed, no way to cancel, no info on error. > -------------------------------------------------------------------------------------- > > Key: JBDS-3863 > URL: https://issues.jboss.org/browse/JBDS-3863 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA, 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (Some components of previous manual CDK install on the system). > Also Windows 10/64. > Reporter: Robert Terzi > Assignee: Denis Golovin > Fix For: 10.2.0.AM1 > > Attachments: box-add-fail-1.1.0-ga.txt, install.log, jbds-install-log-win7-error.txt > > > Using the platform installer, CDK installation failed, progress shown as 99%. At this point the installer was hung. > Note: > * CDK install progress said Failed, with progress stuck at 99%. > * There is no way to cancel out of the install. > * There was no pop-up about error messages. > * No indication of where to look for error messages/logs etc.was provided. > * CDK was previously installed manually. However, the installer window didn't say a previous CDK installation was detected, but the log does show it deleted the previous cdkv2 box. > From the log it looks like the box add command failed. When originally reported it might have been due to disk space, but it's not clear/obvious from the log. As of DevSuite 1.1.0 GA, the problems still exists if the vagrant box add command fails. Note: I've verified this isn't related to disk space and is a Vagrant problem. > Note: after killing the installer and trying the `vagrant box add` command copied from the log file manually in Cygwin bash the box add command succeeded. The test system had 5-15 GB of free space between the installation started. > Full log attached, excerpt here. > Tue, 26 Apr 2016 18:05:38 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - postVagrantSetup called > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute command vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Installing the 'c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem' plugin. This can take a few minutes... > Installed the plugin 'vagrant-registration (1.2.1)'! > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" SUCCESS > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Removing box 'cdkv2' (v0) with provider 'virtualbox'... > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute vagrant box remove cdkv2 -f SUCCESS > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. -- 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