[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3797:
-----------------------------
Fix Version/s: 10.1.0.AM3
(was: 10.1.0.AM2)
> Installer: temporary files are not removed when window is closed
> ----------------------------------------------------------------
>
> Key: JBDS-3797
> URL: https://issues.jboss.org/browse/JBDS-3797
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Reporter: Pavol Pitonak
> Labels: havoc
> Fix For: 10.1.0.AM3
>
>
> # download installer exe
> # run DeveloperPlatformInstaller*.exe
> # when installer's window opens, close the window
> # look into _C:\Users\yourusername\AppData\Local\Temp_
> result:
> Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3890) Devstudio installation takes a long, long time
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3890?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3890:
-----------------------------
Fix Version/s: 10.1.0.AM3
(was: 10.1.0.AM2)
> 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.1.0.AM3
>
> 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, 8 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3868:
-----------------------------
Fix Version/s: 10.1.0.AM3
(was: 10.1.0.AM2)
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Priority: Minor
> Fix For: 10.1.0.AM3
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3914:
-----------------------------
Fix Version/s: 10.1.0.AM3
(was: 10.1.0.AM2)
> 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: Denis Golovin
> Fix For: 10.1.0.AM3
>
> 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, 8 months
[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22305:
-------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM2)
> automate process for fetching latest target platform mirrors
> ------------------------------------------------------------
>
> Key: JBIDE-22305
> URL: https://issues.jboss.org/browse/JBIDE-22305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, updatesite, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.4.1.Final
>
> Attachments: git.diff.txt
>
>
> Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names.
> Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace.
> Thus for webtools we might simply define:
> webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do...
> and we'd end up with:
> http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8....
> * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr
> 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p...
> 2. when all children are done, a downstream job can runs TP update & validation against new .target files
> * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> * parse that into a list of URLs
> * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files
> * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs
> * resulting edited .target files will remain in the workspace, and we can then run
> * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> * when done if success:
> * ideally, generate a PR and attach link in email to jbosstools-dev@
> * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR
> * email should includes boilerplate text to send mail to list announcing new change for review
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months