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 Nick Boldt (JIRA)

Nick Boldt created JBIDE-20904: ---------------------------------- Summary: 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: Bug Components: build Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-20904: ---------------------------------- Assignee: Nick Boldt > 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: Bug > 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 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.0.Alpha1 > 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: Bug > 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-19729) Version Auditing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19729: ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.3.0.Final) > Version Auditing > ---------------- > > Key: JBIDE-19729 > URL: https://issues.jboss.org/browse/JBIDE-19729 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19730: ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.3.0.Final) > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Epic to track issues related to improving how we release software. > This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20889?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20889. ---------------------------------- Resolution: Rejected > javascript New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20889 > URL: https://issues.jboss.org/browse/JBIDE-20889 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, javascript-bower > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > 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] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20889?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-20889: ----------------------------------------- [~ibuziuk], [~akazakov] I believe we have nothing new for 4.3.0.Final > javascript New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20889 > URL: https://issues.jboss.org/browse/JBIDE-20889 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, javascript-bower > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > 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] (JBIDE-20796) neon update sites gets added out of the blue

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20796?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20796: ------------------------------------ For the Eclipse install where you say this weird behaviour (if you still have that Eclipse install available), try this: 1. rm -fr ~/.eclipse/org.eclipse.oomph.* 2. restart that Eclipse install. I'm betting even if you *could* reproduce the problem before purging the oomph metadata, it'll be gone afterwards. > neon update sites gets added out of the blue > -------------------------------------------- > > Key: JBIDE-20796 > URL: https://issues.jboss.org/browse/JBIDE-20796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.1.Final > > Attachments: update-sites.png, update.png > > > When I removed *all* updatesites and added just http://download.jboss.org/jbosstools/mars/development/updates/ (should have just mars cr1), install and then ran check for update my updatesites contained neon references. > See https://www.dropbox.com/s/xo040iyhiw9zhsw/Screenshot%202015-09-24%2009.41... > I'm not sure if I even needed to do the check for updates, but those are the steps I did. > note: I install *everything* and uncheck the "check all updatesites" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20842: ------------------------------------- [~akazakov], great, have created a separate one for refactoring JBIDE-20903 > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-20903: -------------------------------- Description: After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- 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