August 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (OVERLORD-144) "Sales pitch" page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-144?page=com.atlassian.jira.plug... ] Gary Brown commented on OVERLORD-144: ------------------------------------- I think the main argument is, for governance to be effective it must be outside the control of the development organisation, but at the same time not become a burden on them in such a way that it would impact their work. Therefore, development organisation would use CI in support of doing their own development work, running unit and integration tests to ensure they can regressions at the earliest possible time in the development lifecycle, to avoid the issues being detected later in the lifecycle (i.e. by QE), which would increase the cost of fixing the problem considerably. For the same reason, applying governance policies at the earliest possible stage in the development lifecycle reduces the cost of detecting any issues. For example, if a WSDL definition is found to no comply to WS-I during development, it is relatively inexpensive to fix. If the problem is only detected after the system is released, then it is more time consuming to fix. Having governance externalised means that organisations don't have to rely on the development team and their supporting infrastructure to correctly apply the governance policies. It also means the organisation has flexibility to change those policies (or introduce new ones) without impacting the development infrastructure/team. > "Sales pitch" page > ------------------ > > Key: OVERLORD-144 > URL: https://issues.jboss.org/browse/OVERLORD-144 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Create a "sales pitch" page that describes the advantages over traditional CI, repos, etc -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-541: ------------------------------ Description: The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. At a minimum, the spec states that: "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." was:The restrictions on updateContent need beefed up. > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-541: ------------------------------ Summary: Tighten the restrictions on artifact content updates (was: Consider removing artifact/content updates) > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > From [~eric.wittmann] on SRAMP-539: > {quote} > In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail. > All in all I am disappointed in myself for implementing the updateContent feature to begin with. > {quote} > I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-541: ------------------------------ Description: The restrictions on updateContent need beefed up. (was: From [~eric.wittmann] on SRAMP-539: {quote} In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail. All in all I am disappointed in myself for implementing the updateContent feature to begin with. {quote} I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases.) > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > The restrictions on updateContent need beefed up. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-541: ------------------------------ Git Pull Request: (was: https://github.com/Governance/s-ramp/pull/477) > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > The restrictions on updateContent need beefed up. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-144) "Sales pitch" page

by Brett Meyer (JIRA)

Brett Meyer created OVERLORD-144: ------------------------------------ Summary: "Sales pitch" page Key: OVERLORD-144 URL: https://issues.jboss.org/browse/OVERLORD-144 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Create a "sales pitch" page that describes the advantages over traditional CI, repos, etc -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-143) Project roadmaps

by Brett Meyer (JIRA)

Brett Meyer created OVERLORD-143: ------------------------------------ Summary: Project roadmaps Key: OVERLORD-143 URL: https://issues.jboss.org/browse/OVERLORD-143 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Create roadmap pages for each project w/ high level info. Also add a link to forums and ask for discussions -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-553) Artifacts page's search bar should include a link to the query syntax docs

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-553: --------------------------------- Summary: Artifacts page's search bar should include a link to the query syntax docs Key: SRAMP-553 URL: https://issues.jboss.org/browse/SRAMP-553 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-553) Artifacts page's search bar should include a link to the query syntax docs

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-553?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-553: ------------------------------ Priority: Minor (was: Major) > Artifacts page's search bar should include a link to the query syntax docs > -------------------------------------------------------------------------- > > Key: SRAMP-553 > URL: https://issues.jboss.org/browse/SRAMP-553 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-554) Display the equivalent query syntax when the UI search filters are used

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-554: --------------------------------- Summary: Display the equivalent query syntax when the UI search filters are used Key: SRAMP-554 URL: https://issues.jboss.org/browse/SRAMP-554 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 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 August 2014