summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Fix Authorization Matrix property - inheritance strategy"master-patchesZuul2020-07-175-0/+31
|\
| * Fix Authorization Matrix property - inheritance strategyAdam Romanek2020-07-155-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Up until now <inheritanceStrategy> tag was only added to jobs-in-a-folder and folder configs. In JJB the tag's class is always set to "InheritParentStrategy" which according to the docs means the "item will inherit its parent items permissions". Apparently <inheritanceStrategy> tag needs to be present on top-level jobs also. For top-level jobs setting the tag's class value to "InheritParentStrategy" means the job "will inherit the global security security settings" and this is the default behavior. The code has simplified a bit - if it's a folder then we use a different property name for authorization matrix property, other than that the code is the same for all three "variants": folder, job-in-a-folder and job-outside-a-folder (top-level job). Also this change fixes the missing <inheritanceStrategy> tag for job-in-a-folder, where the folder name was specified as part of the "name" key instead of the standalone "folder" key. With this change we no longer check if a job is in a folder or not, so it's implicitly fixed. Added a test case to catch potential regressions in the future. The copyright notice reflects this and the previous contribution in this module. Change-Id: I84b22c09c8a107aab2b4eca20feffc9b61675a92
* | Merge "Updated GHPRB plugin support"Zuul2020-07-158-16/+66
|\ \
| * | Updated GHPRB plugin supportEren ATAS2020-07-078-16/+66
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implemented the following tags that have been missing: - displayBuildErrorsOnDownstreamBuilds - blackListCommitAuthor - GhprbCommentFile - GhprbNoCommitStatus Following tags are printed when the value of the key is empty: - whiteListTargetBranches - blackListTargetBranches - buildDescTemplate - triggeredStatus - startedStatus - statusUrl - addTestResults Also updated tests Change-Id: I1e19841d88728af9ac6aa9e1c78f89fe962a583f Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
* | Merge "Removed the unnecessary empty combinationFilter Tag"Zuul2020-07-1514-17/+0
|\ \
| * | Removed the unnecessary empty combinationFilter TagEren ATAS2020-07-0714-17/+0
| |/ | | | | | | | | | | | | | | | | In the current implementation, jjb creates an empty combinationFilter tag whenever there is `executionStrategy`. This empty tag should not appear. Change-Id: I2bf25ae58d12904ce0a00e0a5cfefbf27d9451ad Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
* | Merge "publishers: add "threshold" support to join-trigger"Zuul2020-07-152-0/+30
|\ \
| * | publishers: add "threshold" support to join-triggerDavid Aguilar2020-06-232-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | The joinTrigger plugin now accepts a resultThreshold field instead of the evenIfDownstreamUnstable boolean. Add support for a "threshold" yaml field to manage this value. Change-Id: I60ba999b963709a76854a4d50387d2b1eefae05f Signed-off-by: David Aguilar <davvid@gmail.com>
* | | Merge "Implement disable discover_pr_origin"Zuul2020-07-152-0/+66
|\ \ \
| * | | Implement disable discover_pr_originRotaru Sergey2020-06-142-0/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In my opinion the best choise for default value of discover_pr_origion is not specified(None value) like it is done for bitbucket scm. Currently there is no way to disable this option for github scm. Added false value as one of valid value for this option, like is done for discover-pr-fork-strategy. In fact any of yaml specification false implementation should work. Change-Id: Ibc26d6b5c39b5455160ba5c84be99575b79fc102
* | | | Merge "Implement GitHub PR Comment Build Plugin"Zuul2020-07-152-0/+8
|\ \ \ \
| * | | | Implement GitHub PR Comment Build PluginSergey Rotaru2020-06-142-0/+8
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support of trigger-build-on-pr-comment, trigger-build-on-pr-rewiev, trigger-build-on-pr-update options for multibranch project. Modified multibranch test case to cover new options. Change-Id: Ia8658b49e7f7806ef1a8f34de10eaee5b3b7b488 Signed-off-by: Rotaru Sergey <badwings@yandex.ru>
* | | | Merge "Implement script-id for multibranch with default."Zuul2020-07-154-1/+74
|\ \ \ \ | |_|_|/ |/| | |
| * | | Implement script-id for multibranch with default.Rotaru Sergey2020-06-154-1/+74
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Main feature to use multibranch with defaults project type is build configuration mode with default groovy script stored in global Jenkins store provided by config-file provider plugin. Options "script-id" and "sandbox" fully implements this feature. Besides both project type support "script-path" and "script-id" mode. It may be convenient to switch mode without changing project type in order to save project history. Change-Id: I4cd62e69c9abe7d8fc2e0dfdbe25d8b07ddf51c5
* | / Added topic-changed-event on triggers.pyEren ATAS2020-06-192-0/+89
| |/ |/| | | | | | | | | | | Depends on https://review.opendev.org/#/c/731169/ Change-Id: I8d1ed67b11e1ff1fcf13325108c007d6baff07c4 Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
* | Merge "Gerrit Trigger: update support to the latest plugin version"Zuul2020-06-1852-50/+754
|\ \ | |/ |/|
| * Gerrit Trigger: update support to the latest plugin versionAdam Romanek2020-06-0152-50/+754
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The changes include: - deprecated the following options and made support for them dependent on the Gerrit Trigger plugin version: - 'no-name-and-email' - 'readable-message' - 'trigger-for-unreviewed-patches' - added a set of new options: - 'name-and-email-parameter-mode' (replaced 'no-name-and-email') - 'commit-message-parameter-mode' (replaced 'readable-message') - 'change-subject-parameter-mode' - 'comment-text-parameter-mode' all these options can have one of the following values: - NONE - PLAIN - BASE64 the default value for the first two options is taken from the respective options they replaced, if they exist in the input YAML file, so the overall change should be backward compatible - fixed the value generated for <dynamicTriggerConfiguration> element it should be "true"/"false" instead of "True"/"False" - added an empty <dynamicGerritProjects> element when dynamic trigger functionality is disabled to match what the plugin does With the above changes the markup generated by JJB is fully aligned with Gerrit Trigger plugin v2.30.x. Tested on Gerrit Trigger plugin v2.30.0. Task: 39871 Story: 2007722 Change-Id: I25800874f51a93a351926a9a1be255cce80b88bd
* | Gradle plugin: Support parameter passingBen Douglas2020-06-012-0/+4
|/ | | | | | | Introduce 2 booleans in the Gradle builder section to support passing parameters by System Properties and Project Properties Change-Id: I0de1e20b85902263e0d83ccadd64d42fc2b37193
* Merge "Introduce disable-host-key-checking for builder ansible-playbook"Zuul2020-05-268-4/+41
|\
| * Introduce disable-host-key-checking for builder ansible-playbookChristian Kanthak2020-05-158-4/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implemented new parameter "disable-host-key-checking" to make the "anbile-playbook" builder compatible with version >=1.0 of the ansible plugin. The parameter defaults to "false" for security reasons (as the plugin does). The old parameter "host-key-checking" is still written to XML to keep code working in a setup with plugin version <1.0. This has no impact on newer setups because the plugin with version >=1.0 ignores the old parameter value. For same security reasons the default value of old parameter "host-key-checking" was changed to "true" to "fix" older setups which have the parameter not defined. Change-Id: I4a592c1a4d6ba8bb4f365ce505296cf5c09f7e19 Task: 39789 Story: 2007678
* | Merge "Pipelines: stop producing unsupported and deprecated XML tags"Zuul2020-05-2511-78/+73
|\ \
| * | Pipelines: stop producing unsupported and deprecated XML tagsAdam Romanek2020-05-2511-78/+73
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The changes include: - <concurrentBuild> should now be represented as <org.jenkinsci.plugins.workflow.job.properties.DisableConcurrentBuildsJobProperty/> property - <triggers> should now be localed inside <org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty> property, in <properties> section - unsupported XML elements got removed: - <blockBuildWhenDownstreamBuilding> - <blockBuildWhenUpstreamBuilding> - <assignedNode> - <canRoam> - <customWorkspace> - got rid of publishers from project_pipeline_template005.{xml,yaml} as these are not supported in Pipeline jobs The above changes align the produced XMLs with the ones from Jenkins 2.190.1 and Pipeline plugin v2.6. Task: 39836 Story: 2007708 Change-Id: I650ef2ee60e872cce8f93de5f391933d68ec81f0
* | Added trim option for String parameter.Igor Lakhtenkov2020-05-227-0/+45
| | | | | | | | | | Task: #22637 Change-Id: Ic2722aac586d3911e3ff5ab4c2d3c5a7a03fa14e
* | Merge "Added missing 'BuiltOn' column for views"Zuul2020-05-182-0/+2
|\ \
| * | Added missing 'BuiltOn' column for viewsSergey Lebedev2020-05-182-0/+2
| |/ | | | | | | | | | | Plugin home - https://plugins.jenkins.io/built-on-column/ Change-Id: I7fd27add618772fe3835f5f4fd4ef30c097b781d
* / Added missing 'Favorite' column for viewsSergey Lebedev2020-05-182-0/+2
|/ | | | | | Plugin home - https://plugins.jenkins.io/favorite/ Change-Id: Ibfaf64721fa25c19812c90c79d12ab82b31451aa
* Fix Authorization Matrix property support on jobs in a folderAdam Romanek2020-05-132-0/+28
| | | | | | | | | | | | | | | | | Without the fix: > 2020-05-11 10:56:12.238+0000 [id=29522] WARNING > o.e.j.s.h.ContextHandler$Context#log: Error while serving http://localhost/job/someFolder/createItem > java.lang.ClassCastException: com.cloudbees.hudson.plugins.folder.properties.AuthorizationMatrixProperty cannot be cast to hudson.model.JobProperty It turns out com.cloudbees.hudson.plugins.folder.properties.AuthorizationMatrixProperty should only be applied to Folders, not Jobs. The latter should use hudson.security.AuthorizationMatrixProperty. Task: 39760 Story: 2007666 Change-Id: I64907265b214fb1e489e1e657a30c90d6ee08c3f
* Add "upstream-committers" to publisher "email-ext"Christian Kanthak2020-05-042-0/+49
| | | | | | | | | | Add support for the recipient item "Upstream Committers" of the "Send To" list of a trigger of the "Email Extension" (email-ext) plugin. Change-Id: Iaa77330bb1910881df154494b0472ce21ea28d99 Task: 39595 Story: 2007607
* Add parameter "cancel-pending-builds-on-update" for trigger "gitlab"Christoph Erhardt2020-04-1610-0/+10
| | | | | | | When this boolean parameter is set to true, updating a merge request cancels any pending merge-request builds. Change-Id: Ic5ef400cf4cd088680b92bd10b88b79520795729
* Add execute-on parameter for post build stepsArtem Nikitin2020-03-122-0/+10
| | | | | | | | | | | executeOn setting is available for PostBuildStep since 2.0 version of the Post Build Script plugin. For previous plugin's version executeOn should be set on the PostBuildScript layer. Change-Id: I6b7c9ccfbd0a2d610499074675835e6b5d96cb17 Task: 39028 Story: 2007411
* Merge "Add support for become in ansible playbook"Zuul2020-03-045-0/+34
|\
| * Add support for become in ansible playbookMichal Ovciarik2020-02-255-0/+34
| | | | | | | | Change-Id: Ia116f715042d4a4c8cc26ac45cf1a91be47435d3
* | Adding view for the Delivery Pipeline PluginJiri Tyr2020-02-076-0/+114
| | | | | | | | | | Change-Id: I8a9a71267562734b078b7260c79d299db7fb4e2b Signed-off-by: Jiri Tyr <jiri.tyr@gmail.com>
* | Merge "Fix authorization property issue"Zuul2020-01-222-0/+35
|\ \
| * | Fix authorization property issueArtem Nikitin2020-01-172-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The change fixes a XML generating error (KeyError: '_use_folder_perms') for project, which isn't contained in a folder and has got authorization properties. Task: 38110 Story: 2007087 Change-Id: I2e0ec6e524d07a935333b35e10eb4204af9256f7
* | | Merge "Add support for opsgenie notification plugin"Zuul2020-01-224-0/+42
|\ \ \ | |/ / |/| |
| * | Add support for opsgenie notification pluginJohn Oram2020-01-074-0/+42
| |/ | | | | | | Change-Id: Id84b3d9282568cf47d5feb930fd618afe969b45f
* | Experimental support for filterChecks traitLuca Milanesio2020-01-082-0/+7
| | | | | | | | | | | | | | | | The gerrit-code-review-plugin v0.4.0 introduces the integration with Gerrit Checks plugin. Introduce the option to query for pending checks. Change-Id: Idb3f290121aa6fbcdc25a0821c9bdc3dd03e21af
* | Fix gerrit-code-review plugin nameLuca Milanesio2020-01-032-2/+2
|/ | | | | | | | The GerritSCMSource type for the multibranch pipeline does not belong to the 'gerrit' plugin but rather to the 'gerrit-code-review' plugin. Change-Id: I5edd81a3506847c3e5910ad66d4498a2b8c899e9
* Merge "Fix the yaml load warning."3.2.0Zuul2019-12-163-8/+8
|\
| * Fix the yaml load warning.Daniel Bengtsson2019-12-103-8/+8
| | | | | | | | | | | | | | | | | | | | | | In the new version of PyYAML the API changed to be more explicit. Now the default value for the Loader is None, see: https://github.com/yaml/pyyaml/blob/5.1/lib3/yaml/__init__.py#L103 The load is unsafe. It's better to use safe_load function. Change-Id: Ia1cd16f2ff970ca220a266c99b6554dd4254ebd9
* | Add support for noSquash (no-squash) in jms-messaging triggerWaldemar Znoinski2019-12-133-0/+3
|/ | | | | | | | | | | It's sometimes required to trigger a job build on every CI message. To achieve that the XML's noSquash (jjb: no-squash) has to be set to True. see triggers section at: https://wiki.jenkins.io/display/JENKINS/JMS+Messaging+Plugin Change-Id: I389e59cca4f649379614f7f6247bf76cf4a0ba95
* Add alias to multijob builderArtem Nikitin2019-11-132-0/+32
| | | | | | | It's helpful to have possibility to set `jobAlias` in case the same job is used multiple times with different configurations. Change-Id: Ic092c6b2f5d893e75ebce4aaebc7eaf88a8978a6
* Add Private and WIP change support for gerritJoseph Kostreva2019-11-064-0/+8
| | | | | | | Updated gerrit trigger support to include the new exclude private and exclude wip changes. Change-Id: I75d8113941e4e455ec34fab23d347816c2ef699b
* Fix double inderection of name templatesJames Harris2019-11-052-0/+59
| | | | | | | | | | Ensure that we can resolve any lazily loaded templates that might be dictionary keys in yaml. For more informmation please see the added test case in tests/yamlparser/fixtures/jinja-string04.yaml. Change-Id: I67fbca422f2165729af15e4d039278ad66f6240b Story: 2006431 Task: 36338
* Allow use of jinja templates in defaultsJames Harris2019-11-052-0/+38
| | | | | | | | | | | | Jinja templates are not deep-copyable so they cannot be used in "defautls" sections or to pick defualts for job groups or projects. This works around the issue by waiting until we render the template to construct the template itself. Story: 2006431 Task: 36337 Change-Id: Ief31fdaac06bb14d0aaba71c8c0e658a7f861671
* Support sectioned viewsJan Zerebecki2019-10-284-0/+58
| | | | Change-Id: Iaf352e8cc62644fb05afaae21630b9bec2cd30c0
* Support nested viewsJan Zerebecki2019-10-244-4/+67
| | | | Change-Id: I13532a16efc6e970ab5a7c021ec4d77be98d3de8
* Merge "Fix Authorization properties for folder and job in Folder"Zuul2019-10-132-0/+34
|\
| * Fix Authorization properties for folder and job in FolderJo Rhett2019-10-022-0/+34
| | | | | | | | | | | | | | | | | | This outputs the correct XML schema for authorization properties for both a folder, and a job inside a folder. Story: 2006493 Story: 2006611 Change-Id: I14662855613ce146f74b85f5978a0ed828f4439b
generated by cgit (git 2.34.1) at 2024-06-20 17:15:36 +0000