Problem Statement
As per @sasi Kumar Ganesan, there is no requirement to release service modules (e.g., mock-abis, mock-mv, ) to Nexus, as they are not intended for distribution. Including these services in the deployment process causes:
-
Unnecessary Overhead:
#* Services take additional time during the release pipeline, delaying the overall process.
-
Nexus Repository Clutter:
#* Service components, which are not reusable, unnecessarily occupy space and can lead to confusion.
-
Non-compliance with Guidelines:
#* Only artifact JARs (e.g., mock-sdk, mock-mds) are required to be published or released, but the current configuration does not differentiate between services and artifact modules.
Complete steps are given in below confluence page :
[https://mosip.atlassian.net/wiki/spaces/DevOps/pages/1521975377/Steps+to+Exclude+Services+from+Nexus+Publishing](https://mosip.atlassian.net/wiki/spaces/DevOps/pages/1521975377/Steps+to+Exclude+Services+from+Nexus+Publishing](https://mosip.atlassian.net/wiki/spaces/DevOps/pages/1521975377/Steps+to+Exclude+Services+from+Nexus+Publishing|smart-link))
Repos list :
-
admin-services
-
audit-manager
-
biosdk-services
-
captcha
-
commons
-
compliance-toolkit-batch-job
-
converters
-
digital-card-service
-
durian
-
esignet
-
esignet-mock-services
-
esignet-signup
-
id-authentication
-
id-repository
-
inji-certify
-
inji-verify
-
keycloak
-
keymanager
-
migration-utility
-
mimoto
-
mock-smtp-sms
-
mosip-automation-tests
-
mosip-compliance-toolkit
-
mosip-file-server
-
mosip-openid-bridge
-
mosip-ref-impl
-
mosip-token-seeder
-
oidc-demo-portal
-
otp-manager
-
packet-manager
-
partner-management-services
-
pre-registration
-
print
-
registration
-
registration-client
-
reporting
-
reporting
-
resident-services
-
tusd-server
-
websub
NOTE : Make sure only mosip services needs to be exlude from being published or released to Nexus.
🔗 Linked Issues
ISSUE
- MOSIP-37917
Status: Closed
- MOSIP-37874
Status: Closed
- MOSIP-38279
Status: Testing
- MOSIP-44934
Status: In Progress
Problem Statement
As per @sasi Kumar Ganesan, there is no requirement to release service modules (e.g., mock-abis, mock-mv, ) to Nexus, as they are not intended for distribution. Including these services in the deployment process causes:
Unnecessary Overhead:
#* Services take additional time during the release pipeline, delaying the overall process.
Nexus Repository Clutter:
#* Service components, which are not reusable, unnecessarily occupy space and can lead to confusion.
Non-compliance with Guidelines:
#* Only artifact JARs (e.g., mock-sdk, mock-mds) are required to be published or released, but the current configuration does not differentiate between services and artifact modules.
Complete steps are given in below confluence page :
[https://mosip.atlassian.net/wiki/spaces/DevOps/pages/1521975377/Steps+to+Exclude+Services+from+Nexus+Publishing](https://mosip.atlassian.net/wiki/spaces/DevOps/pages/1521975377/Steps+to+Exclude+Services+from+Nexus+Publishing](https://mosip.atlassian.net/wiki/spaces/DevOps/pages/1521975377/Steps+to+Exclude+Services+from+Nexus+Publishing|smart-link))
Repos list :
admin-services
audit-manager
biosdk-services
captcha
commons
compliance-toolkit-batch-job
converters
digital-card-service
durian
esignet
esignet-mock-services
esignet-signup
id-authentication
id-repository
inji-certify
inji-verify
keycloak
keymanager
migration-utility
mimoto
mock-smtp-sms
mosip-automation-tests
mosip-compliance-toolkit
mosip-file-server
mosip-openid-bridge
mosip-ref-impl
mosip-token-seeder
oidc-demo-portal
otp-manager
packet-manager
partner-management-services
pre-registration
print
registration
registration-client
reporting
reporting
resident-services
tusd-server
websub
NOTE : Make sure only mosip services needs to be exlude from being published or released to Nexus.
🔗 Linked Issues
ISSUE
Status: Closed
Status: Closed
Status: Testing
Status: In Progress