Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User/mgazda/spl2 framework cli #363

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

mgazda-splunk
Copy link
Contributor

Description

(PR description goes here)

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)

artemrys and others added 6 commits January 27, 2025 12:20
### Description

This is not a breaking change for the reusable workflow, updating
version of the action to v3.0.

This PR will be followed up with a template change.

Tested - splunk/addonfactory-ucc-generator#1525.

### Checklist

- [x] `README.md` has been updated or is not required
- [ ] push trigger tests
- [ ] manual release test
- [ ] automated releaes 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)
TA-> TA Upgrade implementation ADDON-73792

This pull request introduces a new feature to our CI/CD pipeline,
focusing on automating upgrade testing for Technology Add-ons (TA). The
goal is to streamline the release process by incorporating scalable and
user-friendly solutions capable of executing upgrade scenarios

Key Features:
Automated Upgrade Testing: Introduces jobs for upgrade testing within
the GitHub CI/CD pipeline.

Flexible Version Testing: Allows users to provide multiple TA versions
on which upgrade tests should be executed. In this repo,
ta_upgrade_version parameter is responsible for passing the info about
versions being tested. Also, both GitHub and Splunkbase releases are
supported, depending on the format of the version string provided:

vX.X.X - for GitHub releases
X.X.X - for Splunkbase releases
additionally, latest can be passed to use the latest version from GitHub
example run -
https://github.com/splunk/splunk-add-on-for-amazon-web-services/actions/runs/12045945177

Part of
splunk/ta-automation-app-of-apps#27
splunk/ta-automation-k8s-manifests#102
splunk/wfe-test-runner-action#35

---------

Co-authored-by: Adam Wownysz <[email protected]>
@mgazda-splunk mgazda-splunk requested a review from a team as a code owner February 6, 2025 14:36
Copy link

github-actions bot commented Feb 6, 2025

All contributors have NOT signed the CLA Document


I have read the CLA Document and I hereby accept the CLA


4 out of 5 committers have signed the CLA.
✅ (artemrys)[https://github.com/artemrys]
✅ (dkaras-splunk)[https://github.com/dkaras-splunk]
✅ (spanchal-crest)[https://github.com/spanchal-crest]
✅ (mkolasinski-splunk)[https://github.com/mkolasinski-splunk]
@mgazda-splunk
You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants