May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Dmitry Bocharov reassigned JBIDE-21121: --------------------------------------- Assignee: Dmitry Bocharov > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha3 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3910) Include EAP 7.0 in JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3910?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3910: ---------------------------------- Blocked by https://trello.com/c/L5i8c0ff/142-devstudio-bundle-eap-7-0-0-instead-of-t... which is blocked by * https://trello.com/c/HUmodtDe * https://trello.com/c/wwn8i1dW * https://trello.com/c/LzOiis3X > Include EAP 7.0 in JBDS installer > --------------------------------- > > Key: JBDS-3910 > URL: https://issues.jboss.org/browse/JBDS-3910 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Component Upgrade > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > > Include EAP 7.0.0 in JBDS 9.1.0 installer. Once ready, add it to http://www.jboss.org/products/devstudio/download/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21068) Project wizard: Set maximum length for display name

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21068?page=com.atlassian.jira.plugi... ] Dmitry Bocharov reassigned JBIDE-21068: --------------------------------------- Assignee: Dmitry Bocharov (was: Alexey Kazakov) > Project wizard: Set maximum length for display name > --------------------------------------------------- > > Key: JBIDE-21068 > URL: https://issues.jboss.org/browse/JBIDE-21068 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Dmitry Bocharov > Priority: Minor > Labels: openshift_v3, project_wizard > Fix For: 4.4.0.Alpha3 > > > Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3739 at 5/24/16 12:11 PM: --------------------------------------------------------------- Attaching a jstack report of the frozen Eclipse: [^docker-frozen.txt] BTW, I tried this three times and eclipse froze each time. I'm on Mac. Marian does NOT get Eclipse freeze on his linux. was (Author: mmalina): Attaching a jstack report of the frozen Eclipse: [^docker-frozen.txt] BTW, I tried this three times and eclipse froze each time. I'm on Mac. Marian does get Eclipse freeze on his linux. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.x > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21657: ------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20474) combine fewer CI builds into generated composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20474?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20474: ------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > combine fewer CI builds into generated composite site > ----------------------------------------------------- > > Key: JBIDE-20474 > URL: https://issues.jboss.org/browse/JBIDE-20474 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha3 > > > [18/08/2015 15:29:34] Fred Bricon: when building central, I see > [18/08/2015 15:29:36] Fred Bricon: [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,58kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,18kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,93kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,88kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,25kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,77kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,43kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,94kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,74kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,7kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,58kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,95kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,11kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,86kB at 0B/s) > Nick sez: > {quote} > somethign something "store fewer instances of /snapshots/builds /JOB_NAME/TIMESTAMP; more aggressive cleanup required; suggest only keeping 5 builds max" > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3739: -------------------------------- Attachment: docker-frozen.txt Attaching a jstack report of the frozen Eclipse: [^docker-frozen.txt] BTW, I tried this three times and eclipse froze each time. I'm on Mac. Marian does get Eclipse freeze on his linux. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.x > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20904: ------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > automate publishing latest CI build to staging, then from staging to development (or stable) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-comman... > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13671: ------------------------------- Sprint: (was: devex #114 May 2016) > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16158: ------------------------------- Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, devex #115 May 2016 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, devex #114 May 2016) > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha3 > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016