January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25598) TP: update target platform & Central to Oxygen.3

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25598: ---------------------------------- Summary: TP: update target platform & Central to Oxygen.3 Key: JBIDE-25598 URL: https://issues.jboss.org/browse/JBIDE-25598 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.5.2.AM2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.5.2.Final Switch to the latest Oxygen.2, including Jetty 9.4.7 or later Also include RD 2.0.1 https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25597 at 1/18/18 1:14 PM: ------------------------------------------------------------- Details needed: a) which version of Photon would you like? The existing M4 from December, or the forthcoming M5 or M6 milestones? I'll assume you want something based on M6 unless you state otherwise. b) do you need 20+ jobs to run all the builds of all the JBT components against this new TP, or will we for now just have people run locally using {code}-Dtpc.version=4.80.0.AM1-SNAPSHOT{code} I'd prefer to not have to create jobs until we're done with Oxygen.3-based builds for devstudio 11.3 / jbosstools 4.5.3, so as to minimize the overhead in Jenkins and reduce the load on the slaves. Plus it's 2x the number of jobs to have to maintain. But one new job for a new 4.80.x branch of https://github.com/jbosstools/jbosstools-target-platforms/ is totally doable. was (Author: nickboldt): Details needed: a) which version of Photon would you like? The existing M4 from December, or the forthcoming M5 or M6 milestones? I'll assume you want something based on M6 unless you state otherwise. b) do you need 20+ jobs to run all the builds of all the JBT components against this new TP, or will we for now just have people run locally using {code}-Dtpc.version=4.80.0.AM1-SNAPSHOT{code} I'd prefer to not have to create jobs until we're done with Oxygen.3, so as to minimize the overhead in Jenkins and reduce the load on the slaves. Plus it's 2x the number of jobs to have to maintain. But one new job for a new 4.80.x branch of https://github.com/jbosstools/jbosstools-target-platforms/ is totally doable. > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1 > > > In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25597: ------------------------------------ Details needed: a) which version of Photon would you like? The existing M4 from December, or the forthcoming M5 or M6 milestones? I'll assume you want something based on M6 unless you state otherwise. b) do you need 20+ jobs to run all the builds of all the JBT components against this new TP, or will we for now just have people run locally using {code}-Dtpc.version=4.80.0.AM1-SNAPSHOT{code} I'd prefer to not have to create jobs until we're done with Oxygen.3, so as to minimize the overhead in Jenkins and reduce the load on the slaves. Plus it's 2x the number of jobs to have to maintain. But one new job for a new 4.80.x branch of https://github.com/jbosstools/jbosstools-target-platforms/ is totally doable. > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1 > > > In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.6.0.Final) > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1 > > > In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Summary: TP: create target platforms based on Eclipse Photon (was: Photon based TP) > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1 > > > In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) Photon based TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Fix Version/s: 4.6.0.Final (was: 4.5.x) > Photon based TP > --------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.Final > > > In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) Photon based TP

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25597: ---------------------------------- Summary: Photon based TP Key: JBIDE-25597 URL: https://issues.jboss.org/browse/JBIDE-25597 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.5.2.Final Reporter: Jeff MAURY Assignee: Nick Boldt Fix For: 4.5.x In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4667) Job rpm_rh_central_UI_test_one_by_one.weekly should be albe to find out which IU should be installed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4667?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4667: ---------------------------------- If your intent is "install everything from 1 or more URLs, without having to hardcode the list" then you might be able to use this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... Here's an example of how I've used it in a jenkins job: {code} # Install plan is semi-colon-separated pair of URLs: # 1. JBT/JBDS update (or discovery) site # 2. URL with directory.xml # NOTE: Jenkins requires semi-colons, but to pass to shell, must use quotes # On commandline, can use comma-separated pair instead so quotes aren't needed stream_jbt=${JOB_NAME#*_} stream_jbt=${stream_jbt%%/*} # master or 4.4.neon # use composite site with JBT/JBDS + Central (or JBT/JBDS + Central + EA) in order to resolve ALL artifacts in a single operation if [[ ${PROJECT} == "jbosstools" ]]; then INSTALL_PLAN="http://download.jboss.org/jbosstools/${eclipseReleaseName}/snapshots/builds/" INSTALL_PLAN="${INSTALL_PLAN}jbosstools-discovery.central_${stream_jbt}/latest/all/repo/;" INSTALL_PLAN="${INSTALL_PLAN}http://download.jboss.org/jbosstools/${eclipseReleaseName}/snapshots/builds/" INSTALL_PLAN="${INSTALL_PLAN}jbosstools-discovery.${SET}_${stream_jbt}/latest/all/repo/jbosstools-directory.xml" elif [[ ${PROJECT} == "devstudio" ]]; then INSTALL_PLAN="https://devstudio.redhat.com/${devstudioReleaseVersion}/snapshots/builds/" INSTALL_PLAN="${INSTALL_PLAN}jbosstools-discovery.central_${stream_jbt}/latest/all/repo/;" INSTALL_PLAN="${INSTALL_PLAN}https://devstudio.redhat.com/${devstudioReleaseVersion}/snapshots/builds/" INSTALL_PLAN="${INSTALL_PLAN}jbosstools-discovery.${SET}_${stream_jbt}/latest/all/repo/devstudio-directory.xml" fi # comma-separated list of IUs (omit .feature.group) to exclude from installation EXCLUDES="org.eclipse.e4.rcp,.*.epp.package.*,org.eclipse.equinox.*,org.eclipse.help,org.eclipse.platform,org.eclipse.rcp" echo "Install everything into ${eclipseID} from ${PROJECT} and its ${SET} site" ${WORKSPACE}/sources/util/installFromCentral.sh -ECLIPSE ${WORKSPACE}/eclipse -INSTALL_PLAN "${INSTALL_PLAN}" -EXCLUDES "${EXCLUDES}" \ | tee ${WORKSPACE}/log.txt {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Job rpm_rh_central_UI_test_one_by_one.weekly should be albe to find out which IU should be installed > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4667 > URL: https://issues.jboss.org/browse/JBDS-4667 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: rpm > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 11.3.0.AM2 > > > Job rpm_rh_central_UI_test_one_by_one.weekly \[1\] should be albe to find out which IUs should be installed/tested. Now it requires a list of IUs as input parameter. It is not comfortable and needs some maintenance. > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/user/lvalach... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25297) Improve CDK itests so that user do not need to have all CDK versions downloaded himself

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25297?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25297: ---------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.2.Final) > Improve CDK itests so that user do not need to have all CDK versions downloaded himself > --------------------------------------------------------------------------------------- > > Key: JBIDE-25297 > URL: https://issues.jboss.org/browse/JBIDE-25297 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk > Fix For: 4.5.3.AM1 > > > Add mock files that would substitute CDK 2.x Vagrantfile and CDK 3.1.1 binary for purposes of testing UI. These files will be placed in project path in resources/cdk-files. > Let user to pass his vagrant file and cdk-3.1.1 binary path via agrument -Dvagrantfile and -Dminishift in cases where he needs to do so. This argument's values will have priority over files from resources folder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25067) jsf itests job is failing

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25067?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25067: ---------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.2.Final) > jsf itests job is failing > ------------------------- > > Key: JBIDE-25067 > URL: https://issues.jboss.org/browse/JBIDE-25067 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, jsf > Reporter: Pavol Srna > Assignee: Ondrej Dockal > Fix For: 4.5.3.AM1 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018