Skip to content

Conversation

7se7en72025
Copy link
Contributor

Add resource(s)
For resources:
Description
Added a curated set of free Jenkins and Puppet cheat sheets covering core concepts of continuous integration and deployment with Jenkins pipelines, infrastructure as code with Puppet manifests, configuration management, automation workflows, and security best practices in DevOps for 2025.

Why is this valuable (or not)?
Jenkins and Puppet remain foundational tools in DevOps automation, critical for building scalable, reliable software delivery and infrastructure management processes. These cheat sheets provide clear and accessible knowledge for beginners and seasoned DevOps engineers preparing for roles involving automation, pipeline creation, and configuration management. Including these resources will help users quickly grasp practical implementations and best practices for Jenkins pipelines and Puppet automation.

How do we know it's really free?
Selected resources come from reputable educational platforms, community blogs, and official documentation offering free PDF or online cheat sheets without paywalls.

For book lists, is it a book? For course lists, is it a course? etc.
These are cheat sheets and quick reference guides for Jenkins and Puppet.

Checklist:

Search for duplicates (confirmed no duplicates with Jenkins and Puppet cheat sheets)

Include author(s) and platform where appropriate (listed where available)

Put lists in alphabetical order, ensure correct spacing

Add needed indications (PDF, access notes)

Use an informative name for this pull request (e.g., "Add Jenkins and Puppet Cheat Sheets covering CI/CD pipelines, configuration, and automation best practices")

Follow-up
Check GitHub Actions status after creating the PR and fix any warnings/errors

This preserves the original PR organization, checklist items, and just replaces blockchain-specific content with Jenkins and Puppet-focused resources, consistent with their roles as DevOps automation tools. This text can directly replace the original for a similar scope in the DevOps domain focused on Jenkins and Puppet cheat sheets.

added puppet, Jenkins cheatsheets
@rdhyee
Copy link
Contributor

rdhyee commented Oct 19, 2025

Hi @7se7en72025! This PR has the same naming issues as your Kotlin PR (#12622).

❌ Problems:

1. Don't modify existing entries:

-* [Jenkins Cheat Sheet](...)  ← Working entry
+* [Jenkins Cheat Sheet a](...) ← You renamed it!

2. Generic letter suffixes not acceptable:

  • "Jenkins Cheat Sheet a/b/c"
  • "Puppet Cheat Sheet a/b/c"

✅ One good example in your PR:

* [Puppet Cheat Sheet Module Included](...)

This is descriptive! Do this for all entries.

What to fix:

  1. Don't rename existing entries - revert "a" suffixes back to original
  2. Use descriptive titles for all new entries (like you did with "Module Included")
  3. Visit each cheatsheet and use its actual title or create meaningful descriptions

Please review the CONTRIBUTING.md guidelines about entry titles. Thanks! 🎃

@rdhyee rdhyee added the waiting for changes PR has been reviewed and changes/suggestions requested label Oct 19, 2025
@rdhyee
Copy link
Contributor

rdhyee commented Oct 19, 2025

Hi @7se7en72025! I need to apologize - I gave you incorrect guidance in my earlier comment.

My mistake:

I told you to "use descriptive titles" and "create meaningful descriptions" - that was wrong. I should have told you to use the actual titles from the resources themselves.

The correct approach:

According to CONTRIBUTING.md:

We try to take titles from the resources themselves; contributors are admonished not to invent titles or use them editorially if this can be avoided.

What to do:

  1. Visit each cheatsheet URL
  2. Find the actual title on the page (usually at the top, in the <title> tag, or as the main heading)
  3. Use that exact title, preserving the capitalization from the source

For example, instead of inventing "Jenkins Cheat Sheet For Beginners", look at what the page actually calls itself and use that title.

Also fix:

Typo: "Begninners" → "Beginners" (though you should use the actual title from the resource anyway)

Sorry for the confusion in my earlier review! The CONTRIBUTING guidelines are clear - use actual titles, don't invent them. Thanks for your patience!

@7se7en72025
Copy link
Contributor Author

@rdhyee did as said before , in all PRS

@rdhyee
Copy link
Contributor

rdhyee commented Oct 19, 2025

Hi @7se7en72025! Thanks for the update.

However, I still see some issues:

1. Typo still present:

* [Jenkins Cheat Sheet For Begninners](...) ← "Begninners" should be "Beginners"

2. Need to verify these are actual titles:

Please confirm these are the exact titles as they appear on the resource pages, not titles you created:

Jenkins:

  • "Jenkins Cheat Sheet For Begninners" (or "Beginners" after fixing typo)
  • "Jenkins Cheat Sheet Guide to Jenkins"

Puppet:

  • "Puppet Cheatsheet" (CSHero)
  • "Puppet CheatSheet" (DataDisk) - Note: inconsistent capitalization with above
  • "Puppet CheatSheet" (Intellipaat)
  • "Puppet CheatSheet" (Pahul)

If these aren't the actual titles from the pages, please visit each URL and use the exact title you see on the page itself.

Thanks for your patience!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting for changes PR has been reviewed and changes/suggestions requested

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants