External/card-drop
4
0
Fork 0
Code Issues 24 Pull requests 1 Actions Packages Projects 1 Releases 18 Wiki Activity

AS a developer, I want Woodpecker to have an option to manually run a deployment pipeline #163

New issue
Closed
opened 2024-02-12 17:52:36 +00:00 by Vylpes · 2 comments
Vylpes commented 2024-02-12 17:52:36 +00:00
Owner
Copy link

Epic:
Story Points: 3

AS a developer, I want Woodpecker to have an option to manually run a deployment pipeline
SO THAT I can easily restart the bot without needing a code change

Acceptance Criteria

AS a developer
GIVEN I want to restart the bot with the current code state
WHEN I go to the Woodpecker project
THEN I should be able to manually trigger the stage and prod deployments

Subtasks

No subtasks

Notes

No notes

Epic: \ Story Points: 3 --- AS a developer, I want Woodpecker to have an option to manually run a deployment pipeline SO THAT I can easily restart the bot without needing a code change ## Acceptance Criteria AS a developer GIVEN I want to restart the bot with the current code state WHEN I go to the Woodpecker project THEN I should be able to manually trigger the stage and prod deployments ## Subtasks *No subtasks* ## Notes *No notes*
Vylpes added the
type
story
needs criteria
needs estimate
 labels 2024-02-12 17:52:42 +00:00
Vylpes changed title from Woodpecker should let me manually run the pipeline to AS a developer, I want Woodpecker to have an option to manually run a deployment pipeline 2024-02-18 15:12:46 +00:00
Vylpes commented 2024-02-18 15:14:22 +00:00
Author
Owner
Copy link

Will need to check if this is possible, I believe it is just not sure how

Will need to check if this is possible, I believe it is just not sure how
Vylpes removed the
needs criteria
 label 2024-02-18 15:14:36 +00:00
Vylpes commented 2024-03-03 15:06:43 +00:00
Author
Owner
Copy link

Will need to check if this is possible, I believe it is just not sure how

We could also just restart the pipeline, or have the deploy button at least not re-build?

> Will need to check if this is possible, I believe it is just not sure how We could also just restart the pipeline, or have the deploy button at least not re-build?
Vylpes removed the
needs estimate
 label 2024-03-03 15:07:02 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/203-sacrifice-command
feature/204-coins-cron
develop
v0.5.1
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.1
v0.2.0
v0.1.8
v0.1.7
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
blocked

   
duplicate

   
needs criteria

   
needs estimate

   
question
  
type
admin

  
type
bug

  
type
defect

  
type
dependencies

  
type
documentation

  
type
epic

  
type
investigation

  
type
spike

  
type
story

  
won't fix
No labels
blocked
duplicate
needs criteria
needs estimate
question
type
admin
type
bug
type
defect
type
dependencies
type
documentation
type
epic
type
investigation
type
spike
type
story
won't fix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: External/card-drop#163
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?