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

Update CI Systems #3423

Closed
TylerJewell opened this issue Dec 18, 2016 · 5 comments
Closed

Update CI Systems #3423

TylerJewell opened this issue Dec 18, 2016 · 5 comments
Assignees
@riuvshin
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone
5.0.0

Comments

@TylerJewell
Copy link

TylerJewell commented Dec 18, 2016 •
edited
Loading

  1. For testing purposes, we need 'latest' tag added to DockerHub for eclipse/che-cli. Have it temporarily point to 5.0.0-M8 until we make formal release.
  2. Please have eclipse/che image retagged to point to eclipse/che-cli image. It currently points to eclipse/che-launcher.
  3. After Package docker runner in Che #2 is done, we have to make a temporary update to the eclipse/che-launcher docs on README to use the fully qualified image name, not the short-hand.
@TylerJewell TylerJewell added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Dec 18, 2016
@TylerJewell TylerJewell added this to the 5.0.0-M9 milestone Dec 18, 2016
@riuvshin riuvshin self-assigned this Dec 18, 2016
@riuvshin riuvshin added sprint/current team/production status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Dec 18, 2016
@riuvshin
Copy link
Contributor

@TylerJewell 1 and 2 done.
can you please elaborate more what what should I do in 3 it is not clear to me.

btw do we still need che-launcher image?

@TylerJewell
Copy link
Author

#3 is an action item for me - so you can assign it me.

On your question about che-launcher. We should continue to leave the existing images there, but we should not generate new images anymore. In fact, you should disable the nightly builds for the che-launcher now.

@TylerJewell
Copy link
Author

#3 is now done.

@riuvshin
Copy link
Contributor

@TylerJewell should I close issue?

@TylerJewell
Copy link
Author

ok

@vkuznyetsov vkuznyetsov removed sprint/current status/in-progress This issue has been taken by an engineer and is under active development. labels Jan 6, 2017
@bmicklea bmicklea mentioned this issue Jan 13, 2017
Closed
70 tasks
This was referenced Jan 17, 2017
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@riuvshin riuvshin

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Milestone
5.0.0
Development

No branches or pull requests
3 participants
@TylerJewell @riuvshin @vkuznyetsov