Open peter-poki opened 4 years ago
Hey, there -
It is in our long-term plans, but unlikely short term.
Would you be open to a short feedback call so that we could learn more about your use-case to better help with our priorities? If so, please feel free to reach out via email at ejones@cloudbees.com.
Hi there,
it was just a conveniance, because we used it as our source control as we have Azure subscriptions, but we moved to github to make it compatible.
But I understand that not many people probably use Azure Repos, or AWS CodeCommit, or...
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
not stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
/remove-lifecycle stale
Hey, there -
It is in our long-term plans, but unlikely short term.
Would you be open to a short feedback call so that we could learn more about your use-case to better help with our priorities? If so, please feel free to reach out via email at ejones@cloudbees.com.
Hi @ethangj,
Thank you for your response! Recently I'm joining a new company and we use Azure Repo, and our team plan to develop our next generation CI/CD with the help of Jenkins X.
I'd like to try to contribute, but I see there are
Do you think it's would be better to contribute to the upstream, and then our fork merge from upstream? I already left a message in the https://github.com/drone/go-scm/issues/53#issuecomment-906095080 , but I'm also wondering if Cloudbees have core contributors to help me get started with it.
Best regards, Jizu
@jizusun not sure if ur still interested to work on this, but if you are, then making a contribution to the jx go-scm fork is the right place to start.
Hello guys,
Do you support git repositories inside Azure Repos: https://azure.microsoft.com/en-us/services/devops/repos/
Or are there any plans to support it?