[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Leo Gallucci commented on JENKINS-36707 Re: Set environment variable CI=true on all builds I'm pretty sure I'll see this in Jenkins eventually, is not the first time someone resists certain ideas/features, it already happened to me with docker HEALTHCHECK with endless discussions of why and is already in place in docker beta 1.12 Shouldn't be that difficult, `export CI=true` and what is there to lose. But honestly, if has already been decided not to do it I prefer you close this request, just trying to avoid another endless discussion that's all. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Daniel Beck commented on JENKINS-36707 Re: Set environment variable CI=true on all builds I understood this as a compatibility feature for someone who switches from one of the other tools to Jenkins. That kind of feature should not be out of the box, especially given what else we're splitting off into plugins: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20split-plugins-from-core But apparently I'm still wrong? Who are you targeting with this? What's the use case? And how is that not covered by any of the following? Indicate it's a CI system via env vars – we have e.g. JENKINS_COOKIE for this. Allow easy migration of scripts – set the CI env var on nodes "plug and play" of repositories, like travis.yml – Pipeline (Jenkinsfile) which is part of default 2.x installs of Jenkins Can't help the impression that there are substantial unvoiced assumptions/circumstances in this request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Leo Gallucci commented on JENKINS-36707 Re: Set environment variable CI=true on all builds I can think tons of workarounds but the idea was more like knowing this is the default on every Jenkins instance. Doing it via a plugin won't help, nobody will trust the plugin is installed and will simply check for well known Jenkins environment variables instead. IMHO this should be the default at jenkins-core or we simply stay as we are now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Daniel Beck commented on JENKINS-36707 Re: Set environment variable CI=true on all builds FWIW unless you have a giant (but manually managed) set of build agents, it's trivial enough to define one env var on master and each of the agents. This will be inherited by all the builds (possibly only after a restart, but shouldn't matter here). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-36707 Set environment variable CI=true on all builds Change By: Daniel Beck Component/s: plugin-proposals Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Daniel Beck commented on JENKINS-36707 Re: Set environment variable CI=true on all builds Best done as a separate plugin I think. Should be trivial enough, sample-code sized. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Leo Gallucci commented on JENKINS-36707 Re: Set environment variable CI=true on all builds This makes it easier to migrate from TravisCI or CircleCI to Jenkins for example. Some things are cross browser compatible, others are cross operating system, this would be cross CI. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Daniel Beck commented on JENKINS-36707 Re: Set environment variable CI=true on all builds So the dozen or so other environment variables defined by Jenkins don't work for you? This needs a real rationale. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36707) Set environment variable CI=true on all builds
Title: Message Title Leo Gallucci created an issue Jenkins / JENKINS-36707 Set environment variable CI=true on all builds Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Jul/15 9:03 AM Environment: ANY, e.g. jenkins:2.13 Labels: environment-variables Priority: Minor Reporter: Leo Gallucci Very simple: set & expose environment variable `CI=true` on all builds as TravisCI or Drone or CircleCI or other CI tools do. Add Comment
