Question#1 – What is your programming Language

• Version of your Project?
• Make sure the language is configued in your Build Node Server.

Question#2 – Where is the source code for project?

• Branch Name,
• Access of your project?
• SCM tool is installed in Build Node Server

Question#3 – How Frequently you want this JOB to be triggered?

1. Manual Build Trigger:
   • Build can be triggered manually by users through the Jenkins web interface.
2. Scheduled Build Trigger:
   • You can schedule builds at specific times or on a recurring basis using the built-in “Build periodically” or “Build periodically with parameters” triggers in Jenkins.
3. SCM Polling:
   • Jenkins can monitor your version control system (e.g., Git, SVN) for changes and trigger a build automatically when new commits are detected.
4. Webhooks:
   • Integrate Jenkins with your version control system and configure webhooks to trigger builds whenever there is a push or other relevant events.
5. GitHub Hooks:
   • For GitHub repositories, Jenkins can be configured to receive GitHub Webhooks, triggering builds on push events, pull requests, or other GitHub events.
6. Email Notification Trigger:
   • You can configure Jenkins to trigger builds when specific email notifications are received. This is useful for integrating Jenkins with email-based systems.
7. API Trigger:
   • You can trigger builds programmatically using Jenkins’ REST API. This allows external applications to initiate builds when certain conditions are met.
8. Upstream/Downstream Projects:
   • Jenkins allows you to set up relationships between jobs, where one job triggers another when it completes. This is useful for defining complex build pipelines.
9. Parameterized Builds:
   • Jenkins supports parameterized builds, enabling you to pass parameters to jobs when triggering them. This is useful for customizing builds for different scenarios.
10. GitHub Pull Request (PR) Builds:
    • Jenkins can be set up to automatically trigger builds when new pull requests are opened, updated, or merged on GitHub.
11. External Tools and Plugins:
    • Jenkins has a vast ecosystem of plugins that can provide additional triggers. For example, plugins for various version control systems, chat tools, and issue trackers often offer custom triggers.
12. Other Event-Based Triggers:
    • Depending on your needs, you can explore other event-based triggers provided by Jenkins plugins. These may include triggers for specific systems or integrations.
13. Command-Line Trigger:
    • Jenkins can be triggered through the command line using tools like curl or scripts. This is useful for automation or integration with other systems.
14. Polling Specific URLs:
    • Jenkins can periodically poll specific URLs, and if the URL returns a specific response (e.g., success status), it can trigger a build.
15. External Build Triggers:
    • External systems or tools, such as CI/CD orchestration tools, can trigger Jenkins builds via API calls or integration mechanisms.

Question#4 – What is your Builders?

In Jenkins, builders are the build steps or tasks that execute within a job to build, compile, test, and package your code. Jenkins provides a variety of builders, and you can also use plugins to extend the available builder options. Here is a list of commonly used builders in Jenkins:

• Is it installed in Node Server?

1. Execute Shell:
   • This builder allows you to execute shell commands or scripts on Unix-based systems as part of your build process.
2. Execute Windows batch command:
   • Similar to the Execute Shell builder but for Windows-based systems. It allows you to run batch commands or scripts.
3. Ant:
   • This builder is used to build projects using Apache Ant, a Java-based build tool. It’s commonly used for Java projects.
4. Maven:
   • The Maven builder is used to build projects using Apache Maven, a widely-used build and dependency management tool primarily for Java projects.
5. Gradle:
   • For projects that use Gradle as their build tool, this builder allows you to execute Gradle build tasks.
6. Invoke Gradle script:
   • Similar to the Gradle builder but allows you to invoke custom Gradle scripts within your Jenkins job.
7. Batch File:
   • This builder executes a Windows batch script within your Jenkins job.
8. Python:
   • The Python builder allows you to run Python scripts as part of your build process.
9. NodeJS:
   • For JavaScript-based projects, you can use the NodeJS builder to execute Node.js scripts.
10. Invoke top-level Maven targets:
    • If you’re using Maven, this builder lets you invoke specific Maven targets within your Jenkins job.
11. AWS CodeBuild:
    • For AWS CodeBuild integration, this builder allows you to specify CodeBuild projects to run as part of your Jenkins job.
12. Docker Build and Publish:
    • This builder is used to build and publish Docker containers. It’s useful for containerized applications.
13. Custom Script:
    • You can use this builder to run a custom script of your choice, allowing for flexibility in your build process.
14. Jenkins Build Step:
    • This builder lets you trigger another Jenkins job as a build step within your current job, creating build pipelines.
15. Git Publisher:
    • This builder publishes changes to a Git repository, which can be useful for pushing build artifacts or updating version information.
16. Pipeline Script:
    • If you’re using Jenkins Pipelines, you can define your entire build process within a Pipeline script.
17. Conditional Build Step:
    • This builder allows you to add conditional logic to your build steps, executing certain steps based on specified conditions.
18. Jenkinsfile:
    • When using Jenkins Declarative or Scripted Pipelines, you can define the entire build process within a Jenkinsfile as a builder.

Question# 5 – Whom you want to deliver Feedback of Job

here are a few different options for feedback and status in Jenkins jobs. Here are a few of the most common ones:

• Build status: This is the most basic type of feedback. It indicates whether the build was successful or not.
• Build logs: This provides more detailed information about the build, such as the commands that were executed and the output of those commands.
• Test results: This provides information about the results of unit tests and other types of tests that were run as part of the build.
• Static analysis results: This provides information about the results of static analysis tools, such as linters and code scanners.
• Deployment status: This indicates whether the build was successfully deployed to production.
• Chat notifications: This allows you to receive notifications about the build status in a chat application, such as Slack or Discord.
• Email notifications: This allows you to receive notifications about the build status in an email.
• Dashboard widgets: This allows you to display build status and other information on a dashboard.

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I am working at Cotocus. I blog tech insights at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at I reviewed , and SEO strategies at Wizbrand. 

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at PINTEREST
Rajesh Kumar at QUORA
Rajesh Kumar at WIZBRAND