I am wanting to build a CI/CD pipeline Github app. What CI tool can I use to leverage to build this?
I want my application to handle the Github OAuth so as far as the user is concerned, they only connect to their Github but behind the scenes, I run Pipelines through Jenkins, CircleCI, AWS Codepipelines or something similar.
These all require the user authorise these Apps via their own OAuth but I'm hoping for a solution where I can pass an existing access token or clone a repo and send the CI tool the code to then execute the Pipeline on.
Does anybody know of any CI/CD tools that work via providing a Github access token or sending a clone of the code from Github to or would I have to look at rolling my own CI tool for something like this?
If I understood your question correct you just need to add Github personal api token to jenkins credentials as 'username and password'. You can use it in your pipelines.
Also I leave some useful links for you:
GitHub Permissions and API token Scopes for Jenkins
Github branch source plugin - which will automate job creation on jenkins side and will create webhooks on github side.
Youtube channel of Cloudbees - this video is about configuring Github branch source.
Related
Hello We made our own Gitlab installation on our server. I installed Readthedocs Local in the link below. In order to connect our accounts on gitlab with readthedocs, I was asked to make the following settings from the gitlab section in the readthedocs document.
https://readthedocs.org/
https://dev.readthedocs.io/en/latest/install.html
But interestingly, even though I set the settings on our own server gitlab.local, by default django goes to gitlab.com when I connect to gitlab via devthedocs.org. However, it should connect to gitlab.local on my server, how can I fix this problem?
On page 34 of this document here
https://readthedocs.org/projects/django-allauth/downloads/pdf/latest/
"The GitLab provider works by default with https://gitlab.com. It allows you to connect to your private GitLab
server and use GitLab as an OAuth2 authentication provider as described in GitLab docs at http://doc.gitlab.com/
ce/integration/oauth_provider.html"
I need your support in this matter.
Thank you very much.
Configure the applications on GitHub, Bitbucket, and GitLab. For each of these, the callback URI is http://devthedocs.org/accounts//login/callback/ where is one of github, gitlab, or bitbucket_oauth2. When setup, you will be given a “Client ID” (also called an “Application ID” or just “Key”) and a “Secret”.
Take the “Client ID” and “Secret” for each service and enter it in your local Django admin at: http://devthedocs.org/admin/socialaccount/socialapp/. Make sure to apply it to the “Site”.
The bounty expires in 2 days. Answers to this question are eligible for a +50 reputation bounty.
Jimmie Johansson wants to draw more attention to this question.
I have run through AWS Amplify's full-stack application tutorials multiple times to create a react native app, every time with the same result. The UI components created in AWS Amplify Studio are not being synced to my local codebase on pull.
The steps I followed on my most recent attempt:
Create Amplify app via AWS Amplify console
Configure UI Components/sync with Figma
Using the "Local Setup Instructions" link at the top right of Amplify studio, performed an amplify pull
The amplify pull always succeeds but never pulls UI components. If I set up a backend data or auth, I will see those synced properly, but I never see this (screenshot from a youtube vid):
And no ui-components folder is created in my source code. I'm at a loss, I've watched videos and followed tutorials from different people and nothing seems to work. The results are always the same and the rest of the functionality works as expected (graphql schema, auth, etc).
I found this question, which is similar, but outdated as from what I can tell Amplify should now support react native.
I have already deployed my angular app into AWS Amplify into production but I'm now running into Errors and I wish to see the build commands again and edit it if necessary but I couldn't find a way
I'm Expecting some button that shows me the same build methods so i can know what I did and what I should edit
I am using Antora to generate a static site for our documentation. I have followed their guidance for private repository authentication but are being unsuccessful. It seems that they only support HTTPS Basic Auth for GIT over HTTPS. I have tried generating and using an Application Specific Password, GIT Cookie, OAuth token all without success. Do you have any guidance on how to provide authentication?
At the moment Cloud Source Repositories doesn't support this kind of user/password pair authentication. Here is a similar issue for eclipse.
The only supported ways to authenticate at the moment are described in the Public Documentation
If I understood your requirement correctly, you want to connect to GCP source code repository externally to push code. If so you need to use service account with source code repository access rights. Choose appropriate roles using below URL:
https://cloud.google.com/source-repositories/docs/reference/rest
Refer below mentioned URL for connecting to source code repository once you are authenticated and do git operations.
https://cloud.google.com/source-repositories/docs/authentication
Please let me know if this is what you are looking for.
Hope this helps.
I configured a parse server on my AWS elastic beanstalk using this guid I've tested it and it all works fine
Now I can't find a way to deploy parse dashboard on my server.
I did deployed parse dashboard on my local host and connected it to the application on server, But this way I cannot manage (Add and remove) my apps.
Another problem is that parse dashboard missing cloud code on default, I found this on git, but I cant understand where do I add the requested endpoints, is it something like adding app.use('/scripts', express.static(path.join(__dirname, '/scripts'))); on the index.js file?
in order to deploy parse-dashboard to your EC2 you need to follow the Deploying Parse Dashboard section in parse-dashboard github page
parse-dashbard github page
Please make sure that when you deploy parse-dashboard you are using https and also basic authentication (it is also part of the guide)
Now regarding the cloud code: the ability to deploy cloud code via parse CLI and to view the nodejs code in parse dashboard are not available in parse-server but those are parse.com features. Cloud code in parse-server is handled by modifying the main.js file which exist under the cloud folder and deployment should be done manually by you but the big advantage in parse-server cloud code is that you can use any NodeJS module that you want from there and you are not restricted to the modules that were used by parse.com .
Another point about the dashboard. What you can do is to create an express application and then add parse-server and parse-dashboard as a middleware to your express application and deploy the whole application to AWS and then you can enjoy both parse-server (that will be available under the /parse path, unless you changed it to something else) and parse dashboard that will be available under the /dashboard path
Enjoy :)