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

testing on remote environments #51

Closed
abhi18av opened this issue Jul 2, 2024 · 2 comments · Fixed by #53
Closed

testing on remote environments #51

abhi18av opened this issue Jul 2, 2024 · 2 comments · Fixed by #53

Comments

@abhi18av
Copy link
Member

abhi18av commented Jul 2, 2024

Hi @jagedn ,

I was wondering if we could have a task which pushes the built plugin to a remote server via SSH.

This was we can use our locally built latest version and deploy it to the sun-nomadlab or az-nomadlab setups - do you think it makes sense?

@jagedn
Copy link
Collaborator

jagedn commented Jul 2, 2024

yes, I think we can use secrets in GH to store the credentials and execute ssh against these server but not sure how to check if the command finish ok ... will see

another approach is to use custom GH runners ( I think we have an issue opened to investigate this case)

@abhi18av
Copy link
Member Author

abhi18av commented Jul 2, 2024

Exactly, with this approach we can push the built aftifacts directly to az-nomadlab nodes from Github and then trigger something there.

CC @jhaezebr @matthdsm @tomiles

@jagedn jagedn changed the title Gradle tasks for enabling testing on multiple environments testing on remote environments Jul 2, 2024
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 a pull request may close this issue.

2 participants