Private intranet-level Nuget feed: Windows Integrated Security customization - nuget

I'm considering setting up Intranet-level Nuget feed(bunch of teams in my company are supposed to use it).
I've looked briefly through some tutorials + appropriate chapters in Pro Nuget book, however I still do have some question left so far:
How to make windows integrated security working on private feed smoothly and customize access rights for private Nuget feed(for instance, grant everyone to get packages but grant pushing only to several domain users/groups);
How to allow developers to push packages to private feed without having api key?
How to save developers from making such silly mistake as pushing package to public feed? Is that enough to not configure api key for public feed as default?
Has anyone faced with one of these cases?

I did not try this so far, but following those instructions : http://docs.nuget.org/docs/creating-packages/hosting-your-own-nuget-feeds
I would just create a network share on the server hosting the feed, with write access to specific AD group of developers.
This way your repository is public, and only some persons can add packages to it.
Even after, if you have a continuous integration server, you could allow access to the file share (or API key) only to the account building packages. This way packages are published automatically after having passed automated tests.

Related

Manage personal and organizational repos in one project board on Github

to harmonize all the task management, review requests and so I would like to use Github Projects
As I am working on both, personal repos and those of the organization I am working for, I would like to assign all issues all over my Github Account to one single project board.
If I am using a personal project board, I can only assign PRs/issues from personal repos and there is the same "scoping" for the organization of course.
The only way would be to manually copy/paste the URL from either the personal issue to the organizational project board or vice versa.
Does anybody have an idea if this is even possible? I could not for the life of me figure out how to make it work.
Thanks everybody for helping out here.

Connecting to Project Online from Azure DevOps Extension

I have created a Azure DevOps hub extension, it retrieves work items and the goal is to then move some of the work item notes over to Project Online Timesheet Notes. But I can't figure out how I can authenticate my calls from the Azure DevOps Extension to be able to call Project Online.
It seems like the
.getAccessToken(...)
call in the sdk gets an access token encrypted with my extension data, but I need some way I can call into Project instead. I looked into MSAL and it seemed like a good option except I then need to register my extension as a SPA and I can't confirm where it will live.
I'm trying to avoid having the user provide user/pass, anyone know another way?
After speaking with Microsoft learned that this is not supported by Project Online. I was specifically trying to connect to the timesheet for Project Online and was told that it is not supported by the code.

how to allow 3rd party to create repo (repo transfer) in our Org without let them see our private repo?

We have hired a 3rd party to work on a project, we started by not creating any Repo on our Github, but they started with their Repo. So now it's time to transfer the repo. However, in order to transfer the repo, the developer is asking permission to create a Repo in our Org... but as far as I know, I can only invite him first as a collaborator, a member, before he can create any private repo in our Org... that means he can see our other repo...
I couldn't find any good answer online, please help. Thanks!
Have you tried using Github's Organization features? You can create an organization with your team members in it, and control who has access to what.
Here's a Github page that explains a bit more about how it works.
Do not add them as a member to your Org! (this is the only option today from Github, nor owners...of course). If you do so, this will give your external developer access to all of your repos.
The only way I found you can safely invite an external user is to create a Repo first, then add them in that Repo. By doing that, they will be invited only to that repo, and have no access to the others.
This is my workaround. If you have a better solution, please do comment. I am curious how the "transfer" feature works.

Is the actual source code for GitHub on GitHub?

Is the code for the actual GitHub website/application hosted on GitHub?
Yes, GitHub is developed on GitHub, using a variety of repositories. Most of the code is private, but some tools are open source and in public repositories. This is not in any way a secret, and multiple talks have been given about the way GitHub builds GitHub and the way the company uses it, which is relatively nontraditional.
This allows employees to test new features in their everyday work to make sure that they're functional and of excellent quality before release, and to think of new useful functionality to add.

Uploading source code for specific requirement in github

I have heard that, product based companies will look for what we have done outside of projects and also looking for the github profile.
In the meantime, I have created an automation application which addresses the specific requirement (Timesheet) in our organization. So, I thought of uploading this one too.
I have also done the screen cast and uploaded it to YouTube for adding in the profile (Resume).
This exact tool is not useful for all the people , but useful for the people in our organization, in which they can edit/contribute more.
Now I am having the question like, can I upload this kind of the code to GitHub?
Thanks.
Yes, you can.
Code on GitHub does not have to be useful to other people. You can push code there even if it is only useful to you or people in your organization.
You could also use a private repository if you do not want other people to see the code.
See: https://github.com/pricing