December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23566) Include integration-tests (add new update site zip) in staging and stable update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23566?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23566. -------------------------------- Resolution: Done As the PR was applied in master only, this is therefore fixed in 4.4.3.AM1 and can be verified when we stage that for QE using the https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... job in 3 weeks. > Include integration-tests (add new update site zip) in staging and stable update sites > -------------------------------------------------------------------------------------- > > Key: JBIDE-23566 > URL: https://issues.jboss.org/browse/JBIDE-23566 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Cloned from JBIDE-23384 to add the integration-tests ZIP file to the staging/stable sites. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23566) Include integration-tests (add new update site zip) in staging and stable update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23566?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23566: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > Include integration-tests (add new update site zip) in staging and stable update sites > -------------------------------------------------------------------------------------- > > Key: JBIDE-23566 > URL: https://issues.jboss.org/browse/JBIDE-23566 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Cloned from JBIDE-23384 to add the integration-tests ZIP file to the staging/stable sites. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23566) Include integration-tests (add new update site zip) in staging and stable update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23566?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23566: ------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.3.AM1) > Include integration-tests (add new update site zip) in staging and stable update sites > -------------------------------------------------------------------------------------- > > Key: JBIDE-23566 > URL: https://issues.jboss.org/browse/JBIDE-23566 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > Cloned from JBIDE-23384 to add the integration-tests ZIP file to the staging/stable sites. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4112) create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4112?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4112: ----------------------------- Fix Version/s: 10.2.0.GA (was: 10.3.0.AM1) > create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4112 > URL: https://issues.jboss.org/browse/JBDS-4112 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.GA > > > As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2. > Mixing an AM1 staging build into a .GA stable build should not happen. > We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content. > This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals: > * ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content > * foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18848: ------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.3.AM1) > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Component/s: build > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22819) wrap staging build process with a series of jenkins jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22819: ------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.3.AM1) > wrap staging build process with a series of jenkins jobs > -------------------------------------------------------- > > Key: JBIDE-22819 > URL: https://issues.jboss.org/browse/JBIDE-22819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > Job requires about 13 params: > {code} > version (JBT and JBDS) > versionWithRespin (JBT and JBDS) > versionWithRespin_PREV (JBT and JBDS) > target platforms (min, max, central) > respin # (- or a, b, c) > devsuite installerExe url > stream_JBT=master # or 4.4.neon > stream_DS=master # or 10.0.neon > {code} > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23475?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23475: ------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.3.AM1) > split ide-config.properties into multiple files > ------------------------------------------------- > > Key: JBIDE-23475 > URL: https://issues.jboss.org/browse/JBIDE-23475 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, central-update > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation. > So, rather than 1 big file [1] we could split this into 5 files: > * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA) > * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3) > * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA) > * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA) > * ide-config.properties - contains all the other properties for 4.3.x and earlier releases > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value. > From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-4070: ---------------------------------------- So the 1st possible explanation of using EAP5 inapplicable. The screenshots in the doc clearly show OpenShift3 and an OpenShift 3 server adapter being used. The rsync output that's reported shows other weird things: One can see a ROOT.war and a ROOT.EAR being deployed (./ROOT.war, .deploy/ROOT.ear/SimpleHelloWorld.war/Hello.jsp, deploy/ROOT.war etc.) I also suspect that the output being shown does not report the output as is. The deployment is actually happening in 2 phases: # First, the remote is synced down to the local machine # Then, in a 2nd phase, the local machine is synced back up to the remote pod. The 2nd thing to take care of is that existing contents are being mixed in, since we're rsyncing. So the more you deploy the more things might get mixed up. I also suspect "Clean" in the server adapter not to really clear contents [~rob.stryker] correct?). Is it possible for the user to manually clear his deployment folder on the pod and the local Eclipse? * to clear the pod: use the [oc command line tool|https://github.com/openshift/origin/releases/tag/v1.3.0] to login into the pod and rm the deployment folder # oc login https://ose-masterint.mmm.com:8443 # oc project ostestrest # oc get pod # oc rsh <pod running your eap> => you get into a shell in your pod # cd /deployments # rm -rf * * to clear the local deployments folder: # remove the server adapter ([~rob.stryker] this should clear the local artifacts that were synced pod > local, correct?) Once both have been cleared please redeploy and paste the output completely untouched as-is (dont cut off anything), please. I'd love the user to use our latest builds. Could he use an Eclipse Neon and install [JBoss Tools/OpenShift 4.4.2.AM3|http://tools.jboss.org/downloads/jbosstools/neon/4.4.2.AM3.html] into it? We should also make sure the user is using the latest oc binaries that match his openshift version. What version of OpenShift server is being used? The user should use the [oc binaries|https://github.com/openshift/origin/releases] in a version that match the server. Is it possibel to get the projects that the user is using? It would be a great help to have these artifacts, far more efficient that doing guesswork based on screenshots and explanations. Those help, no doubt, but real hands-on is far superior. > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 10.3.0.AM1 > > Attachments: OSDeployRecreate.docx, eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-998) Fuse - Adapt 'RouteManipulationTest' according to FUSETOOLS-2023

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-998?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík resolved JBTIS-998. -------------------------------- Resolution: Done > Fuse - Adapt 'RouteManipulationTest' according to FUSETOOLS-2023 > ----------------------------------------------------------------- > > Key: JBTIS-998 > URL: https://issues.jboss.org/browse/JBTIS-998 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.4.0.Final > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > Changes introduced with https://issues.jboss.org/browse/FUSETOOLS-2023 broke the _RouteManipulationTest_. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 December 2016