Open 0ptaq0 opened 6 days ago
@0ptaq0 that might be a bug :) I investigate :)
There are many sfdx-hardis features embedded within hardis:project:deploy:sources:dx, including JIRA ones.
hardis:source:deploy currently only embeds the errors comment.
The corresponding call of your use case would be the following:
sfdx hardis:project:deploy:sources:dx --check \
--packagexml 'dx-delta/package/package.xml' \
--testlevel $TEST_LEVEL \
--targetusername $SF_USERNAME
you would also need to define the following variables in your gitlab-ci.yml
variables:
SFDX_DEPLOY_WAIT_MINUTES=300
PACKAGE_XML_TO_DELETE=dx-delta/destructiveChanges/destructiveChanges.xml
Please can you try to check if it works on your project ? :)
Additional note: after merge, if you use the following script, you will benefit of QuickDeploy :)
sfdx hardis:project:deploy:sources:dx \
--packagexml 'dx-delta/package/package.xml' \
--testlevel $TEST_LEVEL \
--targetusername $SF_USERNAME
Thank you Nicolas, JIRA integration now works like a charm :)
Regarding packagexml
I needed to place it under ./manifest folder
I have only one issue with destructive changes, the env var PACKAGE_XML_TO_DELETE
does not seem to take any effect. Also, like with packagexml
I placed destructiveChanges.xml
under ./manifest
but also had no success, neither on validation nor deployment.
[sfdx-hardis] Empty package.xml: nothing to deploy
[sfdx-hardis] No deployment to perform
[sfdx-hardis] hardis:project:deploy:sources:dx execution time 0:00:06.365
My flow looks like this:
Run Pipeline
button on Merge Request which initiates deploymentSFDX Git Delta creates a diff package and package.xml + destructiveChanges.xml which I then archive and pass to sfdx-hardis.
Also as mentioned above I am using custom CICD and embedded sfdx-hardis so I do not have any .sfdx-hardis.yml
in my repository, that may also be an issue?
As a workaround, I can also check if destructive Changes are not empty and then call yet another sfdx deployment command, but the best would be to fit everything in one shot ;)
@0ptaq0 do you know that sfdx-git-delta is also embedded within sfdx-hardis and project:source:deploy:dx ? :)
https://sfdx-hardis.cloudity.com/salesforce-ci-cd-config-delta-deployment/
I'm wondering if you are not trying to reproduce the standard sfdx-hardis pipeline :)
https://github.com/hardisgroupcom/sfdx-hardis/blob/main/defaults/ci/.gitlab-ci.yml
https://github.com/hardisgroupcom/sfdx-hardis/blob/main/defaults/ci/.gitlab-ci-config.yml
Can you compare with your pipeline ?
I feel the only difference is that
If you want, please share your gitlab-ci.yml and i'll tell you :)
I am using sfdx hardis in my custom Gitlab pipeline. Pipelines are running bounded to Merge Requests, 'Enable merged results pipelines' option is enabled >> "This pipeline ran on the contents of the merge request combined with the contents of the target branch"
I have added following env variables:
My validation/deployment command looks almost the same, only difference is
--checkonly
flag:During deployment I would expect some success message posted to Merge Request comment and optionally to related JIRA in MR's description, but I am getting below:
However, posting error comments works just fine:
And then I can see a comment with great tips on how to solve errors ;)
Also, nothing is posted to JIRA but that's a minor item, I would just need a success comment to Merge Request at this moment.
What am I missing?