Open
Conversation
|
This would be a big boon for us, as we have a Jenkins master in AWS - at the moment we're having to launch GCE nodes with public IPs and use SSH, which isn't ideal from a security point of view - if inbound agent were supported then we could switch to nodes with private IPs (with a lockdown of the inbound agent port on the master to the Cloud NAT IP of the GCP VPC used for the nodes). Is there a plan on the table to get this into the formal release of the plugin? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enabling Inbound Agent to avoid SSH Connectivity under controlled environment.
Testing done
Installed Plugin to Jenkins and able to create Inbound Agent on-demand by running pipeline with provided label.
Submitter checklist