[JBoss JIRA] (JBTM-1448) Failed to submit/remove Byteman script, because of refused connection
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1448?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reopened JBTM-1448:
---------------------------------
Assignee: Paul Robinson (was: Amos Feng)
(assigning to paul as Amos is away this week)
It looks like we need a "fore-port" for this as it appears to happen on the eap-61 branch: http://172.17.131.2/job/narayana/25/TESTS=XTS,jdk=jdk7.latest,label=linux...
> Failed to submit/remove Byteman script, because of refused connection
> ---------------------------------------------------------------------
>
> Key: JBTM-1448
> URL: https://issues.jboss.org/browse/JBTM-1448
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 4.16.7
>
> Attachments: console.txt
>
>
> See:
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP601/312
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP601/313
> {noformat}
> Tests in error:
> org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase: Failed to submit Byteman script
> org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase: Failed to remove Byteman script
> {noformat}
> {noformat}
> java.lang.RuntimeException: Failed to submit Byteman script
> at org.jboss.as.test.xts.simple.BMScript.submit(BMScript.java:43)
> at org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase.submitBytemanScript(WSBAParticipantCompletionTestCase.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:529)
> at java.net.Socket.connect(Socket.java:478)
> at java.net.Socket.<init>(Socket.java:375)
> at java.net.Socket.<init>(Socket.java:189)
> at org.jboss.byteman.agent.submit.Submit$Comm.<init>(Submit.java:797)
> at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:735)
> at org.jboss.byteman.agent.submit.Submit.addScripts(Submit.java:574)
> at org.jboss.byteman.agent.submit.Submit.addRulesFromFiles(Submit.java:547)
> at org.jboss.as.test.xts.simple.BMScript.submit(BMScript.java:41)
> ... 54 more
> {noformat}
> {noformat}
> java.lang.RuntimeException: Failed to remove Byteman script
> at org.jboss.as.test.xts.simple.BMScript.remove(BMScript.java:53)
> at org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase.removeBytemanScript(WSBAParticipantCompletionTestCase.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
> at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87)
> at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:529)
> at java.net.Socket.connect(Socket.java:478)
> at java.net.Socket.<init>(Socket.java:375)
> at java.net.Socket.<init>(Socket.java:189)
> at org.jboss.byteman.agent.submit.Submit$Comm.<init>(Submit.java:797)
> at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:735)
> at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:646)
> at org.jboss.byteman.agent.submit.Submit.deleteRulesFromFiles(Submit.java:619)
> at org.jboss.as.test.xts.simple.BMScript.remove(BMScript.java:51)
> ... 54 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1558:
-------------------------------------
One thing that this should consider is that when suspend/resume is called on the transactionmanager, we do not call TMSUSPEND/TMRESUME on the registered XAResources. The JTA spec states this is the responsibility of the application server, however there are no appropriate lifecycle callbacks available here: https://svn.jboss.org/repos/jbossas/projects/integration/tags/jboss-trans...
We should consider if this is really SPI or whether it is OK for TM::suspend to maybe XAR::end(TMSUSPEND) resources directly (considered from using JTA outside an AS)
> Prune redundant code from jboss-transaction-spi
> -----------------------------------------------
>
> Key: JBTM-1558
> URL: https://issues.jboss.org/browse/JBTM-1558
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Application Server Integration
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
> Attachments: as8.zip, ij-tx-spi.txt
>
>
> We can use jboss-transaction-spi to get started
> There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana.
> Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1634:
----------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> TX tests failed with "Unable to start a new txn on URI"
> -------------------------------------------------------
>
> Key: JBTM-1634
> URL: https://issues.jboss.org/browse/JBTM-1634
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/246/
> http://172.17.131.2/job/blacktie-linux32/915/
> http://172.17.131.2/job/blacktie-linux64/1472/
> {code}
> 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager
> 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok
> 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1
> 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost
> 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13
> 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
> 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000
> 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096
> 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes
> 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
> Content-Length: 145
> Connection: keep-alive
> Content-Type: text/html
> Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager?
> 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found
> {code}
> It looks like restat-web.war has not regiter as /rest-tx
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1611:
-----------------------------------
Attachment: 0001-JBTM-1611-Make-recovery-passes-configurable.patch
This file patches version 4.17.3.Final
Apply the patch using git apply <file>
The fix will be in 4.17.5
To see if the change fixes the failing tests you need to update qa/TaskImpl.properties, look for the line COMMAND_LINE_12=-DCoreEnvironmentBean.timeoutFactor=1 and set the factor to 2. Alternatively if you are using the CI narayana.sh script just export MFACTOR=2 before running the script.
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1611
> URL: https://issues.jboss.org/browse/JBTM-1611
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Fix For: 4.17.5
>
> Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch
>
>
> During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO).
> Tests which are failing:
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09
> - CrashRecovery09_Test01
> - CrashRecovery09_Test03
> - CrashRecovery09_Test05
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10
> - CrashRecovery10_Test01
> - CrashRecovery10_Test03
> - CrashRecovery10_Test05
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12
> - CrashRecovery12_Test03
> - CrashRecovery12_Test06
> Detailed log could be found in job:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te...
> I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBTM-1653) narayana Jenkins job is allowing lastSuccessfulbuild to expire
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1653?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1653:
-------------------------------------
Seems like it was fixed by a re-boot of Jenkins.
> narayana Jenkins job is allowing lastSuccessfulbuild to expire
> --------------------------------------------------------------
>
> Key: JBTM-1653
> URL: https://issues.jboss.org/browse/JBTM-1653
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 4.17.5, 5.0.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> the narayana multi-config job is supposed to save at least one successful build, but it is allowing it to expire. It seems like a bug, but I can't find a reference to it on Google.
> The problem is that all jobs that use these artefacts will now fail as they can no longer find them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBTM-1653) narayana Jenkins job is allowing lastSuccessfulbuild to expire
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1653?page=com.atlassian.jira.plugin.... ]
Paul Robinson resolved JBTM-1653.
---------------------------------
Resolution: Done
> narayana Jenkins job is allowing lastSuccessfulbuild to expire
> --------------------------------------------------------------
>
> Key: JBTM-1653
> URL: https://issues.jboss.org/browse/JBTM-1653
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 4.17.5, 5.0.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> the narayana multi-config job is supposed to save at least one successful build, but it is allowing it to expire. It seems like a bug, but I can't find a reference to it on Google.
> The problem is that all jobs that use these artefacts will now fail as they can no longer find them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years