Salesforce deployment issue winter 22

[et_pb_section admin_label=”section”] [et_pb_row admin_label=”row”] [et_pb_column type=”4_4″][et_pb_text admin_label=”Text”]

Hi Guys, It’s been a long time since my last post. Been busy with so many works. Was working on various other technologies as well. Learned a lot of stuff, which I will bring in sooner to this platform.

For now, this post is about something which I faced recently, when Salesforce Winter 22 release was made available to the sandboxes.

Winter 22 release deployment issue

In my current org the deployments are done via Jenkins. Jenkins is free and has a great community support. NO, i am not promoting or anyway affiliated to Jenkins 🙂

So here is the flow for my deployments:

1. Developer creates a feature branch from Developer branch, when started working on the story
2. Once done the changes are committed to bitbucket (the source control repository)
3. That commit will be merged into the branches and that event will fire a request to Jenkins
4. Jenkins reads the commit and starts deployment to sandboxes and stuff

The issue after this winter 22 release was very wired and started just after the deployment. So was thinking something wrong with Salesforce and till date they don’t agree it’s their platform issue 🙂

Anyways, the issue is as below:

The issue

I made a code change in developer sandbox to a aura component. The component had 5 files.

1. .cmp file
2. .meta xml file
3. helper .js file
4. controller .js file
5. auradoc file

All of these files have some changes to them.

I created the pull request and merged it to branch and the deployment started. When the deployment was finished, what did I see ???

.js ,.aura files have all the changes I made. The meta file is missing and .cmp file did not have the changes I made in the source. This happens to the new component as well where the .cmp and xml files were missing entrely. If i deploy the same changes to a lower version sandbox summer 21 or some lower it works fine. My guess is something wrong with the ant metadata api Salesforce has. So, it’s an issue they should be looking at. But as per support this is not their issue.

Solution that worked !!!

Fortunately there was a workaround. Noticed, that when we have a destructive change file in the deployment, that’s when it happens. So removed the destructive change xml from the build and apparently it started working.

In case you are also having destructive changes in your build file remove it and try.

Conclusion

There are times when Salesforce do not own their issue and support has been a bit of low quality. But that’s my opinion. That’s it for Salesforce deployment issue winter 22. Hope this post will help someone in need 🙂 Keep reading and sharing.. Also do not forget to subscribe to the blog so you are notified as and when the contents are going live.

[/et_pb_text][/et_pb_column] [/et_pb_row] [/et_pb_section]