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

Additional Transforms Feature #3134

Closed
BlueWombat opened this issue Feb 3, 2017 · 3 comments
Closed

Additional Transforms Feature #3134

BlueWombat opened this issue Feb 3, 2017 · 3 comments
Assignees

Comments

@BlueWombat
Copy link

Hi.

When I'm attempting to use said feature, with line listed below, I get some very strange behavior.
It's attempting to transform my Web.config which is at the root of my package, no problem there. However, the entire task fails because I have another Web.config file nested i a sub-directory, which to my understanding whouldn't be affected by the config I've provided.

Config line:
#{InstallDir}\Web.Support136135.config => Web.config

Log entry:
The XML configuration file D:\Octopus\Applications\Integration\Web.Config.Integration.Master\1.0.0-integration0000124\sitecore\admin\Web.config failed with transformation file D:\web\Website_1.0.0-integration0000124\Web.Support136135.config

Hope you can be of assistance.

Thanks in advance,
Mikkel Petersen.

@Dalmirog-zz
Copy link

Dalmirog-zz commented Feb 3, 2017

Hi, thanks for getting in touch with us. The best way to work through this is to use our support channel: http://octopus.com/support.

We don't actively monitor this backlog for new issues as per our contributing guide.

Looking forward to helping you sort out what's going wrong.
Why was this closed?


We also accept PRs for library step templates such as that one :). Perhaps you can attempt to add this enhancement yourself? It definitely sounds like a solid idea

https://github.com/OctopusDeploy/Library/blob/master/step-templates/slack-notify-deployment.json

@BlueWombat
Copy link
Author

BlueWombat commented Feb 3, 2017 via email

@lock
Copy link

lock bot commented Nov 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants