Bug 1330946 - [RFE] Possibility to create branches in Lifecycle Environment
Summary: [RFE] Possibility to create branches in Lifecycle Environment
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.1.8
Hardware: All
OS: All
unspecified
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 11:04 UTC by Michael Orlov
Modified: 2020-12-11 12:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-24 20:25:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Michael Orlov 2016-04-27 11:04:28 UTC
Currently it is not possible to create a branch in the lifecycle environment, they can be linear only.
IN the complex enterprise environments, it is required from time to time to have this possibility.

Example:
hammer lifecycle-environment list --organization "Amdocs PBG"
---|-------------|------------
ID | NAME        | PRIOR
---|-------------|------------
13 | PBG 9.3 QA  | PBG 9.3 Dev
12 | PBG 9.3 Dev | Library
---|-------------|------------

Would like to create multiple branches per project after the QA (PROD1 , PROD2, etc)
However, after creating one of them, the second is failing with the error:
Could not create environment:
  Validation failed: Prior environment can only have one child

I understand that this is a current design of the lilfecycle environment, but can it be changes in the future versions?

Comment 3 Bryan Kearney 2017-08-24 20:25:27 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.