[JIRA] (JENKINS-39045) Pipeline step for python-plugin (Python script)
Title: Message Title Vlad Dovlekaev commented on JENKINS-39045 Re: Pipeline step for python-plugin (Python script) Was this PR integrated in some version of python plugin? If not, the issue needs to be re-opened. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [scm-sync-configuration-plugin] (JENKINS-15221) scm_sync_configuration do not synchronize changes made on disk
Title: Message Title Vlad Dovlekaev commented on JENKINS-15221 Re: scm_sync_configuration do not synchronize changes made on disk The same issue for the manually updated files in user include directories ( not job configurations), like email-templates/*. Currently using SCM Sync Configuration Plugin 0.0.8 on Jenkins 1.609.1 Any ETA for fixing this issue ? 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] [parameterized-trigger] (JENKINS-23440) Jenkins Parameterized Trigger Plugin doesn't process the 'Projects to Build' parameter correctly
Vlad Dovlekaev
created JENKINS-23440
Jenkins Parameterized Trigger Plugin doesnt process the Projects to Build parameter correctly
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
16/Jun/14 8:17 AM
Description:
We have a matrix parameterized job with a single string parameter 'ChildJobs' which was designed to get the comma separated list of downstream job names to execute.
As a build step we are using the Parameterized Trigger Plugin builder with its 'Projects to Build' parameter set to ${ChildJobs}.
When a single job name is specified with 'ChildJobs' - all works well. When multiple, comma separated names are specified the following error is generated and the matrix job fails.
-
Started by upstream project "TestChildJobs" build number 6
originally caused by:
Started by user anonymous
EnvInject - Loading node environment variables.
Building on master in workspace /jenkins-server/Home/jobs/TestChildJobs/workspace/498111b4
ERROR: Build aborted. Can't trigger undefined projects. -1 of the below project(s) can't be resolved:
${ChildJobs}
Check your configuration!
Notifying upstream projects of job completion
Finished: FAILURE
One note though: all the specified downstream jobs are actually triggered and executed as needed. Only the matrix job's status is set to failure and no other build steps are executed. Not sure if the fact that the job defined as matrix has any impact here.
Environment:
Jenkins 1.509 on
Red Hat 4.4.6-4
Parameterized Trigger Plugin v.2.21
Project:
Jenkins
Priority:
Major
Reporter:
Vlad Dovlekaev
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] [throttle-concurrents] (JENKINS-12240) Cannot throttle a matrix job without throttling the axis children
Vlad Dovlekaev commented on JENKINS-12240 Cannot throttle a matrix job without throttling the axis children Is it possible to configure the job to get the old behavior back. We have a very large matrix job and would like to limit it to execute just a part of the matrix at the same time ( resource limited ). Is the new ticket needed for this issue ? 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] [throttle-concurrents] (JENKINS-20574) throttling needs to account for all child jobs of a multiconfiguration job
Vlad Dovlekaev commented on JENKINS-20574 throttling needs to account for all child jobs of a multiconfiguration job Having the same issue here. Voting to fix/add this feature. Major blocker for us as we have a limited shared resources for very large matrix job and would like to throttle the child jobs as well. 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-5891) Create job with downstream project by remote api doesn't work
Vlad Dovlekaev commented on JENKINS-5891 Create job with downstream project by remote api doesnt work We are currently using Jenkins ver. 1.509.4 and the problem seems to be resolved. 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] [gerrit-trigger] (JENKINS-21036) NullPointerException in StreamWatchdog when trying to stop/restart
Vlad Dovlekaev commented on JENKINS-21036 NullPointerException in StreamWatchdog when trying to stop/restart Which release of Gerrit-Trigger your fix will be available in ? 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/groups/opt_out.
[JIRA] (JENKINS-14161) SVN checkout failure doesn't prevent the build from starting
Vlad Dovlekaev created JENKINS-14161 SVN checkout failure doesnt prevent the build from starting Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 20/Jun/12 12:48 PM Description: It seems that certain types of SVN checkout failures do not prevent the build to continue to execute. In current case the failure was due to the error during the local file delete operation. The problem is that previous workspace is used to execute the build - which caused the wrong results to be reported, obviously. The following log shows the problem: Started by upstream project "PCompiler_vd" build number 46 EnvInject - Preparing an environment for the build. Building remotely on OCL-W764-WST04 in workspace c:\H\workspace\PCompiler_vd\BldT/Debug/TrgtT/Win32/slvT/GP Cleaning up c:\H\workspace\PCompiler_vd\BldT\Debug\TrgtT\Win32\slvT\GP\trunk Deleting c:\H\workspace\PCompiler_vd\BldT\Debug\TrgtT\Win32\slvT\GP\trunk\Binaries.7z Deleting c:\H\workspace\PCompiler_vd\BldT\Debug\TrgtT\Win32\slvT\GP\trunk\build ERROR: Failed to update https://subversion.***/branches/sanity/vd/sanity org.tmatesoft.svn.core.SVNException: svn: Unable to delete c:\H\workspace\PCompiler_vd\BldT\Debug\TrgtT\Win32\slvT\GP\trunk\build\Win32\backend\llvm\bin\Debug at hudson.scm.subversion.UpdateWithCleanUpdater$TaskImpl$1.handleStatus(UpdateWithCleanUpdater.java:78) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.sendUnversionedStatus(SVNStatusEditor.java:358) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.getDirStatus(SVNStatusEditor.java:208) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.closeEdit(SVNStatusEditor.java:114) at org.tmatesoft.svn.core.wc.SVNStatusClient.doStatus(SVNStatusClient.java:380) at hudson.scm.subversion.UpdateWithCleanUpdater$TaskImpl.preUpdate(UpdateWithCleanUpdater.java:66) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:134) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Unable to delete c:\H\workspace\PCompiler_vd\BldT\Debug\TrgtT\Win32\slvT\GP\trunk\build\Win32\backend\llvm\bin\Debug at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:101) ... 22 more Caused by: java.io.IOException: Unable to delete c:\H\workspace\PCompiler_vd\BldT\Debug\TrgtT\Win32\slvT\GP\trunk\build\Win32\backend\llvm\bin\Debug at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:287) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.Util.deleteContentsRecursive(Util.java:198) at hudson.Util.deleteRecursive(Util.java:278) at hudson.scm.subversion.UpdateWithCleanUpdater$TaskImpl$1.handleStatus(UpdateWithCleanUpdater.java:74) ... 21 more
