ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update nexus: fix conflicts and sync local changes

Browse Source
This commit is contained in:
Shen Wei
2026-04-26 12:06:50 +08:00
parent 191797c01b
commit f09834b5a5
2443 changed files with 254323 additions and 255154 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
knowledgebase/csd-wiki/ICSD/Check-isolated-tenants-per-farm_686073691.md
View File

@@ -1,24 +1,24 @@
# Check-isolated-tenants-per-farm_686073691
## Introduction
This document is to introduce how to use Jenkins job to check isolated tenants per farm before upgrade.
## Use Jenkins job to check isolated tenants
1. Open Jenkins job. [https://saas-ops.itsma-ng.net/job/ESM-SaaS-Check-Isolated-Tenants/](https://saas-ops.itsma-ng.net/job/ESM-SaaS-Check-Isolated-Tenants/)
![](attachments/686073691/686073675.png)
2. Click "Build with Parameters", choose "farm\_name" and Click "Build"
3. After the job is completed,check job's status.
1. If job is green(Success),it means that there is no isolated tenants on this farm. Open the build, and Click "Console Output", at the end of the output, it looks like this.
![](attachments/686073691/686073676.png)
2. If job is red(Failed),it means that there is isolated tenants on this farm. Open the build, and Click "Console Output", scroll down to the ending of the output, check the detailed check results.
The job checks SMAX tenant status firstly, if some tenant's status isn't ACTIVE or INACTIVE, the SMAX check result will show tenant ID like below.
![](attachments/686073691/686073679.png) ![](attachments/686073691/686073681.png)
## Attachments:
[image2023-11-14\_16-41-3.png](attachments/686073691/686073675.png) (image/png)
[image2023-11-14\_16-52-26.png](attachments/686073691/686073676.png) (image/png)
[image2023-11-14\_16-55-32.png](attachments/686073691/686073679.png) (image/png)
[image2023-11-14\_16-57-24.png](attachments/686073691/686073681.png) (image/png)
# Check-isolated-tenants-per-farm_686073691
## Introduction
This document is to introduce how to use Jenkins job to check isolated tenants per farm before upgrade.
## Use Jenkins job to check isolated tenants
1. Open Jenkins job. [https://saas-ops.itsma-ng.net/job/ESM-SaaS-Check-Isolated-Tenants/](https://saas-ops.itsma-ng.net/job/ESM-SaaS-Check-Isolated-Tenants/)
![](attachments/686073691/686073675.png)
2. Click "Build with Parameters", choose "farm\_name" and Click "Build"
3. After the job is completed,check job's status.
1. If job is green(Success),it means that there is no isolated tenants on this farm. Open the build, and Click "Console Output", at the end of the output, it looks like this.
![](attachments/686073691/686073676.png)
2. If job is red(Failed),it means that there is isolated tenants on this farm. Open the build, and Click "Console Output", scroll down to the ending of the output, check the detailed check results.
The job checks SMAX tenant status firstly, if some tenant's status isn't ACTIVE or INACTIVE, the SMAX check result will show tenant ID like below.
![](attachments/686073691/686073679.png) ![](attachments/686073691/686073681.png)
## Attachments:
[image2023-11-14\_16-41-3.png](attachments/686073691/686073675.png) (image/png)
[image2023-11-14\_16-52-26.png](attachments/686073691/686073676.png) (image/png)
[image2023-11-14\_16-55-32.png](attachments/686073691/686073679.png) (image/png)
[image2023-11-14\_16-57-24.png](attachments/686073691/686073681.png) (image/png)