Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-545

Beaker infrastructure for testing 3.x->4.x compatibility

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Normal
    • Resolution: Done
    • None
    • SERVER 2.1.0
    • None
    • None

    Description

      This ticket covers everything necessary to write/run acceptance tests with a 3.x agent against a 4.x master/server (not including the tests themselves though).

      Since individual tests don't set up the environment (and thus can't contain everything necessary for testing 3.x->4.x), we're thinking this effort could result in a whole new Jenkins job.

      We'll probably need to involve someone from QE to determine the best way for doing this.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. SERVER-586 Validate 2.1.x pipeline is done done and in production

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Task - A task that needs to be done. SERVER-627 Work with QE / RE to get the 2.1.x branch ready for 2.1.0 release

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          supports

          Task - A task that needs to be done. SERVER-526 Initial scoping / investigation for rewriting Pup 3.x URL requests to Pup 4.x

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          links to

          Web Link Pull Request #2 (2.1.x)

          Web Link Pull Request (2.1.x)

          Web Link Pull Request (master)

          Activity

            People

              Unassigned Unassigned
              nwolfe Nate Wolfe
              Erik Dasher Erik Dasher
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support