October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23368: ---------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-23368: ------------------------------------- Summary: Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard Key: JBIDE-23368 URL: https://issues.jboss.org/browse/JBIDE-23368 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM2 Reporter: Marián Labuda When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-931) Update some properties in SwitchYard Debugger tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-931?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-931. ------------------------------ Resolution: Done PR was pushed to master, jbtis-4.3.x, jbtis-4.4.x branches > Update some properties in SwitchYard Debugger tests > --------------------------------------------------- > > Key: JBTIS-931 > URL: https://issues.jboss.org/browse/JBTIS-931 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.2.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final, 4.3.3.Final > > > Update the following properties: > * switchyard.version in aux project 'hello' > * during debugging you don't need to compare whether the execution has stopped at the exact line (the line number can be changed after applying a fix or something like that) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-929) Fuse project starter is available in Central only if we check EarlyAccess

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-929?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-929: ----------------------------------------- Yes, you can enable the fuse by default in 9.x (currently, there's nothing in EA 9.x) > Fuse project starter is available in Central only if we check EarlyAccess > ------------------------------------------------------------------------- > > Key: JBTIS-929 > URL: https://issues.jboss.org/browse/JBTIS-929 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 9.0.2.GA > Environment: JBDS 9.1.0.GA + JBDS-IS 9.0.2.GA > Reporter: Andrej Podhradsky > > Fuse project starter is available in Central only if we check EarlyAccess. Moreover, if you close and reopen the RedHat Central then the project starter dissappears. You have to uncheck and check the EA again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-3509: ----------------------------------- Work is in progress to get a rh-eclipse46-devstudio rpm package into RHSCL (RH Software Collections), using droplets (not dropins). See JBDS-3984. This means that most (all?) of the dependencies on which jbosstools and devstudio depend are now in Fedora24+ or RHEL7+. But I'm not sure there's any interest/plan in getting a jbosstools.rpm at this time. WDYT [~rgrunber] [~mbenitez] [~mat.booth] [~akurtako] [~akazakov] ? > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12190) enable API Tooling for JBoss Tools components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12190?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12190: ------------------------------------ [~mickael_istria] is this a WONTFIX item? we have the baseline mojo now, so do we still need this? cc: [~rob.stryker] > enable API Tooling for JBoss Tools components > --------------------------------------------- > > Key: JBIDE-12190 > URL: https://issues.jboss.org/browse/JBIDE-12190 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: LATER > > Attachments: JBIDE12190-1.png, JBIDE12190-2.png, JBIDE12190-3.png > > > We should enable API Tooling support in projects so that we can get immediate feedback when someone forgets to upversion their plugins or breaks API. > http://wiki.eclipse.org/Version_Numbering > http://www.eclipse.org/pde/pde-api-tools/ > http://wiki.eclipse.org/PDE/API_Tools/User_Guide > http://www.ibm.com/developerworks/opensource/library/os-eclipse-api-tools > http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.7/org... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-3937: ----------------------------------- Is this still on anyone's radar? we have a much larger suite of integration tests now - does it include anything like what Denis is asking for here? cc: [~vpakan] [~mmalina] [~dgolovin] > Create Stress JUnit Test Suite withch is included all available JUnit tests from all components > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-3937 > URL: https://issues.jboss.org/browse/JBIDE-3937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, qa > Affects Versions: 3.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.x > > > Why we need this? > The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems. > It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20034) Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20034?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20034: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.x) > Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20034 > URL: https://issues.jboss.org/browse/JBIDE-20034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM3 > > > Explanation how to use is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=424691. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23367) use internal IP instead of external domain name to speed up publishing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23367?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23367. ------------------------------ > use internal IP instead of external domain name to speed up publishing > ---------------------------------------------------------------------- > > Key: JBIDE-23367 > URL: https://issues.jboss.org/browse/JBIDE-23367 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Recently found out that we can use the internal IP for the machine that actually contains the data that sits on download.jboss.org and devstudio.redhat.com, which speeds up publishing a CI build to stating by a factor of 3 -- from 2h45 down to 40 mins! > We should do the same for publishing CI jobs too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23367) use internal IP instead of external domain name to speed up publishing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23367?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23367. -------------------------------- Resolution: Done > use internal IP instead of external domain name to speed up publishing > ---------------------------------------------------------------------- > > Key: JBIDE-23367 > URL: https://issues.jboss.org/browse/JBIDE-23367 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Recently found out that we can use the internal IP for the machine that actually contains the data that sits on download.jboss.org and devstudio.redhat.com, which speeds up publishing a CI build to stating by a factor of 3 -- from 2h45 down to 40 mins! > We should do the same for publishing CI jobs too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016