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.

Sign up for GitHub

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

Jump to bottom

Update AvatarCache clone to use proper scm-api version #261

Open
4 tasks
mlasevich opened this issue Dec 4, 2019 · 7 comments · May be fixed by #978
Open
4 tasks

Update AvatarCache clone to use proper scm-api version #261

mlasevich opened this issue Dec 4, 2019 · 7 comments · May be fixed by #978
Assignees
@nfalco79

Comments

@mlasevich
Copy link
Contributor

Your checklist for this issue

  • Jenkins version

  • Plugin version

  • Bitbucket cloud

  • Bitbucket server and version

Description

A placeholder issue to remember to do some housecleaning and remove the local copy of AvatarCache added in #240 , in favor of shared version added in jenkinsci/scm-api-plugin#79 (once the scm-api-plugin 2.6.4 gets released)

:-)
@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 2, 2020
@jetersen
Copy link
Member

jetersen commented Feb 2, 2020

Not stale

@stale stale bot removed the stale label Feb 2, 2020
@stale
Copy link

stale bot commented Apr 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 2, 2020
@jetersen jetersen removed the stale label Apr 2, 2020
@mlasevich
Copy link
Contributor Author

Would be nice if scm-api-plugin would get released :-)

@stale
Copy link

stale bot commented Jun 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 10, 2020
@jetersen
Copy link
Member

Still relevant :(

@stale stale bot removed the stale label Jun 10, 2020
@stale
Copy link

stale bot commented Jun 16, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 16, 2021
@bitwiseman bitwiseman removed the stale label Jun 16, 2021
@nfalco79 nfalco79 self-assigned this Dec 5, 2024
@nfalco79 nfalco79 linked a pull request Jan 26, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nfalco79 nfalco79

Labels
None yet
Projects
None yet
Milestone
No milestone
4 participants
@jetersen @bitwiseman @mlasevich @nfalco79