Integrate Gitlab and TravisCi - ruby

Is there a way where I can integrate TravisCi with Giltab? or at least logging in TravisCi using username and password and not Github credentials?

No, as of right now, Travis-CI is strictly bound to GitHub. While there are certainly talks about lessening this requirement, it's still there for still some time to come.
As a workaround, you could push your stuff to GitHub and from there to Travis, using GitHub only as an intermediary.

Related

CI/CD in GitHub repositories

I want to create a simple CI/CD GitHub system for academic purposes and better understanding of the system. I want to know how can I check if a repository was updated or how can I call and API every time a commit is done. I thought about using GitHub Actions but I think is better if I could do this configurations in the system instead of going in each repository on GitHub.
GitHub Actions is the best way to get started with CI/CD, in my opinion. It's well integrated with GitHub, which most people are already familiar with, and it's plethora of tools are well documented in easy-to-follow tutorials on the GitHub website. If you don't have a very good reason not to use GitHub Actions, and are trying to learn, I would suggest you reconsider.
If you are hellbent on not using GitHub actions, where are you deploying the application? If Azure, use Azure's pipelines (it's the exact same syntax as github actions, btw.); if using AWS or GCP, use the respective CI/CD pipeline UIs offered by those platforms. If you're hosting/deploying on your own machine using something like GitLab, its syntax is very similar to GitHub Actions anyway, and GitLab has good documentation and tutorials as well.
So basically, your options are to use GitHub Actions, which is easy to pick up and highly recommended, or use the pipeline of whichever service you're using to deploy your application.

Are your git repositories accessible by others?

I am putting my code onto git-hub so it can be deployed by Heroku. Will anyone (other than me) be able to access and view the repository that I make? Thanks.
Check the PRICING menu in the home page.
Plans for all workflows
GitHub is free to use for public and open source projects. Work
together across unlimited private repositories with a paid plan.
Answer for your question is Yes, If you have a free GitHub account you can only create public repositories.
There are several ways you can solve your problem with out actually paying to GitHub.
You can use Heroku Git
You can use dropbox
In both of these ways you can have your code private

Sonatype Nexus 3 stuck on OnLine - Ready To Connect status for proxies

I have installed Nexus several times before, but Nexus 3 seems to be a bit different. Taking a basic installation running on Docker, after a few minutes Nexus reports the remote Central proxy as Online - Remote Available. However, I cannot find the perennial asset 'junit'.
I have a non-docker install which is my production install on a multihomed machine. This machine remains for ever stuck on Online - Ready to Connect status. I have tried urlpoke.jar from this machine and I have full communications to the Central repo.
I appreciate the deletion of dialogs and buttons was a design goal but its working against you. Nexus2 was much simpler in this regard and I suggest you resist dummyfication when attempting simplification. You are not apple, and apple fails horribly at this too, just see how people google basic operations on itunes, because iTunes really is a pathetic UI experience which only gets worse with each update.
Please help Sonatype OSS project, or is it time to move to Artifactory?
The "Online - Ready to Connect" just means that the repository is working, and it will connect as soon as you make a request into Nexus that triggers an outbound request to the proxy's remote. Try running a build against Nexus.
It turns out the issue was related to authentication. I had set LDAP as an authentication source and this was allowing me to log in and administer the UI, but not allowing me to access the proxies. Not sure why I did not resolve it.
The entire lot only worked again, without LDAP, when I reinstalled it and blew away my prior configuration.
Although I can now PULL assets from my proxied back-ends, I cannot search the backends.
Nexus 2 used to download or build an index from the backend proxied maven sites, and we used to be able to query our nexus 2 searching for any artifact in the backend proxied sites. For some reason, I don't have this working still. If this feature has been deprecated, Nexus 3 has gravely missed the mark and can no longer effectively be considered as a Maven Repository IMO.

Whats difference between heroku and github

What does it mean production in rails , whats the difference between using github and heroku at the same time . I used github for like a backup / how all of us gonna use heroku . Is it necessary ??
First I need to explain GIT
Git is a distributed version control and source code management (SCM) system with an emphasis on speed. Initially designed and developed by Linus Torvalds for Linux kernel development in 2005. Every Git working directory is a full-fledged repository with complete history and full version tracking capabilities, not dependent on network access or a central server.
GitHub is a web-based hosting service for software development projects that use the Git revision control system. The site provides social networking functionality such as feeds, followers and the social network graph to display how developers work on their versions of a repository.
Heroku (pronounced her-OH-koo) is a web host that uses the Git revision control system. When you push your code to Heroku using git it then builds your server just like you do when you use locate host but for everyone to see.
Heroku is a cloud application platform – a new way of building and deploying web apps. The service lets app developers spend their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
GitHub is a web-based hosting service for projects which uses Git version control system(VCS) It's a code repository where you can store code for better collaboration & contribution. Anybody can contribute to your open source code via cloning it & github will make a branch of code. You can also purchase $9/mth to create private repositories for private collaboration. You can deploy code with Git but you need your own server to host that code.
Visit https://github.com/about
heroku is a PaaS(Platform as a service) web apps hosting service where you can build & deploy web apps. Build great web apps, collaborate & deploy as well with heroku.
Visit https://www.heroku.com/about
Heroku comes with it's own server so you can purchase hosting plan & deploy you web apps easily. In case of Github you need to purchase a separate server to host your web apps.
Github is well known for contribution & collaboration & Heroku is for backend stack available for collaboration & deploying easily.

Heroku-like Amazon EC2

Is there anything that I can install on my EC2 instances that make AWS Heroku-like?
e.g:
heroku create app
git push
But for AWS.
Well, now there is! It's called AWS Elastic Beanstalk (still in beta, as of March 2013)
After running the initial setup, further deployments should be as simple as git aws.push
EDIT: Just a nice and broad overview of deployment possibilities at AWS, by Werner Vogels (AWS CTO):
There are few topics I need to touch on before I can answer your question thoroughly; so please, bear with me.
A bit of insight
With respects to your two examples, Heroku utilizes a number of different technologies in order to achieve the level of simplicity it provides as a service platform. One of these technologies include: Heroku's proprietary toolbelt, which offers a set of command-line tools —that allows developers to interface with their applications— and an interact with many of the tools Heroku provides —such as terminal access for a number of different languages. The toolbelt itself relies on two other technologies: Ruby and Git; which come prepackaged with the install.
In a nutshell
Now, when you create a Heroku app you are effectively creating a git repository on the celedon cedar runtime stack (by default); this repository is then added as a remote repo. This allows you to immediately run git push heroku master. There is a lot more happening behind the scenes: for instance, when you push, your commits get intercepted by a git pre-receive hook which runs your app through a slug compiler and prepackages it for distribution across the dyno manifold; yet, I digress. For more information on more advance topics, check-out: https://devcenter.heroku.com/; there is a wealth of information here to read.
The stack
Now, let me explain the cedar stack as this is mainly what your question concerns. The Celedon cedar is one of many; however, this is the current default (for many reasons). This polyglot runtime stack currently provides six web languages (at the time of writing,) running on Ubuntu (11.04 stable, I belive). All of these technologies are operating on top of the AWS EC2 computing environment.
So to finally answer your question: You will need to install a suitable operating system such like: Ubuntu; a set of languages such like: Ruby, Python, Node.js, etc; Git (for deployment) and the rest is up to you.
If you have fixed number of instances make sense instead of usage Elastic Beanstalk use custom git deployment, like described in the article: http://www.jeffhoefs.com/2012/09/setup-git-deploy-for-aws-ec2-ubuntu-instance/.
Main idea to setup GIT repository on EC2 instance. When you want to deploy something just push your changes to remote repository, installed on EC2 instance.
I think this approach have next benefits in comparison with Elastic Beanstalk:
You don't pay for S3 buckets for storing application versions;
You have full control on application deployment steps.

Resources