(PDOC-6) Allow for different puppet gem versions#9
Merged
1 commit merged intopuppetlabs:masterfrom Sep 25, 2014
Merged
Conversation
In order to make the Gemfile compatible with the puppet strings Jenkins job (which tests against multiple versions of puppet), update the Gemfile to allow for for the Jenkins job to specify which version of puppet it is testing against.
ghost
pushed a commit
that referenced
this pull request
Sep 25, 2014
…-for-jenkins-jobs (PDOC-6) Allow for different puppet gem versions
ghost
merged commit
eputnam
added a commit
to eputnam/puppet-strings
that referenced
this pull request
Mar 19, 2018
# This is the 1st commit message: (PDOC-206) starting work for tasks # This is the commit message puppetlabs#2: (PDOC-206) parser, handler, statement, code_object Adds a parser for json, a task handler, a task statement and a task code_object. the parser uses JSON.parse instead of an AST and some finagling has to be done in the statement and the handler to get YARD to be ok with this. When YARD is registering the task code_object, it expects it to have things like a docstring and comments and so on, but it doesn't have any of those things so they are faked. # This is the commit message puppetlabs#3: (PDOC-206) refactor handler/parser/co interaction and json_spec passes to_hash does not need to behave like it does in other code objects. instead, just take the raw json and iterate over it. # This is the commit message puppetlabs#4: (PDOC-206) things work now # This is the commit message puppetlabs#5: (PDOC-206) small refactor/improvement of input section # This is the commit message puppetlabs#6: moved some things around, added some template logic # This is the commit message puppetlabs#7: (PDOC-206) adds more tests # This is the commit message puppetlabs#8: (PDOC-206) remodel to_hash and start markdown Revamped the to_hash method for task code objects to look more like other objects. The markdown engine cares a lot about this format. # This is the commit message puppetlabs#9: (PDOC-206) update json test, task template
smortex
pushed a commit
to smortex/puppet-strings
that referenced
this pull request
Aug 10, 2025
…ons/actions/download-artifact-5 Bump actions/download-artifact from 4 to 5
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In order to make the Gemfile compatible with the puppet strings
Jenkins job (which tests against multiple versions of puppet), update
the Gemfile to allow for for the Jenkins job to specify which version
of puppet it is testing against.