Device Groups on stages other than the final stage of a DevOps Pipeline
Description
Allow any stage of a Devops Pipeline to be assigned a device group. Where an application needs multiple devices running the same flows in production, this would allow that application to be fully tested in staging.
Which customers would this be available to
None
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
### UX Updates
- [ ] Re-enable 'add stage' button when last stage is Device Group
- [ ] Do not allow Device/Instance stages after a Device Group stage
- [ ] Add Action dropdown when Device Group is selected with single 'Use latest snapshot' option
### Backend Updates
- [ ] Update validation checks to permit Device Group in other pipeline stages
- [ ] Implement deployment action for DeviceGroup to DeviceGroup
Requested by these two Enterprise customers.
https://app-eu1.hubspot.com/contacts/26586079/record/0-2/7039008216 https://app-eu1.hubspot.com/contacts/26586079/record/0-2/8845845707
In a situation where we have:
| Stage 1 | Stage 2 | Stage 3 |
|---|---|---|
| Instance | Device Group A | Device Group B |
Is the expectation here that the push from Stage 2 would in fact collect from Stage 1? As we don't map (currently) the most recently deployed snapshots, or the ability to capture a snapshot from an entire device group.
We do store the current target snapshot against the DeviceGroup.
In this scenario, triggering a deploy from 2->3 should copy the target snapshot id from DGA to DGB. That's the only option the stage should offer.
Have added tasks for this split between backend and frontend.
@knolleary any idea why/how this slipped? Were their technical problems?
@joepavitt just a matter of scheduling. Not aware of any technical blockers.
Hi What is the current state of this 'feature'?
@78wesley - it's is planned for this release, so should be in the next couple of weeks
@Steve-Mcl can this now be closed?