jira's Introduction

Codenvy

Cloud workspaces for development teams. One-click Docker environments to create workspaces with production runtimes. Team onboarding and collaboration with workspace automation and permissions letting devs sync their desktop IDE or use our gorgeous Eclipse Che IDE. Workspace platform for DevOps to manage workspaces at scale with programmable and customizable infrastructure.

Getting Started

You can run Codenvy in the public cloud, a private cloud, or install it on any OS that has Docker 1.11+ installed. Codenvy has been tested on many flavors of Linux, MacOS, and Windows. A private Codenvy install allows you to configure LDAP, permissions, Eclipse Che extensions, Jira integration, Jenkins integration and integration to your private toolchain.

The docs are awesome.

Or, quick start:

docker run codenvy/cli start

Then open http://localhost and log in as admin / password.

The codenvy repository is where we do development. Your license grants you access to the source code for customization, but you are not able to redistribute the source code or use it in commercial endeavors.

Submit bugs and feature requests and help us verify them
Review source code changes
Review the docs and make improvements

License

Codenvy is free for 3 users. For additional users or support, please purchase a Codenvy enterprise license.

Customiziing

There are many ways to customize Codenvy. Codenvy is customized using Eclipse Che including stacks, templates, commands, IDE extensions, server-side extensions plugins, assemblies, RESTful APIs, and editors.

Clone

git clone https://github.com/codenvy/codenvy.git

If master is unstable, checkout the latest tagged version.

Build and Run

cd codenvy
mvn clean install

# A new assembly is placed in:
cd onpremises-ide-packaging-tomcat-codenvy-allinone\target\

# Assembly:
onpremises-ide-packaging-tomcat-codenvy-allinone-${version}.zip

# Run Codenvy with a custom assembly - volume mount this codenvy repository
docker run -v /var/run/docker.sock:/var/run/docker.sock -v <path-to-repo>:/repo codenvy/cli start

Engage

Support: We love to help you.
Roadmap: We maintain the roadmap on the wiki.
Developers: Plug-in developers can use Eclipse Che.

jira's People

Contributors

Stargazers

Watchers

jira's Issues

Clean up factories when the issue is closed

Fidelity asked for an enhancement - it'd be good if when you close an issue, develop and review factories are deleted.

Factory links not being created properly from JIRA plugin

Aurea has installed our JIRA plugin in their JIRA system (version 7.1.9).

They have gone through the configuration described here: https://dash.readme.io/project/codenvy/docs/issue-management and everything appeared to work. However, when they create an issue in a codenvy-enabled project they don't get hyperlinks, they only get text.

I am only able to download JIRA 7.2 for mac and the plugin is not certified for this version so can't be installed.

Please see if you can replicate the behavior they're seeing.

Factory clone operation for JIRA plugin not working to spec

When a developer clicks on a Codenvy Factory link in JIRA the behavior should match this diagram:

Example of correct behavior

Starting State
JIRA issue ID: MKTG-097
Origin repo has no branch called "MKTG-097"

Process Flow

Developer clicks the Factory link in JIRA issue MKTG-097.
Codenvy checks the origin repo to see what it should clone:
- Is there a branch called MTKG-097?
  - Yes: then clone from head of that branch.
  - No: proceed to next check.
- Is there a defined startPoint parameter?
  - Yes: then clone from head of the branch defined in startPoint.
  - No: clone from head of master branch.

Current behavior

It appears the checks are not being run and if the origin repo doesn't have a branch named for the issue ID, then the clone fails.

Recommend Projects

codenvy / jira Goto Github PK