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

Feature/step #2

Draft
wants to merge 179 commits into
base: develop
Choose a base branch
from
Draft

Feature/step #2

wants to merge 179 commits into from

Conversation

mPokornyETM
Copy link
Owner

See #XXXXX

Testing done

Proposed upgrade guidelines

N/A

Submitter checklist

  • The Github issue, if it exists, is well-described.
  • The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
    • The changelog generator for plugins uses the pull request title as the changelog entry.
    • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.
  • For dependency updates, there are links to external changelogs and, if possible, full differentials.
  • Changes in the interface are documented also as examples.

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There is at least one (1) approval for the pull request and no outstanding requests for change.
  • Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
  • Changelog entries in the pull request title are accurate, human-readable, and in the imperative mood.
  • If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).

@oleg-kondaurov
Copy link

@mPokornyETM Can you provide some examples of using new locker in declarative pipelines, please?

@mPokornyETM
Copy link
Owner Author

@oleg-kondaurov sorry, This repository shall be delted. I provide the functionality here

jenkinsci/lockable-resources-plugin#457

but there are many changes and I am not finish yet. Maybe you want contribute?

@oleg-kondaurov
Copy link

oleg-kondaurov commented Mar 20, 2023

@mPokornyETM I don't have any knowledge of Java at all. Only Python and a little bit Groovy. Can help with Ukrainian and Russian localization.

@mPokornyETM
Copy link
Owner Author

@mPokornyETM I don't have any knowledge of Java at all. Only Python and a little bit Groovy. Can help with Ukrainian and Russian localization.

can you pls switch to this channel ? https://app.gitter.im/#/room/#jenkinsci_lockable-resources:gitter.im We can discuss it there. thx

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

Successfully merging this pull request may close these issues.

2 participants