October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23093: ------------------------------- Description: We have a number of inconsistencies between jobs / pom.xml: * TARGET_PLATFORM_CENTRAL_MAX vs. JBTCENTRALTARGET_VERSION * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX * stream_jbt vs. jbosstools_site_stream * version_jbt, versionWithRespin_jbt, JBT_buildversion * version_ds, vesionWithResin_ds, JBDS_buildversion * devstudioReleaseVersion, JBDSVersion Should standardize these. Can script relationship between version_* and versionWithRespin_*: {code} version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') {code} was: We have a number of inconsistencies between jobs / pom.xml: * TARGET_PLATFORM_CENTRAL_MAX vs. JBTCENTRALTARGET_VERSION * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX * stream_jbt vs. jbosstools_site_stream * version_jbt, versionWithRespin_jbt * version_ds, vesionWithResin_ds Should standardize these. Can script relationship between version_* and versionWithRespin_*: {code} version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') {code} > use consistent variables across all jenkins jobs for streams, TP versions, etc. > ------------------------------------------------------------------------------- > > Key: JBIDE-23093 > URL: https://issues.jboss.org/browse/JBIDE-23093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We have a number of inconsistencies between jobs / pom.xml: > * TARGET_PLATFORM_CENTRAL_MAX vs. JBTCENTRALTARGET_VERSION > * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN > * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX > * stream_jbt vs. jbosstools_site_stream > * version_jbt, versionWithRespin_jbt, JBT_buildversion > * version_ds, vesionWithResin_ds, JBDS_buildversion > * devstudioReleaseVersion, JBDSVersion > Should standardize these. > Can script relationship between version_* and versionWithRespin_*: > {code} > version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) Client: setup jenkins build

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23379: ---------------------------------------- Summary: Client: setup jenkins build Key: JBIDE-23379 URL: https://issues.jboss.org/browse/JBIDE-23379 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.2.AM3 Reporter: Andre Dietisheim Assignee: Nick Boldt We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) Client: setup jenkins build

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23379?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23379: ------------------------------------- Affects Version/s: 4.4.1.AM2 (was: 4.4.2.AM3) > Client: setup jenkins build > --------------------------- > > Key: JBIDE-23379 > URL: https://issues.jboss.org/browse/JBIDE-23379 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > > We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23378) Client: deploy and use openshift-restclient-java 5.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23378?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23378: ---------------------------------------- Assignee: Andre Dietisheim > Client: deploy and use openshift-restclient-java 5.2.0.Final > ------------------------------------------------------------ > > Key: JBIDE-23378 > URL: https://issues.jboss.org/browse/JBIDE-23378 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23378) Client: deploy and use openshift-restclient-java 5.2.0.Final

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23378: ---------------------------------------- Summary: Client: deploy and use openshift-restclient-java 5.2.0.Final Key: JBIDE-23378 URL: https://issues.jboss.org/browse/JBIDE-23378 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23378) Client: deploy and use openshift-restclient-java 5.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23378?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23378: ------------------------------------- Fix Version/s: 4.4.2.AM3 > Client: deploy and use openshift-restclient-java 5.2.0.Final > ------------------------------------------------------------ > > Key: JBIDE-23378 > URL: https://issues.jboss.org/browse/JBIDE-23378 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-3937: -------------------------------------- It is not on mine radar. If integration tests are running in the same eclipse session, that would be a fair substitute for what was requested in this issue. > Create Stress JUnit Test Suite withch is included all available JUnit tests from all components > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-3937 > URL: https://issues.jboss.org/browse/JBIDE-3937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, qa > Affects Versions: 3.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.x > > > Why we need this? > The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems. > It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ] Denis Golovin edited comment on JBIDE-3937 at 10/17/16 12:32 PM: ----------------------------------------------------------------- {quote}Ok. But a performance test must be "static", ie the content of the test mustn't change over time or it invalidates the time trend. So, if it's about performance test, it's necessary to have a dedicated test case or test suite that won't move with time. I don't think integration tests fit well. I know [~vpakan] is currently working on setting up some performance tests for JBoss Tools.{quote} I agree, so it just a suggestion for a stress test to see if fully loaded product survives through such rigorous eclipse session. was (Author: dgolovin): {qoute}Ok. But a performance test must be "static", ie the content of the test mustn't change over time or it invalidates the time trend. So, if it's about performance test, it's necessary to have a dedicated test case or test suite that won't move with time. I don't think integration tests fit well. I know [~vpakan] is currently working on setting up some performance tests for JBoss Tools.{quote} I agree, so it just a suggestion for a stress test to see if fully loaded product survives through such rigorous eclipse session. > Create Stress JUnit Test Suite withch is included all available JUnit tests from all components > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-3937 > URL: https://issues.jboss.org/browse/JBIDE-3937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, qa > Affects Versions: 3.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.x > > > Why we need this? > The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems. > It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20034) Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20034?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20034: --------------------------------------- Sounds like it is. If it works as expected, facade generation would just create additional files and then p2 would just pack them into repo zip. > Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20034 > URL: https://issues.jboss.org/browse/JBIDE-20034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM3 > > > Explanation how to use is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=424691. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23374) Update sites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.central/4.4.1.Final/compositeArtifacts.xml return 404 errors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23374?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23374: ------------------------------------ I did some cleanup last week to remove old staging builds. Why do you need old staging builds when the content is live under /stable/ and /development/ ? > Update sites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... return 404 errors > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23374 > URL: https://issues.jboss.org/browse/JBIDE-23374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.2.AM2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... includes references to: > * http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.Final > * http://download.jboss.org/jbosstools/neon/staging/updates/central/4.4.1.F... > Both of these links return 404 errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016