Setting up GitHub Webhooks in Jenkins


One of the most important aspects of a good Continuous Integration (CI) process is quick feedback whenever there is a change. This means that it is important to execute builds as soon as possible after a code change is pushed to source control. One of the best ways to do this with GitHub and Jenkins is to use webhooks to have GitHub notify Jenkins when there is a change so that Jenkins can automatically start the build.

  1. Create Personal Access token in GitHub by going to | Profile | Settings | Developers Settings

    GitHubDeveloperSettings

  2. Personal access tokens

    Need an API token for scripts or testing? Generate a personal access token for quick access to the GitHub API.

    Personal access tokens function like ordinary OAuth access tokens. They can be used instead of a password for Git over HTTPS, or can be used to authenticate to the API over Basic Authentication.

    My personal access token is called “Jenkins” and select Admin:repo_hook and click Generate Token

    admin_repo_hook_access_token

  3. Copy your personal access token

    personal_access_token

  4. Now go to Jenkins

    Manage Jenkins | Configure System and add GitHub Server

    Add-GitHub-Server

  5. Add Jenkins to GitHub Server

    Add-Jenkins-To-GitHub-Server

  6. For Kind Select Secret Text and copy and past secret key from personal access token (Step 3). Create a name for ID and Description and ADD

    Jenkins_Credentials_Secret_Key

  7. Click drop down in credentials and select new credentials which we just created. In my case I called it as “GitHubKey”  Make sure Manage Hook SELECTED

    Manage_WebHooks

  8. Now go back to your project and the GitHub URL in Source Code Management and under Build Triggers select GitHub Hook Triggers GitSCM poling

    source_code_management_git_repositories

  9. To verify, go to your GitHub Repository | Settings | WebHooks

    webhooks-in-Github

How to install and run the Gradle Wrapper


To install and run the Gradle Wrapper

mkdir my-project
cd my-project
gradle wrapper
./gradlew build

Install-Gradel-Wrapper

[root@aryan-34252e5f2 ~]# mkdir my-project
[root@aryan-34252e5f2 ~]# cd my-project
[root@aryan-34252e5f2 my-project]# gradle wrapper
Starting a Gradle Daemon (subsequent builds will be faster)

BUILD SUCCESSFUL in 6s
1 actionable task: 1 executed
[root@aryan-34252e5f2 my-project]# ./gradlew build
Downloading https://services.gradle.org/distributions/gradle-4.7-bin.zip
……………………………………………………………..

> Task :buildEnvironment

————————————————————
Root project
————————————————————

classpath
No dependencies

A web-based, searchable dependency report is available by adding the –scan option.

BUILD SUCCESSFUL in 6s
1 actionable task: 1 executed
[root@aryan-34252e5f2 my-project]#

 

How to install Gradle


To install Gradle in CentOS

get -O ~/gradle-4.7-bin.zip https://services.gradle.org/distributions/gradle-4.7-bin.zip
sudo yum -y install unzip java-1.8.0-openjdk
sudo mkdir /opt/gradle
sudo unzip -d /opt/gradle/ ~/gradle-4.7-bin.zip
sudo vi /etc/profile.d/gradle.sh

Open Vi Editor and add this line

export PATH=$PATH:/opt/gradle/gradle-4.7/bin

Then set permissions on gradle.sh:

do chmod 755 /etc/profile.d/gradle.sh

log out of the server and logging back in:

gradle --version

how-to-install-gradle

How to “Unlock Jenkins”?


Unlock Jenkins

To ensure Jenkins is securely set up by the administrator, a password has been written to the log (not sure where to find it?) and this file on the server:

/var/lib/jenkins/secrets/initialAdminPassword

Please copy the password from either location and paste it below.

how-to-unlock-jenkins

To Unlock Jenkins, you need to go to following directory
/var/lib/jenkins/secrets/initialAdminPassword

To view the Jenkins password use following commands in Linux
“sudo cat /var/lib/jenkins/secrets/initialAdminPassword”

print-out-jenkins-unlock-password