search

xebialabs-community / xlr-xlrelease-plugin

Create and start another XL Release template from a parent template
MIT License
3 stars 14 forks source link

Create and Start Sub Release, when using a template in a folder #18

Closed vsorrentinomed closed 7 years ago

vsorrentinomed commented 7 years ago

hi - With the 6.0.x version of XLRelease, when using version 1.9.0 of this plug in, I am seeing the following error when trying to kick of another XLRelease template from within a Release template. Response: com.xebialabs.xlrelease.domain.folder.Folder cannot be cast to com.xebialabs.xlrelease.domain.Release

I believe the issue is when you have a template inside the XLRelease's new Folder capabilities, the template ID is no longer just a two pathed id, it is now 3.

pre 6.0.1 Applications/Release793057504 post 6.1.0 Applications/Folder129167294/Release9578172

Therefore the code that is doing the split expecting just 2 values to be returned is now returning the Folderxxxx ID and that can't be casted into what is expected, the Releasexxxx.

I have templates in folders and not in folders so can this be handled for both?

Thank you Vicky

jdewinne commented 7 years ago

How about using the standard XLR Create Release task. See also: https://docs.xebialabs.com/xl-release/how-to/create-a-create-release-task.html

Would it be possible to switch to that one?

vsorrentinomed commented 7 years ago

This would require me to redo all templates that currently use this; that is more work than I was hoping for for this upgrade. Plus I have to see if this will even work as I expect it to; which is the same way as this plug in

jdewinne commented 7 years ago

Can we maybe first check how many instances you have of that task? Maybe you can use the REST api to get all the templates in json format and search on the number of occurrences of xlr.CreateAndStartSubRelease?

vsorrentinomed commented 7 years ago

203 occurrences. I appreciate the help! I think I am going to take on the project to convert these because the offering in the XLRelease built in Create release is friendlier than the plug in.

jdewinne commented 7 years ago

Closing because of inactivity

vnaiduuhg commented 6 years ago

Hi, I am also facing the same issue with xlr-create and start sub release with this below error Going to use xlr_api_url: /api/v1/templates?filter=UHC_Benefits%20%28Dev%2CTest%2CAlpha%2CStage%2CMaster%29 Failed to find template in XL Release UHC_Benefits (Dev,Test,Alpha,Stage,Master) Status: 401

could you please suggest me what us going wrong here.

Stargirly2 commented 6 years ago

I am using the build in xlrelease start release now…

From: vnaiduuhg [mailto:notifications@github.com] Sent: maandag 23 oktober 2017 17:27 To: xebialabs-community/xlr-xlrelease-plugin xlr-xlrelease-plugin@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [xebialabs-community/xlr-xlrelease-plugin] Create and Start Sub Release, when using a template in a folder (#18)

Hi, I am also facing the same issue with xlr-create and start sub release with this below error Going to use xlr_api_url: /api/v1/templates?filter=UHC_Benefits%20%28Dev%2CTest%2CAlpha%2CStage%2CMaster%29 Failed to find template in XL Release UHC_Benefits (Dev,Test,Alpha,Stage,Master) Status: 401

could you please suggest me what us going wrong here.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/xebialabs-community/xlr-xlrelease-plugin/issues/18#issuecomment-338696736, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATAhji0_RGtCMawNzCfagXhZ4zGdqPrjks5svLAygaJpZM4MSelC.

This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing.

brhahlen commented 6 years ago

Fixed bij #22