October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20904: ---------------------------------------- I also have a proposal on the devdoc, to make it support parallel steps and be more looking like a script or a job config (ie refactoring what are the actual input value vs the "transient" ones) > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/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.0.Alpha1 > > > 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-20904: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build-ci/pull/137, https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/131 (was: https://github.com/jbosstools/jbosstools-build-ci/pull/137) > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/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.0.Alpha1 > > > 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20833. --------------------------------- I can confirm that JBDS 9.0.0.CR2 respin-b B124 includes build 24 of playground plugins: {code} org.jboss.tools.playground.easymport.jee_1.0.0.Final-v20150925-1225-B24.jar org.jboss.tools.playground.easymport.maven_1.0.0.Final-v20150925-1225-B24.jar {code} Closing. > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20695) tools.jboss.org/features: Add Bower

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20695?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20695. ------------------------------ Verified. > tools.jboss.org/features: Add Bower > ----------------------------------- > > Key: JBIDE-20695 > URL: https://issues.jboss.org/browse/JBIDE-20695 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.3.0.Final > > > We should add our new Bower feature to tools.jboss.org/features. > Not sure if it should go to the existing HTML5/JS/CSS or we need a new JavaScript page? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- Hi [~mhusnain], I have completed my work on the Install Guide. Details of doc: Content Spec ID: 23020 DocBuilder Link: http://docbuilder.usersys.redhat.com/23020/ Thanks - supriya > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- Confirmed with Jan about this release being GA and not CR2 (cr2 build is being used internally) Added the CR1 ss in the Install JBDS BYOE when Online chapter (we can have an SS with GA only after it is released tomorrow and is available to be installed through the Eclipse Marketplace) Added an entry in the Rev History chapter Had Jan have a look at the install guide for his approval; he has given a go-ahead > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20904: ---------------------------------------- I made a short test to verify that bash variable substitution happens early enough (to make sure that we can use the same "ID" variables in iteration with some good isolation: {code} mistria@mistria-laptop:~$ ID=1; sleep 2 && echo 1st=$ID & sleep 1 && ID=2 && echo 2nd=$ID; wait 2nd=2 1st=1 {code} Here we can see that what matters is the value at the variable while passing the instruction to bash, not when actually starting the instruction. > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/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.0.Alpha1 > > > 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20879?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20879. ------------------------------ Verified. > Forge New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20879 > URL: https://issues.jboss.org/browse/JBIDE-20879 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3535: -------------------------------- Attachment: install-progress.png > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3535: -------------------------------- Description: It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). It is now a narrow stripe and the text that we display over it does not look nice. !install-progress.png! was: It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). It is now a narrow stripe and the text that we display over it does not look nice. > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015