January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23677: ------------------------------- Component/s: build > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 closed JBIDE-20904. ------------------------------ Resolution: Done Everything here is done except for https://issues.jboss.org/browse/JBIDE-22172 so closing. > 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.3.AM1 > > > 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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Sprint: devex #126 January 2017 (was: devex #125 December 2016) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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.3.Final (was: 4.4.3.AM1) > 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 > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > 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 (v7.2.3#72005)

9 years, 2 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.3.AM2 (was: 4.4.3.AM1) > 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: Feature Request > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > 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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM1) > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23643) wrap process for moving a .Final target platform into /static/ folder w/ a Jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23643?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23643: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > wrap process for moving a .Final target platform into /static/ folder w/ a Jenkins job > -------------------------------------------------------------------------------------- > > Key: JBIDE-23643 > URL: https://issues.jboss.org/browse/JBIDE-23643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > When it's time to release the next set of .Final target platforms, the process ought to be run by a jenkins job rather than a local "copy this script into your console" operation. > See https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23678: ------------------------------- Description: Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515. Install manifest contains: * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions), * 1.6.201 (2 versions), and * 2.0.200 (1 version) - *total 7 references*! Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement. was: Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515. > remediation required installing jbosstools 4.4.3.AM1 on Neon.2 > -------------------------------------------------------------- > > Key: JBIDE-23678 > URL: https://issues.jboss.org/browse/JBIDE-23678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png > > > Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515. > Install manifest contains: > * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions), > * 1.6.201 (2 versions), and > * 2.0.200 (1 version) - *total 7 references*! > Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23678: ---------------------------------- Assignee: Nick Boldt > remediation required installing jbosstools 4.4.3.AM1 on Neon.2 > -------------------------------------------------------------- > > Key: JBIDE-23678 > URL: https://issues.jboss.org/browse/JBIDE-23678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png > > > Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515. > Install manifest contains: > * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions), > * 1.6.201 (2 versions), and > * 2.0.200 (1 version) - *total 7 references*! > Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017