| Author |
Message
|
| pradeepkumartangudu |
 Posted: Thu Apr 30, 2015 2:13 am Post subject: Adding some information to the build BAR file |
 |
|
Newbie
Joined: 07 Aug 2014
Posts: 7
|
Hi Team,
I created a BAR file with ANT tool. Now i need to add some information to that build BAR file .
Information like:
1)Build Release.
2)Build by User_id.
How such type of information we can add to BAR. if you Know could you please suggest me. |
|
| Back to top |
|
 |
| paustin_ours |
| Posted: Thu Apr 30, 2015 3:28 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
| you may want to think about adding those information to the flow itself. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 30, 2015 4:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| paustin_ours wrote: |
| you may want to think about adding those information to the flow itself. |
The bar file is simply a container. Nothing about the bar file survives the deploy process to be recorded in the broker. Also (and dependant on your build process), the fact that the bar file is built by a specific id doesn't indicate authorship of the flow.
It's probably more valuable (and very simple) to add the release (which WMB & IIB refer to as "Version") and others infomation (like author's id) to flows or even individual nodes / ESQL. I'd strongly recommend that tack for your use case.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pradeepkumartangudu |
| Posted: Thu Apr 30, 2015 4:21 am Post subject: |
|
|
Newbie
Joined: 07 Aug 2014
Posts: 7
|
Hello paustin
Adding UDP to Flows we Know.But we need to give above information in BAR level Could you please suggest any Other way to me. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 30, 2015 4:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pradeepkumartangudu wrote: |
| Adding UDP to Flows we Know. |
And that's not what @paustin_ours or myself are talking about. A UDP is a property visiable to the code at run time. What you're talking about is meta data associated with the code, and that's what we're talking about too.
| pradeepkumartangudu wrote: |
| But we need to give above information in BAR level |
You need to explain clearly why the release number and user id need to be associated with the bar file and not with the code elements it contains. What are you using this information for and, most importantly, how are you reading it back later?
Consider this use case, and explain how you intend this to work:
You have set the user and release on the bar file as you say here. At some later point during testing or production, you suspect that the code running in the broker is the wrong release. How will you check the release number associated with the running code?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 30, 2015 4:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Why does this information need to be in the contents of the bar file, rather than in the name of the bar file?
A Bar file is just a zip file. It can have METADATA in it. |
|
| Back to top |
|
|
| pradeepkumartangudu |
| Posted: Thu Apr 30, 2015 5:00 am Post subject: |
|
|
Newbie
Joined: 07 Aug 2014
Posts: 7
|
| We can add this (build by user,build version ,build release) in broker.xml ? any one U. As per my requirement after build compilation that bar files bring to IIB Tool kit.When the developer view this bar file in IIB toolkit we have property view in that view there we see (bar name , bar file path, bat type,Last modified ) such information comes by default. In same view we need to see (build by user,build version ,build release) information. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 30, 2015 5:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pradeepkumartangudu wrote: |
| We can add this (build by user,build version ,build release) in broker.xml ? any one U |
Yes - as people keep saying, these are properties of the flows and code that the bar file contains.
| pradeepkumartangudu wrote: |
| . As per my requirement after build compilation that bar files bring to IIB Tool kit. |
Why? Why would you build code in the toolkit, feed it through ANT to build a bar file and then pull the bar file back into the Toolkit? What value does that offer? Why are you doing that?
| pradeepkumartangudu wrote: |
| When the developer view this bar file in IIB toolkit we have property view in that view there we see (bar name , bar file path, bat type,Last modified ) such information comes by default. In same view we need to see (build by user,build version ,build release) information. |
Why? I know the view you mean, but if the developer actually opens the bar file there's a version column next to all the artifacts.
You also have not explained how you would deal with my use case?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pradeepkumartangudu |
| Posted: Thu Apr 30, 2015 6:14 am Post subject: |
|
|
Newbie
Joined: 07 Aug 2014
Posts: 7
|
We build this bar files with our own ant script only, not with IIB Tool kit.
As per our requirement we need to add this information (build by user,build version ,build release) to bar file. so can we add this information or not could you suggest me?. my team will open this bar file in there IIB tool kit at that time they need this information so we requesting. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 30, 2015 6:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Why does this information need to be inside the bar file, rather than in the name of the bar file?
What use is this information actually going to be put to?
What happens if the contents of a bar file are replaced, without changing this data? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 30, 2015 6:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pradeepkumartangudu wrote: |
| We build this bar files with our own ant script only, not with IIB Tool kit. |
Weird.
| pradeepkumartangudu wrote: |
| As per our requirement |
What requirement? "We need to add this information" is not a requirement; what are you required to do? What do you use this information for?
| pradeepkumartangudu wrote: |
| so can we add this information or not |
Not. The properties view you quote is looking at the properties of the bar file, which are the same properties that you'd see in Windows Explorer (though I accept the modified date and file path are formatted differently).
| pradeepkumartangudu wrote: |
| could you suggest me? |
We keep suggesting, but you seem bound and determined to track the bar file not the code it contains. We suggest tracking the code because it's valuable to do that, easy to do that and is useful past a developer inexplicably checking to see when a bar file was built. The key disadvantages with our suggested methods appear to be that the developer would have to double click the bar file, and look slightly above where they're used to looking, and you seem to feel these make the suggested solution unacceptable.
So you'll need to identify an alternate solution.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 30, 2015 6:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| What happens if the contents of a bar file are replaced, without changing this data? |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Thu Apr 30, 2015 9:50 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
| mqjeff wrote: |
| Why does this information need to be inside the bar file, rather than in the name of the bar file? |
You need to stop and think about what is being asked of you and how it applies to broker when people here are asking these sorts of questions. It indicates what you want to do has not been found to be useful with broker or even worse, gives a false impression of something.
These sorts of "issues" pop up when people from other technology stacks (looking at you Java) think that their methodologies will work just fine with other tech. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 30, 2015 10:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| joebuckeye wrote: |
| These sorts of "issues" pop up when people from other technology stacks (looking at you Java) think that their methodologies will work just fine with other tech. |
That's quite a good catch - you can see how this "requirement" would come up if someone thought a bar file was an ear file with a typo.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
