Now all that remains for Github to do is to add a build platform as alternative to Jenkins and a deployment framework. Source code, build platform, artifact storage and deployment - all co-located.
GitHub Package Registry
201–210 of 389 posts
Re: GitHub Package Registry
#202Where is for python
Re: GitHub Package Registry
#203I did not see packaging for python
Re: GitHub Package Registry
#204funny thing for js or well maybe npm you could already consume packages from github by just sayaing ```npm i -S @githubusername/bozopackage
Re: GitHub Package Registry
#205Earlier quoted context omitted.
The NPM support is basically not more than a proof of concept. It cannot be used for anything production-like. https://twitter.com/eatingfoodbrb/status/1101461965036244993
GitLab Product Manager here Thanks for your feedback on NPM registry support in GitLab. We release minimal viable change (MVC) and then iterate on our product functionality. Here are some of the issues we have related to NPM support: https://gitlab.com/gitlab-org/gitlab-ee/issues/10024 https://gitlab.com/gitlab-org/gitlab-ee/issues/10050 https://gitlab.com/gitlab-org/gitlab-ee/issues/9164 https://gitlab.com/gitlab-or…
Hey. You can probably find my name in each of the zendesk comments/issues. Thiago posted a few for me. I have been very vocal about what I feel needs to be done through my sales leads (my client has a EEU subscription).
Re: GitHub Package Registry
#206You have to authenticate to github just to install a public package with maven? What a joke.
Re: GitHub Package Registry
#207Now all that remains for Github to do is to add a build platform as alternative to Jenkins and a deployment framework. Source code, build platform, artifact storage and deployment - all co-located.
Azure Pipelines?
https://azure.microsoft.com/en-us/services/devops/pipelines/
Re: GitHub Package Registry
#208So we are in the “extend” phase of Microsoft’s standard strategy? Can’t see how Microsoft replacing Maven is a good thing.
Re: GitHub Package Registry
#209Earlier quoted context omitted.
> MS's core competency has always been developers. As a developer who still has to work very hard to forgive MS for all the pain IE6 put me through a decade ago, this grates on my ears, even though I understand that it might be true in the abstract. Classically, MS has been good to developers who agree to be chained to their platform, but has made life extremely difficult for developers who want or need to be platfor…
A lot has happened since IE6.. I think it might be time to move on. Eg their main focus for .net Core has been multi platform - ie the last 3-4 years! Visual Studio Code. And on browsers they are building what will probably be a better Chromium than Google's Chrome, in the new Edge.
[deleted]