Week 12 Class 33 Mon Nov 09 Posted: Nov 09

Class session:

  1. Screencast: Jenkins Introduction
  2. Screencast: Jenkins Setup

    On Sunday, I was setting up so that ports, such as 8080, were open on the class server. That way, you could run your Jenkins in a container on the class server and get access to it via a web browser. To do so, I have to manage ports. There are many ways to manage ports, but I chose ufw . When I set it up, it warned me about ssh sessions, but I did not think about it.

    So I enabled ufw to manage ports. By default, ufw blocks all ports. I enabled port 8080 and was able to see in my local browser Jenkins running in a container on the class server.

    Later that night, watching some TV, I noticed the Discord messages about the class server being down. I quickly realized what I had done. I had blocked the SSH port. Luckily, I had an open ssh session to the class server as root and was able to open it back up quickly.

    When you will do something that could affect SSH, they always say to have an open SSH session as root running. I know that Linode has another way into the machine (that bypasses the restrictions), but that would take a lot more time.

  3. Exercises 77 & 78: Jenkins Setup

    Get Jenkins running in a container and add a project from a GitHub URL. Jenkins can be in a container on your local machine, or you can use the class server (see notes on this below).

    In the screencast, I forgot to run the command with a named volume, so be sure to do so:

    Then show the following:

    Upload to Exercises 77 & 78: Jenkins Setup

    To run Jenkins in docker on the class server, you can find an individual port on the Brightspace course page. In the following, replace 8090 with your individual port:

    port
    volume
    URL

Screencast Folder: Class 33 Mon Nov 09

Exercise Due Date: 4 pm on Tuesday, Nov 10

Reminders: