[JBoss JIRA] (JBDS-3890) Devstudio installation takes a long, long time
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3890?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3890:
----------------------------------
i suspect p2 is computing something to validate the installation, or is generating metadata so future startups are faster.
Not sure what we can do to make this faster without making the initial startup slower. I'd rather the install takes a couple minutes longer than that the user stares at the splash screen for 2-3 minutes.
> Devstudio installation takes a long, long time
> ----------------------------------------------
>
> Key: JBDS-3890
> URL: https://issues.jboss.org/browse/JBDS-3890
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.Alpha1
> Environment: Fedora 22 x64
> OpenJDK 1.8.0_91
> jboss-devstudio-10.0.0.Alpha1-v20160517-0518-B5370-installer-standalone.jar
> Reporter: Jan Richter
> Priority: Critical
> Fix For: 10.0.1.S116
>
> Attachments: install.png, res.png
>
>
> Some actual data here:
> - Alpha1 (staged) build took 2:05 to install on my machine
> - Alpha1 nightly (B5370) took 5:15 to install
> Around the minute mark the installation just freezes in this state:
> !install.png|thumbnail!
> Meanwhile the trace says:
> {noformat}
> Committing the provisioning operation.
> Operation completed in 275702 ms.
> {noformat}
> That is quite a long time it spent doing that operation.
> Some jstack info can be found here:
> http://pastebin.test.redhat.com/374700
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3914:
-----------------------------
Story Points: 10 (was: 3)
Sprint: devex #116 2016/06/15 - 07/05
> Build zip distribution for Mac OS X and Linux
> ---------------------------------------------
>
> Key: JBDS-3914
> URL: https://issues.jboss.org/browse/JBDS-3914
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Fix For: 10.0.1.S116
>
> Attachments: zip in exe fails.png
>
>
> We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3914:
-----------------------------
> Build zip distribution for Mac OS X and Linux
> ---------------------------------------------
>
> Key: JBDS-3914
> URL: https://issues.jboss.org/browse/JBDS-3914
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Fix For: 10.0.1.S116
>
> Attachments: zip in exe fails.png
>
>
> We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3914:
-----------------------------
Status: New (was: New)
Target Release: 10.0.1.GA
> Build zip distribution for Mac OS X and Linux
> ---------------------------------------------
>
> Key: JBDS-3914
> URL: https://issues.jboss.org/browse/JBDS-3914
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Fix For: 10.0.1.S116
>
> Attachments: zip in exe fails.png
>
>
> We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15388?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15388:
-------------------------------
Sprint: devex #117 June 2016
> Compute whether to publish or not based on output signature rather than commits
> -------------------------------------------------------------------------------
>
> Key: JBIDE-15388
> URL: https://issues.jboss.org/browse/JBIDE-15388
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: LATER
>
>
> [Assuming we already have reproducible qualifiers...]
> Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication.
> However there are some case not correctly supported:
> * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen
> * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it.
> instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13671:
-------------------------------
Sprint: devex #116 June 2016
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.x
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months