Skip to content
master
Go to file
Code

Latest commit

OpenPaaS-Suite/esn/issues#8 fix unit backend test

See merge request linagora/lgs/openpaas/esn!1297
0eada30

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time

README.md

OpenPaaS

OpenPaaS is your next collaboration platform, for enterprises & organizations.

Discover

Try it in docker

Discover the OpenPaaS platform on your machine within 5 minutes by checking out the demo docker-compose recipe.

Install it on your server

Check out the installation guide to install OpenPaaS on a Linux server and start using it now! If you're a developer looking for a development setup, head to the next section:

Improve it with us

Developers are more than welcome to help build OpenPaaS! To get your development environement up & running, see our developers installation documentation.

Once you are ready to go, you can explore the project's documentation site and this repository's documentation. If you have any question, don't hesitate to come and ask on the forum!

Our CI

We are currently using Gitlab CI.
Hence, you can have a look at the .gitlab-ci.yml file on the root of this repository for more information.

However, some jobs are more complicated than expected, as they are depending on external tools.
Hopefully for you, such jobs are the latest in the pipeline execution; linters, build & tests jobs are simple.
The "complexe" jobs are those dedicated to CD (Continuous Delivery) which main reason is that we are delivering Docker images to two different registries.

The main complexity is about git branches & their related delivery, the following matrix might help you:

Branch name Internal registry DockerHub
master openpaas-snapshots/openpaas-esn:branch-master linagora/esn:branch-master
release-* (1) openpaas-snapshots/openpaas-esn:* linagora/esn:branch-*
feature-* (2) openpaas-snapshots/openpaas-esn:* linagora/esn:*

(1) The goal of release branches is to be able to maintain release (bug fix backport, CVE fixes...), and then produce minor releases based on this major release.
They should be prefixed by release-. e.g. git branch name release-1.6.x build will deliver:

  • openpaas-snapshots/openpaas-esn:1.6
  • openpaas-snapshots/openpaas-esn:1.6.3 (depending on the minor release)
  • linagora/esn:branch-1.6.3

(2) Feature branches are not release. They are used in order to publish & validate features (maybe several MRs & commits). They should be prefixed by feature-. e.b. git branch name feature-friday-delivery build will deliver:

  • openpaas-snapshots/openpaas-esn:feature-friday-delivery
  • linagora/esn:feature-friday-delivery

Licence

Affero GPL v3

Special thanks

drawing

BrowserStack for supporting open source projects.

You can’t perform that action at this time.