August 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 updated JBIDE-20904: ------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016, devex #118 July 2016, devex #119 August 2016 (was: devex #115 May 2016, devex #116 June 2016, devex #118 July 2016) > 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.1.Final > > > 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, 7 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.1.Final (was: 4.4.1.AM3) > 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.1.Final > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22728: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22819: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > wrap staging build process with a jenkins job > --------------------------------------------- > > Key: JBIDE-22819 > URL: https://issues.jboss.org/browse/JBIDE-22819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Job requires about 13 params: > {code} > version (JBT and JBDS) > versionWithRespin (JBT and JBDS) > versionWithRespin_PREV (JBT and JBDS) > target platforms (min, max, central) > respin # (- or a, b, c) > devsuite installerExe url > stream_JBT=master # or 4.4.neon > stream_DS=master # or 10.0.neon > {code} > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22884) test failure in org.jboss.tools.vpe.jsp.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22884?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22884: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > test failure in org.jboss.tools.vpe.jsp.test > -------------------------------------------- > > Key: JBIDE-22884 > URL: https://issues.jboss.org/browse/JBIDE-22884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Fix For: 4.4.1.Final > > Attachments: _view_.txt, _view_more.txt > > > {code} > 21:32:03 [INFO] org.jboss.tools.vpe.jsp.test ....................... FAILURE [ 01:00 h] > 21:32:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.25.0:test (default-test) on project org.jboss.tools.vpe.jsp.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22699: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.Final > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22446: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22446: ------------------------------------ No, it shouldn't fail... because there is no SNAPSHOT dependency in openshift at the moment (it was replaced with RC1 [1]). [1] https://github.com/jbosstools/jbosstools-openshift/commit/9213c7febc4afe3... If you re-insert a SNAPSHOT dep, then yes, it will fail: {code:title=1. tweak parent pom to set new BUILD_ALIAS=Final and switch to non-SNAPSHOT target platform version} cd ~/tru/jbosstools-build/parent/ cat pom.xml | grep AM3 sed -i -e "s#<BUILD_ALIAS>AM3</BUILD_ALIAS>#<BUILD_ALIAS>Final</BUILD_ALIAS>#" -e "s#4.60.1.AM3-SNAPSHOT#4.60.1.Final#g" pom.xml mvn clean install {code} {code:title=2. use SNAPSHOT version of restclient jar in openshift.client, then rebuild using existing target platform 4.60.1.AM3-SNAPSHOT (because Final doesn't exist yet)} cd ~/tru/jbosstools-openshift git revert 9213c7febc4afe37889eb300340ecb24e9a1e60c mvn clean verify -DskipTests -Dtycho.baseline=disable -U -DTARGET_PLATFORM_VERSION=4.60.1.AM3-SNAPSHOT {code} {code:title=3. openshift.client plugin fails} [INFO] --- maven-enforcer-plugin:1.4.1:enforce (warn-no-snapshots-AM3) @ org.jboss.tools.openshift.client --- Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (789 B at 2.0 KB/sec) [ERROR] Found property openshift-restclient-java.version = 5.0.0-SNAPSHOT [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-no-snapshots-Final) @ org.jboss.tools.openshift.client --- [ERROR] Found property openshift-restclient-java.version = 5.0.0-SNAPSHOT [INFO] Found BUILD_ALIAS = Final (for buildAliasSearch = Final|GA) [WARNING] Rule 0: org.jboss.tools.releng.NoSnapshotsAllowed failed with message: When BUILD_ALIAS (Final) matches /Final|GA/, cannot include SNAPSHOT dependencies. [INFO] BUILD FAILURE {code} So, this DOES work, but the enforcer plugin is NOT looking at commandline params. It's only looking at the values hardcoded in the parent pom. Not sure if this is a good thing or a bug. [~mickael_istria] [~mmalina] WDYT? > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22765) In FTL file in editor are missing directives in code assistant

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22765?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22765: ---------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > In FTL file in editor are missing directives in code assistant > -------------------------------------------------------------- > > Key: JBIDE-22765 > URL: https://issues.jboss.org/browse/JBIDE-22765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160715-2233-B5663 > Build date: 20160715-2233 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.Final > > > In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-834?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-834: ----------------------------- Description: *Reason:* IS dependency for Fuse/SY *Project page/sources:* *Version:* 4.3.3 *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ *Include Sources:* Yes *Affected JBoss Tools components:* Integration Stack *Include in JBDS:* Yes JBDSIS *Type of dependency:* testing|central-only|distribution *List of bundles added/removed:* {code} {code} The JBT core TP dependencies are: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... was: Need to add: org.eclipse.swtbot.ide_2.3.0.201506081302.jar as an IS dependency for Fuse/SY from The JBT core TP dependencies are: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... The Mars swtbot JBT mirror is: http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ > JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY > ---------------------------------------------------------------------------- > > Key: JBTIS-834 > URL: https://issues.jboss.org/browse/JBTIS-834 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.2.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* IS dependency for Fuse/SY > *Project page/sources:* > *Version:* 4.3.3 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ > *Include Sources:* Yes > *Affected JBoss Tools components:* Integration Stack > *Include in JBDS:* Yes JBDSIS > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > {code} > {code} > The JBT core TP dependencies are: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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