February 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-138) Upgrade the SimpleReleaseProcess

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-138?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-138. ----------------------------- Resolution: Done > Upgrade the SimpleReleaseProcess > -------------------------------- > > Key: SRAMP-138 > URL: https://issues.jboss.org/browse/SRAMP-138 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > So it includes a notification after deployment, with a url to the taskform to approve the smoke test. Then a notification afterwards to display the status text the SmokeTester put in OK/FAIL. > Later we can make a more complex/realistic workflow, but this at least shows off the capabilities. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-138) Upgrade the SimpleReleaseProcess

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-138?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-138: ---------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/178 > Upgrade the SimpleReleaseProcess > -------------------------------- > > Key: SRAMP-138 > URL: https://issues.jboss.org/browse/SRAMP-138 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > So it includes a notification after deployment, with a url to the taskform to approve the smoke test. Then a notification afterwards to display the status text the SmokeTester put in OK/FAIL. > Later we can make a more complex/realistic workflow, but this at least shows off the capabilities. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-144) see if we can use XMLProperty to read version info in the maven poms

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-144: ------------------------------- Summary: see if we can use XMLProperty to read version info in the maven poms Key: SRAMP-144 URL: https://issues.jboss.org/browse/SRAMP-144 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kurt Stam Assignee: Kurt Stam Fix For: Milestone 4 It seems easy to use XMLProperty to read version info in our pom, so we can rid our ant scripts of hardcoded versions. Not sure if this approach works in the distro. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-143) ModeShape should persist between restarts

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-143: ------------------------------- Summary: ModeShape should persist between restarts Key: SRAMP-143 URL: https://issues.jboss.org/browse/SRAMP-143 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: Milestone 3 (Workflow and Relationships) Reporter: Kurt Stam Assignee: Kurt Stam Fix For: Milestone 4 The ModeShape service is not persisting data between restarts, iow it must be in memory at the moment. I thought it was set to files on disk but apparently not so.. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-142) governance console to pick up tasks

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-142: ------------------------------- Summary: governance console to pick up tasks Key: SRAMP-142 URL: https://issues.jboss.org/browse/SRAMP-142 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Governance Reporter: Kurt Stam Assignee: Kurt Stam Fix For: Milestone 4 I'd like to put in a link to the exact task in the notification email. I can link to the jbpm-console, but it'd be a lot nicer if we can embed the taskforms in a governance ui. Note that we typically use groupIds (dev, qa, etc), and that people in this group need to claim this task first, before they can work on it. Something like, Scott being in qa, and looking for the tasks he is participating in, and then claiming task 53: http://localhost:8080/gwt-console-server/rs/tasks/scott/participation {"tasks":[{"id":53,"processInstanceId":"87","processId":"overlord.demo.SimpleReleaseProcess","name":"overlord.demo.CheckDeployment","assignee":"","isBlocking":true,"isSignalling":false,"outcomes":[],"currentState":"OPEN","participantUsers":[],"participantGroups":[],"url":"http://localhost:8080/gwt-console-server/rs/form/task/53/render","priority":0}]} POST http://localhost:8080/gwt-console-server/rs/task/53/assign/scott -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-122) Restructure way jbossas modules are created

by Gary Brown (JIRA)

Gary Brown created BAM-122: ------------------------------ Summary: Restructure way jbossas modules are created Key: BAM-122 URL: https://issues.jboss.org/browse/BAM-122 Project: Business Activity Monitoring Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 Use a similar approach to switchyard to build the modules, and allow external modules (e.g. drools, mvel) where they don't already exist. So only overwrite the external modules if not already present. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-8) Integration with Maven to push artifacts to a PROD repository

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-8?page=com.atlassian.jira.plugin.sy... ] Kurt Stam updated SRAMP-8: -------------------------- Fix Version/s: Milestone 4 > Integration with Maven to push artifacts to a PROD repository > ------------------------------------------------------------- > > Key: SRAMP-8 > URL: https://issues.jboss.org/browse/SRAMP-8 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > As part of some workflow an approved artifact can be pushed to a maven repository with production artifacts. Probably using Apache Wagon. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-121) Move switchyard helper classes for activity reporting and active collection access to general JEE module

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-121?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-121. ---------------------------- Resolution: Done > Move switchyard helper classes for activity reporting and active collection access to general JEE module > -------------------------------------------------------------------------------------------------------- > > Key: BAM-121 > URL: https://issues.jboss.org/browse/BAM-121 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > The helper classes that have been developed to simplify activity reporting and accessing active collections from a switchyard app should be moved to a JEE generic module, as not switchyard specific. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-121) Move switchyard helper classes for activity reporting and active collection access to general JEE module

by Gary Brown (JIRA)

Gary Brown created BAM-121: ------------------------------ Summary: Move switchyard helper classes for activity reporting and active collection access to general JEE module Key: BAM-121 URL: https://issues.jboss.org/browse/BAM-121 Project: Business Activity Monitoring Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 The helper classes that have been developed to simplify activity reporting and accessing active collections from a switchyard app should be moved to a JEE generic module, as not switchyard specific. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-26) Investigate deserialising custom activity types

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-26?page=com.atlassian.jira.plugin.sys... ] Gary Brown resolved BAM-26. --------------------------- Resolution: Done Added CustomActivity with a type field and can use properties to provide specific details. > Investigate deserialising custom activity types > ----------------------------------------------- > > Key: BAM-26 > URL: https://issues.jboss.org/browse/BAM-26 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Currently the JSON deserialization uses a type field to determine the ActivityType. > However this is only possible because the types have been registered against the ActivityType class using the Jackson JsonSubTypes annotation. > The benefit of the type field approach is that it is language independent (whereas @class is Java specific) and the amount of information in the json encoding is smaller (i.e. no package name). > However this approach means it is not easy for users to add new ActivityType derived classes, as the class would need to be added to the JsonSubTypes derived in the annotations for ActivityType class. > Another approach would be to have own type registry that custom activity type classes could also be registered with. > Need to investigate the possibilities and how the user's custom classes would be added to the AS7 installation easily. May need to update the org.overlord.bam module? -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2013