We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are using Jenkins to do out production deploy, after file copying, jenkins will call CodeIgniter's spark to do some init jobs.
spark
Since Jenkins 2.286, Jenkins changed it's behaviour, added CI=true environment variable. https://issues.jenkins.io/browse/JENKINS-36707 This change merged into Jenkins LTS 2.289.1 since 2021-06-02
CI=true
This breaks our deployment config, since CodeIgniter will tread Jenkins as Testing environment.
We had modify spark to force specific the environment as production as temp solution.
But is there a better way to archive it: using Jenkins to do deployment, and not tread Jenkins as Testing environment.
The text was updated successfully, but these errors were encountered:
What CI version are you using? As of v4.1.2, this has been resolved by #4692 .
Sorry, something went wrong.
No branches or pull requests
We are using Jenkins to do out production deploy, after file copying, jenkins will call CodeIgniter's
spark
to do some init jobs.Since Jenkins 2.286, Jenkins changed it's behaviour, added
CI=true
environment variable.https://issues.jenkins.io/browse/JENKINS-36707
This change merged into Jenkins LTS 2.289.1 since 2021-06-02
This breaks our deployment config, since CodeIgniter will tread Jenkins as Testing environment.
We had modify
spark
to force specific the environment as production as temp solution.But is there a better way to archive it: using Jenkins to do deployment, and not tread Jenkins as Testing environment.
The text was updated successfully, but these errors were encountered: