We have 7 repos in our Github account and they are currently deployed using Github actions. I wanna confirm if we can convert the account into an organisation and this won't affect my services and website running right now via Github action runners.
Related
We have a hosted GitHub Enterprise (GHE) account which needs to integrate with Azure Pipelines. I have installed the Azure Pipelines app from the GitHub Marketplace for our GHE account. The installation of the Azure Pipelines app asks to select an Azure DevOps project and GHE repo to setup the integration. This results in one pipeline being connected to a GHE repo.
But my question is, how to we setup other pipelines within Azure DevOps to use repos in GHE?
Nowhere in the Azure Pipelines interface can I find an option to select a GHE repo. Only public GitHub and GitHub Enterprise (on-prem) server repos. It seems that only the Azure Pipelines app setup wizard allows you to configure a pipeline with a GHE.
I can't imagine that we would have to initiate the setup wizard of the Azure Pipelines app every time we want to connect a pipeline to a GHE repo. That wouldn't even be possible, because most coworkers won't have the permissions to do that. What am I missing?
Remark: I realize that we could create a service connection in Azure DevOps using on a Personal Access Token or username+password. But that's tied to someone's personal account. If that person would leave, the connection is broken. Unless you create a service/dummy account, which doesn't seem very elegant.
If you use GitHub Enterprise, then you can integrate with Azure AD. Then based on group membership you can assign access to repositories with the help of Github Teams.
Then based on those permissions the repos to which somebody has access will be visible during the setup of the Azure DevOps pipeline.
Some useful resources:
https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/github-tutorial
https://github.blog/2019-09-24-azure-active-directory-team-synchronization-now-available-with-enterprise-cloud/
https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams
https://enterprise.github.com/support
I found out the cause of the issue.
First of all, when you install the Azure Pipelines app from the GitHub marketplace, you first need to make sure that you select your GitHub organisation and not your personal account.
Secondly, during the installation you are taken to Azure DevOps to setup your project. Two different authorization pages will be shown; "Azure Pipelines by Microsoft would like to [...]" and the page for OAuth authorization. As can be seen in below image, there is a small grant button that's easily overlooked. You need to press that button before you press the large green that says "Authorize AzurePipelines"
I am now able to select my GitHub Enterprise repositories when I create a new pipeline in Azure DevOps. I simply choose GitHub as the source where my repository lives.
Overview:
I'm using GitHub Pages feature to host documentation. I'm working on a CI/CD process to automate the build so that when the source for the documentation is updated it automatically rebuilds the content and deploys to GitHub Pages.
Details:
So far, using AWS CodeBuild, I've implemented the following:
Pulls down source from GitHub Repo
Uses MkDocs to build and deploy to the special gh-pages branch using the "mkdocs gh-deploy" command.
This is done with command lines in the CodeBuild Buildspec. The reason I'm using commands is that I want to use GitHub Deploy Keys opposed to creating user account (used as a machine account) that my team would need to manage.
I have it all working except what triggers the build. If the process was using a user account to authenticate then I can use AWS CodePipeline which creates a Webhook within the GitHub repo, and then notifications are sent via the Webhook to say that the master branch was updated, which would trigger a new build.
I'd like to implement a similar process but using the GitHub repo's Deploy Key. Any suggestions?
I have a GitLab running for my Github Organization members to log in. I have configured GitLab to use GitHub to login. I know that I can set GitLab to block every new user, so that I can manually unblock them as I want.
GitHub announced last year that you can now select new scopes such as
read:org
which allows my GitLab to get the user's organizations. Is it possible to configure GitLab to create new users only for members of my organization? If not, I don't want to fork the code and implement it myself, but a plug-in solution would also do the trick. Any advice?
I want to use github to deploy my webapp on Azure. I setup github on Azure as my deployment source. But since I have a custom domain instead of using the free azurewebsits.net, I think I am having issues seeing the website from github. The webhook on github shows azurewebsites.net.... same on azure. I can edit the webhook on github but can't on Azure. What is the best way to integrate github with azure with a custom domain?
You don't need to edit the webhook on github, let it stick with the default sitename.azurewebsites.net.
When you setup a custom domain name, your default domain name (sitename.azurewebsites.net) still keeps working. Github will use that to deploy to your site
We have a Jenkins setup on a server, and are building projects from multiple Github enterprise servers (currently 3 Github enterprise servers). I wanted to use the git pull request builder plugin. However, this plugin only lets us configure one Github account.
Is there a method to include other Github server accounts as well?
The GitHub pull-request builder plugin does mention:
The first fifty characters in the Description are used to differentiate credentials per job, so again use something semi-descriptive
So as long as your project are built in separate job, you should be able to select in their respective job configuration different credentials.