[JBoss JIRA] (JBIDE-19449) p2.director install script is finding non-IU IUs to install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19449?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19449.
------------------------------
> p2.director install script is finding non-IU IUs to install
> -----------------------------------------------------------
>
> Key: JBIDE-19449
> URL: https://issues.jboss.org/browse/JBIDE-19449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha2
>
>
> p2.director install script is finding non-IU IUs to install such as:
> {code}eclipse.buildId
> java.version{code}
> {code}
> list.ius:
> [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ...
> [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties
> {code}
> Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
> Reason: here's what's in the plugin.list.properties file:
> {code}
> !SESSION 2015-03-13 18:06:15.934 -----------------------------------------------
> eclipse.buildId=4.5.0.I20150203-1300
> java.version=1.8.0_40
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233
> !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> ch.qos.logback.classic=1.0.7.v20121108-1250
> ch.qos.logback.core=1.0.7.v20121108-1250
> ...
> tern.server.nodejs=0.9.0.201502141213
> ternjs=0.9.0.201502141213
> Operation completed in 183432 ms.
> {code}
> So we need to filter out the header garbage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19702) installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19702?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19702:
-------------------------------
Summary: installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin (was: installFromCentral.sh should support installing from earlyaccess plugin (not just the central one))
> installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19702
> URL: https://issues.jboss.org/browse/JBIDE-19702
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
>
> Today, installFromCentral.sh assumes two incorrect things:
> a) central URL is always different than the JBT/JBDS site URL [no longer true, since JBT/JBDS & Central content are now co-located]
> b) the plugin to parse for IUs is ONLY the central one, not the EA one [we should parse ONE or BOTH, depending on cmdline flag]
> {code}
> # get a list of IUs to install from the Central site (based on the discovery.xml -> plugin.jar -> plugin.xml)
> CENTRAL_URL=${INSTALL_PLAN#*,} # includes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL
> if [[ $CENTRAL_URL != $INSTALL_PLAN ]]; then
> # echo $CENTRAL_URL
> wget ${CENTRAL_URL} -q --no-check-certificate -N -O directory.xml
> PLUGINJAR=`cat ${WORKSPACE}/directory.xml | egrep "org.jboss.tools.central.discovery_|com.jboss.jbds.central.discovery_" | sed "s#.\+url=\"\(.\+\).jar\".\+#\1.jar#"`
> # echo "Got $PLUGINJAR"
> CENTRAL_URL=${SITES#*,} # excludes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL
> wget ${CENTRAL_URL}/${PLUGINJAR} -q --no-check-certificate -N -O plugin.jar
> unzip -oq plugin.jar plugin.xml
> ...
> {code}
> https://github.com/jbosstools/jbosstools-build-ci/blob/4.3.x/util/install...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19702) installFromCentral.sh should support installing from earlyaccess plugin (not just the central one)
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19702:
----------------------------------
Summary: installFromCentral.sh should support installing from earlyaccess plugin (not just the central one)
Key: JBIDE-19702
URL: https://issues.jboss.org/browse/JBIDE-19702
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, updatesite
Affects Versions: 4.3.0.Alpha2
Reporter: Nick Boldt
Today, installFromCentral.sh assumes two incorrect things:
a) central URL is always different than the JBT/JBDS site URL [no longer true, since JBT/JBDS & Central content are now co-located]
b) the plugin to parse for IUs is ONLY the central one, not the EA one [we should parse ONE or BOTH, depending on cmdline flag]
{code}
# get a list of IUs to install from the Central site (based on the discovery.xml -> plugin.jar -> plugin.xml)
CENTRAL_URL=${INSTALL_PLAN#*,} # includes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL
if [[ $CENTRAL_URL != $INSTALL_PLAN ]]; then
# echo $CENTRAL_URL
wget ${CENTRAL_URL} -q --no-check-certificate -N -O directory.xml
PLUGINJAR=`cat ${WORKSPACE}/directory.xml | egrep "org.jboss.tools.central.discovery_|com.jboss.jbds.central.discovery_" | sed "s#.\+url=\"\(.\+\).jar\".\+#\1.jar#"`
# echo "Got $PLUGINJAR"
CENTRAL_URL=${SITES#*,} # excludes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL
wget ${CENTRAL_URL}/${PLUGINJAR} -q --no-check-certificate -N -O plugin.jar
unzip -oq plugin.jar plugin.xml
...
{code}
https://github.com/jbosstools/jbosstools-build-ci/blob/4.3.x/util/install...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19158) Batch Validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-19158.
----------------------------------
Resolution: Done
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: validation.png
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level.
> 5. Sequence of execution elements defined by @next and @to should not loop.
> 6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
> !validation.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19158) Batch Validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19158:
-----------------------------------
Attachment: validation.png
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: validation.png
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level.
> 5. Sequence of execution elements defined by @next and @to should not loop.
> 6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19158) Batch Validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19158:
-----------------------------------
Description:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level.
5. Sequence of execution elements defined by @next and @to should not loop.
6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
!validation.png!
was:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level.
5. Sequence of execution elements defined by @next and @to should not loop.
6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: validation.png
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level.
> 5. Sequence of execution elements defined by @next and @to should not loop.
> 6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
> !validation.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years