openlmis-reference-ui

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

5.1.0 release

Changed version to 5.1.0-SNAPSHOT

5.1.0-RC3 release

Changed version to 5.1.0-SNAPSHOT

5.1.0-RC2 release

Changed version to 5.1.0-SNAPSHOT

5.1.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
changed requisition and reference-ui versions for 3.3.1 release
changed requisition and reference-ui versions for 3.3.1 release
OLMIS-5037: released reference-ui 5.0.7

OLMIS-5037: changed version to next SNAPSHOT

OLMIS-5037: updated releasing components version to SNAPSHOTs

OLMIS-5037: updated Jenkisfile

bumped version to 5.1.0-SNAPSHOT

OLMIS-4963: Disable building image

OLMIS-4963: Disable building image

OLMIS-4963: Disable building image

OLMIS-4963: Update bower; disable tests

OLMIS-4963: Update bower; disable tests

OLMIS-4963: Update bower; disable tests