You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2022. It is now read-only.
When CI is setup in an internet-less environment, then tools or resources need to be pre-configured. For example, the cf cli is downloaded from the internet but would like to also be able to set it up as either a resource (Concourse) or a tool (Jenkins). In Jenkins I'm thinking it would be done like this using the declarative syntax:
As a workaround, for now, I guess you'll need to remove the curl command from the scripts. I think we could provide a switch so as not to curl anything.
When CI is setup in an internet-less environment, then tools or resources need to be pre-configured. For example, the cf cli is downloaded from the internet but would like to also be able to set it up as either a resource (Concourse) or a tool (Jenkins). In Jenkins I'm thinking it would be done like this using the declarative syntax:
Then, pipeline shell scripts would need to know or be told when something is preconfigured or needs to be downloaded.
The text was updated successfully, but these errors were encountered: