openlmis-ui-components

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Changed version to 6.0.1-SNAPSHOT

6.0.0 release

Revert "Revert "Revert "6.0.0 release"""

This reverts commit 33620fbcbe48d5bfe801db7bb087b52767df1e4e.

Revert "Revert "6.0.0 release""

This reverts commit 3472cce8d23ee50ddcfaee89e675543c7feb89b9.

Revert "6.0.0 release"

This reverts commit fd3d8d86c609e673173b24edd168ae5d6b0dce21.

6.0.0 release

Updated changelog

Changed version to 6.0.0-SNAPSHOT

6.0.0-RC2 release

what about zero?

what about zero?

is this string value? can we change it to if (value) { ?

is this string value? can we change it to
if (value) {
?

OLMIS-5144: added tests

OLMIS-5144: Fixed bug with formatting money values
OLMIS-5144: Fixed bug with formatting money values
OLMIS-5144: Fixed bug with formatting money values

Changed version to 6.0.0-SNAPSHOT

6.0.0-RC1 release

Done.

Done.

OLMIS-5002: Removed duplications

Yes, this is possible. I'm working on it.

Yes, this is possible. I'm working on it.

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-5002: Added email notifications after failures

OLMIS-5002: Added email notification after failure
OLMIS-5002: Added email notification after failure
Please fix duplicated description.

Please fix duplicated description.