-
Notifications
You must be signed in to change notification settings - Fork 25
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
Support for Azure DevOps Server #8
Comments
Hi, looks like same issue as with the pipelines package, hardcoded "dev.azure.com" hostname. I can get to it in a couple of days, otherwise you can open a PR same as with the other package. Thanks |
Hi @antoniobergas, |
Hi! Thanks for take a look on this. Will test it ASAP |
Hi, I'm sorry for the big delay, still pending to double check, I had no time yet. We are currently in adoption of Backstage and will need to do more tempaltes in the scaffolder soon, will check then if this works properly. Sorry and thanks for the hard work |
Still pending to test this one, will probably have time after the next week |
Hi @certainty3452 , I would like to ask you about the current state of both backstage plugins! Do you know something about the rest of maintainers? WE have some topics opened in both that would be great to have some answers! Thanks a lot! PD: I think your solution its working good for Azure DevOps Server! |
Hi @antoniobergas sorry for being silent last time, had lots of important topics besides of Backstage. |
@certainty3452 Thanks for the fast response! I'm glad to hear, thanks! As I mentioned in the RFC, let me know if you need some help 😄 I'm willing to make contributions |
Hi!
We are trying to use this backstage scaffolder actions, unfortunately, I had and error that make me think that somehow the implementation is not compatible with Azure DevOps Server
Is this possible to implement? Will be awesome to have as the pipelines actions works well with Azure DevOps Server and we want to be able to make PRs with the scaffolder 😊
Thanks!
The text was updated successfully, but these errors were encountered: