Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement Request Summary : Externalizing profile, 'other' option given in POM wizard, does not work if property file (profile) is referenced using relative path. We are using Jenkins job to build EAR file using BW6 Application code & Profile property file (DEV/QA/PROD etc) residing in separate folders in Git Repo and eventually another jenkins job to deploy the built EAR to runtime (TEA). #399

Closed
bankarswapnil opened this issue Jan 7, 2020 · 11 comments
Assignees

Comments

@bankarswapnil
Copy link

My setup[Windows10_64bit+BW650+TEA230+EMS851+TIB_BW_Maven_Plugin_240]

Steps to reproduce the issue:
Main Issues :

  1. If Application has Application level properties set, Build fails
    ---->Workaound : delete the app level property settings and retry.
  2. Relative profile path does not work, ex. ../QA.substvar
    Subsequent couple of issues I have observed,
  3. Although am deleting application from TEA before re-deployment,
    a. Getting exception as 'Failed to remove stats of Application [1.0|Greetings.application] in AppSpace [MyAppSpace] of Domain [MyDomain]'
    but actually it does delete the application.
    b. am able to see earlier/old deployment endpoint URL instances in TEA on subsequent deployments.
  4. Although, we have selected profile as 'other' pointing to QA (which is not a default profile),
    a. Deployed application endpoint still points to default profile property values, say HTTPPort:8071 instead of 8383.
    workaround : just restart the application

Additional environment details if any:

Describe the results you received:

Describe the results you expected:
In POM, Relative path is supported ? or only absolute path is supported ?

Additional information you deem important (e.g. issue happens only occasionally):
I will attach a WebEx to convey steps followed to reproduce the issue.

Thanx,
-Swapnil
CICD_Ext_Profile_Failed_3.zip

@swapnilbankar
Copy link

Hello Sujata,
If possible can we have a quick call. We have to showcase demo to client before this week ends.
Let me know your suitable time.
Thanx,
-Swapnil

@SujataDarekar
Copy link
Contributor

@bankarswapnil Please find my below comments:

  1. If Application has Application level properties set, Build fails
    --> Could you please share the detailed steps to reproduce this issue. It will really help to reproduce issue in our environment

  2. Relative profile path does not work, ex. ../QA.substvar
    --> We do not support the relative path option

  3. Although am deleting application from TEA before re-deployment,
    a. Getting exception as 'Failed to remove stats of Application [1.0|Greetings.application] in AppSpace [MyAppSpace] of Domain [MyDomain]'
    but actually it does delete the application.
    b. am able to see earlier/old deployment endpoint URL instances in TEA on subsequent deployments.
    --> This issue does not seem from maven side but still we will check and let you know.

  4. Although, we have selected profile as 'other' pointing to QA (which is not a default profile),
    a. Deployed application endpoint still points to default profile property values, say HTTPPort:8071 instead of 8383.
    workaround : just restart the application
    --> will look into this.

@swapnilbankar
Copy link

swapnilbankar commented Jan 13, 2020 via email

@swapnilbankar
Copy link

Hello Sujata,
By any chance, you are able to find the way we can use Jenkins job to build EAR file using BW6 Application code & Profile property file residing in separate folders in Git Repo and Deploy the EAR to TEA ?
This is the only part blocking in our BW6 CICD pipeline framework using BW6 Maven plugin.
Help on this front is highly appreciated.
Thanx,
-Swapnil

@SujataDarekar
Copy link
Contributor

@bankarswapnil Currently we only absolute path support for external profile where external profile should be present on the same machine. Now For jenkins, we will required code changes where the external profile will be downloaded from mentioned URL.

@swapnilbankar
Copy link

Hi Sujata,
Does that mean, you have created a enhancement request to support for external profile where external profile can reside on different folder of git repo and path can have either link or relative path of profile?
If that is the case, can you share the time lines by when we can have this feature implemented ?

Meanwhile, if you know any workarounds (possibly from existing clients who are using the plugin)
please do share.

Thanx,
-Swapnil

@SujataDarekar
Copy link
Contributor

@swapnilbankar You can create the new enhancemnt with your requirement So that I will plan it accordingly.

@swapnilbankar
Copy link

Hi Sujata,
Can you transform this issue into Enhancement (or assign label as Enhancement) ? I could not find option for creating Enhancement though.

Thanx,
-Swapnil

@swapnilbankar
Copy link

Hi Sujata,

Did you transfer the issue into enhancement ? or let me know how to create it ?
This requirement is very crucial for many customers and we are stuck on this.
Your help will be highly appreciated.

Thanx,
-Swapnil

@SujataDarekar
Copy link
Contributor

@bankarswapnil I have marked this issue as enhancement. Please just change the issue title with requirement summary

@bankarswapnil bankarswapnil changed the title Externalizing profile, 'other' option given in POM wizard, does not work completely. Enhancement Request Summary : Externalizing profile, 'other' option given in POM wizard, does not work if property file (profile) is referenced using relative path. As a part of BW6 Accelerators, we are in process of developing BW6 CICD pipeline framework using BW6 Maven plugin. We are using Jenkins job to build EAR file using BW6 Application code & Profile property file (DEV/QA/PROD etc) residing in separate folders in Git Repo and eventually another jenkins job to deploy the built EAR to runtime (TEA). As I understood from you, current plug-in (2.4.0)does support absolute path for external profile where external profile should be present on the same machine. And For jenkins, you will require code changes where the external profile will be downloaded from mentioned URL. Feb 19, 2020
@bankarswapnil bankarswapnil changed the title Enhancement Request Summary : Externalizing profile, 'other' option given in POM wizard, does not work if property file (profile) is referenced using relative path. As a part of BW6 Accelerators, we are in process of developing BW6 CICD pipeline framework using BW6 Maven plugin. We are using Jenkins job to build EAR file using BW6 Application code & Profile property file (DEV/QA/PROD etc) residing in separate folders in Git Repo and eventually another jenkins job to deploy the built EAR to runtime (TEA). As I understood from you, current plug-in (2.4.0)does support absolute path for external profile where external profile should be present on the same machine. And For jenkins, you will require code changes where the external profile will be downloaded from mentioned URL. Enhancement Request Summary : Externalizing profile, 'other' option given in POM wizard, does not work if property file (profile) is referenced using relative path. We are using Jenkins job to build EAR file using BW6 Application code & Profile property file (DEV/QA/PROD etc) residing in separate folders in Git Repo and eventually another jenkins job to deploy the built EAR to runtime (TEA). Feb 19, 2020
@bankarswapnil
Copy link
Author

Hi Sujata,
I tried to abstract an Enhancement Summary as much as possible.
Hope you have my all webex shared on this to reproduce the issue (https://github.com/TIBCOSoftware/bw6-plugin-maven/files/4031216/CICD_Ext_Profile_Failed_3.zip)

Looking forward to have this feature as early as possible.
Thank you for all support.

-Swapnil

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants