Community / Support Team,
I would like to bring attention to a significant discrepancy between the task description and the actual validation criteria in the deploy-job Jenkins pipeline lab.
The Issue:
The task explicitly states:
“Update the content of the file index.html under the same repository to Welcome to xFusionCorp Industries and push the changes to the origin into the master branch.”
However, the validation system actually checks for a random pre-seeded string that is already present in the Gitea repository (e.g., c899chnjunrk , wv9x96vbtjsw , etc.), NOT the welcome message stated in the instructions.
What Happens:
Participants who follow the instructions and update index.html to “Welcome to xFusionCorp Industries” will fail the validation.
Participants who ignore the instruction and deploy whatever string is already in Gitea will pass .
Evidence:
The attached console output shows a successful build where the pipeline deployed c899chnjunrk (the pre-seeded string) and passed validation — even though this directly contradicts the written requirement.
Recommendation:
Please review and align one of the following:
- Update the task description to reflect that participants should deploy the existing content from Gitea, OR
- Update the validation to accept “Welcome to xFusionCorp Industries” as the correct content.
Currently, the lab penalizes participants who follow the written instructions. This has caused confusion for multiple learners.
Thank you for your attention to this matter.