Roadmap

[anbraten]

This is a general roadmap for the project covering the most requested epics. They are sorted in some kind of priority (considered by maintainers), but this is not forced.

General roadmap

• RFC: How to add new pipeline events without needing to ignore them each time #1451
• Add more pipeline events New pipeline events #3425
  • Cron Cron triggers #8 Add cron jobs #934
  • Support manually triggering a pipeline Add support to trigger pipelines manually #83 Create build from API? #240
  • PR close Support PR closed event #286
  • Release (type: draft, pre, stable; action: created, updated, deleted) Add release event #3226
  • comments (create, delete, update) / Add support for comment commands #814
  • label (added, removed, issue, PR)
  • issues (created, updated, closed, reopened)
• well known RFC: Establish well-known spec to communicate logs/cicd-stuff back to forges on request #2159
• Autoscaler Autoscaler #999
• BringYourOwnAgent Allow users to register own agents #267
• non root images Add support for nonroot OCI images #1077
• pipeline compile step RFC: pipeline compile step #2254
• enhance plugins so they can easily be used for caching Pipeline caching #2295
• multiple forges Add support for multiple forges  #138
• UI configured forges Set gitea-client and gitea-secret in web UI #425
• Admin panel [Feature] Admin Panel #345
• UI plugins which can be used by plugins UI plugins #2287
• Add support for HA setup RFC: Clustering (refactor pub-sub) #2304
• Decide to use Swagger docs or Graphql Update swagger docs #292
• Anonymous usage tracking #84
• repo extensions (external secrets, registries, config compilers) Configuration Extension #783
• deprecation warnings Warn users for bad-habits and deprecations in configs #922

[anbraten]

As 1.0 was released now this is my plan for issues I want to work on next:

• Enhance linter and errors #1572, Enhance config linter #276, Warn users for bad-habits and deprecations in configs #922
• Support PR closed event #286
• think about caching Pipeline caching #2295
• Add support for multiple forges  #138
• maybe Allow users to register own agents #267
• some kind of advanced pipeline config maybe by sth like RFC: pipeline compile step #2254 Support shared configs #2286

[anbraten]

Breaking changes

• pipeline to steps Fail on deprecated pipeline keys #2180
• branches to when.branch Fail on deprecated pipeline keys #2180
• platform to labels Remove deprecated options parsing #2480
• step needs keyword / DAG drop step.group in favour of depends_on to create a DAG #1860
• pre-processor syntax Refactor pre-processor syntax #2473
• remove custom clone step property: clone Remove custom clone property #2474
• drop detach: true in favor of "normal" service https://woodpecker-ci.org/docs/next/usage/services#detachment
• handle new events (filters) RFC: How to add new pipeline events without needing to ignore them each time #2174

[6543]

I'm against removing detatched:

There is no equivalent ... services wont do as they start before while detatched can start and use e.g. artifacts build by a step before

[qwerty287]

I'd rather implement something like #2495 so the service is only active as long it's needed.

[qwerty287]

#3411 will allow this