Automated deployments using Team Foundation Server?

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
Novak
Participant
Posts: 97
Joined: Mon May 21, 2007 10:08 pm
Location: Australia

Automated deployments using Team Foundation Server?

Post by Novak »

Hi experts,

Would you please be able to share your experiences with setting up automated deployment of DataStage, Information Analyzer and ISD jobs? What is the best approach these days?

We will have 2 release Microsoft TFS Servers to support our non-Prod and Prod ETL servers. Looking to avoid installing IIS client on these release servers if possible but still need to be able:

- deploy IA and DS jobs at minimum
- compile DataStage jobs on target server after deployment automatically
- capture deployment/compilation status logs

Regards,

Novak
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

Why compile objects on your target hosts when you can deploy the executables in the isx file?

istools.sh should be used to import/export your jobs (isx format) via the command line.
FranklinE
Premium Member
Premium Member
Posts: 739
Joined: Tue Nov 25, 2008 2:19 pm
Location: Malvern, PA

Post by FranklinE »

Novak, our protocol as an example:

Code and unit test in DEV, export design only.

Import design to INT (integration), compile and test.

Export design and executable from INT.

Import design and executable to SAT/CAT (test).

Run final tests.

Export design and executable from SAT/CAT (or, with no test fails, use the export from INT), for import to PRD.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson

Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
Novak
Participant
Posts: 97
Joined: Mon May 21, 2007 10:08 pm
Location: Australia

Post by Novak »

Hi guys,

I have not explained this well.
The focus is on the automated deployment tools, ie. Jenkins, Mamboo or TFS in our case.
What are some of the best practices these days.
An option could be to have IIS objects:

1) compiled
2) exported
3) stored into version control
4) tagged with the relevant release ID (or sprint name)

but what would be the best approach beyond that? TFS can only use istool if IIS client is installed on its server. Or can istool be accessed from release server remotely?

Cheers,

Novak
stuartjvnorton
Participant
Posts: 527
Joined: Thu Apr 19, 2007 1:25 am
Location: Melbourne

Post by stuartjvnorton »

Might be worth checking this out:

https://www.mettleci.com/
Post Reply