[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23733:
------------------------------------
Two questions re: DEVSTUDIO_VERSION variable.
a) Do you want the x.y.z version, qualified version, or fully-qualified version? 10.3.0, 10.3.0.GA, or 10.3.0.GA-20170221-1419-B79 ?
b) where in a job such as https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... are you actually USING this variable? Is it to replace the version in the URL in INSTALLER_URL, eg., http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi... ?
c) depending on your answer for (a), can I suggest a different variable name? I've already been using variables for the devstudio version in my staging/promotion scripts/jobs and in other places, and I'd like to be consistent w/ what's used there and in the parent pom, too.
d) Why are you using a 10.2.0 build for these smoke tests? Why not use the 10.3.0 CI builds? here's the latest: http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi...
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23733 at 1/31/17 10:24 AM:
--------------------------------------------------------------
Four questions re: DEVSTUDIO_VERSION variable.
a) Do you want the x.y.z version, qualified version, or fully-qualified version? 10.3.0, 10.3.0.GA, or 10.3.0.GA-20170221-1419-B79 ?
b) where in a job such as https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... are you actually USING this variable? Is it to replace the version in the URL in INSTALLER_URL, eg., http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi... ?
c) depending on your answer for (a), can I suggest a different variable name? I've already been using variables for the devstudio version in my staging/promotion scripts/jobs and in other places, and I'd like to be consistent w/ what's used there and in the parent pom, too.
d) Why are you using a 10.2.0 build for these smoke tests? Why not use the 10.3.0 CI builds? here's the latest: http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi...
was (Author: nickboldt):
Two questions re: DEVSTUDIO_VERSION variable.
a) Do you want the x.y.z version, qualified version, or fully-qualified version? 10.3.0, 10.3.0.GA, or 10.3.0.GA-20170221-1419-B79 ?
b) where in a job such as https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... are you actually USING this variable? Is it to replace the version in the URL in INSTALLER_URL, eg., http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi... ?
c) depending on your answer for (a), can I suggest a different variable name? I've already been using variables for the devstudio version in my staging/promotion scripts/jobs and in other places, and I'd like to be consistent w/ what's used there and in the parent pom, too.
d) Why are you using a 10.2.0 build for these smoke tests? Why not use the 10.3.0 CI builds? here's the latest: http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi...
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23761.
--------------------------------
Verified, closing.
> ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23761
> URL: https://issues.jboss.org/browse/JBIDE-23761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
>
> [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute?
> [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas...
> [7:31 AM] Pavol Srna: what do you think?
> [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild?
> [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2].
> [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
> [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> Submit PR against this:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23389?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-23389.
------------------------------
ITests are running fine with Devstudio 10.3.0.AM2 against openshift 3.4. Closing.
> OpenShift 3.4 support
> ---------------------
>
> Key: JBIDE-23389
> URL: https://issues.jboss.org/browse/JBIDE-23389
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM2
>
>
> OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it.
> cc: [~adietish]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 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:
------------------------------------
+100, moving shared ITest configuration to parent pom totally makes sense.
Can you throw me a PR to add all the jbosstools.test.* properties and anything else shared among the ITests into the jbosstools-build parent pom?
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml
Maybe this should be done in 4.5.0.AM1-SNAPSHOT, once we branch in 3 weeks?
> 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
> Fix For: 4.4.3.Final
>
>
> 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
(v7.2.3#72005)
8 years, 8 months
[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 commented on JBDS-4257:
----------------------------------
By the way, re: "Rh-eclipse46 provides 4 packages, devstudio provides 539 packages" ... rh-eclipse46 is a meta-package which just wraps other packages. Maybe you should compare rh-eclipse46-devstudio to rh-eclipse46-base? or to rh-eclipse46-eclipse-cdt-native ?
> 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: 10.3.0.GA
>
> 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)
8 years, 8 months
[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 commented on JBDS-4257:
----------------------------------
OK, I understand. You want the RPM to not "provide" the plugins that are contained in the RPM, including not providing all the stuff from jbosstools, the devstudio branding plugins, and all the 3rd party stuff from Eclipse Orbit which is needed for the jbosstools/devstudio plugins and which are not available from other rh-eclipse46-* packages.
How would I do that? Can you suggest a PR for this spec file?
https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu...
Also, you'll notice that I removed a lot of the features/plugins from the com.jboss.devstudio.core.rpm.feature so it installs considerably less as part of the RPM, in order to de-dupe items already installed by upstream rh-eclipse46-* rpms.
https://github.com/jbdevstudio/jbdevstudio-product/commit/63b136ad12e6db6...
https://github.com/jbdevstudio/jbdevstudio-product/commit/1d53969a727011d...
https://github.com/jbdevstudio/jbdevstudio-product/commit/fad4c74a963079a...
Therefore when I run `rpm -q --provides -p ./rh-eclipse46-devstudio-10.3-0.20170130.2225.el7.x86_64.rpm | wc -l` I now only get 513 plugins provided by the devstudio rpm.
> 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: 10.3.0.GA
>
> 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)
8 years, 8 months