February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-28) Setup Jenkins Jobs Pipeline for CI

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-28: ----------------------------------- Summary: Setup Jenkins Jobs Pipeline for CI Key: SWSQE-28 URL: https://issues.jboss.org/browse/SWSQE-28 Project: Swift Sunshine QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Sunil kondkar New Jenkins jobs pipeline is needed on Jenkins 2 to do the following actions: # Trigger per PR # Trigger Nightly # Call "hawkular-qe-utils.git/tree/sws/scripts/prepare_env.sh" to install Istio on OC # Call "hawkular-qe-utils.git/tree/sws/scripts/prepare_env.sh" to install SWS on OC # Run SWSQE automation over SWS. # Report the Run results. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3617) Unable to enable disabled deployment through the CLI in domain mode

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3617?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3617: ---------------------------------------------- [~mstefank], seems that this issue and WFCORE-3563 are duplicate. This is not exactly the same scenario (1 server-group vs 2 server-group) but this look like the same root cause. > Unable to enable disabled deployment through the CLI in domain mode > ------------------------------------------------------------------- > > Key: WFCORE-3617 > URL: https://issues.jboss.org/browse/WFCORE-3617 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Beta1 > Reporter: Martin Stefanko > Assignee: Martin Stefanko > > The CLI detects duplicate resource when trying to enable disabled deployment for a server-group in domain mode: > {code} > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ > (\"server-group\" => \"main-server-group\"), > (\"deployment\" => \"app.war\") > ]"}} > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3566) Different results of disabling commands already disabled deployment

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3566?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3566: ---------------------------------------------- These 2 issues could be related to this one. > Different results of disabling commands already disabled deployment > ------------------------------------------------------------------- > > Key: WFCORE-3566 > URL: https://issues.jboss.org/browse/WFCORE-3566 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vratislav Marek > Assignee: Martin Stefanko > > *Different command result of disabling already disabled deployment in standalone and domain mode* > * In standalone return > {noformat} > WFLYCTL0155: 'steps' may not be null > {noformat} > * In domain return nothing, no warning or error > {noformat} > [standalone@localhost:9990 /] deployment info > NAME RUNTIME-NAME PERSISTENT ENABLED STATUS > cli-test-another-deploy.war cli-test-another-deploy.war true true OK > cli-test-app1-deploy.war cli-test-app1-deploy.war true false STOPPED > cli-test-app2-deploy.war cli-test-app2-deploy.war true true OK > [standalone@localhost:9990 /] deployment disable cli-test-app1-deploy-all.war > WFLYCTL0155: 'steps' may not be null > [standalone@localhost:9990 /] > {noformat} > {noformat} > [domain@localhost:9990 /] deployment info --server-groups=main-server-group > NAME RUNTIME-NAME STATE > cli-test-another-deploy-all.war cli-test-another-deploy-all.war enabled > cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war added > cli-test-app2-deploy-all.war cli-test-app2-deploy-all.war not added > cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war enabled > [domain@localhost:9990 /] deployment disable --server-groups=main-server-group cli-test-app1-deploy-all.war > [domain@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1) Automate Installing of SWS on BC Openshift

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-1?page=com.atlassian.jira.plugin.sy... ] Hayk Hovsepyan updated SWSQE-1: ------------------------------- Parent: SWSQE-27 Issue Type: Sub-task (was: Task) > Automate Installing of SWS on BC Openshift > ------------------------------------------ > > Key: SWSQE-1 > URL: https://issues.jboss.org/browse/SWSQE-1 > Project: Swift Sunshine QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-27) Implement CI on SWS Project over Nightly builds and per PR

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-27: ----------------------------------- Summary: Implement CI on SWS Project over Nightly builds and per PR Key: SWSQE-27 URL: https://issues.jboss.org/browse/SWSQE-27 Project: Swift Sunshine QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3566) Different results of disabling commands already disabled deployment

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3566?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3566: ---------------------------------------------- [~mstefank], you should ask [~vmarek] for the tests he developed to cover this case. > Different results of disabling commands already disabled deployment > ------------------------------------------------------------------- > > Key: WFCORE-3566 > URL: https://issues.jboss.org/browse/WFCORE-3566 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vratislav Marek > Assignee: Martin Stefanko > > *Different command result of disabling already disabled deployment in standalone and domain mode* > * In standalone return > {noformat} > WFLYCTL0155: 'steps' may not be null > {noformat} > * In domain return nothing, no warning or error > {noformat} > [standalone@localhost:9990 /] deployment info > NAME RUNTIME-NAME PERSISTENT ENABLED STATUS > cli-test-another-deploy.war cli-test-another-deploy.war true true OK > cli-test-app1-deploy.war cli-test-app1-deploy.war true false STOPPED > cli-test-app2-deploy.war cli-test-app2-deploy.war true true OK > [standalone@localhost:9990 /] deployment disable cli-test-app1-deploy-all.war > WFLYCTL0155: 'steps' may not be null > [standalone@localhost:9990 /] > {noformat} > {noformat} > [domain@localhost:9990 /] deployment info --server-groups=main-server-group > NAME RUNTIME-NAME STATE > cli-test-another-deploy-all.war cli-test-another-deploy-all.war enabled > cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war added > cli-test-app2-deploy-all.war cli-test-app2-deploy-all.war not added > cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war enabled > [domain@localhost:9990 /] deployment disable --server-groups=main-server-group cli-test-app1-deploy-all.war > [domain@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-26) Convert Hack Scripts to Cucushift Step or Ansible Playbooks

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-26?page=com.atlassian.jira.plugin.s... ] Hayk Hovsepyan commented on SWSQE-26: ------------------------------------- Good question, not yet, it is next step. Current installation script is: http://git.app.eng.bos.redhat.com/git/hawkular-qe-utils.git/tree/sws/scri... Currently is supposes that istio-system is installed on OS by hack/istio-install-openshift.sh Feel free to add that step if you need. > Convert Hack Scripts to Cucushift Step or Ansible Playbooks > ----------------------------------------------------------- > > Key: SWSQE-26 > URL: https://issues.jboss.org/browse/SWSQE-26 > Project: Swift Sunshine QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Michael Foley > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2338) MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2338?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2338: ------------------------------------- I cannot reproduce the problem. The following test case works for me. Can you please send a similar test case that demonstrates this issue? {code} @Test public void testHelloWorldWithSpace() throws Exception { KieServices ks = KieServices.Factory.get(); KieFileSystem kfs = ks.newKieFileSystem().write( "src/main/resources/my test/r1.drl", createDrl( "R1" ) ); ks.newKieBuilder( kfs ).buildAll(); KieSession ksession = ks.newKieContainer(ks.getRepository().getDefaultReleaseId()).newKieSession(); ksession.insert(new Message("Hello World")); int count = ksession.fireAllRules(); assertEquals( 1, count ); } {code} > MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2338 > URL: https://issues.jboss.org/browse/DROOLS-2338 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final, 7.5.0.Final, 7.6.0.Final > Environment: any > Reporter: Alexander Kotikhov > Assignee: Mario Fusco > Attachments: Снимок экрана от 2018-02-19 18-08-49.png > > > If a directory where any files are placed contains spaces > MemoryFileSystem.getFile(String path) returns object with truncated name. > To fix this error (in version 7.4.0) it is nessassary line 107 > *String name = decode( path ).substring( lastSlashPos + 1 );* > replace with > *String name = decode( path.substring( lastSlashPos + 1 ) );* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1517) SurefireBooterForkException during execution testsuite on HP-UX

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1517: --------------------------------- Summary: SurefireBooterForkException during execution testsuite on HP-UX Key: ELY-1517 URL: https://issues.jboss.org/browse/ELY-1517 Project: WildFly Elytron Issue Type: Bug Components: Testsuite Affects Versions: 1.2.0.Final Reporter: Ondrej Lukas When testsuite is run on HP-UX then no tests are executed and following exception occurs in log: {code} Process Exit Code: 1 at org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:496) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:443) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:295) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:955) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290) at org.apache.maven.cli.MavenCli.main(MavenCli.java:194) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? {code} This start to happen after upgrade of maven surefire plugin from version 2.20 to version 2.20.1 (as part of upgrade org.jboss:jboss-parent from version 24 to 25 in [1]). When I downgrade version back to 2.20 then tests run correctly. Even if issue is not directly on Wildfly Elytron project I suggest to downgrade surefire plugin back to version 2.20 until issue will be fixed in surefire. I reported [2] for it. [1] https://github.com/wildfly-security/wildfly-elytron/commit/aa515a5c2dff6f... [2] https://issues.apache.org/jira/browse/SUREFIRE-1479 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3623) Remove ModuleIndexService

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3623?page=com.atlassian.jira.plugi... ] Stuart Douglas commented on WFCORE-3623: ---------------------------------------- Usage in full is bogus, see https://github.com/wildfly/wildfly/pull/10908/files > Remove ModuleIndexService > ------------------------- > > Key: WFCORE-3623 > URL: https://issues.jboss.org/browse/WFCORE-3623 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > ModuleIndexService is never used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018