Month: August 2017

Jenkins on Oracle BMCS

Last time, I posted the installation of GitLab. So, we have the Git…. what’s next?

A lot of people suggest CI – continuous integration. Thus, I’m going to talk about Jenkins in this post.

ASSUMPTION / PREREQUISITE:

  • we have a BMCS subscription
  • we already create a Linux VM or BM, have the VCN and Internet Gateway setup

We can put Jenkins in the same VM/BM as GitLab, or we can use another VM to run Jenkins.

Steps

  1. Similar to GitLab, the first step here is to get the Jenkins installation binary. We can navigate to Oracle Cloud Marketplace
    https://cloudmarketplace.oracle.com/marketplace/en_US/listing/16132843
    for details
    Screen Shot 2017-08-02 at 9.43.18 AM
  2. Just click the [Get App>] button and follow the instruction. It will guide us throughout the Jenkins installation process.
  3. Actually, what we need to do is to ssh to the VM/BM to download and install Jenkins. In the VM/BM use wget to download Jenkins.
    Screen Shot 2017-08-02 at 10.43.51 AM
  4. The download will take a while. wait for the download to complete. Then change the file permission to so that we can run the installer.
    Screen Shot 2017-08-02 at 10.43.32 AM
  5. In our example, we will install Jenkins in the same VM/BM as GitLab. We will use non-privilliged port to run Jenkins and run it with oracle user.
    Screen Shot 2017-08-02 at 10.45.02 AM
  6. The installer will install Gradle along with Jenkins.
    – Answer [Y] and press [Enter] when it ask for Gradle.
    – Answer [Y] and press [Enter] when it ask you to confirm.
    Screen Shot 2017-08-02 at 10.45.57 AM
  7. Next, the installer will prompt you for installation folder. Enter your desired folder. In our example, we will put it under /u01
    Screen Shot 2017-08-02 at 10.46.53 AM
  8. Enter your desired Jenkins SUPER ADMINISTRATION username and password
    Screen Shot 2017-08-02 at 10.47.56 AM
  9. The installer will then ask you for Apache and Tomcat port to be used for Jenkins. You can just keep the default values.
    Screen Shot 2017-08-02 at 10.48.40 AM
  10. Enter [Y] for the last confirmation and wait for the installation to complete.
    Screen Shot 2017-08-02 at 10.48.55 AM
  11. Jenkins should starts automatically after the installation.

How to start / stop / restart Jenkins

Just navigate to the target folder and use the ctlcscript, e.g.

[oracle@kmean jenkins-2.60.2-0]$ ./ctlscripts.sh start

 

or

[oracle@kmean jenkins-2.60.2-0]$ ./ctlscripts.sh stop

 

Screen Shot 2017-08-02 at 10.53.46 AM

How to access / navigate / login to Jenkins

It is simple, just use a browser and go to
http://your-vm-bm-ip-fqdn:apache-port/
e.g. http://jenkins.mydomain.com:8080/

Screen Shot 2017-08-02 at 10.56.41 AM

Click the [Access Jenkins] link and login with the username/password we’ve entered during installation.

Setting up GitLab in Oracle BMCS

Not sure if you heard something like this 🙂

  • Github is good but I want my own private repo.
  • Well I know you have DevCS, but I want something I can have full control…

Today, I’m going to talk about Bring Your Own Git – I’m going to use GitLab CE as my example.

Assumption / Prerequisite:

  • we have a BMCS subscription
  • we already created a Linux VM or BM, have the VCN and Internet Gateway setup

Steps

  1. The first step is to get the GitLab CE, we can navigate to Oracle Cloud Marketplace
    https://cloudmarketplace.oracle.com/marketplace/en_US/listing/16076589
    for details
    Screen Shot 2017-08-01 at 8.41.35 AM
  2. Just click the [Get App>] button and follow the instructions. It will guide us how to download and install GitLab CE for Oracle BMCS.
  3. Actually, what we need is to ssh to the VM/BM to download and install GitLab. In the VM/BM, use wget to download GitLab 
      wget -O gitlab-linux-installer.run \
    https://bitnami.com/stack/gitlab/download_latest/linux-x64

    Screen Shot 2017-08-01 at 10.06.06 AM

  4. The download will take a while, wait for the download to complete
    Screen Shot 2017-08-01 at 10.11.52 AM
  5. Change the file permission so that we can run the installer. Then, we can run the installer. If we want to have GitLab running on privileged port, i.e. 80/443, we will need to run the installer as root (or sudo).
    Screen Shot 2017-08-01 at 10.12.27 AM
  6. The installer will ask us to confirm the installation. Simply answer Y and press enter.
    Screen Shot 2017-08-01 at 10.13.04 AM
  7. Next, the install will ask us to setup the super admin account password for GitLab. Enter the desired password and press enter. Of course, we will need to enter the desired password the second time as confirmation. After that, we will be prompted to continue again – answer Y and press enter at this point.
    Screen Shot 2017-08-01 at 10.14.45 AM
  8. Installation will take a while. Just wait for the completion.
    Screen Shot 2017-08-01 at 10.15.02 AM
  9.  Once we see installation complete, we are ready to rock and roll.
    Screen Shot 2017-08-01 at 10.17.45 AM

How to start / stop the GitLab stack?

To start GitLab, use the command

[oracle@kmean ~]$ sudo /opt/bitnami/ctlscript.sh start

To stop GitLab, use the command

[oracle@kmean ~]$ sudo /opt/bitnami/ctlscript.sh stop

To check the status, use the command
Screen Shot 2017-08-01 at 3.36.39 PM

How to configure / re-configure GitLab?

We will need to edit the config file(s) – we will cover this topic later. BTW, you probably NEED to do reconfigure BEFORE the first run 🙂 just use the command

[root@kmean ~]# gitlab-ctl reconfigure

or sudo gitlab-ctl reconfigure command if you are not running as root user.
Screen Shot 2017-08-01 at 11.59.59 AM
again, reconfigure might take a while
Screen Shot 2017-08-01 at 12.00.19 PM
also, the first time to do reconfigure, we will need to set the GitLab root password again.

How to access my new Git?

It is simple, just use the browse to navigate to the host. I’ll recommend you use SSL port 🙂 https://{your-vm-bm-ip-fqdn}/

Screen Shot 2017-08-01 at 3.47.01 PM

I will cover more about custom configurations, custom SSL/TLS cert, GitLab integration, DevOps in BMCS later 🙂 please stay tuned.