May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21785 at 5/6/16 10:10 AM: ------------------------------------------------------------- Seems as though PR jobs won't also build commits automatically: {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/} >> GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge conflicts. 734e1c3a03355c0a57e21bb723241e98f2286751 refs/remotes/origin/pr/412/merge Test Result (69 failures / ±0) {code} vs. {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/} JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f) >> Started by build flow jbosstools-buildflow_master build number 286. Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f refs/remotes/origin/master Test Result (3 failures / ±0) {code} So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the projects into building anything they haven't already built. was (Author: nickboldt): Seems as though PR jobs won't also build commits automatically: {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/} GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge conflicts. 734e1c3a03355c0a57e21bb723241e98f2286751 refs/remotes/origin/pr/412/merge Test Result (69 failures / ±0) {code} vs. {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/} JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f) Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f refs/remotes/origin/master Test Result (3 failures / ±0) {code} So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the projects into building anything they haven't already built. > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-475) Build of Drools/jBPM tools for Eclipse Mars fails with Java 7

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-475?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-475. ----------------------------------- Verified with JBDS-IS 9.0.0.GA which contains Drolls/jBPM plugin 6.4.1.Final-v20160503-1355-B205 and it works fine with JDK 8. > Build of Drools/jBPM tools for Eclipse Mars fails with Java 7 > ------------------------------------------------------------- > > Key: JBTIS-475 > URL: https://issues.jboss.org/browse/JBTIS-475 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: drools/ jBPM > Affects Versions: 4.3.0.Final-TP > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 4.3.0.Final-TP > > > Drools/jBPM requires building with Java 7, while apparently the Mars JBTIS requires a Java 8 runtime. This is causing a problem in the tycho surefire plugin when I try to build the droolsjbpm-tools project against the Mars JBTIS (currently 4.3.0.Beta1e) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21785: ------------------------------------ Seems as though PR jobs won't also build commits: {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/} GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge conflicts. 734e1c3a03355c0a57e21bb723241e98f2286751 refs/remotes/origin/pr/412/merge Test Result (69 failures / ±0) {code} vs. {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/} JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f) Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f refs/remotes/origin/master Test Result (3 failures / ±0) {code} So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the projects into building anything they haven't already built. > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-479) Add SwitchYard to 9.0.0.Alpha1/Mars

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-479?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-479. ----------------------------------- Verified with JBDS-IS 9.0.0.GA where SwitchYard 2.1.0.Beta3-v20160226-2057-B645 is on early access > Add SwitchYard to 9.0.0.Alpha1/Mars > ----------------------------------- > > Key: JBTIS-479 > URL: https://issues.jboss.org/browse/JBTIS-479 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha2 > > > Add switchyard to the IS for Mars. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22228: ----------------------------------------------- OpenShiftServerUtils.getService() method could have null connection addressed in line 309 only in master. [~tmader], could you please test several builds back to the moment you got the issue? Pinpointing the build that 'accidentally' fixed this issue will let close it. > NPE when deploying to Openshift EAP > ----------------------------------- > > Key: JBIDE-22228 > URL: https://issues.jboss.org/browse/JBIDE-22228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Max Rydahl Andersen > Fix For: 4.4.x > > > When I try to publish to an EAP in the CDK, I get a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-482. ----------------------------------- Verified with JBTIS 4.3.0.Final and JBDSIS 9.0.0.GA. Only ESB and jBPM3 use the old license but they are now deprecated. Please reopen if this is a problem. > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png, lic1.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-483) B*MS - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-483?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-483. ----------------------------------- Verified with JBTIS 4.3.0.Final and JBDSIS 9.0.0.GA > B*MS - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------ > > Key: JBTIS-483 > URL: https://issues.jboss.org/browse/JBTIS-483 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPEL, BPMN2, drools/ jBPM, jBPM3 > Reporter: Paul Leacu > Assignee: Robert (Bob) Brodt > Fix For: 4.3.0.Beta1 > > Attachments: lic1.png > > > Please make sure that the B*MS IS components are including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-487) SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-487?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-487. ----------------------------------- Verified with JBTIS 4.3.0.Final and JBDSIS 9.0.0.GA > SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------ > > Key: JBTIS-487 > URL: https://issues.jboss.org/browse/JBTIS-487 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: IS-projects-using-old-license.png, IS-projects-using-old-license_2.png > > > Please make sure that SwitchYard is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-485) ModeShape - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-485?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-485. ----------------------------------- Verified with JBTIS 4.3.0.Final and JBDSIS 9.0.0.GA > ModeShape - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ----------------------------------------------------------------------- > > Key: JBTIS-485 > URL: https://issues.jboss.org/browse/JBTIS-485 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: modeshape > Affects Versions: 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Dan Florian > Priority: Blocker > Fix For: 4.3.0.Alpha2, 9.0.0.Alpha2 > > > Please make sure that ModeShape is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-484) Teiid Designer - - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-484?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-484. ----------------------------------- Verified with JBTIS 4.3.0.Final and JBDSIS 9.0.0.GA > Teiid Designer - - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------------- > > Key: JBTIS-484 > URL: https://issues.jboss.org/browse/JBTIS-484 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: teiid > Reporter: Paul Leacu > Assignee: Barry LaFond > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: lic1.png, td1.png > > > Please make sure that Teiid Designer is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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