Jump to content
NJKirchner

Build Hook Info

Recommended Posts

I saw in the archive that the extension of Hook attributes is being expanded, but for the time being, is there any recommended workaround to getting some extra info post/pre-build?

An intermediate file that we can investigate?

 

Thanks

Share this post


Link to post
Share on other sites
I saw in the archive that the extension of Hook attributes is being expanded, but for the time being, is there any recommended workaround to getting some extra info post/pre-build?

An intermediate file that we can investigate?

 

Do you have anything specific you are looking for? What would you like to do?

Share this post


Link to post
Share on other sites

A key piece that is missing for us is to associate a build w/ the current versions of the files in SCC.

We're using P4 and the way that we'll overcome this is to, via a post build hook, make a P4 label w/ all the files in the build under SCC.

 

But somehow I need to name this new label, and preferably it would be based off of the package name and version.

 

So the idea is build a package->make a label.

Share this post


Link to post
Share on other sites
A key piece that is missing for us is to associate a build w/ the current versions of the files in SCC.

We're using P4 and the way that we'll overcome this is to, via a post build hook, make a P4 label w/ all the files in the build under SCC.

 

But somehow I need to name this new label, and preferably it would be based off of the package name and version.

 

So the idea is build a package->make a label.

 

Hi Norm,

 

I think it's a great idea to add Package Name and Version to the parameters passed into the build hooks.

 

You should be able to parse these parameters from the "Output Package File Path", which is accessible in the post-build hook parameters. Would that work for you, in the short term?

Share this post


Link to post
Share on other sites
I think it's a great idea to add Package Name and Version to the parameters passed into the build hooks.

PS: build hooks kick ass! We use the location to get everything we need to do a bunch of stuff, including automated documenation generation that gets built into the package and then linked to individual VIs. Thanks for exposing the functionality JKI ;)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.