Skip to content
This repository has been archived by the owner on Apr 20, 2022. It is now read-only.

Full support for air gapped environments #108

Open
malston opened this issue Nov 2, 2017 · 1 comment
Open

Full support for air gapped environments #108

malston opened this issue Nov 2, 2017 · 1 comment

Comments

@malston
Copy link
Contributor

malston commented Nov 2, 2017

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:

pipeline {
    agent any
    tools {
        cf 'cf-cli-6.29.1+d5129d651.2017-08-17' 
    }
    stages {
        stage('Example') {
            steps {
                sh 'cf -v'
            }
        }
    }
}

Then, pipeline shell scripts would need to know or be told when something is preconfigured or needs to be downloaded.

@marcingrzejszczak marcingrzejszczak added this to the 1.0.0.M8 milestone Nov 3, 2017
@marcingrzejszczak
Copy link
Contributor

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.

@marcingrzejszczak marcingrzejszczak removed this from the 1.0.0.M8 milestone Jun 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants