March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22172) create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.4.AM2) > create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too) > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > To better automate staging & release, we need a way to run a smoke test of a given installer jar, then to install all the GA & EA content in Central. > Steps to script: > a. wget installer jar > b. headless install (via -console or install.xml script) > c. install grinder or p2director install all the things in Central. > Also need to smoke test the BYOE cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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: ----------------------------- Fix Version/s: 11.x (was: 10.4.0.AM2) > 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 > Fix For: 11.x > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Fix Version/s: 4.5.x (was: 4.4.4.AM2) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM3 > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} > Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > So we could use this to create composite sites in folders like: > * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date) > But also to point to remote (/stable/) URLs from pointer sites, like: > * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd) > * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1) > * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23510: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.4.AM2) > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1069) Missing org.jboss.tools.ws.feature in JBTIS-TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1069?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1069: ----------------------------------- [~apodhrad] - do you need it. There's no point in mirroring artifacts that we don't need - it was removed for efficiency. > Missing org.jboss.tools.ws.feature in JBTIS-TP > ---------------------------------------------- > > Key: JBTIS-1069 > URL: https://issues.jboss.org/browse/JBTIS-1069 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.2.Final-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > I noticed that the feature > {code} > org.jboss.tools.ws.feature > {code} > was removed in 4.4.2.Final-TP but it was available in 4.4.1.Final-TP. Is there any reason for that? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1069) Missing org.jboss.tools.ws.feature in JBTIS-TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1069?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1069: --------------------------------- Assignee: Paul Leacu > Missing org.jboss.tools.ws.feature in JBTIS-TP > ---------------------------------------------- > > Key: JBTIS-1069 > URL: https://issues.jboss.org/browse/JBTIS-1069 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.2.Final-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > I noticed that the feature > {code} > org.jboss.tools.ws.feature > {code} > was removed in 4.4.2.Final-TP but it was available in 4.4.1.Final-TP. Is there any reason for that? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4233: ----------------------------- Sprint: devex #128 February 2017, devex #130 April 2017 (was: devex #128 February 2017, devex #129 March 2017) > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24182) wrap staging/release process with pipeline job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24182: ------------------------------- Sprint: devex #130 April 2017 > wrap staging/release process with pipeline job > ---------------------------------------------- > > Key: JBIDE-24182 > URL: https://issues.jboss.org/browse/JBIDE-24182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. > However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile > [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4346) migrate target platform view jobs to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4346?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4346. ---------------------------- Resolution: Done Done. > migrate target platform view jobs to CCI > ---------------------------------------- > > Key: JBDS-4346 > URL: https://issues.jboss.org/browse/JBDS-4346 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM2 > > > migrate jobs in https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... to CCI Jenkins: > 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, 1 month

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 March 2017