Sebastian Brudziński

Move 3.3.1 release notes to release branch

    • -0
    • +172
    /docs/source/releases/openlmis-ref-distro-v3.3.1.rst
Fix rst underlines in release notes for 3.3.1

Bump requisition and UI versions to RC2 for UAT deployments

Since this needs to be repeated eight times and it looks exactly the same for each step, is there any way to extract what happens at the failure and define it in one place in the jenkinsfile?

Since this needs to be repeated eight times and it looks exactly the same for each step, is there any way to extract what happens at the failure and define it in one place in the jenkinsfile?

OLMIS-4930 Trying upping mem limit for some containers

OLMIS-4768 Added CHANGELOG

OLMIS-4768 Modified unique status changes check
OLMIS-4768 Modified unique status changes check
OLMIS-4768 Modified unique status changes check

The previous implementation could raise false positives

in case two status changes had the same createdDate timestamp.

Using Spring's built-in Redis caching could be cool. Worth researching further and potentially replacing when we start using Redis more.

Using Spring's built-in Redis caching could be cool. Worth researching further and potentially replacing when we start using Redis more.

I know this is a late answer~ Actually I tried starting with Spring Data Redis. 2.x couldn't be used due to lack of compatibility with Spring Boot 1.X however and I had some problem that I no longe...

I know this is a late answer~
Actually I tried starting with Spring Data Redis. 2.x couldn't be used due to lack of compatibility with Spring Boot 1.X however and I had some problem that I no longer remember with latest 1.x of Spring Data Redis...

Revert "OLMIS-5037: changed versions on perttest for 3.3.1 release testing"

This reverts commit ed8f87a948986edd8c6c59b972c595f0d10db3ae.

Revert "changed reference-ui and requisition versions to patch release 3.3.1 on demo server"

This reverts commit e20687aebabbb8daccdbcc963b9c1abeb81293fd.

Simple Contract test would be awesome.

Simple Contract test would be awesome.

And which test is supposed to catch this scenario (using DTOs)? I just wonder why none of the existing tests caught this and I don't really see any new one that would fail if we started using DTOs ...

And which test is supposed to catch this scenario (using DTOs)? I just wonder why none of the existing tests caught this and I don't really see any new one that would fail if we started using DTOs again.

Łukasz Lewczyński What was the cause of this bug and do we have a test that reproduces this?

Łukasz Lewczyński What was the cause of this bug and do we have a test that reproduces this?

OLMIS-4917 Add contract tests to pipeline throttle category

The goal of this change is to prevent contract tests running

on the same node together with other pipeline builds. The

reason for this is to prevent conflicts running services like

db.