Dev main conflict #411
Closed
Dev main conflict #411
Conversation
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
### Description Test run: https://github.com/splunk/splunk-add-on-for-github-audit-log-monitoring/actions/runs/14998008338/job/42137066553 https://github.com/splunk/splunk-add-on-for-salesforce/actions/runs/15015649052/job/42192839796 ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done (for each selected checkbox, the corresponding test results link should be listed here)
### Description This is an adaptation to the new interface of the `ucc-test-modinput` command. From now on `ucc-test-modinput` does not perform `ucc-test-modinput gen` by default, so it must be explicitly specified. ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done - [X] backward compatibility (versions lower than 1.0.0): https://github.com/splunk/splunk-add-on-for-google-cloud-platform/actions/runs/15323624242 - [X] latest framework version (version 1.0.0): https://github.com/splunk/splunk-add-on-for-box/actions/runs/15325196621/job/43118599310
### Description This PR bumps k8s repository version. k8s changes are related to vendor installation for ucc modinput tests. Full Changelog: splunk/ta-automation-k8s-manifests@v3.3.3...v3.3.4 ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done - https://github.com/splunk/splunk-add-on-for-tomcat/actions/runs/15702434384 - https://github.com/splunk/splunk-add-on-for-palo-alto-networks/actions/runs/15702466025
### Description Run `appinspect api` job for `release/` branches in `build-test-release` pipeline Ticket: https://splunk.atlassian.net/browse/ADDON-77779 Tested in the following cases where appinspect api job is: - Running for PR with “release/“ base: https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/13626390125 - Running for manual trigger on “release/“ branch: https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/13626413937 - Not running for chore/ branch: https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/13626445165 ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done (for each selected checkbox, the corresponding test results link should be listed here)
### Description [ [ADDON-78394](https://splunk.atlassian.net/browse/ADDON-78394) ] Added conditions skip tests, build, app-inspect and publish if the changes in PR are only related to documentation. Tests: https://docs.google.com/document/d/1IFxbIwzDM0lBkO3ciNxFrPlOPPE9YQhcaVStQg7lYEM/edit?usp=sharing ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done (for each selected checkbox, the corresponding test results link should be listed here)
### Description Added a new job validate-docs-change. This job will attempt to serve the documentation and fail if there are any errors. If errors occur, they will be printed in the check logs step. Another stage, enforce-docs-changes, reviews the result of validate-docs-change and uses run metadata to determine whether the job should fail the pipeline. When the PR targets the main branch, enforce-docs-changes will enforce failure on broken documentation and block merge. For other branches, it serves as an indicator of documentation issues without blocking the merge. ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done (for each selected checkbox, the corresponding test results link should be listed here)
This PR bumps the k8s-manifests-branch version from v3.3.2 to v3.4.1 related PR: splunk/ta-automation-k8s-manifests#120 - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed - https://github.com/splunk/splunk-add-on-for-unix-and-linux/actions/runs/14701563721 --------- Co-authored-by: Dmytro Kvashnin <dkvashnin@splunk.com>
### Description I think it makes more sense to make a fix release each time we update appinspect version. We'd prevent ourselves from rolling out the template each time there is a feat release of appinspect. ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done No tests are needed
### Description update appinspect-cli-action to 2.10 ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done (for each selected checkbox, the corresponding test results link should be listed here)
### The file `.github/workflows/reusable-build-test-release.yml` had merge conflicts when merging develop into main. This PR resolves those conflicts and syncs the changes accordingly. --------- Co-authored-by: mkolasinski-splunk <105011638+mkolasinski-splunk@users.noreply.github.com> Co-authored-by: Dmytro Kvashnin <dkvashnin@splunk.com> Co-authored-by: Dmytro Kvashnin <139753462+dkvashninsplunk@users.noreply.github.com> Co-authored-by: mgrandys-splunk <153620320+mgrandys-splunk@users.noreply.github.com> Co-authored-by: dvarasani-crest <151819886+dvarasani-crest@users.noreply.github.com> Co-authored-by: kdoroszko-splunk <kdoroszko@splunk.com>
### The file `.github/workflows/reusable-build-test-release.yml` had merge conflicts when merging develop into main. This PR resolves those conflicts and syncs the changes accordingly. --------- Co-authored-by: mkolasinski-splunk <105011638+mkolasinski-splunk@users.noreply.github.com> Co-authored-by: Dmytro Kvashnin <dkvashnin@splunk.com> Co-authored-by: Dmytro Kvashnin <139753462+dkvashninsplunk@users.noreply.github.com> Co-authored-by: mgrandys-splunk <153620320+mgrandys-splunk@users.noreply.github.com> Co-authored-by: dvarasani-crest <151819886+dvarasani-crest@users.noreply.github.com> Co-authored-by: kdoroszko-splunk <kdoroszko@splunk.com>
…" (#404) This reverts commit e30a821. ### Description This PR reverts the previous implementation of documentation validation and enforcement, and reintroduces those capabilities using a **reusable GitHub Actions workflow** along with a **template `validate-deploy-docs.yml` workflow file** in the template repository. ## Changes with PR reference - Removes the hardcoded docs validation logic. - Changes related to document validation and deployment is made in this PR: splunk/addonfactory-repository-template#743 ### Checklist - [ ] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [ ] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done (for each selected checkbox, the corresponding test results link should be listed here)
### Description This PR removes the deprecated version (ubuntu 14.04) and add support of Ubuntu 20.04 and redhat 9.5 for scripted inputs. ### Checklist - [x] `README.md` has been updated or is not required - [ ] push trigger tests - [ ] manual release test - [ ] automated releases test - [x] pull request trigger tests - [ ] schedule trigger tests - [ ] workflow errors/warnings reviewed and addressed ### Testing done Test run: https://github.com/splunk/splunk-add-on-for-unix-and-linux/actions/runs/15417614522
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
(PR description goes here)
Checklist
README.mdhas been updated or is not requiredTesting done
(for each selected checkbox, the corresponding test results link should be listed here)