January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23733: ------------------------------------ If the jobs are to be run every week, it doesn't really matter if they're run in a matrix (multi-configuration job) or in several jobs -- the tests will get run. I just figured it'd be easier to MANAGE the jobs when it's time to move them to a new version of target platform or maven version if you have 1 job per github repo than 1 job per subproject within the github repos. Thus javaee == 1 job, not 4, for example. But as long as you guys know what's being tested and devs can run those jobs themselves if they want to, your set up is fine with me. cc:[~rob.stryker] [~jeffmaury] > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4257: ---------------------------------- Please create a list of rpms that rh-eclipse46 should depend on, and we can then remove those from the devstudio rpm spec file. You can ping [~mat.booth] or open a RH BZ to get this fixed in the upstream project. > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4257: -------------------------------- Assignee: Lukáš Valach (was: Nick Boldt) > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Priority: Minor > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4257: ----------------------------- Summary: rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 (was: rh-eclipse46-devstudio provides a lot of packages) > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4241) Automated end-to-end tests for Devsuite 1.3

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4241?page=com.atlassian.jira.plugin.... ] Jan Richter resolved JBDS-4241. ------------------------------- Resolution: Done > Automated end-to-end tests for Devsuite 1.3 > ------------------------------------------- > > Key: JBDS-4241 > URL: https://issues.jboss.org/browse/JBDS-4241 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM1 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.3.0.AM2 > > > Create or update existing automated tests for devsuite installer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23776) RedDeer: Allow multiple requirement definition in single config.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23776?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23776: ---------------------------------- Affects Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > RedDeer: Allow multiple requirement definition in single config.xml file > ------------------------------------------------------------------------ > > Key: JBIDE-23776 > URL: https://issues.jboss.org/browse/JBIDE-23776 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.3.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.4.3.AM2 > > > https://github.com/jboss-reddeer/reddeer/issues/1586 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-23136: --------------------------------------- I believe you in correct in that pushing to registry does create an IS; I seem to recall someone saying that to me previously. Also, I have noticed that pushing to the registry before the project exists will error. I'm not sure if that is relevent to this discussion. On Tue, Jan 24, 2017 at 3:42 PM, Andre Dietisheim (JIRA) <issues(a)jboss.org> -- -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering OpenShift Integration Services Red Hat, Inc. *Office*: 703-748-4420 | 866-546-8970 ext. 8162420 jcantril(a)redhat.com http://www.redhat.com > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23776) RedDeer: Allow multiple requirement definition in single config.xml file

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-23776: ------------------------------------- Summary: RedDeer: Allow multiple requirement definition in single config.xml file Key: JBIDE-23776 URL: https://issues.jboss.org/browse/JBIDE-23776 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.4.3.AM2 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Priority: Critical Fix For: 4.4.3.AM2 https://github.com/jboss-reddeer/reddeer/issues/1586 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Steps to Reproduce: EXEC: Create a new OpenShift EAP 6.4 application: Open New OpenShift application wizard, select eap64-basic-s2i template, proceed to next wizard page, change CONTEXT_DIR param to helloworld, click Finish and let import application to your workspace once you are prompted. EXEC: Create a new OpenShift 3 server adapter for the application. ASSERT: There is a started server adapter for the application in Servers view. EXEC: Restart server adapter in debug mode. ASSERT: Server adapter is in debug mode, synchronized. EXEC: Rename method or add a field to class (e.g. in HelloService) = do HCR incompatible change in class structure. EXEC: Save editor. ASSERT: Dialog warning about failed HCR is shown. EXEC: Click button Restart buttons in Hot Code Replace Failed dialog. ASSERT: Module is deployed on a remote server. RESULT: Debugger is out of sync. EXPECTED RESULT: Debugger is back to sync. EXEC: Make a HCR compatible change (in method body e.g. change returned message). EXEC: Save editor. RESULT: Hot Code Replace Failed dialog is shown. EXPECTED RESULT: Change is propagated successfully, there is no HCR Failed dialog and debugger is in sync. was: EXEC: Create a new OpenShift EAP 6.4 application. Open New OpenShift application wizard, select eap64-basic-s2i template, proceed to next wizard page, change CONTEXT_DIR param to helloworld, click Finish and let import application to your workspace once you are prompted. EXEC: Create a new OpenShift 3 server adapter for the application. ASSERT: There is a started server adapter for the application in Servers view. EXEC: Restart server adapter in debug mode. ASSERT: Server adapter is in debug mode, synchronized. EXEC: Rename method or add a field to class (e.g. in HelloService) = do HCR incompatible change in class structure. EXEC: Save editor. ASSERT: Dialog warning about failed HCR is shown. EXEC: Click button Restart buttons in Hot Code Replace Failed dialog. ASSERT: Module is deployed on a remote server. RESULT: Debugger is out of sync. EXPECTED RESULT: Debugger is back to sync. EXEC: Make a HCR compatible change (in method body e.g. change returned message). EXEC: Save editor. RESULT: Hot Code Replace Failed dialog is shown. EXPECTED RESULT: Change is propagated successfully, there is no HCR Failed dialog and debugger is in sync. > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23729) Implement integration ui tests for validation of job.xml file in design view tab

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23729?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23729: ---------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > Implement integration ui tests for validation of job.xml file in design view tab > --------------------------------------------------------------------------------- > > Key: JBIDE-23729 > URL: https://issues.jboss.org/browse/JBIDE-23729 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.4.3.Final > > > Implement ui int. tests for batch job.xml validation that is used in design view tab. It is a subset of features referenced in [jira|https://issues.jboss.org/browse/JBIDE-23728]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017