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
Added CargoConfigureLocal task #144
Conversation
Any progress on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the pull request. Would you mind also updating the documentation?
build.gradle
Outdated
@@ -19,7 +19,7 @@ def compatibilityVersion = 1.6 | |||
sourceCompatibility = compatibilityVersion | |||
targetCompatibility = compatibilityVersion | |||
group = 'com.bmuschko' | |||
version = '2.2.2' | |||
version = '2.2.3' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please revert the version number change? I am doing that as part of the release process.
class CargoConfigureLocal extends LocalCargoContainerTask { | ||
CargoConfigureLocal() { | ||
action = 'configure' | ||
description = 'Configures the container' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should say "Configures the local container". Please also add a dot at the end of the description so it aligns with the other task descriptions.
Thanks again for your pull request. I release a new version with your changes. |
You're welcome. |
Added a task to run the 'configure' task in cargo with a cargoConfigureLocal task.
I'd like the ability to bundle the containers configuration manually onto target via SSH (rather than having to specify usernames and passwords to remotes), so a 'configure' only task is a useful option.
This is also useful as I can add additional generated configuration directories (rather than using configFiles) into the container configuration before starting the container.
Also, I can now manually run and background the start of (e.g.) tomcat on the target using ssh rather than the blocking cargoRunLocal task.
There don't seem to be any tests around creating the cargo*Local tasks, but the implementation is trivial, so I haven't added any either.