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.

Sign up for GitHub

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

Jump to bottom

Adapt CICD tests to recent maven changes and optimize test results storage #25320

Closed
victoralfaro-dotcms opened this issue Jun 22, 2023 · 2 comments
Closed

Adapt CICD tests to recent maven changes and optimize test results storage #25320

victoralfaro-dotcms opened this issue Jun 22, 2023 · 2 comments
Labels
Merged QA : Not Needed Release : 23.08.16 Team : Falcon Type : New Functionality

Comments

@victoralfaro-dotcms
Copy link
Contributor

victoralfaro-dotcms commented Jun 22, 2023 •
edited

Parent Issue

None

User Story

As a Scrum Master, I want to modify the Github Actions workflows and/or actions required to run the tests in the pipeline.

Acceptance Criteria

  1. The modified workflows and actions should take into consideration the recently made Maven integration changes for caching ~/.m2/repository dependencies.
  2. A new fresh test results repository called 'core-test-results' should be used.
  3. The storage of test results should be optimized for master and release branches by creating a new branch based on the original branch plus a GitHub SHA suffix.
  4. For development branches, the test results should be overridden since they will be removed in a few weeks.

dotCMS Version

master

Proposed Objective

To improve the efficiency and reliability of the test execution process in the pipeline.

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

None

Assumptions & Initiation Needs

None

Quality Assurance Notes & Workarounds

None

Sub-Tasks & Estimates

None

Please note that the markdown generated above follows the provided template. Let me know if you need any further assistance!
@victoralfaro-dotcms victoralfaro-dotcms self-assigned this Jun 22, 2023
victoralfaro-dotcms added a commit that referenced this issue Jun 22, 2023
@victoralfaro-dotcms
#25320: Changing test results branch creation model for master/relea…
d1c75dc 
…se and the rest
@victoralfaro-dotcms
Copy link
Contributor Author

PR: #25323

victoralfaro-dotcms added a commit that referenced this issue Jun 22, 2023
@victoralfaro-dotcms
#25320: Changing test results branch creation model for master/relea…
656e828 
…se and the rest
victoralfaro-dotcms added a commit that referenced this issue Jun 22, 2023
@victoralfaro-dotcms
#25320: Changing test results branch creation model for master/relea…
ef73c20 
…se and the rest
dsilvam pushed a commit that referenced this issue Jun 23, 2023
@victoralfaro-dotcms
#25320: Changing test results branch creation model for master/relea…
3569391 
…se and the rest (#25323)
@dsilvam dsilvam removed the Triage label Jun 23, 2023
@victoralfaro-dotcms
Copy link
Contributor Author

Closing as it does not required QA.

manuelrojas pushed a commit that referenced this issue Jun 23, 2023
@victoralfaro-dotcms @manuelrojas
#25320: Changing test results branch creation model for master/relea…
60b1d85 
…se and the rest (#25323)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Merged QA : Not Needed Release : 23.08.16 Team : Falcon Type : New Functionality
Projects
dotCMS - Product Planning
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dsilvam @victoralfaro-dotcms