August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21381) Ensure JBT/JBDS are building on RHEL 7 slaves where applicable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21381?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21381. ------------------------------ Fix Version/s: 4.4.1.Final (was: 4.3.x) (was: 4.4.x) Resolution: Done > Ensure JBT/JBDS are building on RHEL 7 slaves where applicable > -------------------------------------------------------------- > > Key: JBIDE-21381 > URL: https://issues.jboss.org/browse/JBIDE-21381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > We currently use an *<assignedNode>* or *label_exp* like this for most of our jobs: > * (RHEL6||RHEL7||jboss-prod)&&!ia64&&!rhts > * (RHEL6||jboss-prod)&&!ia64&&!ppc64&&!rhts > * (RHEL6||RHEL7||jboss-prod)&&(x86||x86_64) > However, there are currently no slaves in the RHEL7 label [0], so this query really just means RHEL6||jboss-prod. > [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/RHEL7/ > But, since the jboss-prod slaves do NOT have x86 or x86_64 labels, using jboss-prod&&(x86||x86_64) also means ZERO slaves [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28jboss-prod%29&&%... > Therefore (RHEL6||RHEL7||jboss-prod)&&(x86||x86_64) == RHEL6&&(x86||x86_64) == RHEL6. > And, jboss-prod only includes RHEL6 slaves [2]: > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/jboss-prod/ > Here's a label query which actually includes some RHEL7 slaves, from the RHEL7-ipv6 bucket of THREE slaves [3]: > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/RHEL7-ipv6/ > Note too that there are no longer any rhts slaves [4], but there are still some ia64 [5] and ppc64 [6] slaves: > [4] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/rhts/ > [5] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/ia64/ > [6] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/ppc64/ > So... if we want a pool of >60 of RHEL6||jboss-prod and also RHEL7-ipv6 (all three of them), we can use these slaves from *(RHEL6||RHEL7-ipv6||jboss-prod)*: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28RHEL6||RHEL7-ipv... > There are also some unshared RHEL7 slaves we can use: > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/brms-rhel7-x86-64/ (5 disabled) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/beaker-fsw-rhel7/ (4 disabled) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/EAP-RHEL7/ (14 enabled, 2 disabled) > So, here's the combined RHEL7 label: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/brms-rhel7-x86-64||... (17 enabled, 11 disabled) > And the combined RHEL6 label: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28RHEL6||jboss-pro... (60 enabled, 4 disabled) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22968: ------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016) > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15388?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15388. ------------------------------ > Compute whether to publish or not based on output signature rather than commits > ------------------------------------------------------------------------------- > > Key: JBIDE-15388 > URL: https://issues.jboss.org/browse/JBIDE-15388 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.1.Final > > > [Assuming we already have reproducible qualifiers...] > Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication. > However there are some case not correctly supported: > * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen > * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it. > instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15388?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-15388. -------------------------------- Fix Version/s: 4.4.1.Final (was: LATER) Resolution: Partially Completed Marking this as partially done. Future work can be done in https://issues.jboss.org/browse/JBIDE-20177 or https://issues.jboss.org/browse/JBIDE-22968 > Compute whether to publish or not based on output signature rather than commits > ------------------------------------------------------------------------------- > > Key: JBIDE-15388 > URL: https://issues.jboss.org/browse/JBIDE-15388 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.1.Final > > > [Assuming we already have reproducible qualifiers...] > Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication. > However there are some case not correctly supported: > * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen > * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it. > instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20177: ------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20177 > URL: https://issues.jboss.org/browse/JBIDE-20177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > If we can migrate this logic into the mojo... > {code} > if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then > {code} > ... we'll be able to remove this step in all jobs: > {code} > <hudson.tasks.Maven> > <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets> > <mavenName>maven-3.2.5</mavenName> > <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip > outputDirectory=${WORKSPACE}/sources > trimVersion=true > mdep.stripClassifier=true > mdep.stripVersion=true</properties> > <usePrivateRepository>false</usePrivateRepository> > <settings class="jenkins.mvn.DefaultSettingsProvider"/> > <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/> > </hudson.tasks.Maven> > {code} > ... and instead, just pass in those vars to maven: > {code} > -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing} > -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo > -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-832) Add ELK (Eclipse Layout Kernel) dependency to Neon TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-832?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-832: ---------------------------------- The ELK update site appear to be Mars-based. [~lhein] to check with forums to see what their Neon strategy is. > Add ELK (Eclipse Layout Kernel) dependency to Neon TP > ----------------------------------------------------- > > Key: JBTIS-832 > URL: https://issues.jboss.org/browse/JBTIS-832 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Reporter: Paul Leacu > Assignee: Paul Leacu > > Fuse Tooling would like to use the Eclipse/KIELER graphical layout manager in Neon. > http://download.eclipse.org/elk/updates/releases/0.1.0/ > https://www.eclipse.org/elk/ > It can be used for GMF and/or Graphiti based editor or even for custom ones. > Formerly it was https://rtsys.informatik.uni-kiel.de/confluence/display/KIELER/Home -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-21201: ------------------------------------ I tend to see this error from time to time. Last seen in JBT 4.4.1.AM3. > TernError: No type found at the given position. > ----------------------------------------------- > > Key: JBIDE-21201 > URL: https://issues.jboss.org/browse/JBIDE-21201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.0.Beta1 > Environment: tern 1.1.0 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: LATER > > > 1. Create JSF 1.2 Kick Start project > 2. Open inputUserName.jsp in VPE > 3. Click on 'user' text within <h:inputText> tag > 4. Press F3 key > {code} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-21201: -------------------------------- Sprint: devex #119 August 2016 > TernError: No type found at the given position. > ----------------------------------------------- > > Key: JBIDE-21201 > URL: https://issues.jboss.org/browse/JBIDE-21201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.0.Beta1 > Environment: tern 1.1.0 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: LATER > > > 1. Create JSF 1.2 Kick Start project > 2. Open inputUserName.jsp in VPE > 3. Click on 'user' text within <h:inputText> tag > 4. Press F3 key > {code} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-21198: -------------------------------- Story Points: 2 > "Tern - Go to definition" hyperlink opens nothing > ------------------------------------------------- > > Key: JBIDE-21198 > URL: https://issues.jboss.org/browse/JBIDE-21198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150912-1100-B100 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: LATER > > > 1. Install AngularJS from JBoss Central (Enable Early Access) > 2. Create JSF 1.2 Kick Start project > 3. Open inputUserName.jsp in VPE > 4. Click on 'user' text within <h:inputText> tag > 5. Press F3 key > ERROR: Nothing happened. User.java file should be opened in editor > 6. Hover with mouse over the same text and push Ctrl key > ASSERT: Menu with these tree actions appeared: > * Tern - Go to definiton > * Open User.java > * Open 'User - demo' > Action Open User.java opens User.java in editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-21198: -------------------------------- Sprint: devex #119 August 2016 > "Tern - Go to definition" hyperlink opens nothing > ------------------------------------------------- > > Key: JBIDE-21198 > URL: https://issues.jboss.org/browse/JBIDE-21198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150912-1100-B100 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: LATER > > > 1. Install AngularJS from JBoss Central (Enable Early Access) > 2. Create JSF 1.2 Kick Start project > 3. Open inputUserName.jsp in VPE > 4. Click on 'user' text within <h:inputText> tag > 5. Press F3 key > ERROR: Nothing happened. User.java file should be opened in editor > 6. Hover with mouse over the same text and push Ctrl key > ASSERT: Menu with these tree actions appeared: > * Tern - Go to definiton > * Open User.java > * Open 'User - demo' > Action Open User.java opens User.java in editor -- 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