Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1534

Create a runPCT step

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      • There is a step, which allows running PCT as a pipeline step
      • PCT runs for a defined WAR and the list of plugins
      • The step produces and publishes the report
        • Optionally using test prefixes in the junit step to not overwrite standard tests
      • The step optionally fails if PCT run fails
      • PCT step is able to take a custom PCT docker image, so that we can run PCT with custom environments

        Attachments

          Issue Links

            Activity

            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Raul Arabaolaza
            Path:
            Dockerfile
            README.md
            src/main/docker/run-pct.sh
            http://jenkins-ci.org/commit/plugin-compat-tester/7ed31749144e21f3a5bad7b898bd797bba84c14e
            Log:
            INFRA-1534 Using a volume for maven settings file caused a lot of problems

            When running in parallel in a pipeline you can not just mount several volumes
            with the same name so you need to use docker.inside and move the settings file into the folder
            But as m2-settings.xml was defined as volume it is created as a folder, hence
            run-pct script failed to recognize the custom settings as it was looking for
            a regular file

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: Dockerfile README.md src/main/docker/run-pct.sh http://jenkins-ci.org/commit/plugin-compat-tester/7ed31749144e21f3a5bad7b898bd797bba84c14e Log: INFRA-1534 Using a volume for maven settings file caused a lot of problems When running in parallel in a pipeline you can not just mount several volumes with the same name so you need to use docker.inside and move the settings file into the folder But as m2-settings.xml was defined as volume it is created as a folder, hence run-pct script failed to recognize the custom settings as it was looking for a regular file
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Raul Arabaolaza
            Path:
            Dockerfile
            README.md
            src/main/docker/run-pct.sh
            http://jenkins-ci.org/commit/plugin-compat-tester/d9c2b51ce106e96cfc8d33d4f2dbb40ed51fec8f
            Log:
            INFRA-1534 Allow to set the location of custom maven settings without using volumes

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: Dockerfile README.md src/main/docker/run-pct.sh http://jenkins-ci.org/commit/plugin-compat-tester/d9c2b51ce106e96cfc8d33d4f2dbb40ed51fec8f Log: INFRA-1534 Allow to set the location of custom maven settings without using volumes
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Raul Arabaolaza
            Path:
            README.md
            http://jenkins-ci.org/commit/plugin-compat-tester/bdb02b7ab7e73d291b5aaca35f89eb57243b0ec8
            Log:
            INFRA-1534 Typo

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: README.md http://jenkins-ci.org/commit/plugin-compat-tester/bdb02b7ab7e73d291b5aaca35f89eb57243b0ec8 Log: INFRA-1534 Typo
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Raul Arabaolaza
            Path:
            README.md
            http://jenkins-ci.org/commit/plugin-compat-tester/c56c85db1a32db25b37a38593360733e1ee61e8d
            Log:
            INFRA-1534 Another typo

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Raul Arabaolaza Path: README.md http://jenkins-ci.org/commit/plugin-compat-tester/c56c85db1a32db25b37a38593360733e1ee61e8d Log: INFRA-1534 Another typo
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            README.md
            src/main/docker/run-pct.sh
            http://jenkins-ci.org/commit/plugin-compat-tester/82286e40646de03747ab7bd42c89c22a094a7965
            Log:
            Merge pull request #73 from raul-arabaolaza/INFRA-1534-0

            INFRA-1534 Using a volume for maven settings file caused a lot of problems

            Compare: https://github.com/jenkinsci/plugin-compat-tester/compare/b126e3d5f48e...82286e40646d

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: README.md src/main/docker/run-pct.sh http://jenkins-ci.org/commit/plugin-compat-tester/82286e40646de03747ab7bd42c89c22a094a7965 Log: Merge pull request #73 from raul-arabaolaza/ INFRA-1534 -0 INFRA-1534 Using a volume for maven settings file caused a lot of problems Compare: https://github.com/jenkinsci/plugin-compat-tester/compare/b126e3d5f48e...82286e40646d

              People

              Assignee:
              rarabaolaza Raul Arabaolaza
              Reporter:
              rarabaolaza Raul Arabaolaza
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: