* Fix perf test failure due to a wrong step added earlier
* Remove all the steps added to make perf tests work on EE
Co-authored-by: Satish Gandham <hello@satishgandham.com>
## Description
- This PR adds a new fat-migration.yml file which will run all cases in fat container instead of dev.app.appsmith
- This PR will not affect any existing Push/Workflow dispatches as its a separate action file
- Moving to fat container will not be put into action until RBAC is live - so as to not trigger any new challenge at last minute
## Type of change
- New .yml file
## How Has This Been Tested?
- Cypress CI runs
## Checklist:
### QA activity:
- [X] Test plan has been approved by relevant developers
- [X] Test plan has been peer reviewed by QA
- [X] Cypress test cases have been added and approved by either SDET or manual QA
- [X] Organized project review call with relevant stakeholders after Round 1/2 of QA
- [X] Added Test Plan Approved label after reveiwing all Cypress test
* - Add missing env variables to fix perf tests failures in EE
* - Delete source maps on CI only for EE
* - Add the additional steps that might be required for running perf tests on EE
* Update if condition
* Update if condition
* Switch to bash from using sh in build.sh
* Check if the server started later
* Update the check to see if the server has started
Co-authored-by: Satish Gandham <hello@satishgandham.com>
* Rearrange client build steps
* Remove PR from the run meta insert query
* Add repo to the query
Co-authored-by: Satish Gandham <hello@satishgandham.com>
* - Add S3 credentials to environment
- Change the workflow name
- Create performance run meta data record at the begining.
* Fix a typo
* Fix a typo
* Store DB credentials as plain values instead of JSON
* Fix SQL insert query
* Add missing secrets
* Continue even if the meta creation fails
* Fix SQL insert command
* Rename workflow
Co-authored-by: Satish Gandham <hello@satishgandham.com>
* Add option to run only perf tests on github
* Add new line at the end of the file
* - Run the artifacts step even on failure
- Add link to the perf run details
- Remove the perf comment on the PR
Co-authored-by: Satish Gandham <hello@satishgandham.com>
## Description
- This PR includes changes for starting rts server for AST changes to take effect
## Type of change
- yml file updates
## 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 includes changes for starting rts server for AST changes to take effect
## Type of change
- yml file updates
## 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
* update rts logic to use updated shared AST logic
* Make changes to naming conventions
* Add test cases for RTS and rename ast functions
* Add running jest test to RTS workflow
* Install dependencies and then trigger jest tests in workflow
* Close server connection after test ends
* Remove logs
* Improve jest test descriptions
Fix ci cache & rts build for push workflow
## Description
Fix ci cache & rts build for push workflow
## 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
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
## Description
The depot docker step wasn't initialized. This was causing Docker builds to fail.
## Type of change
- Bug fix (non-breaking change which fixes an issue)
## How Has This Been Tested?
- Relying on CI
## 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>
Reverts #14636
Reverting this change for now because there is an issue when re-running the failed specs. The action is unable to find the correct directory.
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>
* Adding visual tests for layout validation
* updating screenshot to match CI's screenshot resolution
* updating screenshot as per CI
* setting failure threshold for the image comparision
Co-authored-by: Parthvi Goswami <parthvigoswami@Parthvis-MacBook-Pro.local>
Currently, all three services' artifact names are set to build. This leads to a single artifact with files from all three services as siblings. This has two problems:
1. If there's an overlap in a filename among the files in build folder of two services, one of them will be overwritten with the other.
2. The same large artifact is downloaded every time we do a download-artifact, once for server, once for client, and once for RTS, the same large artifact is downloaded thrice before building the Docker images.
Now we can add multiple title regexes for a PR and the labeler will automatically tag the PR with the appropriate labels. This will be useful when generated the release notes in a categorized fashion.
* Call cloud services to fetch mock datasets
* Call cloud services to fetch mock datasets
* Change the MockData Config,
* Remove unused import statements and fix small indentation issues
* 1. Moved the mock data creation and fetching to a separate class
2. Added plugin type to mockdata class
3. Used pluginName to identify the db type
4. Removed the block call mock data creating method
5. Added unit tests for the mockdata
* 1. Removed unused field from contract and
2. Updated the url to cloud service
* 1. renamed the field of mockdata contract
2. Updated the test cases
* using new mock datasources apis
* 1. Added the Cloud Service release end point to env variable
Co-authored-by: Pranav Kanade <pranav@appsmith.com>
* Release frozen related changes
* Switched image used to PR head instead of target
* Update .github/workflows/client-test.yml
Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com>
* PRs into release should use release server code
