| Author |
Message
|
| EricCox |
 Posted: Tue Oct 01, 2013 6:17 am Post subject: Bar File Meta Data Version Tag |
 |
|
Master
Joined: 08 Apr 2011
Posts: 292
|
To all,
How do I tag a bar file with a version meta data tag so that our deployment automation tool can be told to deploy a particular version?
Right now we have the tool scripted to pick up a bar file name, but we need to ensure we deploy a particular version of the bar.
All help is always greatly appreciated.
Thanks,
EMC |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Oct 01, 2013 6:30 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| EricCox |
| Posted: Tue Oct 01, 2013 6:34 am Post subject: Pure Compute Node and ESQL |
|
|
Master
Joined: 08 Apr 2011
Posts: 292
|
We are primarily a pure WMB Compute Node/ESQL shop. We do not build and deploy very much JCN/jar.
Isn't there anything for bar files?
Thanks |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Oct 01, 2013 6:37 am Post subject: Re: Pure Compute Node and ESQL |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| EricCox wrote: |
We are primarily a pure WMB Compute Node/ESQL shop. We do not build and deploy very much JCN/jar.
Isn't there anything for bar files?
Thanks |
You have absolutely no JCNs in your code ?
You can add the version keyword to the beginning of ESQL files :
| Code: |
| -- $MQSI_VERSION=1.0.0.1MQSI$ |
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 01, 2013 6:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Oct 01, 2013 7:11 am Post subject: Re: Pure Compute Node and ESQL |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
You can add the version keyword to the beginning of ESQL files :
| Code: |
| -- $MQSI_VERSION=1.0.0.1MQSI$ |
|
Yeah and watch some releases of subversion/tools either mangle them or ignore them totally.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Oct 01, 2013 7:17 am Post subject: Re: Pure Compute Node and ESQL |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
You can add the version keyword to the beginning of ESQL files :
| Code: |
| -- $MQSI_VERSION=1.0.0.1MQSI$ |
|
Yeah and watch some releases of subversion/tools either mangle them or ignore them totally. |
Thats why we use the meta-inf folder in the jar. Alas, Eric's environment is severely biased against them.
Java has drawbacks, I'm not saying that it doesn't. But no more or less than any other language. People should get over it. Whether you use ESQL, Java, .Net, PHP, or any other Compute node, they all work and do pretty much the same thing.
As Nancy Pelosi says, "We have to pass the bill before we know whats in it." Even better : Margaret Thatcher ( RIP April 8, 2013 ), "the problem with other people's money is, you eventually run out."
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 01, 2013 7:21 am Post subject: Re: Pure Compute Node and ESQL |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| As Nancy Pelosi says, "We have to pass the bill before we know whats in it." |
Unless you read it. I know I'm not that familiar with American legislation but I suspect they write it somewhere. Or is it Schrodinger's Legislation?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mapa |
| Posted: Wed Oct 02, 2013 9:00 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
You could solve your problem by just including the version in the bar-file name...
We keep it fairly simple and do it like this.
CI tool (we manually trigger the job instead of using webhooks or polling trunk):
- bump version number of the CI build job
- create a tag in Subversion that contains the version number
- export the tag (to get correctly updated MQSI keywords in the built bar)
- build the bar file(s)
- packages the bar file with all the other stuff such as automated installscripts, mqsc, docs etc.
- publish the built distributionpackage (one .zip and one .tar.gz) which contains the versionnumber.
- the deployjob then uses the versionnumber to fetch the correct package and deploys it to the environment for that job. (CI tool uses slightly different approaches and there is one build server that deploys to test, and then there is one deploy server for QA and Production, the Prod server only fetches stuff from already built (and tested) deploypackages in Subversion)
Works perfectly but there are probably more fancy ways of doing it.
But at least we succeed with the build once - deploy many that is an important part. |
|
| Back to top |
|
|
|
|
