nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LS WF, no deployments

nipper

New setup. trying to use LS workflow, but the deployments are not heading out. I changed the bean and rebuilt the GUI. Not certain how to debug.

There is no indication that any deployments were pushed. Nothing in the logs anywhere, tips on debugging this ? Where to start ?

Andy

Find more posts tagged with

Comments

vpatel

Is this OOTB PLC WF? Anything in the servletd log? That'll be the first place to start and then go to OD log files. Also turn up the level of logging for relevant packages.

nipper

It was a hack of the OOTB PLC WF. Renamed production because I have 3 different prod servers, depending on the branch.

I restored the OOTB and one bean an it works, so I am applying once change at a time.

Nothing in the servlet D log, no OD logs, so it seems as if the prod deployment was being skipped completely

Faizi

Do you have hack the "Deploy to Production" task?
What i understand, you have written your own code (bean class) for deploying the content to 3 different servers.
Or you have 3 different Deployment task for different server?

All the Servlet container (Tomcat) error/exception logged into servletd_out.log file. If the bean class is being called then logging should be in that file. Otherwise workflow is not able to call that class.

nipper

Do you have hack the "Deploy to Production" task?
What i understand, you have written your own code (bean class) for deploying the content to 3 different servers.
Or you have 3 different Deployment task for different server?

All the Servlet container (Tomcat) error/exception logged into servletd_out.log file. If the bean class is being called then logging should be in that file. Otherwise workflow is not able to call that class.

No not touching the task. I have it set that if I am have branch1, I use the Prod1 bean, branch2 and Prod2, etc.

FormAPI sets the correct destination (I think), but it *seems* as if the task is being bypassed completely, so I am working on the ProductionDeploy flag.

Faizi

No not touching the task. I have it set that if I am have branch1, I use the Prod1 bean, branch2 and Prod2, etc.

FormAPI sets the correct destination (I think), but it *seems* as if the task is being bypassed completely, so I am working on the ProductionDeploy flag.

It means you didn't change/add any task into the workflow. You have just hack the workflow instantiation screen for selecting branch and corresponding deployment server. Now in workflow using script variable you are setting that deployment server through conditional link (as i understand). Is it right?