June 2016 - jbosstools-issues - Jboss List Archives

[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 commented on JBIDE-20904: ------------------------------------ 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 > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22372) Publish CI snapshots to a directory containing BUILD_ALIAS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22372: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Publish CI snapshots to a directory containing BUILD_ALIAS > ---------------------------------------------------------- > > Key: JBIDE-22372 > URL: https://issues.jboss.org/browse/JBIDE-22372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.4.x > > > To avoid even more "crossing streams", we could consider also adding the BUILD_ALIAS to the URL of snapshots sites produced by CI. An advantage is that building a new version wouldn't require to cleanup the /4.4.neon branch for example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16158: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[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 updated JBIDE-22173: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16158: ------------------------------------ Slip. > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3941) use new logo in UI of Development Suite installer

by SJ Cox (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] SJ Cox updated JBDS-3941: ------------------------- Attachment: logo_RHDS-08.svg [~dgolovin] Please use this new logo instead to match the product name. Thanks! [~nickboldt], [~crobson]. [^logo_RHDS-08.svg] > use new logo in UI of Development Suite installer > ------------------------------------------------- > > Key: JBDS-3941 > URL: https://issues.jboss.org/browse/JBDS-3941 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: installer-new-logo-confirmation.png, installer-new-logo-login.png, logo_RHDP.svg, logo_RHDS-08.svg, new-new-branding.png, RedHatDeveloperStudio_Logo_Installer.ico, screenshot-1.png > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22590) Central tests fail due to ide-config.properties examples keyset being to strict

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22590: ----------------------------------- Summary: Central tests fail due to ide-config.properties examples keyset being to strict Key: JBIDE-22590 URL: https://issues.jboss.org/browse/JBIDE-22590 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.4.0.Final Reporter: Fred Bricon http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... fails due to using 4.4.0 instead 4.4, introduced by mistake in https://github.com/jbosstools/jbosstools-download.jboss.org/commit/9b5dd3... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3940) use new logo in icon for Development Suite installer .exe

by Todd Mancini (JIRA)

[ https://issues.jboss.org/browse/JBDS-3940?page=com.atlassian.jira.plugin.... ] Todd Mancini commented on JBDS-3940: ------------------------------------ Approved. > use new logo in icon for Development Suite installer .exe > --------------------------------------------------------- > > Key: JBDS-3940 > URL: https://issues.jboss.org/browse/JBDS-3940 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: dpinstaller-new-icon-and-properties-2.png, dpinstaller-new-icon-and-properties.png, icons.png, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22514) Unable to build the workspace

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22514?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22514. ---------------------------------- > Unable to build the workspace > ----------------------------- > > Key: JBIDE-22514 > URL: https://issues.jboss.org/browse/JBIDE-22514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Environment: Eclipse > Reporter: Megha Kesharwani > Assignee: Viacheslav Kabanovich > Priority: Trivial > Fix For: 4.2.0.Final > > Attachments: .log > > > I am using eclipse Kepler with plugins JBOSS(wildfly-8.2.0.Final) and ClearCase, while building the workspace i am getting the following error "ENTRY org.eclipse.core.jobs 4 2 2016-06-02 11:07:19.724 > !MESSAGE An internal error occurred during: "Building workspace". > !STACK 0 > java.lang.StackOverflowError" > Attached logs. > We have tried the following solutions: > 1. We tried increasing the memory size in eclipse.ini file as below but it doesn't seems to work: > --launcher.XXMaxPermSize > 1024M > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 1024m > --launcher.appendVmargs > -vm "C:\Program Files\Java\jre7" > -Dosgi.requiredJavaVersion=1.7 > -Xms2048m > -Xmx2048m > 2. When the RAM was checked using task manager eclipse was taking 365MB of memory. > Please guide us some other workaround to resolve the issue. > thanks, > Megha -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22514) Unable to build the workspace

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22514?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-22514. ------------------------------------ Resolution: Out of Date Thanks [~scabanovich]. So, please update your JBoss Tools plugins (and Eclipse!). Resolving. > Unable to build the workspace > ----------------------------- > > Key: JBIDE-22514 > URL: https://issues.jboss.org/browse/JBIDE-22514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Environment: Eclipse > Reporter: Megha Kesharwani > Assignee: Viacheslav Kabanovich > Priority: Trivial > Fix For: 4.2.0.Final > > Attachments: .log > > > I am using eclipse Kepler with plugins JBOSS(wildfly-8.2.0.Final) and ClearCase, while building the workspace i am getting the following error "ENTRY org.eclipse.core.jobs 4 2 2016-06-02 11:07:19.724 > !MESSAGE An internal error occurred during: "Building workspace". > !STACK 0 > java.lang.StackOverflowError" > Attached logs. > We have tried the following solutions: > 1. We tried increasing the memory size in eclipse.ini file as below but it doesn't seems to work: > --launcher.XXMaxPermSize > 1024M > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 1024m > --launcher.appendVmargs > -vm "C:\Program Files\Java\jre7" > -Dosgi.requiredJavaVersion=1.7 > -Xms2048m > -Xmx2048m > 2. When the RAM was checked using task manager eclipse was taking 365MB of memory. > Please guide us some other workaround to resolve the issue. > thanks, > Megha -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016