[JBoss JIRA] (JBDS-4076) "RPM release" mismatch between src.rpm and x86_64.rpm
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4076?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4076:
------------------------------------
Assignee: Nick Boldt
[~nickboldt] it looks like we need a new "RPM" component in JBDS project ;)
> "RPM release" mismatch between src.rpm and x86_64.rpm
> -----------------------------------------------------
>
> Key: JBDS-4076
> URL: https://issues.jboss.org/browse/JBDS-4076
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, installer
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
>
> This is an issue with upcoming rh-eclipse46-devstudio.rpm.
> Sometimes there's a mismatch in the "RPM release" between a built RPM and its src.rpm. For example https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... contains:
> rh-eclipse46-devstudio-10.2-0.20161004.0056.el7.src.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> The RPM release part is "0.20161004.0057.el7"; looks constructed using the date and time of building. The time bits are different between the two files.
> The SOURCERPM info in the RPM is broken as well:
> {{$ rpm -q --qf='%{SOURCERPM}\n' -p rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.src.rpm
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23285:
------------------------------------
According to https://access.redhat.com/articles/112673 EAP 4.x contains AS 4.x, which means it's in (or soon to be in) ELS-2 support [1].
* 4.2 -> ELS-2 to Jun 2018
* 4.3 -> ELS-2 to Nov 2019
[1] https://access.redhat.com/support/policy/updates/jboss_notes/
So, I would argue that we no longer need to keep running the EAP 4.x tests, but should keep them available in case an ELS-2 support case is opened. [~akazakov] WDYT?
But for EAP 2.x and 3.x, we can simply remove the test cases that rely on those runtimes.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4076) "RPM release" mismatch between src.rpm and x86_64.rpm
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4076?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4076:
---------------------------------
Component/s: build
> "RPM release" mismatch between src.rpm and x86_64.rpm
> -----------------------------------------------------
>
> Key: JBDS-4076
> URL: https://issues.jboss.org/browse/JBDS-4076
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, installer
> Reporter: Václav Kadlčík
>
> This is an issue with upcoming rh-eclipse46-devstudio.rpm.
> Sometimes there's a mismatch in the "RPM release" between a built RPM and its src.rpm. For example https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... contains:
> rh-eclipse46-devstudio-10.2-0.20161004.0056.el7.src.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> The RPM release part is "0.20161004.0057.el7"; looks constructed using the date and time of building. The time bits are different between the two files.
> The SOURCERPM info in the RPM is broken as well:
> {{$ rpm -q --qf='%{SOURCERPM}\n' -p rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.src.rpm
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23285:
-------------------------------
Description:
While running the integration tests today to investigate JBDS-4077, I discovered that:
* org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
{code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
* org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
[1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
So, three problems here:
a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
was:
While running the integration tests today to investigate JBDS-4077, I discovered that:
* org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
{code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
* org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
[1] https://access.redhat.com/support/policy/updates/jboss_notes/eol
So, three problems here:
a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23285:
------------------------------------
Suggestions to fix:
* use a shared folder for requirements, perhaps under the root folder, which is NOT purged for a `mvn clean`; add a new profile `purge-runtimes` to do this if needed
* rather than defining version of WFLY 10 to use in specific test plugins, set these values in the root pom so that all tests use the same version
* remove versions of runtimes which are EOL, and remove tests which verify those old runtimes
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23285:
----------------------------------
Assignee: Martin Malina
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23285:
-------------------------------
Summary: integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes (was: integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips)
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23285:
-------------------------------
Description:
While running the integration tests today to investigate JBDS-4077, I discovered that:
* org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
{code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
* org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
[1] https://access.redhat.com/support/policy/updates/jboss_notes/eol
So, three problems here:
a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
was:
While running the integration tests today to investigate JBDS-4077, I discovered that:
* org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes:
{code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
* org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
So, two problems here:
a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months