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

Start analyze using local tools connected to Che workspace #15016

Closed
evidolob opened this issue Oct 29, 2019 · 15 comments
Closed

Start analyze using local tools connected to Che workspace #15016

evidolob opened this issue Oct 29, 2019 · 15 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@evidolob
Copy link
Contributor

evidolob commented Oct 29, 2019

We need to analyze different tools which we can use to connect Che workspace to local environment

We may use various tools to synchronize project files between Che workspace and local PC:

@evidolob evidolob added kind/task Internal things, technical debt, and to-do tasks to be performed. team/ide2 labels Oct 29, 2019
@evidolob
Copy link
Contributor Author

cc @slemeur

@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 29, 2019
@l0rd
Copy link
Contributor

l0rd commented Oct 29, 2019

Please look at KSync for files syncing

@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 29, 2019
@tsmaeder
Copy link
Contributor

@l0rd Is there a roadmap item this connects to?

@l0rd
Copy link
Contributor

l0rd commented Oct 30, 2019

@tsmaeder I don't know where this issue come from honestly. Will discuss that tomorrow during priorisation with @slemeur

@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Oct 30, 2019
@evidolob evidolob modified the milestone: Backlog - IDE 2 Oct 30, 2019
@AndrienkoAleksandr AndrienkoAleksandr added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Oct 31, 2019
@AndrienkoAleksandr
Copy link
Contributor

During investigation ksync usage found that ksync doesn't work with volumes such like /projects

@l0rd
Copy link
Contributor

l0rd commented Mar 10, 2020

We should look at https://github.com/ernoaapa/kubectl-warp as well

@l0rd
Copy link
Contributor

l0rd commented Jun 2, 2020

@benoitf in order to close this issue we should have, in Che documentation, a reference to the blog posts.

@che-bot
Copy link
Contributor

che-bot commented Jan 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2021
@l0rd l0rd removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2021
@sympatheticmoose
Copy link

@l0rd so is this just waiting on a doc update? Do we have a corresponding issue to add those links?

@l0rd
Copy link
Contributor

l0rd commented Jan 14, 2021

@sympatheticmoose no we do not have a specific issue. We can use this one or close it and open a new one.

@sympatheticmoose
Copy link

cc @rkratky - thoughts on adding links vs incorporating somehow in Che docs?

@che-bot
Copy link
Contributor

che-bot commented Jul 19, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2021
@l0rd
Copy link
Contributor

l0rd commented Jul 20, 2021

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 20, 2021
@che-bot
Copy link
Contributor

che-bot commented Jan 16, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 16, 2022
@che-bot che-bot closed this as completed Jan 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

7 participants