openlmis-ui-layout

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
5.1.1 release

Changed version to 5.1.1-SNAPSHOT

5.1.1-RC2 release

Changed version to 5.1.1-SNAPSHOT

5.1.1-RC1 release

OLMIS-5002: Removed unnecessary bracket

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
Enabled eslint

    • -5
    • +5
    /src/openlmis-loading/loading.service.js
Fixed tech debt

OLMIS-4805: Updated sonar.sh and Jenkinsfile to enable branch analysis

maybe we could replace it with SONAR_BRANCH=$GIT_BRANCH?

maybe we could replace it with SONAR_BRANCH=$GIT_BRANCH?

OLMIS-4805: Enabled Sonar branch analysis
OLMIS-4805: Enabled Sonar branch analysis
Done

Done

OLMIS-4946: Push image and trigger reference-ui job after build stage on master

+1

+1

Sure

Sure

Should I also replicate this to UI components? Nikodem Graczewski, Łukasz Lewczyński, Mateusz Kwiatkowski

Should I also replicate this to UI components? Nikodem Graczewski, Łukasz Lewczyński, Mateusz Kwiatkowski

I'm OK with pushing image but I'm not sure about deploying to test always, if others are OK with it let do it in other services

I'm OK with pushing image but I'm not sure about deploying to test always, if others are OK with it let do it in other services