[JIRA] (JENKINS-61238) Missing start function in configuration of a slave which is a virtual machine
Title: Message Title
Reiner Wirtz commented on JENKINS-61238
Re: Missing start function in configuration of a slave which is a virtual machine
Possible it depends on a duplicate name ("launcher") in the xml-structure. After saving the configuration the inner block with name "launcher" is missing in the configuration file "config.xml" for the node. If the inner block in the node confguration is missing, there are problems in connecting the slave. This is true for both slaves, linux (connected by ssh-launcher) or windows (slave as windows service).
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204793.1582726396000.8368.1584450900122%40Atlassian.JIRA.
[JIRA] (JENKINS-61238) Missing start function in configuration of a slave which is a virtual machine
Title: Message Title Reiner Wirtz created an issue Jenkins / JENKINS-61238 Missing start function in configuration of a slave which is a virtual machine Issue Type: Bug Assignee: Giuseppe Landolfi Attachments: Jenkins-2.222-ConfigurationSlaves.png Components: slave-setup-plugin Created: 2020-02-26 14:13 Environment: Jenkins 2.22 running on a linux machine as master Priority: Minor Reporter: Reiner Wirtz If you select the agent management and you try to reconfigure an agent, you will not see the field startfunction if the agent is a virtual machine, which can be started over a vcenter. If the agent is a real unix system you will see the field. In the attachment I show the configration of 2 different agent. The agent with name "sst-j-a7w9d0" is a real server with operating system AIX 7.2. The agent will be started by SSH. The second agent with name "sst-j-r7e7o2" is a linux virtual machine managed by a vcenter. The machine will be reset to a snapshot and then started by the vcenter. After some time (currently we wait about 5 minutes) the jenkins slave is started by SSH like the slave on AIX. But you cant't change the start method in the configuration. If you create a new node by copying an existing you will also not be able to change the primary start method. You are not able to change the start method to JNLP connection if the agent is a windows virtual machine with the jenkins slave installed as a windows service. If you save the configuration of a so configured windows agent (jenkins slave as windows service) the slave will no longer be able to connect to the
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Reiner Wirtz commented on JENKINS-60641 Re: IllegalArgumentException: No script is provided I got the same error. I use now version 2.211. Thir version works for me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2502.1578301140366%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Reiner Wirtz commented on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) We have a similar problem on AIX 7.2. The binary to start is of type ELF. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.3376.1572271440291%40Atlassian.JIRA.
[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url
Title: Message Title Reiner Wirtz commented on JENKINS-58667 Re: NumberFormatException when parsing deploy url If there is a new version available, please let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200949.1564120752000.2791.1564401900107%40Atlassian.JIRA.
[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url
Title: Message Title Reiner Wirtz commented on JENKINS-58667 Re: NumberFormatException when parsing deploy url I did the update to version 1.14 again and followed the hints given by Robin Jansohn. I saved the job, which used the plugin without any changes. Now the deploy worked again. Thanks for the help! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200949.1564120752000.2789.1564401780087%40Atlassian.JIRA.
[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url
Title: Message Title Reiner Wirtz updated an issue Jenkins / JENKINS-58667 NumberFormatException when parsing deploy url Change By: Reiner Wirtz Summary: NumNumberFormatException NumberFormatException when parsing deploy url Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200949.1564120752000.1622.1564134060145%40Atlassian.JIRA.
[JIRA] (JENKINS-58667) NumNumberFormatException when parsing deploy url
Title: Message Title Reiner Wirtz commented on JENKINS-58667 Re: NumNumberFormatException when parsing deploy url The error happens in all of my different test agents. That means: I have a jenkins master and at leat 17 slaves with different test environments. Every slave has two webapplication servers, one at port 8080 (jboss, wildfly) and one at port 28080 (apache-tomcat). The slaves are VMs with different operating systems (linux, windows, in different versions, different java versions, different wildfly versions, different tomcat versions). To deploy the needed applications to jboss or wildlfy, I use the commandline interface of the web application server. To deploy the needed application to apache-tomcat, I use the jenkins plugin "Deploy to container", which is used in a jenkins job,which will run locally on the slave machine. So the URL ist always the same "http://localhost:28080". In the definition of the jenkins job I selected the tomcat version "7.x" in the plugin for deploying. For authentification I have a user script inthe configuration of all the apache-tomcat activated. As long as I use plugin version 1.13 every thing went well. With plugin version 1.14 released on July, 24 I got the error listed in the description. Please, don't hesitate to conact me if I can give you more information. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200949.1564120752000.1620.1564134000148%40Atlassian.JIRA.
[JIRA] (JENKINS-58667) NumNumberFormatException when parsing deploy url
Title: Message Title Reiner Wirtz created an issue Jenkins / JENKINS-58667 NumNumberFormatException when parsing deploy url Issue Type: Bug Assignee: Unassigned Components: deploy-plugin Created: 2019-07-26 05:59 Priority: Minor Reporter: Reiner Wirtz After Updating deploy to container plugin from 1.13 to 1.14 I got a NumberFormatException parsing the deploy URL "http://localhost:28080". The Errormessage was: 01:01:53 [DeployPublisher][INFO] Attempting to deploy 2 war file(s)01:01:54 ERROR: Step ‘Deploy war/ear to a container’ aborted due to exception: 01:01:54 java.lang.NumberFormatException: For input string: "28080null"01:01:54 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)01:01:54 at java.lang.Integer.parseInt(Integer.java:580)01:01:54 at java.lang.Integer.parseInt(Integer.java:615)01:01:54 at java.net.URLStreamHandler.parseURL(URLStreamHandler.java:222)01:01:54 at java.net.URL.(URL.java:622)01:01:54 Caused: java.net.MalformedURLException: For input string: "28080null"01:01:54 at java.net.URL.(URL.java:627)01:01:54 at java.net.URL.(URL.java:490)01:01:54 at java.net.URL.(URL.java:439)01:01:54 at hudson.plugins.deploy.tomcat.TomcatAdapter.configure(TomcatAdapter.java:50)01:01:54 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to sst-j-trunk*01:01:54* at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)01:01:54 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)01:01:54 at hudson.remoting.Channel.call(Channel.java:957)01:01:54 at hudson.FilePath.act(FilePath.java:1072)01:01:54 at hudson.FilePath.act(FilePath.java:1061)01:01:54 at hudson.plugins.deploy.CargoContainerAdapter.redeployFile(CargoContainerAdapter.java:133)01:01:54 at hudson.plugins.deploy.PasswordProtectedAdapterCargo.redeployFile(PasswordProtectedAdapterCargo.java:95)01:01:54 at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:113)01:01:54 at
[JIRA] (JENKINS-58483) Jenkins 2.185 won't connect to SSH agents
Title: Message Title Reiner Wirtz edited a comment on JENKINS-58483 Re: Jenkins 2.185 won't connect to SSH agents Yes, trilead-api-plugin version 1.0.4 ist is installed h1. Über Trilead API Plugin 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200621.1563143371000.10413.1563181560653%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58483) Jenkins 2.185 won't connect to SSH agents
Title: Message Title Reiner Wirtz commented on JENKINS-58483 Re: Jenkins 2.185 won't connect to SSH agents Yes, trilead-api-plugin version 1.0.4 ist installed Über Trilead API Plugin 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200621.1563143371000.10400.1563181200368%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58483) Jenkins 2.185 won't connect to SSH agents
Title: Message Title Reiner Wirtz commented on JENKINS-58483 Re: Jenkins 2.185 won't connect to SSH agents Same issue here, We have to go back to Version 2.184 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200621.1563143371000.10192.1563173460411%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57074) Version 2.173 creates tmp-files and doesn't delete them
Title: Message Title Reiner Wirtz updated an issue Jenkins / JENKINS-57074 Version 2.173 creates tmp-files and doesn't delete them Change By: Reiner Wirtz Summary: Version 2.173 creates tmp-files and doesn't delete them SInce I updated jenkins from 2.172 to 2.173 my tmp-filesystem filled with about 75 GB of files, owned by the user jenkins, who started the process jenkins, and filled all my space on the /tmp filesystem during my nightly tests with about 20 slaves.The names are always like "jar_cache*.tmp"When the filesystem has been filled, jenkins stops Please delete this issue, it looks there is a test application that creates the files Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57074) Version 2.173 creates tmp-files and doesn't delete them
Title: Message Title Reiner Wirtz created an issue Jenkins / JENKINS-57074 Version 2.173 creates tmp-files and doesn't delete them Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-17 07:01 Environment: Oracle Java 1.8.0_161 64 Bit, SUSE-Linux 12 SP3, 32 GB RAM, filesystem: 90 GB "/", 500GB "/data1" Priority: Major Reporter: Reiner Wirtz SInce I updated jenkins from 2.172 to 2.173 my tmp-filesystem filled with about 75 GB of files, owned by the user jenkins, who started the process jenkins, and filled all my space on the /tmp filesystem during my nightly tests with about 20 slaves. The names are always like "jar_cache*.tmp" When the filesystem has been filled, jenkins stops Add Comment
[JIRA] (JENKINS-47442) Parameterized Trigger hangs waiting for downstream job
Title: Message Title Reiner Wirtz commented on JENKINS-47442 Re: Parameterized Trigger hangs waiting for downstream job We transformed most of our jenkins jobs to jenkins pipeline. We never got a problem starting another jenkins job from piepeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title Reiner Wirtz commented on JENKINS-35330 Re: Matrix plugin forwards subversion tag parameter value as null Today i tried the version 1.7.1 again with jenkins 2.15. I discovered, that none of my jenkins variablen defined in the job are passed to the matrix jobs, except the matrix defining variable. The count of the defined variables does not have any effect. The parameter -Dhudson.model.ParametersAction.keepUndefinedParameters=true is set in the environment. 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-27948) Script timeout during start of configure a jenkins job
Title: Message Title Reiner Wirtz commented on JENKINS-27948 Re: Script timeout during start of configure a jenkins job Hello, it seems that the bug is fixed. I have two jobs, which took about 10 minutes to open for edit with jenkins up to 2.11 Since I use 2.12 the same jobs takes about 10 to 20 seconds to open for edit. And the browser does'n allocated about 10 GB of memory to open the job any more. 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-34814) Trigger build parameters not getting passed downstream
Title: Message Title Reiner Wirtz commented on JENKINS-34814 Re: Trigger build parameters not getting passed downstream I added the define -Dhudson.model.ParametersAction.keepUndefinedParameters=true in the startline of jenkins and it works fine. 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title Reiner Wirtz commented on JENKINS-35330 Re: Matrix plugin forwards subversion tag parameter value as null Yesterday I mixed the names of the pdf. The smaller PDF with 1_6 in the name, a hardcopy of job #593, was done with plugin version 1.7 active. The larger PDF with 1_7 in the name, a hardcopy of job #594, was done with plugin version 1.6 active. Beg your pardon for my mistake. 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title Reiner Wirtz edited a comment on JENKINS-35330 Re: Matrix plugin forwards subversion tag parameter value as null How many Jenkins-Variable are in use in these cases?I have a complex test environment.My jobs have about 70 Variable to describe the different test environments of the slaves and the different test steps to execute for the slaves.If I try to use Matrix plugin 1.7 I see only 49 of the variables in the matrix jobs after the split.If I go back to version 1.6 of the matrix project plugin I see all the variables in matrix job after the splitI'm using* Jenkins 2.10 with define -Dhudson.model.ParametersAction.keepUndefinedParameters=true set I added two attachments with harcopys of the different varaible listing with the diferent plugin versions 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title Reiner Wirtz updated an issue Jenkins / JENKINS-35330 Matrix plugin forwards subversion tag parameter value as null Change By: Reiner Wirtz Attachment: Jenkins-Variable-List-Matrix-Project-Plugin-1_7.pdf 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title Reiner Wirtz updated an issue Jenkins / JENKINS-35330 Matrix plugin forwards subversion tag parameter value as null Change By: Reiner Wirtz Attachment: Jenkins-Variable-List-Matrix-Project-Plugin-1_6.pdf 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title Reiner Wirtz commented on JENKINS-35330 Re: Matrix plugin forwards subversion tag parameter value as null How many Jenkins-Variable are in use in these cases? I have a complex test environment. My jobs have about 70 Variable to describe the different test environments of the slaves and the different test steps to execute for the slaves. If I try to use Matrix plugin 1.7 I see only 49 of the variables in the matrix jobs after the split. If I go back to version 1.6 of the matrix project plugin I see all the variables in matrix job after the split I'm using Jenkins 2.10 with define -Dhudson.model.ParametersAction.keepUndefinedParameters=true set 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] [jobgenerator-plugin] (JENKINS-34814) Trigger build parameters not getting passed downstream
Title: Message Title Reiner Wirtz commented on JENKINS-34814 Re: Trigger build parameters not getting passed downstream I discovered such a problem for every jenkins parameter in 2.3, 2.4 and 2.5. No Parameter can be evaluated in the started jenkins child job. 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz commented on JENKINS-34529 Re: The environment variable WORKSPACE is set to the workspace of the parallel running job Please close this issue. It was my fault. For test statements in the shell, I set the environment variable WORKSPACE in this shell. Today I restarted jenkins in this shell. In every executed jenkins job was the environment variable WORKSPACE set to the value the variable set in the shell. 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz commented on JENKINS-34529 Re: The environment variable WORKSPACE is set to the workspace of the parallel running job the version of the environment inject plugin is 1.92.1 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz commented on JENKINS-34529 Re: The environment variable WORKSPACE is set to the workspace of the parallel running job I'm confused now. I created 2 jobs, which both executes a single shell-Script. "Debug_job_a" executes: pwd echo $WORKSPACE sleep 300 echo $WORKSPACE "Debug_job_b" executes: pwd echo $WORKSPACE I started at first "Debug_job_a" and a minute later "Debug_job_b": I got the following results: Debug_job_a: [EnvInject] - Loading node environment variables. Baue auf Master in Arbeitsbereich /data1/jenkins/.jenkins/jobs/Debug_job_a/workspace [workspace] $ /bin/sh -xe /tmp/hudson553827305033427036.sh + pwd /data1/jenkins/.jenkins/jobs/Debug_job_a/workspace + echo /data1/jenkins/.jenkins/jobs/DOXiS4_CSB-Build-Complete/workspace /data1/jenkins/.jenkins/jobs/DOXiS4_CSB-Build-Complete/workspace + sleep 300 + echo /data1/jenkins/.jenkins/jobs/DOXiS4_CSB-Build-Complete/workspace /data1/jenkins/.jenkins/jobs/DOXiS4_CSB-Build-Complete/workspace Collecting metadata... Metadata collection done. Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS Debug_job_b: [EnvInject] - Loading node environment variables. Baue auf Master in Arbeitsbereich /data1/jenkins/.jenkins/jobs/Debug_job_b/workspace [workspace] $ /bin/sh -xe /tmp/hudson931674571424483368.sh + pwd /data1/jenkins/.jenkins/jobs/Debug_job_b/workspace + echo /data1/jenkins/.jenkins/jobs/DOXiS4_CSB-Build-Complete/workspace /data1/jenkins/.jenkins/jobs/DOXiS4_CSB-Build-Complete/workspace Collecting metadata... Metadata collection done. Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS The value of WORKSPACE is in both cases the workspace of the mentioned long running compile job. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz edited a comment on JENKINS-34529 Re: The environment variable WORKSPACE is set to the workspace of the parallel running job Yes, i installed all the modules recommended by jenkins during the first start of jenkins 2.0. I added a file with the list of the currently installed modules 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz updated an issue Jenkins / JENKINS-34529 The environment variable WORKSPACE is set to the workspace of the parallel running job Change By: Reiner Wirtz Attachment: jenkins-module-list 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz commented on JENKINS-34529 Re: The environment variable WORKSPACE is set to the workspace of the parallel running job Yes, i installed all the modules recommended by jenkins during the first start of jenkins 2.0. 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz updated an issue Jenkins / JENKINS-34529 The environment variable WORKSPACE is set to the workspace of the parallel running job Change By: Reiner Wirtz Labels: 2.0 Environment: Suse Linux 11 Sp2, Oracle Java 1.7.0_79, jenkins 2.0 or 2.1 with internal web interface, Mozilla FireFox 45.0.2 on Windows 10 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz commented on JENKINS-34529 Re: The environment variable WORKSPACE is set to the workspace of the parallel running job I don't use a special plugin for long running jobs. The jobs executed some maven goals and some shellscripts, so a job takes about 2 hour to run. I discovered the problem with jenkins 2.0 and 2.1. With jenkins 1.656 which I used before the environment variable WORKSPACE points always to the current workspace of the job. 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] [envinject-plugin] (JENKINS-34529) The environment variable WORKSPACE is set to the workspace of the parallel running job
Title: Message Title Reiner Wirtz created an issue Jenkins / JENKINS-34529 The environment variable WORKSPACE is set to the workspace of the parallel running job Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 2016/May/02 11:00 AM Priority: Major Reporter: Reiner Wirtz If I was running a job in jenkins (ita a long running build job) and started during the time a new jenkins jobs containing a shell script build step wihich needs the environment variable WORKSPACE for copying data. The value of the variable WORKSPACE points to the workspace of the parallel running build job, notto the current workspace Add Comment
[JIRA] [antisamy-markup-formatter-plugin] (JENKINS-27948) Script timeout during start of configure a jenkins job
Title: Message Title Reiner Wirtz commented on JENKINS-27948 Re: Script timeout during start of configure a jenkins job I have a jenkins job, which has about 20 steps. Every step has a condition depending on a _expression_ with jenkins variables. About 15 of the steps call simple a unix shell script, two others system groovy scripts. The size of the unix shell scripts vary from 5 to 30 lines. To open this job for configure takes more than 2 minutes. I haven't seen a difference in time if I use the workaround mentioned by Scott Hebert or not. 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Title: Message Title Reiner Wirtz edited a comment on JENKINS-23459 Re: Cannot restrict a matrix build job to one node/label @ Mark Peter :ThakYouverymuchforthenote,thatapluginisneededfortheworkaround 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Title: Message Title Reiner Wirtz edited a comment on JENKINS-23459 Re: Cannot restrict a matrix build job to one node/label @Mark:ThakYouverymuchforthenote,thatapluginisneededforthe workaround workaround 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Title: Message Title Reiner Wirtz commented on JENKINS-23459 Re: Cannot restrict a matrix build job to one node/label @Mark: Thak You very much for the note, that a plugin is needed for the work around 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job Depending on the time, I configure as timeout value for the time a script may run, there are different _javascript_s active at the time the browser stops the script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job Skript: http://sst-bld-master.sst.loca…/0da8a904/scripts/prototype.js:2188 It seems the script is calculating the size of the objects to display. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job Excuse my late answer. I am glad that I can help. I started configuring the job I added in this call as example. The browser was about 3 minutes in the state loading data. At this time a call to the threadDump URL does not show a thread "Handling POST" or "configSubmit". The only Thread with Hanling was the threadDump itself. It look like jenkins generates _javascript_, which runs all the time in the browser. It seems it runs a lot longer, if there a more objects or lines to display. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Reiner Wirtz commented on JENKINS-23459 Cannot restrict a matrix build job to one node/label @Jordan Spiker: I don't understand the question. The master is the master of the jenkins installation. It isn't a slave. As far as I understand the call, the problem was to create for every object in a list a subjob and in this case to run all the subjobs on the master node of the jenkins installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Reiner Wirtz commented on JENKINS-23459 Cannot restrict a matrix build job to one node/label Have you read the help (question mark at the right side)? It starts as follow: Return value from Groovy script is treated as Label _expression_. It is treated as followings: A non-string value will be converted to a string using toString() When null or blank string is returned, node restriction does not take effect (or is not overwritten). When exception occurred or Label _expression_ is not parsed correctly, builds are canceled. It sounds for me, that the return value "Master" from groovy script is treated as a label for the master node. But I haven't tried it in my environment. But if some else tested it, it would be nice to hear from him. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz updated JENKINS-27948 Script timeout during start of configure a jenkins job The attached zip file contains the config.xml file from a job called DOXiS4_CSB-Test-All-Comb". Opening this job for configuration exceeds the limit of 100 seconds configured in my firefox-browser. During this time one core of the quad-core-cpu is busy for the whole time. Change By: Reiner Wirtz (15/Apr/15 2:47 PM) Attachment: config.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job The list of the installed plugins (copied from display of the system properties): pre ant 1.2 true true antisamy-markup-formatter 1.3 true true any-buildstep 0.1 true false artifactdeployer 0.33 true false audit-trail 2.1 true false backup 1.6.1 true false batch-task 1.17 true false build-blocker-plugin 1.6 true false build-environment 1.4 true false build-pipeline-plugin 1.4.7 true false build-user-vars-plugin 1.4 true false clone-workspace-scm 0.6 true false conditional-buildstep 1.3.3 true false config-file-provider 2.7.5 true false copy-to-slave 1.4.4 true false copyartifact 1.35 true false credentials 1.22 true true custom-tools-plugin 0.4.4 true false CustomHistory 1.6 true false cvs 2.12 true true dashboard-view 2.9.4 true false delivery-pipeline-plugin 0.8.11 true false dependencyanalyzer 0.7 true false deploy 1.10 true false disk-usage 0.25 true false downstream-buildview 1.9 true false downstream-ext 1.8 true false dynamic-axis 1.0.3 true false dynamic_extended_choice_parameter 1.0.1 true false dynamicparameter 0.2.0 true false email-ext 2.39.3 true false envfile 1.2 true false envinject 1.91.2 true false extended-choice-parameter 0.35 true false extensible-choice-parameter 1.2.2 true false external-monitor-job 1.4 true true flexible-publish 0.15.1 true false git 2.3.5 true false git-client 1.16.1 true false git-server 1.6 true false groovy 1.24 true false groovy-label-assignment 1.1.0 true false groovyaxis 0.3 true false ivy 1.24 true false javadoc 1.3 true true job-log-logger-plugin 1.0 true false job-node-stalker 1.0.3 true false jobConfigHistory 2.10 true false jquery 1.11.2-0 true false jquery-ui 1.0.2 true false junit 1.5 true true labeled-test-groups-publisher 1.2.7 true false ldap 1.11 true true m2-repo-reaper 1.0 true false mailcommander 1.0.0 true false mailer 1.15 true true managed-scripts 1.1.1 true false mantis 0.26 true false mapdb-api 1.0.6.0 true false matrix-auth 1.2 true true matrix-combinations-parameter 1.0.7 true false matrix-project 1.4.1 true false Matrix-sorter-plugin 1.1 true false maven-plugin 2.9 true true metadata 1.1.0b true false metrics 3.0.9 true false monitoring 1.55.0 true false nodelabelparameter 1.5.1 true false pam-auth 1.2 true true parameterized-trigger 2.26 true false periodicbackup 1.3 true false postbuild-task 1.8 true false postbuildscript 0.17 true false PrioritySorter 2.11 true false role-strategy 2.2.0 true false run-condition 1.0 true false scm-api 0.2 true false script-security 1.13 true false scriptler 2.7 true false selection-tasks-plugin 1.0 true false shared-objects 0.44 true false show-build-parameters 1.0 true false skip-certificate-check 1.0 true false sonar 2.2 true false ssh-credentials 1.11 true true ssh-slaves 1.9 true true statusmonitor 1.3 true false strawboss 1.3 true false subversion 2.5 true true support-core 2.20 true false svn-tag 1.17 true false testlink 3.10 true false throttle-concurrents 1.8.4 true false token-macro 1.10 true false translation 1.12 true true uno-choice 0.24 true false update-sites-manager 1.0.1 true false validating-string-parameter 2.3 true false vsphere-cloud 2.4 true false weblogic-deployer-plugin 3.2 true false websphere-deployer 1.3-SNAPSHOT (private-08/05/2014 09:34-nothhard) true false windows-slaves 1.0 true false ws-cleanup 0.25 true false xunit 1.94 true false /pre This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz edited a comment on JENKINS-27948 Script timeout during start of configure a jenkins job The list of the installed plugins (copied from display of the system properties): ant 1.2 true true antisamy-markup-formatter 1.3 true true any-buildstep 0.1 true false artifactdeployer 0.33 true false audit-trail 2.1 true false backup 1.6.1 true false batch-task 1.17 true false build-blocker-plugin 1.6 true false build-environment 1.4 true false build-pipeline-plugin 1.4.7 true false build-user-vars-plugin 1.4 true false clone-workspace-scm 0.6 true false conditional-buildstep 1.3.3 true false config-file-provider 2.7.5 true false copy-to-slave 1.4.4 true false copyartifact 1.35 true false credentials 1.22 true true custom-tools-plugin 0.4.4 true false CustomHistory 1.6 true false cvs 2.12 true true dashboard-view 2.9.4 true false delivery-pipeline-plugin 0.8.11 true false dependencyanalyzer 0.7 true false deploy 1.10 true false disk-usage 0.25 true false downstream-buildview 1.9 true false downstream-ext 1.8 true false dynamic-axis 1.0.3 true false dynamic_extended_choice_parameter 1.0.1 true false dynamicparameter 0.2.0 true false email-ext 2.39.3 true false envfile 1.2 true false envinject 1.91.2 true false extended-choice-parameter 0.35 true false extensible-choice-parameter 1.2.2 true false external-monitor-job 1.4 true true flexible-publish 0.15.1 true false git 2.3.5 true false git-client 1.16.1 true false git-server 1.6 true false groovy 1.24 true false groovy-label-assignment 1.1.0 true false groovyaxis 0.3 true false ivy 1.24 true false javadoc 1.3 true true job-log-logger-plugin 1.0 true false job-node-stalker 1.0.3 true false jobConfigHistory 2.10 true false jquery 1.11.2-0 true false jquery-ui 1.0.2 true false junit 1.5 true true labeled-test-groups-publisher 1.2.7 true false ldap 1.11 true true m2-repo-reaper 1.0 true false mailcommander 1.0.0 true false mailer 1.15 true true managed-scripts 1.1.1 true false mantis 0.26 true false mapdb-api 1.0.6.0 true false matrix-auth 1.2 true true matrix-combinations-parameter 1.0.7 true false matrix-project 1.4.1 true false Matrix-sorter-plugin 1.1 true false maven-plugin 2.9 true true metadata 1.1.0b true false metrics 3.0.9 true false monitoring 1.55.0 true false nodelabelparameter 1.5.1 true false pam-auth 1.2 true true parameterized-trigger 2.26 true false periodicbackup 1.3 true false postbuild-task 1.8 true false postbuildscript 0.17 true false PrioritySorter 2.11 true false role-strategy 2.2.0 true false run-condition 1.0 true false scm-api 0.2 true false script-security 1.13 true false scriptler 2.7 true false selection-tasks-plugin 1.0 true false shared-objects 0.44 true false show-build-parameters 1.0 true false skip-certificate-check 1.0 true false sonar 2.2 true false ssh-credentials 1.11 true true ssh-slaves 1.9 true true statusmonitor 1.3 true false strawboss 1.3 true false subversion 2.5 true true support-core 2.20 true false svn-tag 1.17 true false testlink 3.10 true false throttle-concurrents 1.8.4 true false token-macro 1.10 true false translation 1.12 true true uno-choice 0.24 true false update-sites-manager 1.0.1 true false validating-string-parameter 2.3 true false vsphere-cloud 2.4 true false weblogic-deployer-plugin 3.2 true false websphere-deployer 1.3-SNAPSHOT (private-08/05/2014 09:34-nothhard) true false windows-slaves 1.0 true false ws-cleanup 0.25 true false xunit 1.94 true false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Reiner Wirtz commented on JENKINS-23459 Cannot restrict a matrix build job to one node/label In the first section of the multiconfiguration is an option to enter a groovy script to restrict where the job could be run. Activating this option opens an edit field for the groovy script. In this field I entered the mini groovy script: return "Master"; This worked fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job If I should present the data in a special way or format, please feel free to contact me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Reiner Wirtz updated JENKINS-23459 Cannot restrict a matrix build job to one node/label the attached png shows the script in a screen shot Change By: Reiner Wirtz (15/Apr/15 2:28 PM) Attachment: MatrixConfigurationToRunAllOnMaster.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job I increased the timeout value for scripts to run to 200 seconds. The start to configure the job I added in the attachments took 180 seconds (yes 3 minutes) on my machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz created JENKINS-27948 Script timeout during start of configure a jenkins job Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Apr/15 8:09 AM Description: I updated jenkins from version 1.596 to version 1.609. No I get a script timeout if I try to configure some of the larger jobs. I can configure small jobs without any problems. I increase the firefox script timeout from 10 seconds to 100 seconds. Now I can configure the jenkins jobs, but it takes a very long time to start editing. With version 1.596 it was possible to start configuring of the same larger jobs in the predefined timout of 10 seconds Environment: Suse Linux 11 Sp2, Oracle Java 1.7.0_45, jenkins with internal web interface, Mozilla FireFox 37.0.1 on Windows 7 Project: Jenkins Labels: jenkins performance configuration Priority: Minor Reporter: Reiner Wirtz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Reiner Wirtz commented on JENKINS-23459 Cannot restrict a matrix build job to one node/label Hello, I think I solved my problem. I tried to restriced at first the execution of the matrix jobs bei a label _expression_ in the advanced project settings. But that does not work. Now I use a simple groovy script to restrict the job to the master. The script is pre return "Master"; /pre Now all the matrix childs are executed on the jenkins master as I need in my test environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Reiner Wirtz commented on JENKINS-23459 Cannot restrict a matrix build job to one node/label I have a problem using the following situation. I use a jenkins master and some virtual machines as slaves to start parallel tests. The virtual machines are configured to use a special test environment (database, WAS, JDK) in every vm. The test uses a matrix configuration to manage the different test configuration. At the start of the test every slave VM is resetted to a defined snapshot, to make sure the test conditions are always equal. After booting the VM, the build, selected for testing is installed on the jenkins slave VMs. If the Matrix jobs are started on a slave, the testresult is always failure due to the reset to the snapshot of the slave VM and the resultng network error. So I need the possibility to make sure, all the matrix jobs are started on jenkins master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
