May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24322: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: - OS: Windows 7 > - JbossDev: 10.3.0.0 > - Openshift Client: 3.4 > - Openshift Enterprise: 3.4 > - Workspace location: it's inside a network drive > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24322: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: - OS: Windows 7 > - JbossDev: 10.3.0.0 > - Openshift Client: 3.4 > - Openshift Enterprise: 3.4 > - Workspace location: it's inside a network drive > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24322: ------------------------------------------ merged into master and cherry-picked into jbosstools-4.4.x > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: - OS: Windows 7 > - JbossDev: 10.3.0.0 > - Openshift Client: 3.4 > - Openshift Enterprise: 3.4 > - Workspace location: it's inside a network drive > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24413: ------------------------------- Description: JIRA to track infrequent failures due to slaves getting their disks full. Will collect data over time in this spreadsheet: https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... was: JIRA to track infrequent failures due to slaves getting their disks full. > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Fix For: 4.5.0.AM1 > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24413: ---------------------------------- Assignee: Josef Kopriva > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24413: ------------------------------- Fix Version/s: 4.5.0.AM1 > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24413: ---------------------------------- Summary: No space left on device for some rhel7-devstudio-releng slaves Key: JBIDE-24413 URL: https://issues.jboss.org/browse/JBIDE-24413 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.4.Final Reporter: Nick Boldt JIRA to track infrequent failures due to slaves getting their disks full. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4321: ---------------------------------- I was able to reproduce the wiring problems here too. :( Not sure if we can do anything but tell people to run with -clean every time. > Unable to start Devstudio without -clean after install of any stuff from RH Central > ----------------------------------------------------------------------------------- > > Key: JBDS-4321 > URL: https://issues.jboss.org/browse/JBDS-4321 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.4.0.AM2 > Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_Fedora24_strict.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_RHEL7_strict.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt > > > When I install something from Red Hat Central and then start Devstudio without -clean then I get this error: > {code} > !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689 > !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi > !STACK 0 > java.lang.NullPointerException > {code} > There are multiple errors but this one seems to be common for multiple items. > And this window appear: > !Start_without_clean.png|thumbnail! > There is easy workaround but user won't start Devstudio with -clean and many of them could be upset. > Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean. > CC: [~psrna] [~vkadlcik] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24381) jbosstools aggregate update site being deployed to nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24381?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24381. -------------------------------- Resolution: Done I've updated these poms to set the skip flag for deploying to nexus stage: https://github.com/jbosstools/jbosstools-build/commit/99d0a1b3b9260d25220... https://github.com/jbosstools/jbosstools-browsersim/commit/b670dc4f48bd34... (set to FALSE since this project IS deployed to Nexus) https://github.com/jbosstools/jbosstools-build-sites/commit/ca51e8bf8100e... https://github.com/jbosstools/jbosstools-locus/commit/f48d7acf23e791f7149... https://github.com/jbdevstudio/jbdevstudio-product/commit/1283845c2d556a3... https://github.com/jbosstools/jbosstools-integration-tests/commit/97fb0e4... > jbosstools aggregate update site being deployed to nexus > -------------------------------------------------------- > > Key: JBIDE-24381 > URL: https://issues.jboss.org/browse/JBIDE-24381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Despite setting maven.deploy.skip=true, the JBT aggregate update site is being pushed to Nexus, which wastes 4 mins an a bunch of space in Nexus: > {code} > 10:28:46 [INFO] Deploying remotely... > 10:28:46 [INFO] Bulk deploying locally gathered artifacts from directory: > 10:28:46 [INFO] * Bulk deploying locally gathered snapshot artifacts > 10:28:46 [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:28:47 [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.7 KB/sec) > 10:28:47 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:42 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (522353 KB at 2215.2 KB/sec) > 10:32:42 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:43 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (10 KB at 28.7 KB/sec) > 10:32:43 [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:43 [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (400 B at 0.9 KB/sec) > 10:32:43 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 2.8 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (400 B at 1.0 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (48 KB at 105.8 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:45 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.0 KB/sec) > 10:32:45 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:45 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (100 B at 0.3 KB/sec) > 10:32:45 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:46 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.0 KB/sec) > 10:32:46 [INFO] * Bulk deploy of locally gathered snapshot artifacts finished. > 10:32:46 [INFO] Remote deploy finished with success.{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24381) jbosstools aggregate update site being deployed to nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24381?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24381 at 5/8/17 12:32 PM: ------------------------------------------------------------- I've updated these poms to set the skip flag for deploying to nexus stage: https://github.com/jbosstools/jbosstools-build/commit/99d0a1b3b9260d25220... https://github.com/jbosstools/jbosstools-browsersim/commit/b670dc4f48bd34... (set to FALSE since this project IS deployed to Nexus) https://github.com/jbosstools/jbosstools-build-sites/commit/ca51e8bf8100e... https://github.com/jbosstools/jbosstools-locus/commit/f48d7acf23e791f7149... (set to FALSE since this project IS deployed to Nexus) https://github.com/jbdevstudio/jbdevstudio-product/commit/1283845c2d556a3... https://github.com/jbosstools/jbosstools-integration-tests/commit/97fb0e4... was (Author: nickboldt): I've updated these poms to set the skip flag for deploying to nexus stage: https://github.com/jbosstools/jbosstools-build/commit/99d0a1b3b9260d25220... https://github.com/jbosstools/jbosstools-browsersim/commit/b670dc4f48bd34... (set to FALSE since this project IS deployed to Nexus) https://github.com/jbosstools/jbosstools-build-sites/commit/ca51e8bf8100e... https://github.com/jbosstools/jbosstools-locus/commit/f48d7acf23e791f7149... https://github.com/jbdevstudio/jbdevstudio-product/commit/1283845c2d556a3... https://github.com/jbosstools/jbosstools-integration-tests/commit/97fb0e4... > jbosstools aggregate update site being deployed to nexus > -------------------------------------------------------- > > Key: JBIDE-24381 > URL: https://issues.jboss.org/browse/JBIDE-24381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Despite setting maven.deploy.skip=true, the JBT aggregate update site is being pushed to Nexus, which wastes 4 mins an a bunch of space in Nexus: > {code} > 10:28:46 [INFO] Deploying remotely... > 10:28:46 [INFO] Bulk deploying locally gathered artifacts from directory: > 10:28:46 [INFO] * Bulk deploying locally gathered snapshot artifacts > 10:28:46 [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:28:47 [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.7 KB/sec) > 10:28:47 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:42 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (522353 KB at 2215.2 KB/sec) > 10:32:42 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:43 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (10 KB at 28.7 KB/sec) > 10:32:43 [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:43 [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (400 B at 0.9 KB/sec) > 10:32:43 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 2.8 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (400 B at 1.0 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (48 KB at 105.8 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:45 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.0 KB/sec) > 10:32:45 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:45 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (100 B at 0.3 KB/sec) > 10:32:45 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:46 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.0 KB/sec) > 10:32:46 [INFO] * Bulk deploy of locally gathered snapshot artifacts finished. > 10:32:46 [INFO] Remote deploy finished with success.{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 May 2017