[JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3532:
----------------------------------
{quote}
2015-10-01 15:29:24) dgolovin: nickboldt: if installer build is fine, then installer should be fine, because build runs automated installation from built installer jar to verify it works.
(2015-10-01 15:30:00) nickboldt: dgolovin: yep, that part passed once I had enough disk space free :D
{quote}
----
Comparing filesizes from my local build to the sizes in CR1 release:
{code:title=http://www.jboss.org/products/devstudio/download/}
Installer With EAP (633mb)
Stand-alone Installer (489mb)
Update Site Zip (514mb)
Source Zip (223mb)
{code}
{code:title=locally built}
Installer With EAP (633mb)
Stand-alone Installer (489mb)
Update Site Zip (514mb)
Source Zip (223mb)
{code}
So... win!
Next: disabling the stuff in the _master job we no longer need & kicking that job anew:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >= 4000 !
(Yes, with this fix we'll be #overFourThousand. Onward to 9000!)
> Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-3532
> URL: https://issues.jboss.org/browse/JBDS-3532
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 9.0.0.CR2
> Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar
> jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip
> downloaded from
> http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0....
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 9.0.0.GA
>
>
> The update site zip has a later timestamp than what you get from the installer but it is still the same build.
> So you can basically update to the same build because of that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20848) Release publish scripts and use them
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-20848.
------------------------------
Closing. Found another related issue in JBIDE-20900 but that's not urgent.
> Release publish scripts and use them
> ------------------------------------
>
> Key: JBIDE-20848
> URL: https://issues.jboss.org/browse/JBIDE-20848
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.CR1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.3.0.CR2, 4.3.0.Final
>
>
> Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3532:
----------------------------------
{quote}
(2015-10-01 14:58:02) nickboldt: akazakov: it built great in master branch for me; verified contents but haven't tried install yet
(2015-10-01 14:59:28) akazakov: nickboldt, can you try to install it now? If everything works then +1 from me
(2015-10-01 15:00:53) nickboldt: akazakov: yes, in progress
(2015-10-01 15:01:15) nickboldt: akazakov: first, a BYOE feature install ...
(2015-10-01 15:04:19) nickboldt: akazakov: dgolovin: install of master branch's new update site zip (with the above PR) worked here for BYOE feature
(2015-10-01 15:04:32) nickboldt: now going to try installing the Branded Product feature
(2015-10-01 15:04:42) nickboldt: (which isn't really supported but curious)
(2015-10-01 15:05:12) nickboldt: meanwhile building the same PR in 4.3.x branch to verify it works there too
(2015-10-01 15:07:09) nickboldt: site built but installer part of the build still going. starting JBDS 9 install from new update site zip test...
(2015-10-01 15:09:48) nickboldt: JBDS 10 install test worked. (Remediation presented to support updating from EPP to JBDS product, but that's 100% expected and necessary)
(2015-10-01 15:11:36) nickboldt: ...and I ran out of disk space. :(
(2015-10-01 15:13:40) akazakov: nickboldt, +1 if all tests passed. Merge into 4.3.x.
(2015-10-01 15:16:43) nickboldt: install test passed for JBDS 9 BYOE and Product features into Mars.1.RC3 JEE
(2015-10-01 15:17:06) nickboldt: going to try to complete the build of the installer (freed up some disk)
{quote}
I've merged the PR while I re-run the part of the full JBDS build that failed due to lack of disk (just the product/installer/pom.xml module, which is unaffected by this).
> Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-3532
> URL: https://issues.jboss.org/browse/JBDS-3532
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 9.0.0.CR2
> Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar
> jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip
> downloaded from
> http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0....
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 9.0.0.GA
>
>
> The update site zip has a later timestamp than what you get from the installer but it is still the same build.
> So you can basically update to the same build because of that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20900:
-------------------------------
Summary: why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ? (was: why do we need both zip and tar.gz for releng-scripts?)
> why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20900
> URL: https://issues.jboss.org/browse/JBIDE-20900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha1
>
>
> When publishing, we use this:
> {code}
> [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final
> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200"
> -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true
> -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip
> -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources
> -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
> {code}
> But there's also this:
> {code}
> [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
> [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
> [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
> [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
> [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
> [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
> So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for releng-scripts?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-20900:
----------------------------------
Summary: why do we need both zip and tar.gz for releng-scripts?
Key: JBIDE-20900
URL: https://issues.jboss.org/browse/JBIDE-20900
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.4.0.Alpha1
When publishing, we use this:
{code}
[jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
{code}
But there's also this:
{code}
[INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
[INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
[INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
[INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
[INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
[INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for releng-scripts?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20900:
-------------------------------
Description:
When publishing, we use this:
{code}
[jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final
-DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200"
-DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true
-Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip
-DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources
-Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
{code}
But there's also this:
{code}
[INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
[INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
[INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
[INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
[INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
[INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
was:
When publishing, we use this:
{code}
[jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
{code}
But there's also this:
{code}
[INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
[INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
[INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
[INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
[INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
[INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
> why do we need both zip and tar.gz for releng-scripts?
> ------------------------------------------------------
>
> Key: JBIDE-20900
> URL: https://issues.jboss.org/browse/JBIDE-20900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha1
>
>
> When publishing, we use this:
> {code}
> [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final
> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200"
> -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true
> -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip
> -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources
> -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
> {code}
> But there's also this:
> {code}
> [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
> [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
> [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
> [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
> [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
> [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
> So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months