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

Automatically publish editions

Tim__D

I want to publish editions automatically on a schedule. Once a week or bi-weekly. I'd also like to send an email when this occurs. Can someone point me in the right direction or provide a link to some documentation?

Thanks,

- Tim

Find more posts tagged with

Comments

iwovGraduate

Can be done in many different ways:

One way is to write a script that will calll iwpublish command and send an email and run it as cron/at job.

Documentation:
I don't think you will find a step-by-step instructions on this with examples (unless you want to pay to somebody who will provide this) since this is not OOTB functionality. Search the forums and KBs - you might find something useful.
Read documentation on iwpublish CLT.
How to write a script to send emails, etc., and run it on schedule - I guess you can google it.

nipper

Depends on what you want. If this is on a schedule it isbest not done in WF. Set up a cron job (if Unix)
to iwpublish and then iwdeploy.

Easy. You can also use the OD scheduler, though you need a publish event before.

HTH

Andy

Adam Stoller

The recent versions of OD 5.6, 6.x allow you to perform the publish event via a dnrDeploymentJob *before* the actual deployment - so that you don't have to have a wrapper script around the invokation of OD. Earlier versioins of OD didn't have dnrDeploymentJob and thus you needed the wrappre script.

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

gzevin

if you are on Solaris, I can post a very simple email script and a publish edition script with a crontab sample

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

CSVGroupReport.rptdesign

Tim__D

I'm on a windows box running 5.52.

gzevin

here's some code to publish editions - modify it for windows, though


use TeamSite::Config;
use strict;

my $branch_name = shift;

die "usage: publish_edition branch_name" unless $branch_name;
my $DEBUG=1;


#
# Set some global strings to run iw commands
my $iw_home =  TeamSite::Config::iwgethome();

my $fname = "\/tmp\/publish_edition.tmp"; # debug file name

if ($DEBUG) {
 open (DEBUG,">$fname")|| die "Could not open $fname: $!";
}

# we can now publish a new edition

#iwpublish main/branch1 STAGING ed_002 'checkpoint'
my $publish_cmd = "$iw_home\/bin\/iwpublish \-g  $branch_name STAGING \'Published_by_publish_edition\.ipl\'";
print DEBUG "publish_cmd: $publish_cmd \n" if $DEBUG;
`$publish_cmd`;

close DEBUG;

as for mail - there is a well know mail sending utility blat.exe... And there are heaps of examples on the net how to use it with perl. Put it together woth publish edition code, and then you can schedule its execution in windows.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

Greg -
What the heck are all those back-slashes for? You don't need them - they only detract from the readability of the code.
Why use blat when you can use Mail: Smiley Frustrated

endmail or Mail::Mailer? - which are more efficient process-wise and more portable platform-wise.
You also might want to use File::Temp's tempfile() routine for creating temporary / debugging files. Something like:#!.../iwperl
use strict; # I prefer to put this first, unless there's a good reason not to
use warnings; # TS6.x and above
use File::Temp qw(tempfile);
use TeamSite::Config;
(my $me = $0) =~ s|^.*[/\\]||;
die "usage: $me branch_name" unless @ARGV;
my $branch_name = shift;
my $DEBUG = 1;
my $iwhome = TeamSite::Config::iwgethome();
my($dfh, $fname) = tempfile("pubedxxxxx") if ($DEBUG);
my $publish_cmd = qq($iwhome/bin/iwpublish -g $branch_name STAGING "Published by $me");
print $dfh "publish_cmd: $publish_cmd\n" if ($DEBUG);
my @results = qx($publish_cmd);
close($dbh);
...

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

Migrateduser

Just an addendum to what Ghoti said, you can upgrade to OD 6 and stay on TS 5.5.2.

hth

lissa

gzevin

Adam,

yes, I even have a perl module for logging, but that script probably was not even written by me, and is so simple, so I did not feel changing it.

as for blat.exe - it is matter of choice, again.

PS. your instisting on a certain coding style in perl starts to amuse me

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

I don't insist on the coding style - I simply like to promote it ;-)

The use of blat.exe is certainaly okay - but not portable - if you don't care about portability then it doesn't matter if you use that or any other mechanism for sending email.

The use of File::Temp qw(mktemp) is again a portability thing - it also provides some very nice features for real *temporary* files (such as automatic unlinking after the program ends)

Having a logging module is a good thing - I was simply commenting on the code as shown.

I still don't understand the back-slashes you had in the original code.

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