[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-654:
-------------------------------------------
As I said when we talked I think reusing all the logic and just allow for in the build to start which runtime to include is better.
But what is it that #3 panel is supposed to do that is not just unzipping the content ?
Any setup beyond that I would initially have expected to happen inside devstudio.
Also, from Aileen it sounds like you have different runtime zips per OS ? is that true ?
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
Hey [~akazakov] - I'm actually targeting any neon release - but that's fine - I'd like to get [~dgolovin] ideas on the feasibility of my suggestion as he's got the most experience with it.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22294) Build Configuration: Git Source section is cropped on OSX
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22294?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22294:
-------------------------------------
Fix Version/s: 4.4.1.Alpha1
(was: 4.4.0.Alpha2)
> Build Configuration: Git Source section is cropped on OSX
> ---------------------------------------------------------
>
> Key: JBIDE-22294
> URL: https://issues.jboss.org/browse/JBIDE-22294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.4.1.Alpha1
>
>
> After creating a new openshift application, selecting a builder image, then on the next page:
> !http://content.screencast.com/users/fbricon/folders/Jing/media/5e21b5d7-9cb1-43cf-bfe9-05c1ef6e0dad/00000404.png|width=800!
> Context directory field / label are cropped.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBTIS-654:
--------------------------------------
[~leacu] I really not sure we currently have resources for such enhancements in the devstudio installer code base for the next release.
Can you guys try to take care of it yourself? :) [~dgolovin] could help you as a consultant and also help with reviewing your Pull Request.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
Hey [~dgolovin] [[~akazakov] - I know you guys are extremely busy with the summit release. This is a post-summit enhancement request.
I talked with [~maxandersen] about how best to architect this support. He was of the opinion that it would make
more sense to parameterize the devstudio installer support to allow it to take a platform-specific runtime as
opposed to migrating the p2-director and izpack installer infrastructure over in the integration stack build.
Having migrated the two over in a prototype it did amount to a near duplication of the code. I'm currently successfully using Denis' p2 director installer enhancement (AdditionalFeaturesSpec.json) to allow the IS to specify its features into the devstudio installer. We'll release that in the Mars stream. What I'd like is to extend that...
Is it possible to get into a future devstudio 10.0.x (neon) release enhanced installer support where a user could specify:
1. A stand-alone installer jar - this would be the devstudio-is (Integration Stack) stand-alone installer.
2. A compressed runtime (zip) that would be expanded into an appropriate runtime folder within the devstudio footprint (using the EAP one or a seperate folder). This would likely go into its own pack ID - "Red Hat JBoss Developer Studio Component Runtime" - something like that?
ref: jboss-fuse-full-6.3.0.redhat-075.zip
3. A specific IzPack panel binary - tailored to the platform we're offering. This would be installed into the specified IS installer (1) to create the new extended installer based on what was passed in.,
The goal would be to provide an abstract way to specify a runtime zip and installer panel associated with the runtime into a pre-existing stand-alone installer. The existing runtime detection would need to be augmented as well. That would allow greater flexibilty in creating full stand-alone installers for Fuse, Teiid Designer, etc and leverage the existing devstudio installer to the greatest extent.
I'm open to any other ideas as well.
WDYT?
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22173) write validation tests to ensure published content has been correctly published
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22173?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22173:
------------------------------------
Work in progress and will be more done in this sprint for Final, but since jiralint is complaining I'll move it to 4.4.x
> write validation tests to ensure published content has been correctly published
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22173
> URL: https://issues.jboss.org/browse/JBIDE-22173
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, install-tests
> Affects Versions: 4.3.1.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> Once we're done running stage.sh, we need a way to automatically review the content has been correctly published.
> Today, we do this:
> {code}
> versionWithRespin=4.3.1.CR1b # a, b, c...
> tmpfile=/tmp/jbosstools-staging__verify.txt
> for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do
> if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi
> echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile
> echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${v... " >> $tmpfile
> done
> for site in browsersim-standalone; do
> if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi
> echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile
> done
> echo "" >> $tmpfile
> cat $tmpfile
> firefox `cat $tmpfile`
> rm -fr $tmpfile
> # verify changes
> echo "Check 6 URLs:"
> firefox \
> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \
> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \
> http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \
> http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \
> http://download.jboss.org/jbosstools/mars/staging/updates/core/ \
> http://download.jboss.org/jbosstools/mars/staging/updates/
> {code}
> or
> {code}
> versionWithRespin=9.1.0.CR1b # a, b, c...
> tmpfile=/tmp/jbosstools-staging__verify.txt
> for site in central earlyaccess discovery.central discovery.earlyaccess; do
> if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi
> echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile
> echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWit... " >> $tmpfile
> done
> echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile
> echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${vers... " >> $tmpfile
> echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${ver... " >> $tmpfile
> echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_su... " >> $tmpfile
> echo "" >> $tmpfile
> cat $tmpfile
> firefox `cat $tmpfile`
> popd >/dev/null
> rm -fr $tmpfile
> # verify changes
> echo "Check 4 URLs:"
> firefox \
> https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \
> https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \
> https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \
> https://devstudio.redhat.com/9.0/staging/updates/
> {code}
> But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published.
> Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present.
> May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20904:
-------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> automate publishing latest CI build to staging, then from staging to development (or stable)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20904
> URL: https://issues.jboss.org/browse/JBIDE-20904
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> Suggestion:
> rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed.
> So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion.
> [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui...
> Examples of using a series of commands in parallel w/ a wait at the end:
> http://stackoverflow.com/questions/19543139/bash-script-processing-comman...
> {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code}
> echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $#
> {code}
> More discussion:
> {quote}
> [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions
> [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just:
> * add && after the 1st rsync in each loop
> * add & after the last one
> * put a wait after the last loop
> * give the big piece of code to procede directly to bash
> {quote}
> After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template.
> And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job.
> Scary, but much faster!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months