QRun-IO/qqq-orb
Archived
2
0 Fork 0
Code Issues 6 Actions Packages Projects Releases 17 Wiki Activity

Support Feature Snapshot Releases #1

New Issue
Closed
opened 2025-09-20 12:04:39 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2025-09-20 12:04:39 +00:00 (Migrated from github.com)
Copy link
Copy source

🚀 Feature Description

New Orb Workflow to publish unique snapshots from feature branches during development

💡 Motivation

Helping CTL developers downstream with their internal QA workflows

📋 Detailed Description

Update the orb to allow for a unique style of publishing. CTL Developers in particular have a complex integration and qa process which would benefit from having the ability to use feature branch snapshots downstream in CTL - prior to development and rc merges.

This request is to have feature/ branches able to publish unique snapshots on a tag push into those branches

  • What: What should the feature do?
    • Create and publish a unique snapshot when a trigger tag is pushed to a feature branch
  • Why: Why is this feature important?
    • CTL developers are requesting the ability to use this as integration testing downstream, prior to develop or rc workflows
  • How: How should it work?
  • 1 - full branch feature name, up to 100chars
  • 2 - publish will trigger on "branch only [feature/STAR]" and "tags only [publish-STAR]" , this will create files like 0.2.0-circleci-orb-upgrade-577524c-SNAPSHOT
  • When: When would this be used?
    • Only in feature branches

🔧 Implementation Ideas

maybe as extra nice milk, it will put a message in here - or to the developer that triggered it, what the snapshot name was and that is is now published

to avoid having to log into circleci and read the steps to figure out what name was just published

📊 Priority

  • Low - Nice to have
  • Medium - Would be helpful
  • High - Important for workflow
  • Critical - Blocking current work
## 🚀 Feature Description New Orb Workflow to publish unique snapshots from feature branches during development ## 💡 Motivation Helping CTL developers downstream with their internal QA workflows ## 📋 Detailed Description Update the orb to allow for a unique style of publishing. CTL Developers in particular have a complex integration and qa process which would benefit from having the ability to use feature branch snapshots downstream in CTL - prior to development and rc merges. This request is to have feature/ branches able to publish unique snapshots on a tag push into those branches - **What**: What should the feature do? - - Create and publish a unique snapshot when a trigger tag is pushed to a feature branch - **Why**: Why is this feature important? - - CTL developers are requesting the ability to use this as integration testing downstream, prior to develop or rc workflows - **How**: How should it work? - 1 - full branch feature name, up to 100chars - 2 - publish will trigger on "branch only [feature/STAR]" and "tags only [publish-STAR]" , this will create files like 0.2.0-circleci-orb-upgrade-577524c-SNAPSHOT - **When**: When would this be used? - - Only in feature branches ## 🔧 Implementation Ideas maybe as extra nice milk, it will put a message in here - or to the developer that triggered it, what the snapshot name was and that is is now published to avoid having to log into circleci and read the steps to figure out what name was just published ## 📊 Priority - [ ] Low - Nice to have - [ ] Medium - Would be helpful - [x] High - Important for workflow - [ ] Critical - Blocking current work
👍 1
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No labels enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qqq-orb#1