Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to assign steps to services #2495

Open
4 tasks done
qwerty287 opened this issue Sep 23, 2023 · 2 comments · May be fixed by #3411
Open
4 tasks done

Allow to assign steps to services #2495

qwerty287 opened this issue Sep 23, 2023 · 2 comments · May be fixed by #3411
Labels
feature add new functionality

Comments

@qwerty287
Copy link
Contributor

Clear and concise description of the problem

Services always run, even if the pipeline fails before a step runs that needs the service

Suggested solution

Add a parameter like steps: [ s1, s2 ] to services that allows to control for which steps services must start.
Don't start the step before it is clear that the assigned steps will run, and shut it down after the steps has finished.

Alternative

No response

Additional context

No response

Validations

  • Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
  • Read the Contributing Guidelines.
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@qwerty287 qwerty287 added the feature add new functionality label Sep 23, 2023
@anbraten
Copy link
Member

You could currently use a step with the detached keyword.

@qwerty287
Copy link
Contributor Author

When does this step is shut down? After the pipeline finished?

Also, this is listed for removal in #2170 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature add new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants