Go to file
Florent BENOIT 5554345aae [cli] Fix cli tests by reworking how integration tests are launched (#3991)
* Fix #3980 by reworking how integration tests are launched
- We used OS path mounted into container path (it makes issues as on Windows we don’t have these paths)
- Now use /dockerfiles path inside the container
- add skip check for nightlies or it was downloading new images while testing the current nightly
- add —rm for cleaning containers at the end of docker run
- introduce of some asserts instead of custom checks
- Fix windows issue (like path with spaces)
- Fix teardown of che start tests

Change-Id: I352d7c475796df641c1e34f461c55a76c897922d
Signed-off-by: Florent BENOIT <fbenoit@codenvy.com>
2017-02-02 09:43:48 +01:00
.github Update PULL_REQUEST_TEMPLATE.md 2017-01-31 06:59:08 -08:00
.mvn
agents [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
assembly [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
core [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
dashboard [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
dockerfiles [cli] Fix cli tests by reworking how integration tests are launched (#3991) 2017-02-02 09:43:48 +01:00
docs [cli] Fix cli tests by reworking how integration tests are launched (#3991) 2017-02-02 09:43:48 +01:00
ide [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
plugins [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
samples [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
wsagent [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
wsmaster [maven-release-plugin] prepare for next development iteration 2017-02-01 13:31:32 +00:00
.gitattributes
.gitignore Added {% include base.html %} to all markdown. (#3490) 2016-12-23 10:18:44 -06:00
CHANGELOG.md Changelog for 5.2.0 2017-02-01 14:02:15 +00:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md Update CONTRIBUTING.md 2017-01-29 08:26:21 -08:00
CUSTOMIZING.md Update CUSTOMIZING.md (#3752) 2017-01-16 15:54:10 -06:00
Chefile
LICENSE
NUMBERING.md
README.md Update README.md (#3584) 2017-01-02 13:38:16 -06:00
pom.xml RELEASE:Set next development version of parent pom 2017-02-01 13:59:52 +00:00

README.md

Eclipse Che - Eclipse Next-Generation IDE

Join the chat at https://gitter.im/eclipse/che Eclipse License Build Status

https://www.eclipse.org/che/. Next-generation Eclipse platform, developer workspace server and cloud IDE. Che defines workspaces that include their dependencies including embedded containerized runtimes, Web IDE, and project code. This makes workspaces distributed, collaborative, and portable to run anywhere on a desktop or a server ... Read More

Eclipse Che

Getting Started

You can run Che in the public cloud, a private cloud, or install it on any OS. Che has been tested on Ubuntu, Linux, MacOS and Windows. The step by step guide will get you going along with our docs.

The che repository is where we do development and there are many ways you can participate, for example:

Customizing

There are many ways to customize Che out-of-the-box including stacks, templates, commands, IDE extensions, server-side extensions plugins, assemblies, RESTful APIs, and editors.

Contributing

If you are interested in fixing issues and contributing directly to the code base, please see How to Contribute. It covers:

Feedback

  • Support: You can ask questions, report bugs, and request features using GitHub issues.
  • Roadmap: We maintain the roadmap on the wiki.
  • Weekly Meetings: Join us on a hangout.

License

Che is open sourced under the Eclipse Public License 1.0.