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; } } }

What's the best way?

DavidMusser

Ok,

I have the following requirements...

1. Publish Editions Nightly on all branches
2. Deploy Nightly on all branches

I'm trying to decide if I want to use Deploy and Run to publish an Edition, and then do a deployment, or if I want to have them be seperate. I can think of reasons to do it either way, so I'm curious what others think.

Benefits of doing both at the same time, if I chance to a multi-day deployment but still scheduled I do not have change anything in the code, only the OD Schedule.

Benefit of doing them seperate is I can write a script that will run through the entire list of branches doing a publish command, and it would not be tied to OD

Anyway looking for thoughts.

David R. Musser
MCSE & MCP+I
Eye Street Software

Phone: 540-542-5257
Email: dmusser@eyestreet.com

Find more posts tagged with

Comments

Adam Stoller

I believe you need to be using at least OD5.6 in order to use a DNR to publish an edition and then deploy it -- because you would need to use the dnrDeploymentJob specification which was introduced in 5.6.

Other than that - I think it's pretty much of a 6-of-1/half-dozen-of-the-other kind of thing.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

DavidMusser

Yes, I'm using 6.01 of OD, the other question I have along this line to make it easier scripting wise... is when I call the DNR, the command... can I pass in information from the deployment configuration... i.e. source area. This way I would only have to name the go publish script in the command line, in the dnr section, and not pass a value for each one that I create in the OD Scheduler.

i.e. comand=publishSourceArea.. and that could be the same in all of my schedules vs doing something like

command=publish:srcarea=/default/main/myarea1 for one schedule
command=publish:srcarea=/default/main/myarea2 for another and so on...

since all of that information is already in the configuration...

David R. Musser
MCSE & MCP+I
Eye Street Software

Phone: 540-542-5257
Email: dmusser@eyestreet.com

Adam Stoller

If you're passing that information in via the command line with '-k' flags to the deployment using "variables" within the deployment configuration file - you should be able to use those same variables in the command line for your DNR script as well.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com