December 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2053) Add CI support for Mac

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2053?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2053: ----------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > Add CI support for Mac > ---------------------- > > Key: JBTM-2053 > URL: https://issues.jboss.org/browse/JBTM-2053 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > We need to create a new user and and then add the machine as a slave to the NCL CI cluster. > We should then configure a weekly job to run CI on it. We need to add the jdbc profile for the machine name. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2061: --------------------------------------- I'm deploying missing artifacts separatelly > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2060) STM not compiling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2060?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2060: ------------------------------------- Affects IPV6 too: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/150/ [~marklittle], unless you object, I would like to revert your last commit as it certainly appears to affect all our CI builds? > STM not compiling > ----------------- > > Key: JBTM-2060 > URL: https://issues.jboss.org/browse/JBTM-2060 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Priority: Blocker > Fix For: 5.0.0.CR3 > > > CI is failing to build past STM so marking as a blocker. > This is the line that if I comment out the build succeeds: > https://github.com/jbosstm/narayana/blob/master/STM/src/main/java/org/jbo... > It could be a JDK bug if it works for you? Here is what I am using: > Fedora 18 > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ env | grep JAVA > JAVA_HOME=/usr/lib/jvm/java-1.7.0 > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ which java > /usr/lib/jvm/java-1.7.0/bin/java > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ java -version > java version "1.7.0_45" > OpenJDK Runtime Environment (fedora-2.4.3.0.fc18-x86_64 u45-b15) > OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) > Can we git revert https://github.com/jbosstm/narayana/commit/d1e5c1adb175104e95db578d8b3001... till we know what the issue is? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-2061 at 12/12/13 12:04 PM: ---------------------------------------------------------------- [~tomjenkinson], I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporary issue with Nexus during your deployment. was (Author: gytis): [~tomjenkinson], I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporal issue with Nexus during your deployment. > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-2061 at 12/12/13 12:04 PM: ---------------------------------------------------------------- I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporary issue with Nexus during your deployment. was (Author: gytis): [~tomjenkinson], I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporary issue with Nexus during your deployment. > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Gytis Trikleris edited comment on JBTM-2061 at 12/12/13 11:54 AM: ------------------------------------------------------------------ [~tomjenkinson], I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporal issue with Nexus during your deployment. was (Author: gytis): I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporal issue with Nexus during your deployment. > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2061: --------------------------------------- I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporal issue with Nexus during your deployment. > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2061: ------------------------------------- Thanks for the update, personally I think it is most likely there is an issue with Nexus. I wish I had noticed it earlier so I could check my log. As you suggested via email, maybe do a snapshot release and check that you see the blacktie-all pom etc being uploaded? > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2061: --------------------------------------- There were only three blacktie commits between 5.0.0.CR1 and 5.0.0.CR2, none of which modified poms. However, narayana-all pom was updated to use jboss-parent in that period. > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2061: --------------------------------------- Artifacts which where available with CR1 and are still available with CR2: * org.jboss.narayana.blacktie:blacktie-idl-jacorb * org.jboss.narayana.blacktie:blacktie-jatmibroker-nbf * org.jboss.narayana.blacktie:blacktie-jatmibroker-xatmi * org.jboss.narayana.blacktie:btadmin Artifacts which were available with CR1 but are not in CR2: * org.jboss.narayana.blacktie:blacktie-all * org.jboss.narayana.blacktie:blacktie-common * org.jboss.narayana.blacktie:blacktie-idl * org.jboss.narayana.blacktie:blacktie-java * org.jboss.narayana.blacktie:blacktie-xsd * org.jboss.narayana.blacktie.plugins:blacktie-cpp-plugin > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2013