May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22415) Target Platform PR build produces empty p2diffs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22415?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22415: ------------------------------------ I'd rather see the diffs than empty files. Maybe you could produce a full diff and a summary diff (ignore simple version changes) too ? > Target Platform PR build produces empty p2diffs > ----------------------------------------------- > > Key: JBIDE-22415 > URL: https://issues.jboss.org/browse/JBIDE-22415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > Attachments: _view_.txt, _view_2.txt > > > When rolling back a change [1], the build [2] produced two empty p2diff files. > [1] https://github.com/jbosstools/jbosstools-target-platforms/commit/935dcedc... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21283) Update Central to Spring IDE 3.7.3 release when available (replaces CI build)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21283?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-21283. -------------------------------- Resolution: Done Done: https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentral... > Update Central to Spring IDE 3.7.3 release when available (replaces CI build) > ----------------------------------------------------------------------------- > > Key: JBIDE-21283 > URL: https://issues.jboss.org/browse/JBIDE-21283 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > [~mlippert] said: {quote} > Sorry for the inconvenience regarding the weaving hook versions, the AJDT build uses a specific self-built version of that instead of the one that is included in the Mars and Neon repos. However, this will change in the near future. We are switching to a new build and had to made a few additional changes (as a heads-up): > org.eclipse.equinox.weaving.aspectj(.source) will be moved to the AJDT project, therefore no longer in Neon (from M5 on, I think) > org.eclipse.equinox.weaving.sdk(.feature.group) will be moved to the AJDT project as well, also no longer in the Neon repo (from M5 on as well) > Both will have higher version numbers and being distributed as part of the AJDT build (instead of Equinox). > I think this will affect the AJDT versions for Eclipse 4.5 + 4.6, so you might come across a similar situation with the Mars repositories (two different versions of the weaving.sdk feature, two different versions of the weaving.hook bundle). > {quote} > Then [~dgolovin] said: {quote}Didn't test it, but it seems good to be applied and get Spring IDE back to Central. But it is a nightly build, isn't it? We should remember to update it to released version at some point. Could you create issue for that?{quote} > So here's that tracker issue, to ensure we get a working SpringIDE 3.7.3 for Neon once it's released, along with a working version of AJDT. May require TWO mirrors instead of one, as we used to have for Mars. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Fix For: 4.4.x > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Fix For: 4.4.x > > > To better automate staging & release, we need a way to run a smoke test of a given installer jar, then to install all the GA & EA content in Central. > Steps to script: > a. wget installer jar > b. headless install (via -console or install.xml script) > c. install grinder or p2director install all the things in Central. -- 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.0.Alpha3 (was: 4.4.0.Alpha2) > 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 > Fix For: 4.4.0.Alpha3 > > > 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-20474) combine fewer CI builds into generated composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20474?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20474: ------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > combine fewer CI builds into generated composite site > ----------------------------------------------------- > > Key: JBIDE-20474 > URL: https://issues.jboss.org/browse/JBIDE-20474 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha3 > > > [18/08/2015 15:29:34] Fred Bricon: when building central, I see > [18/08/2015 15:29:36] Fred Bricon: [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,58kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,18kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,93kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,88kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,25kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,77kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,43kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,94kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,74kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,7kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,58kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,95kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,11kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,86kB at 0B/s) > Nick sez: > {quote} > somethign something "store fewer instances of /snapshots/builds /JOB_NAME/TIMESTAMP; more aggressive cleanup required; suggest only keeping 5 builds max" > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20850: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha3 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- 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.0.Alpha3 (was: 4.4.0.Alpha2) > 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.0.Alpha3 > > 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-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.0.Alpha3 (was: 4.4.0.Alpha2) > 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.0.Alpha3 > > > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016