December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Hiram Chirino (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Hiram Chirino commented on JBDS-4105: ------------------------------------- Yes, you basically have to run the same build that the S2I source builders for FIS use. The options are different for Karaf vs SB based apps. > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4105: --------------------------------------- [~chirino] Do we have already some maven goal/phase that can be used to produced the Source to be deployed? What is the time required to generate it? it is to know if we can imagine it on Incremental build on on a full build only. [~jeffmaury] [~rob.stryker] apart from the service/pod issue, how Eclipse OpenShift Tooling knows which folder/files it needs to redeploy using the s2i binary way? (it is using the s2i binary right?) And by writing this question, i realize that we have the service/pod fix as requirements so we might be forced to provide just an "ignore" m2e connector for this plugin for the first release? the implication that I see is no leverage of the Eclipse OpenShift Tooling: - will require manual rebuild - no hot-deploy - what else? > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 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 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)

7 years, 7 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)

7 years, 7 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)

7 years, 7 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)

7 years, 7 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)

7 years, 7 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)

7 years, 7 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)

7 years, 7 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)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016