[JIRA] (JENKINS-35024) Parametrized build doesn't set environment variables in Mutli-configuration projects
Title: Message Title Ashish Behl resolved as Fixed Thanks. the problem was definitely with credentials plugin. But after upgrading the credentials plugin, now passing credentials to shell script as job parameters does not work. crashes when adding "use secret texts -> bindings" Marking this issue as resolved. Thanks for the help and a quick answer. Jenkins / JENKINS-35024 Parametrized build doesn't set environment variables in Mutli-configuration projects Change By: Ashish Behl Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl resolved as Duplicate Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Status: Open Resolved Resolution: Duplicate 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-35024) Parametrized build doesn't set environment variables in Mutli-configuration projects
Title: Message Title Ashish Behl reopened an issue Please see the issue: https://issues.jenkins-ci.org/browse/JENKINS-35921 I am still facing the problem. Please let me know if there is any other specific plugin to update in jenkins? Jenkins / JENKINS-35024 Parametrized build doesn't set environment variables in Mutli-configuration projects Change By: Ashish Behl Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Labels: Parameterized-Trigger-Plugin core envinject-plugin environment-variables multi-configuration parameterized parameterized-trigger 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Labels: Parameterized-Trigger-Plugin core envinject-plugin environment-variables multi-configuration parameterized parameterized-trigger 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl updated an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Change By:
Ashish Behl
Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.) Project type: Multi configuration project. Plugins: a) Build With Parameters: version 1.3 b) Environment Injector Plugin: version 1.92.1 c) Groovy: 1.29 http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variablesProblem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version.EDIT[2016-22-june]: THESE PARAMETERS ARE VISIBLE AS ENV VARIABLES ON MASTER BUT NOT ON THE SLAVES.Steps:Create a parameterized build with a multi configuration project.Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).Add a build step "Execute shell" to the job.Access these parameters in this shell script as env variables.echo " building $lib_name ($lib_version) ++"Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars.def map = ['lib_name':'lib1']map['lib_version'] = 'master'return mapThis makes these "Hardcoded" variables visible in jenkins shell script..+++EDIT: 23-july-2016: (tested with adding section "_Prepare an environment for the run_" *Logs from Master.*[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Executing and processing the following script content: export BRANCH_NAME=${BRANCH_NAME}export BUILD_STAGE=${BUILD_STAGE}[] $ /bin/bash -xe /tmp/hudson803008212850989562.sh+ export BRANCH_NAME=feature/ABC+ BRANCH_NAME=feature/ABC+ export BUILD_STAGE=STAGE1+ BUILD_STAGE=STAGE1*Logs from SLAVE.*[EnvInject] - Inject global passwords.[EnvInject] - Mask passwords passed as build parameters.Gestartet durch vorgelagertes Projekt "COMPACT2", Build 1originally caused by: Gestartet durch Benutzer ABC DEF GHI[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Executing and processing the following script content: export BRANCH_NAME=${BRANCH_NAME}export BUILD_STAGE=${BUILD_STAGE}[] $ /bin/bash -xe /tmp/hudson7212379337542594663.sh+ export BRANCH_NAME=+ BRANCH_NAME=+ export BUILD_STAGE=+ BUILD_STAGE=[EnvInject] - Script executed successfully.[EnvInject] -
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl updated an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Change By:
Ashish Behl
Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.) Project type: Multi configuration project. Plugins: a) Build With Parameters: version 1.3 b) Environment Injector Plugin: version 1.92.1 c) Groovy: 1.29 http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variablesProblem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version.EDIT[2016-22-june]: THESE PARAMETERS ARE VISIBLE AS ENV VARIABLES ON MASTER BUT NOT ON THE SLAVES.Steps:Create a parameterized build with a multi configuration project.Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).Add a build step "Execute shell" to the job.Access these parameters in this shell script as env variables.echo " building $lib_name ($lib_version) ++"Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars.def map = ['lib_name':'lib1']map['lib_version'] = 'master'return mapThis makes these "Hardcoded" variables visible in jenkins shell script.. +++EDIT: 23-july-2016:*Logs from Master.*[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Executing and processing the following script content: export BRANCH_NAME=${BRANCH_NAME}export BUILD_STAGE=${BUILD_STAGE}[] $ /bin/bash -xe /tmp/hudson803008212850989562.sh+ export BRANCH_NAME=feature/ABC+ BRANCH_NAME=feature/ABC+ export BUILD_STAGE=STAGE1+ BUILD_STAGE=STAGE1*Logs from SLAVE.*[EnvInject] - Inject global passwords.[EnvInject] - Mask passwords passed as build parameters.Gestartet durch vorgelagertes Projekt "COMPACT2", Build 1originally caused by: Gestartet durch Benutzer ABC DEF GHI[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Executing and processing the following script content: export BRANCH_NAME=${BRANCH_NAME}export BUILD_STAGE=${BUILD_STAGE}[] $ /bin/bash -xe /tmp/hudson7212379337542594663.sh+ export BRANCH_NAME=+ BRANCH_NAME=+ export BUILD_STAGE=+ BUILD_STAGE=[EnvInject] - Script executed successfully.[EnvInject] - Injecting contributions.
[JIRA] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl closed an issue as Fixed Jenkins / JENKINS-30200 Nullpointer exception while connecting to a docker container Change By: Ashish Behl Status: Open Closed Resolution: Fixed 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl updated an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Change By:
Ashish Behl
Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.) Project type: Multi configuration project. Plugins: a) Build With Parameters: version 1.3 b) Environment Injector Plugin: version 1.92.1 c) Groovy: 1.29 http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variablesProblem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version. * EDIT[2016-22-june]: THESE PARAMETERS ARE VISIBLE AS ENV VARIABLES ON MASTER BUT NOT ON THE SLAVES. * Steps:Create a parameterized build with a multi configuration project.Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).Add a build step "Execute shell" to the job.Access these parameters in this shell script as env variables.echo " building $lib_name ($lib_version) ++"Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars.def map = ['lib_name':'lib1']map['lib_version'] = 'master'return mapThis makes these "Hardcoded" variables visible in jenkins shell script..
Add Comment
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl updated an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Change By:
Ashish Behl
Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.) Project type: Multi configuration project. Plugins: a) Build With Parameters: version 1.3 b) Environment Injector Plugin: version 1.92.1 c) Groovy: 1.29 http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variablesProblem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version. *EDIT[2016-22-june]: THESE PARAMETERS ARE VISIBLE AS ENV VARIABLES ON MASTER BUT NOT ON THE SLAVES.* Steps:Create a parameterized build with a multi configuration project.Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).Add a build step "Execute shell" to the job.Access these parameters in this shell script as env variables.echo " building $lib_name ($lib_version) ++"Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars.def map = ['lib_name':'lib1']map['lib_version'] = 'master'return mapThis makes these "Hardcoded" variables visible in jenkins shell script..
Add Comment
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl commented on JENKINS-35921 Re: Parameterised build in jenkins: Not getting parameters as env variables Is the bug related to : https://issues.jenkins-ci.org/browse/JENKINS-12108 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Labels: core envinject-plugin environment-variables multi-configuration parameterized parameterized-trigger 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Component/s: envinject-plugin 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Priority: Critical Major 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Priority: Major Critical 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Component/s: build-with-parameters-plugin 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl updated an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Change By:
Ashish Behl
Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.) Project type: Multi configuration project. Plugins: a) Build With Parameters: version 1.3 b) Environment Injector Plugin: version 1.92.1 c) Groovy: 1.29 http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variablesProblem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version.Steps:Create a parameterized build with a multi configuration project.Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).Add a build step "Execute shell" to the job.Access these parameters in this shell script as env variables.echo " building $lib_name ($lib_version) ++"Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars.def map = ['lib_name':'lib1']map['lib_version'] = 'master'return mapThis makes these "Hardcoded" variables visible in jenkins shell script..
Add Comment
This message was
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Labels: core environment-variables multi-configuration parameterized parameterized-trigger 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Priority: Major Critical 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl updated an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Change By:
Ashish Behl
http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variablesProblem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version.Steps:Create a parameterized build with a multi configuration project.Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).Add a build step "Execute shell" to the job.Access these parameters in this shell script as env variables.echo " building $lib_name ($lib_version) ++"Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars.def map = ['lib_name':'lib1']map['lib_version'] = 'master'return map This makes these "Hardcoded" variables visible in jenkins shell script..
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Environment: Jenkins version: 2.6 - 2.9Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.)Project type: Multi configuration project.Plugins:a) Build With Parameters: version 1.3b) Environment Injector Plugin: version 1.92.1c) Groovy: 1.29 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-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title
Ashish Behl created an issue
Jenkins / JENKINS-35921
Parameterised build in jenkins: Not getting parameters as env variables
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Jun/15 11:23 AM
Environment:
Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, runninf in VM. ( jenkins installed through system repos and updated.) Project type: Multi configuration project. Plugins: a) Build With Parameters: version 1.3 b) Environment Injector Plugin: version 1.92.1 c) Groovy: 1.29
Labels:
parameterized multi-configuration environment-variables
Priority:
Major
Reporter:
Ashish Behl
http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variables Problem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version. Steps: Create a parameterized build with a multi configuration project. Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ). Add a build step "Execute shell" to the job. Access these parameters in this shell script as env variables. echo " building $lib_name ($lib_version) ++" Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars. def map = ['lib_name':'lib1'] map['lib_version'] = 'master'
[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Environment: Jenkins version: 2.6 - 2.9Host: Debian 8, Linux 63 bit machine, runninf running in VM. ( jenkins installed through system repos and updated.)Project type: Multi configuration project.Plugins:a) Build With Parameters: version 1.3b) Environment Injector Plugin: version 1.92.1c) Groovy: 1.29 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl edited a comment on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container So, I tried with the latest docker plugin, version 0.14.0, and I can connect to the docker service.The problem that I now have is that I cannot use docker version > 1.8.0 with jenkins, but as I read above, this might be due to the custom containers that I create.So, Please let me know what I should I change while creating containers to make them work with docker > 1.8.0 and latest docker plugin? [Edit]Also, any way to start systemd in docker containers and connect to them through the docker plugin? Thanks,Ashish. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl commented on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container So, I tried with the latest docker plugin, version 0.14.0, and I can connect to the docker service. The problem that I now have is that I cannot use docker version > 1.8.0 with jenkins, but as I read above, this might be due to the custom containers that I create. So, Please let me know what I should I change while creating containers to make them work with docker > 1.8.0 and latest docker plugin? Thanks, Ashish. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl edited a comment on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container provide full description of issue --> Upgrade toJenkins ver. 1.626Docker plugin version: 0.12.1Plugin started producing the mentioned error.check Manage Jenkins -> Manage Old Data for not updated configuraiton and provide this info--> "No old data was found."provide full list of installed plugins with versions, jenkins core version--> Please see PluginsInstalled Attachment.check and provide errors from system jenkins.log and errors from Manage Jenkins -> System Log--> Already added to the bug when reporting.provide Cloud section from $JENKINS_HOME/config.xml file--> the cloud section contains a lot of images. I am attaching partially in "clouds_section_config.xml".describe how your docker infrastructure looks like--> 2 docker servers, around 84 containers images . The docker servers and Jenkins are all separate Virtual machines.--> The jobs are all sequential, running one container at a time.provide docker host/api version--> Tried two docker versions 1.6.1 and 1.8.1provide steps for reproducing--> Just create a node with the mentioned configuration and jenkins and docker version as written before. Run a job. The run fails.any code or log example surround with right markdown https://help.github.com/articles/github-flavored-markdown/--> configuration and logs already attached. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl edited a comment on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container provide full description of issue --> Upgrade to Jenkins ver. 1.626Docker plugin version: 0.12.1Plugin started producing the mentioned error.check Manage Jenkins -> Manage Old Data for not updated configuraiton and provide this info--> "No old data was found."provide full list of installed plugins with versions, jenkins core version--> Please see PluginsInstalled Attachment.check and provide errors from system jenkins.log and errors from Manage Jenkins -> System Log--> Already added to the bug when reporting.provide Cloud section from $JENKINS_HOME/config.xml file--> the cloud section contains a lot of images. I am attaching partially in "clouds_section_config.xml".describe how your docker infrastructure looks like--> 2 docker servers, around 84 containers. The docker servers and Jenkins are all separate Virtual machines.--> The jobs are all sequential, running one container at a time.provide docker host/api version--> Tried two docker versions 1.6.1 and 1.8.1provide steps for reproducing--> Just create a node with the mentioned configuration and jenkins and docker version as written before. Run a job. The run fails.any code or log example surround with right markdown https://help.github.com/articles/github-flavored-markdown/--> configuration and logs already attached. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl commented on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container Another Observation: Downgrading to Docker plugin v 0.9.2 and using Docker v 1.6.1 again works. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-30200 Nullpointer exception while connecting to a docker container Change By: Ashish Behl Attachment: PluginsInstalled Attachment: clouds_section_config.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl commented on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container provide full description of issue --> Upgrade Jenkins ver. 1.626 Docker plugin version: 0.12.1 Plugin started producing the mentioned error. check Manage Jenkins -> Manage Old Data for not updated configuraiton and provide this info --> "No old data was found." provide full list of installed plugins with versions, jenkins core version --> Please see PluginsInstalled Attachment. check and provide errors from system jenkins.log and errors from Manage Jenkins -> System Log --> Already added to the bug when reporting. provide Cloud section from $JENKINS_HOME/config.xml file --> the cloud section contains a lot of images. I am attaching partially in "clouds_section_config.xml". describe how your docker infrastructure looks like --> 2 docker servers, around 84 containers. The docker servers and Jenkins are all separate Virtual machines. --> The jobs are all sequential, running one container at a time. provide docker host/api version --> Tried two docker versions 1.6.1 and 1.8.1 provide steps for reproducing --> Just create a node with the mentioned configuration and jenkins and docker version as written before. Run a job. The run fails. any code or log example surround with right markdown https://help.github.com/articles/github-flavored-markdown/ --> configuration and logs already attached. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl created an issue Jenkins / JENKINS-30200 Nullpointer exception while connecting to a docker container Issue Type: Bug Assignee: Kanstantsin Shautsou Components: docker-plugin Created: 28/Aug/15 3:23 PM Environment: Linux, Docker plugin, docker 1.8.1 Priority: Critical Reporter: Ashish Behl Jenkins ver. 1.626 Docker plugin version: 0.12.1 Container settings: Docker command: /sbin/init 3 (without custom command also crashes) Hostname: debian8_32bit_32bit_INIT3_CONTAINER DNS: Volumes: /sys/fs/cgroup:/sys/fs/cgroup:ro Environment: container=docker Privileged : true Remote filing root: /home/jenkins labels: debian8_32bit_32bit_INIT3_CONTAINER Port: 22 Problem: Crash when running a job. The container is started within docker server but jenkins cannot see it. Jenkins logs state: Aug 28, 2015 2:29:20 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFORMATION: Asked to provision 1 slave(s) for: deb
