## Description
Fix ui-test cache
Fixes # (issue)
## Type of change
- Bug fix (non-breaking change which fixes an issue)
## How Has This Been Tested?
Code review
## Checklist:
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have commented my code, particularly in hard-to-understand areas
- [X] I have made corresponding changes to the documentation
- [X] My changes generate no new warnings
- [X] I have added tests that prove my fix is effective or that my feature works
- [X] New and existing unit tests pass locally with my changes
## Description
Fix ui-test cache
Fixes # (issue)
## Type of change
- Bug fix (non-breaking change which fixes an issue)
## How Has This Been Tested?
Code review
## Checklist:
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have commented my code, particularly in hard-to-understand areas
- [X] I have made corresponding changes to the documentation
- [X] My changes generate no new warnings
- [X] I have added tests that prove my fix is effective or that my feature works
- [X] New and existing unit tests pass locally with my changes
## Description
The problem with the RTS workflow after the induction of AST parsing was that while copying the `node_modules`, Ubuntu doesn't follow the symlink and copy the content. It simply copies the symlink as is. This causes issues for RTS service to start.
## Type of change
- Bug fix (non-breaking change which fixes an issue)
## How Has This Been Tested?
- Personal repository
## Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
Refer to #16020 for details. This PR has been opened since we could not modify the previous PR since it's a contribution by an external contributor.
Co-authored-by: kylegalbraith <kyle.galbraith459@gmail.com>
## Description
- This PR makes changes to run CI on latest stable Chrome always
## Type of change
- Browser update
## Checklist:
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [X] My changes generate no new warnings
- [X] I have added tests that prove my fix is effective or that my feature works
- [X] New and existing unit tests pass locally with my changes
## Description
- This PR makes changes for moving from Chrome to Electron browser for CI runs & fixes the git hub runners failure issue incases of Chrome version updates
## Type of change
- Browser name update
## Checklist:
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [X] My changes generate no new warnings
- [X] I have added tests that prove my fix is effective or that my feature works
- [X] New and existing unit tests pass locally with my changes
Moving server builds to Buildjet to confirm if it's faster and more reliable
Also, cleaning up some CI workflows to remove references to release-frozen branch.
## Description
This PR adds the string `Community` along with the Appsmith version. This will help users identify the type of instance that they are running.
## Type of change
- New feature (non-breaking change which adds functionality)
## How Has This Been Tested?
Manually
## Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
* Clean up the perf folder and update integration commnds to use the new repo
* Use a different token for github auth
* Update the token
* - Remove directory listing command
* Move perf checkout command to the back
* resolve conflicts
* Add directory listing code
* Fix an issue with directory listing
* - Remove directory listing code
Co-authored-by: Satish Gandham <satish@appsmith.com>
* Clean up the perf folder and update integration commnds to use the new repo
* Use a different token for github auth
* Update the token
* - Remove directory listing command
* Move perf checkout command to the back
* resolve conflicts
* Add directory listing code
* Fix an issue with directory listing
Co-authored-by: Satish Gandham <satish@appsmith.com>
* Clean up the perf folder and update integration commnds to use the new repo
* Use a different token for github auth
* Update the token
* - Remove directory listing command
* Move perf checkout command to the back
* resolve conflicts
* Add directory listing code
Co-authored-by: Satish Gandham <satish@appsmith.com>
* Clean up the perf folder and update integration commnds to use the new repo
* Use a different token for github auth
* Update the token
* - Remove directory listing command
Co-authored-by: Satish Gandham <satish@appsmith.com>
* Clean up the perf folder and update integration commnds to use the new repo
* Use a different token for github auth
* Update the token
Co-authored-by: Satish Gandham <satish@appsmith.com>
* Clean up the perf folder and update integration commnds to use the new repo
* Use a different token for github auth
Co-authored-by: Satish Gandham <satish@appsmith.com>
* Run perf tests only on buildjet machine
* - Set chrome process priority to maximum to stabilise the run data
* Update index.js
* Update perf.js
* Update index.js
* - Move around args
* - Add --no-sandbox option to initial setup
* -We don't need sudo on the main script, we can use sudo in node scripts to set process priority
* - Some tweaks to the perf scripts.
* - Remove no-sandbox option in puppeteer launch
* - Remove sudo at unnecessary places
* - Add code to force grabage collection in chrome
* Update logins and some cleanup
* Remove unsed import
Co-authored-by: Satish Gandham <satish@appsmith.com>
We use github actions cache to store jobstate for the previous runs. The default cache is invalidated incase the job fails. To support rerunning only failed tests, we use custom cache martijnhols/actions-cache@v3. Recently new changes into custome cache broke our workflow https://github.com/MartijnHols/actions-cache.
Co-authored-by: Yatin <yatin.chaubal@gmail.com>
