Linked Projects in JENKINS:

Lab:

> Continue from Previous Lab

• Go to Google Chrome → localhost:8080 → Login to Jenkins
• Concept of “Upstream Linked Project”
  • Go to “New Item” & name the Job “JobA” → Click “OK”
  • Go to Build section & enter the command echo “Hello” → Click “Save”
  • Go to Dashboard & Click on the “JobA” → Click on “Configure” Option → Scroll Down & Go to “Post-build Actions” → Click on “Add Post-build Action” → Select the “Build other project” → Enter any previously created Project name → Select “Trigger only if build is stable” → Click “Save”
  • Go back to Dashboard → Click on the “JobA” → Click on “Build Now”
  • You can check in the Build Queue that after JobA build is done, then the next job which is add in the Post-build Action will start building, that’s the example of “Upstream Linked Project”
• Concept of “Downstream Linked Project”
  • Go to “New Item” & name the Job “JobB” → Click “OK”
  • Go to Build section & Copy the job from “Mymavenproject” → Click “Save”
  • Go to Dashboard & Click on the “Mymavenproject” → Click on “Configure” Option → Go to “Build Triggers” Section → Select “Build after other projects are built” Option → Enter recently created Project name “JobB” → Select “Trigger only if build is stable” Option → Click “Save”
  • Go back to Dashboard → Click on the “JobB” → Click on “Build Now”
  • You can check in the Build Queue that after JobB build is done, then “Mymavenproject” will start building, that’s the example of “Downstream Linked Project”

Views in JENKINS:

In Jenkins, "Views" are used to organize and manage jobs (projects) within the Jenkins dashboard. They provide a way to categorize and group related jobs together, making it easier to navigate and manage them, especially in environments with a large number of jobs.

Purpose of Views in Jenkins:

1. Organization: Views help in organizing jobs into logical groups. For instance, you can create separate views for different teams, projects, or environments (e.g., development, testing, production).
2. Simplification: By grouping related jobs, views simplify the Jenkins interface, making it easier for users to find and manage the jobs relevant to their role or current task.
3. Access Control: Views can be configured with specific permissions, allowing administrators to control which users or teams can access certain views. This enhances security and ensures that users only see the jobs relevant to them.
4. Monitoring and Reporting: Views can be used to monitor the status of groups of jobs. You can set up views to display only the jobs you are interested in tracking, making it easier to keep an eye on the progress and health of specific projects or environments.

How to Create a View in Jenkins:

1. Navigate to the Dashboard: Go to the Jenkins dashboard.