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
bumped version to 5.1.0-SNAPSHOT

Add missing module name.

Add missing module name.

Allows getting?

Allows getting?

remove this

remove this

So...... this line is replacing placeholders in openlmis.js with env variables and saving result to some temp file. The problem is that if envsubst encounters any ${SOMETHING} and there is no SOMET...

So...... this line is replacing placeholders in openlmis.js with env variables and saving result to some temp file. The problem is that if envsubst encounters any ${SOMETHING} and there is no SOMETHING variable exported empty string will be placed there, unfortunately there is one place in some library that uses "${". The only way to avoid this is to pass every env variable name that we want to replace to envsubst so I'm passing those using "`printf ${%s}.......

Yes you are right so we can stay with current approach https://review.openlmis.org/static/ogdo0b/2static/images/wiki/icons/emoticons/wink.gif

Yes you are right so we can stay with current approach

Then we would have a lot of code duplication

Then we would have a lot of code duplication

A lot of ng-if here. Maybe it would be better to have two files and select correct based on flag? Not sure if this is a easy task in angular/js

A lot of ng-if here. Maybe it would be better to have two files and select correct based on flag? Not sure if this is a easy task in angular/js

http://mrwgifs.com/wp-content/uploads/2013/10/The-Big-Lebowski-WTF-Expression-While-Checking-Things-Out.gif