August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3977) Devstudio version string needs update

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3977?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3977: ----------------------------------- Assignee: Jan Richter (was: Denis Golovin) > Devstudio version string needs update > ------------------------------------- > > Key: JBDS-3977 > URL: https://issues.jboss.org/browse/JBDS-3977 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.1.0.AM3 > > > As per requirements.json, the static version field for devstudio is still set to 10.0.1.Alpha1. We need to update this and preferably find some way to do this effortlessly any time the version changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22877) Update RedDeer in TP for JBT 4.4.1.AM3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22877?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-22877 at 8/4/16 4:37 PM: --------------------------------------------------------------- Wait a minute, I thought you copy the bits from a location one time to the TP and then it's there. So you're saying that the TP will always only point to the location that I give you? OK then, fair enough. I tried to run jbosstools_rsync here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... The build is red, but the update site still seems to be up at http://download.jboss.org/jbosstools/neon/development/updates/reddeer/1.1... The cleanup script could not be found. {code} 16:17:02 /tmp/hudson38112553799167838.sh: line 26: jbosstools-cleanup.sh: command not found {code} It worked for me two weeks ago. I noticed that while rsync is referenced correctly in the shell step: {code}${WORKSPACE}/sources/publish/rsync.sh{code} the cleanup script is called like this: {code}jbosstools-cleanup.sh{code} which doesn't seem right - shouldn't that be this instead? {code}${WORKSPACE}/sources/util/cleanup/jbosstools-cleanup.sh{code} So I fixed this and now the build is blue. But please check that I didn't screw it up. Regarding a Final version - yes, 1.1.0.Final is planned in time for the TP freeze at the end of August. But I would like to point out that what we have in the TP right now is not a Final either, so I'm not sure what you'd want to roll back to ;) was (Author: mmalina): Wait a minute, I thought you copy the bits from a location one time to the TP and then it's there. So you're saying that the TP will always only point to the location that I give you? OK then, fair enough. I tried to run jbosstools_rsync here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... The build is red, but the update site still seems to be up at http://download.jboss.org/jbosstools/neon/development/updates/reddeer/1.1... The cleanup script could not be found. {code} 16:17:02 /tmp/hudson38112553799167838.sh: line 26: jbosstools-cleanup.sh: command not found {code} It worked for me two weeks ago. I noticed that while rsync is referenced correctly in the shell step: ${WORKSPACE}/sources/publish/rsync.sh the cleanup script is called like this: jbosstools-cleanup.sh which doesn't seem right - shouldn't that be this instead? ${WORKSPACE}/sources/util/cleanup/jbosstools-cleanup.sh So I fixed this and now the build is blue. But please check that I didn't screw it up. Regarding a Final version - yes, 1.1.0.Final is planned in time for the TP freeze at the end of August. But I would like to point out that what we have in the TP right now is not a Final either, so I'm not sure what you'd want to roll back to ;) > Update RedDeer in TP for JBT 4.4.1.AM3 > -------------------------------------- > > Key: JBIDE-22877 > URL: https://issues.jboss.org/browse/JBIDE-22877 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient. > Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.) > Once this is done, it should be available on the current TP within a day? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22877) Update RedDeer in TP for JBT 4.4.1.AM3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22877?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22877: --------------------------------------- Wait a minute, I thought you copy the bits from a location one time to the TP and then it's there. So you're saying that the TP will always only point to the location that I give you? OK then, fair enough. I tried to run jbosstools_rsync here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... The build is red, but the update site still seems to be up at http://download.jboss.org/jbosstools/neon/development/updates/reddeer/1.1... The cleanup script could not be found. {code} 16:17:02 /tmp/hudson38112553799167838.sh: line 26: jbosstools-cleanup.sh: command not found {code} It worked for me two weeks ago. I noticed that while rsync is referenced correctly in the shell step: ${WORKSPACE}/sources/publish/rsync.sh the cleanup script is called like this: jbosstools-cleanup.sh which doesn't seem right - shouldn't that be this instead? ${WORKSPACE}/sources/util/cleanup/jbosstools-cleanup.sh So I fixed this and now the build is blue. But please check that I didn't screw it up. Regarding a Final version - yes, 1.1.0.Final is planned in time for the TP freeze at the end of August. But I would like to point out that what we have in the TP right now is not a Final either, so I'm not sure what you'd want to roll back to ;) > Update RedDeer in TP for JBT 4.4.1.AM3 > -------------------------------------- > > Key: JBIDE-22877 > URL: https://issues.jboss.org/browse/JBIDE-22877 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient. > Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.) > Once this is done, it should be available on the current TP within a day? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22872) Create integration tests PR check job for mylyn

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22872?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22872: --------------------------------- Original Estimate: 3 hours Remaining Estimate: 3 hours > Create integration tests PR check job for mylyn > ----------------------------------------------- > > Key: JBIDE-22872 > URL: https://issues.jboss.org/browse/JBIDE-22872 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.4.x > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.4.x > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22776) Create integration tests PR check job for arquilian

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22776?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22776: --------------------------------- Original Estimate: 3 hours (was: 3 days) Remaining Estimate: 3 hours (was: 3 days) > Create integration tests PR check job for arquilian > --------------------------------------------------- > > Key: JBIDE-22776 > URL: https://issues.jboss.org/browse/JBIDE-22776 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Len DiMaggio > Fix For: 4.4.x > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22882) vagrant-sshfs plugin prevents CDK server adapter from starting

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22882?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22882: ------------------------------------- Fails to work on linux: [rob@rawbdor rhel-ose]$ uname -a Linux rawbdor 4.4.13-200.fc22.x86_64 #1 SMP Wed Jun 8 15:59:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux {code} [rob@rawbdor 20160720]$ vagrant plugin uninstall vagrant-sshfs Uninstalling the 'vagrant-sshfs' plugin... [rob@rawbdor 20160720]$ vagrant plugin install ./vagrant-sshfs-1.1.0.issue.41.gem Installing the './vagrant-sshfs-1.1.0.issue.41.gem' plugin. This can take a few minutes... /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/resolver.rb:439:in `resolve_for_zero': Unable to resolve dependency: 'vagrant-sshfs (= 1.1.0.issue.41)' requires 'win32-process (>= 0)' (Gem::UnsatisfiableDependencyError) from /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/resolver.rb:350:in `resolve_for' from /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/resolver.rb:196:in `resolve' from /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/request_set.rb:363:in `resolve' from /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/dependency_installer.rb:483:in `resolve_dependencies' from /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/dependency_installer.rb:383:in `install' from /usr/share/vagrant/lib/vagrant/bundler.rb:124:in `block in install_local' from /usr/share/vagrant/lib/vagrant/bundler.rb:284:in `block in with_isolated_gem' from /home/rob/.rvm/rubies/ruby-2.2.4/lib/ruby/site_ruby/2.2.0/rubygems/user_interaction.rb:45:in `use_ui' from /usr/share/vagrant/lib/vagrant/bundler.rb:283:in `with_isolated_gem' from /usr/share/vagrant/lib/vagrant/bundler.rb:121:in `install_local' from /usr/share/vagrant/lib/vagrant/plugin/manager.rb:47:in `install_plugin' from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:37:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builder.rb:116:in `call' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `block in run' from /usr/share/vagrant/lib/vagrant/util/busy.rb:19:in `busy' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in `action' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:32:in `block in execute' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `each' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `execute' from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in `execute' from /usr/share/vagrant/lib/vagrant/cli.rb:42:in `execute' from /usr/share/vagrant/lib/vagrant/environment.rb:301:in `cli' from /usr/share/vagrant/bin/vagrant:174:in `<main>' {code} If I install win32-process, it errors differently: {code} [rob@rawbdor rhel-ose]$ vagrant plugin install win32-process Installing the 'win32-process' plugin. This can take a few minutes... Installed the plugin 'win32-process (0.8.3)'! [rob@rawbdor rhel-ose]$ vagrant plugin install ../../../../vagrant-sshfs-1.1.0.issue.41.gem Installing the '../../../../vagrant-sshfs-1.1.0.issue.41.gem' plugin. This can take a few minutes... Installed the plugin 'vagrant-sshfs (1.1.0.issue.41)'! [rob@rawbdor rhel-ose]$ SUB_USERNAME=xxx SUB_PASSWORD=xxx vagrant up Vagrant failed to initialize at a very early stage: The plugins failed to load properly. The error message given is shown below. unable to resolve type 'uintptr_t' {code} > vagrant-sshfs plugin prevents CDK server adapter from starting > -------------------------------------------------------------- > > Key: JBIDE-22882 > URL: https://issues.jboss.org/browse/JBIDE-22882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > > This is a follow up issue on JBIDE-22604. > The problem was fixed in CDK 2.1.0 by removing sshfs setup in the default Vagrant file. The original upstream issue still need to be fixed if we want to enable sshfs setup in the default Vagrant file which is used by devstudio by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22680: --------------------------------- Original Estimate: 3 days Remaining Estimate: 3 days > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > Fix For: 4.4.x > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22883) Client: release and use a final 5.0 artifact of openshift-restclient-java

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22883?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22883: ------------------------------- Description: 4.4.1.AM3 is using openshift-restclient-java 5.0.0-SNAPSHOT. We should release a final version of the client and use it in the tooling https://repository.jboss.org/nexus/#nexus-search;gav~com.openshift~opensh... was:4.4.1.AM3 is using openshift-restclient-java 5.0.0-SNAPSHOT. We should release a final version of the client and use it in the tooling > Client: release and use a final 5.0 artifact of openshift-restclient-java > -------------------------------------------------------------------------- > > Key: JBIDE-22883 > URL: https://issues.jboss.org/browse/JBIDE-22883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.1.Final > > > 4.4.1.AM3 is using openshift-restclient-java 5.0.0-SNAPSHOT. We should release a final version of the client and use it in the tooling > https://repository.jboss.org/nexus/#nexus-search;gav~com.openshift~opensh... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22883) Client: release and use a final 5.0 artifact of openshift-restclient-java

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22883?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22883: ------------------------------- Description: 4.4.1.AM3 is using openshift-restclient-java 5.0.0-SNAPSHOT. We should release a final version of the client and use it in the tooling (was: 4.4.0.Alpha2 is using openshift-restclient-java 4.0.4-SNAPSHOT. We should release a final version of the client and use it in the tooling) > Client: release and use a final 5.0 artifact of openshift-restclient-java > -------------------------------------------------------------------------- > > Key: JBIDE-22883 > URL: https://issues.jboss.org/browse/JBIDE-22883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.1.Final > > > 4.4.1.AM3 is using openshift-restclient-java 5.0.0-SNAPSHOT. We should release a final version of the client and use it in the tooling -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22883) Client: release and use a final 5.0 artifact of openshift-restclient-java

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22883: ---------------------------------- Summary: Client: release and use a final 5.0 artifact of openshift-restclient-java Key: JBIDE-22883 URL: https://issues.jboss.org/browse/JBIDE-22883 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.4.0.Final 4.4.0.Alpha2 is using openshift-restclient-java 4.0.4-SNAPSHOT. We should release a final version of the client and use it in the tooling -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016