April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21634: --------------------------------------- @fbricon and I talked about how this would be manifested in the UI. I proposed a context menu that would offer 3 entries: * Scale Up (increments replica count by 1) * Scale Down (decrements replica count by 1) * Scale To... (presents user with an input box) max would be same as what web offers This change would only affect the replica controller and would fall back to what is defined in the DC if a new deployment occurs. Possible enhancement would allow a user to also update their dc (or we would just update the dc which would trigger a new deployment with the given number of replicas) [~fbricon] [~adietish] [~maxandersen] Thoughts? > Explorer, Properties: Allow a user to scale their deployment > ------------------------------------------------------------ > > Key: JBIDE-21634 > URL: https://issues.jboss.org/browse/JBIDE-21634 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of: > 1. deployment (replication controller) > 2. eclipse view of a deployment (server) -> walk back to the currrent deployment > 3. pod -> walk back to the current deployment > updating 'spec.replicas' causes a new pods to spin up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-527: ---------------------------------- After discussing with Nick - I rolled all versions back from 9.0.0.GA to 9.0.0-SNAPSHOT but still failed to generate a full version formatted feature jar based on 'qualifer' . I don't want to change this much this close to GA (we're at smoke test) so I'll tackle this again post JBDSIS 9.0.0.GA (9.0.1). ref: https://github.com/jbosstools/jbosstools-jst/blob/master/features/org.jbo... https://github.com/jbosstools/jbosstools-jst/blob/master/features/org.jbo... [~apodhrad] [~nickboldt1] ^^ > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.A... I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22141) jboss-app.xml validate problem in JBDS 8.0.0.GA.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22141?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22141: ------------------------------------- https://github.com/jboss/metadata/pull/105 for a patch to the upstream > jboss-app.xml validate problem in JBDS 8.0.0.GA. > ------------------------------------------------ > > Key: JBIDE-22141 > URL: https://issues.jboss.org/browse/JBIDE-22141 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final > Reporter: xu zhang > Assignee: Rob Stryker > Fix For: 4.4.x > > > Create "jboss-app.xml" from attachment of article "https://access.redhat.com/solutions/268733" in JBDS 8.0.0, error shows: > ~~~ > No grammar constraints (DTD or XML Schema) referenced in the document. > ~~~ > Customer wants JBDS to validate "jboss-app.xml" correctly. > Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-527: ----------------------------- Priority: Minor (was: Blocker) > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.A... I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22226) Forge Wizard Cheatsheet Line Bug when moving backwards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22226?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22226: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 > Forge Wizard Cheatsheet Line Bug when moving backwards > ------------------------------------------------------ > > Key: JBIDE-22226 > URL: https://issues.jboss.org/browse/JBIDE-22226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Burr Sutter > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha2 > > > See the video > http://screencast.com/t/xmTabea5I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 #6 April 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.Alpha1 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17117) Simplify release (milestone or GA) process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17117?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17117: ------------------------------- Sprint: devex #7 May 2017 (was: devex #6 April 2016) > Simplify release (milestone or GA) process > ------------------------------------------ > > Key: JBIDE-17117 > URL: https://issues.jboss.org/browse/JBIDE-17117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > We could work on improving the publishing process for milestones or GA. Some ideas: > * Why do we rename the files we pull on sf.net. Also, renaming files could happen on sf.net. > * Files from sf.net could be fetch after (for example in parallel with creating marketplace entry) > * webtools should be published in a similar way as other parts (moved to tools/static/releases and then referenced in the composite file) > * Replace the .core, .webtools, .hibernatetools, .coretests suffix by actual URL segments, so one would only have to move a single folder instead of 4 ones. > * Identify things that can be done in parallel. > * ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22151?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22151: -------------------------------- Story Points: 1 > Failed to install JBT in Eclipse > -------------------------------- > > Key: JBIDE-22151 > URL: https://issues.jboss.org/browse/JBIDE-22151 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.0.Alpha1 > Environment: Operating System: have tried Fedora 17 and 22 > jbt version: 3.2.0.Alpha1-v20160409-1043-B1241 > eclipse: > Version: Neon Milestone 6 (4.6.0M6) > Build id: 20160329-0659 > Reporter: Chunyun Chen > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > Attachments: jbt_installation_1.png, jbt_installation_2.png > > > Will meet below dependency errors when installing jbt in eclipse: > " > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241) > Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found > Cannot satisfy dependency: > From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241) > To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241] > " -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17117) Simplify release (milestone or GA) process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17117?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17117: ------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > Simplify release (milestone or GA) process > ------------------------------------------ > > Key: JBIDE-17117 > URL: https://issues.jboss.org/browse/JBIDE-17117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > We could work on improving the publishing process for milestones or GA. Some ideas: > * Why do we rename the files we pull on sf.net. Also, renaming files could happen on sf.net. > * Files from sf.net could be fetch after (for example in parallel with creating marketplace entry) > * webtools should be published in a similar way as other parts (moved to tools/static/releases and then referenced in the composite file) > * Replace the .core, .webtools, .hibernatetools, .coretests suffix by actual URL segments, so one would only have to move a single folder instead of 4 ones. > * Identify things that can be done in parallel. > * ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21870) Update Arquillian bot tests to be in synch with name change to Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21870?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21870: -------------------------------------- Fix Version/s: 4.3.0.Final Assignee: Len DiMaggio Resolution: Done > Update Arquillian bot tests to be in synch with name change to Central > ---------------------------------------------------------------------- > > Key: JBIDE-21870 > URL: https://issues.jboss.org/browse/JBIDE-21870 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.1.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.Final > > > JBoss Central is now "Red Hat Central" > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016