[JIRA] (JENKINS-15507) Environment variables are not injected in parent matrix job
Gregory Boissinot commented on JENKINS-15507 Environment variables are not injected in parent matrix job With a matrix job, by default for a SCM checkout, this step is exectued: at job level (before each axe) for each axe All source code are gathered in a single directory: the workspace Can you confirm it the same behaviour for the Clearcase Jenkins plugin? EnvInject variables are only injected at the moment for each axe. Therefore, you're right there is an 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
[JIRA] (JENKINS-15507) Environment variables are not injected in parent matrix job
Gregory Boissinot started work on JENKINS-15507 Environment variables are not injected in parent matrix job Change By: Gregory Boissinot (14/Oct/12 9:12 AM) Status: Open InProgress 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
[JIRA] (JENKINS-15475) CreateProcess error=87, The parameter is incorrect
Gregory Boissinot started work on JENKINS-15475 CreateProcess error=87, The parameter is incorrect Change By: Gregory Boissinot (14/Oct/12 9:14 AM) Status: Open InProgress 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
[JIRA] (JENKINS-15475) CreateProcess error=87, The parameter is incorrect
Gregory Boissinot commented on JENKINS-15475 CreateProcess error=87, The parameter is incorrect 0.21 is a very old version for the EnvInject plugin. Each new version keeps backward compatibility (at least in theory, i try). Maybe, I missed a thing with the dostrigger plugin. I can try to reproduce the problem. Please could you attach your job configuration file (confg.xml)? 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
[JIRA] (JENKINS-15515) Provide environment variable for the last changeset that contributed to a projects build
Andrew West commented on JENKINS-15515 Provide environment variable for the last changeset that contributed to a projects build Sorry for that, maybe this example might make things a little clearer. Given the depot layout //depot/project1/test.txt //depot/project2/test.txt Which contains the history Change 1 by andrew@desktop on 2012/10/14 11:04:05 Added test.txt to Project1 Affected files ... ... //depot/project1/test.txt#1 add Change 2 by andrew@desktop on 2012/10/14 11:07:12 Added test.txt to project2 Affected files ... ... //depot/project2/test.txt#1 add If I'd set up a project in jenkins using the view map //depot/project1/... //workspace/... Which is simply a job that calls; echo "P4_CHANGELIST = $P4_CHANGELIST" Building this job after changeset 1 is submitted (before changeset 2 is submitted) I get the expected output P4_CHANGELIST = 1 Then if I submit changeset 2 and build the project again I get the response P4_CHANGELIST = 2 Am I misconstruing what P4_CHANGELIST represents? I'd expect it to be the changeset id of the last changeset associated with a project, but under all the projects I've used it with it seems to be the last sync'd changeset regardless of the workspace. 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
[JIRA] (JENKINS-15515) Provide environment variable for the last changeset that contributed to a projects build
Andrew West commented on JENKINS-15515 Provide environment variable for the last changeset that contributed to a projects build Output log of build #2 for Project1 Started by user Andrew West Building on master in workspace /var/lib/jenkins/jobs/Project1/workspace Using master perforce client: Project1 workspace $ /usr/local/bin/p4 workspace -o Project1 Last build changeset: 1 workspace $ /usr/local/bin/p4 changes -s submitted -m 1 //... workspace $ /usr/local/bin/p4 -s changes -s submitted //Project1/...@2,@2 Sync'ing workspace to changelist 2. workspace $ /usr/local/bin/p4 -s sync //Project1/...@2 Sync complete, took 17 ms workspace $ /bin/sh -xe /tmp/hudson6120382511269786976.sh + echo P4_CHANGELIST = 2 P4_CHANGELIST = 2 Finished: SUCCESS p4d version: Rev. P4D/LINUX26X86_64/2012.2/525804 (2012/09/18). p4 version: Rev. P4/LINUX26X86_64/2012.2/525804 (2012/09/18). perforce plugin version: 1.3.17 jenkins version: 1.485 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
[JIRA] (JENKINS-15515) Provide environment variable for the last changeset that contributed to a projects build
Andrew West commented on JENKINS-15515 Provide environment variable for the last changeset that contributed to a projects build Apologies for this, maybe this is a bug in perforce. Ignoring jenkins for the moment and going straight to the command line 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
[JIRA] (JENKINS-15515) Provide environment variable for the last changeset that contributed to a projects build
Andrew West edited a comment on JENKINS-15515 Provide environment variable for the last changeset that contributed to a projects build Apologies for this, maybe this is a bug in perforce. Ignoring jenkins for the moment and going straight to the command line Using the workspace path andrew@www:depot$ P4CLIENT=Project1 P4PORT=www:1666 p4 changes -s submitted //... Change 2 on 2012/10/14 by andrew@desktop 'Added test.txt to project2 ' Change 1 on 2012/10/14 by andrew@desktop 'Added test.txt to Project1 ' Using the depot path andrew@www:depot$ P4CLIENT=Project1 P4PORT=www:1666 p4 changes -s submitted //depot/project1/... Change 1 on 2012/10/14 by andrew@desktop 'Added test.txt to Project1 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
[JIRA] (JENKINS-15516) System groovy script file succeeds on build slave when script does not exist
Andrew West
created JENKINS-15516
System groovy script file succeeds on build slave when script does not exist
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy
Created:
14/Oct/12 12:51 PM
Description:
Configure a job to run on a non-master node, and define an "Execute system Groovy script" that calls a "Groovy script file" called "test.groovy"
"test.groovy" contains
println("testing")
If the file "test.groovy" doesn't exist in the non-master node's workspace the build step succeeds.
Project:
Jenkins
Priority:
Major
Reporter:
Andrew West
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
[JIRA] (JENKINS-15507) Environment variables are not injected in parent matrix job
SCM/JIRA link daemon commented on JENKINS-15507 Environment variables are not injected in parent matrix job Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java http://jenkins-ci.org/commit/envinject-plugin/d196214e3aa9c739b7a15e25a19537a72ea1d0f1 Log: Proposal to JENKINS-15507 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
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
SCM/JIRA link daemon resolved JENKINS-15132 as Fixed Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 Change By: SCM/JIRA link daemon (14/Oct/12 2:21 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
SCM/JIRA link daemon commented on JENKINS-15132 Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/AbstractCvs.java src/main/java/hudson/scm/CvsModule.java http://jenkins-ci.org/commit/cvs-plugin/4822c4fbb2f1be2bcadd8853713f87d433ecbc84 Log: FIXED JENKINS-15132 Don't add '-d' flag on checkout if module name is not over-ridden 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
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
Michael Clarke assigned JENKINS-15132 to Michael Clarke Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 Change By: Michael Clarke (14/Oct/12 2:27 PM) Assignee: MichaelClarke 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
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
Michael Clarke commented on JENKINS-15132 Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 This issue will still exist for the following situations due to the workings of CVS (i.e. there's not an easy way to fix them in CVS plugin): 1. Checking out a single file into a workspace in non legacy mode - updates will checkout all sibling files and sub-modules (initial checkout will be ok) 2. Checking out a single file into a workspace with the local name set the same as the remote name - checks-out out the file into a folder named the same as the file name (e.g. remote name of /path/to/file.txt would cause file to be checked out into /path/to/file.txt/file.txt). Work around this by setting the local name to only include the module directory names (e.g checking out /path/to/file.txt should set local name as /path/to) 3. Checking out a single file with a remote name set - updates will checkout all sibling files and sub-modules. 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
[JIRA] (JENKINS-13176) how to restore deleted hudson job
Michael Clarke closed JENKINS-13176 as Not A Defect how to restore deleted hudson job There is no way to restore the job unless you have a backup from an external source or use a plugin that backs-up your job config. Also, consider setting access restrictions on your server that prevent un-trusted users from deleting jobs. Change By: Michael Clarke (14/Oct/12 2:40 PM) Status: Open Closed Assignee: MichaelClarke Resolution: NotADefect 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
[JIRA] (JENKINS-15507) Environment variables are not injected in parent matrix job
Gregory Boissinot commented on JENKINS-15507 Environment variables are not injected in parent matrix job I don't know why I previously excluded the environment injection at the matrix job level. However, I added it. Please could you check if this new version suit you (about an official release)? The snapshot version can be found here: https://buildhive.cloudbees.com/job/jenkinsci/job/envinject-plugin/59/org.jenkins-ci.plugins$envinject/ 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
[JIRA] (JENKINS-14051) A PollingLog would be helpful in setting up dosTrigger
Gregory Boissinot started work on JENKINS-14051 A PollingLog would be helpful in setting up dosTrigger Change By: Gregory Boissinot (14/Oct/12 2:49 PM) Status: Open InProgress 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
[JIRA] (JENKINS-14051) A PollingLog would be helpful in setting up dosTrigger
Gregory Boissinot commented on JENKINS-14051 A PollingLog would be helpful in setting up dosTrigger Please could update the status or add a comment? Without any further activity, I suggest closing the issue due to 'DosTrigger doesn't have current maintener' and it exists an another plugin: the ScriptTrigger plugin and it covers all dos-trigger features. 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
[JIRA] (JENKINS-14051) A PollingLog would be helpful in setting up dosTrigger
Gregory Boissinot assigned JENKINS-14051 to Gregory Boissinot A PollingLog would be helpful in setting up dosTrigger Change By: Gregory Boissinot (14/Oct/12 2:49 PM) Assignee: GregoryBoissinot 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
[JIRA] (JENKINS-13273) cannot launch Jenkins on a Windows 7
Michael Clarke updated JENKINS-13273 cannot launch Jenkins on a Windows 7 Change By: Michael Clarke (14/Oct/12 2:50 PM) Component/s: core Component/s: lastsuccessversioncolumn 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
[JIRA] (JENKINS-14053) Being able to read environment variables in dos-trigger would be helpful
Gregory Boissinot commented on JENKINS-14053 Being able to read environment variables in dos-trigger would be helpful Could you test the ScriptTrigger plugin. It is supposed to meet all dos-trigger features (and more). Additionally, environment variables are supposed to be handle very 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
[JIRA] (JENKINS-14053) Being able to read environment variables in dos-trigger would be helpful
Gregory Boissinot started work on JENKINS-14053 Being able to read environment variables in dos-trigger would be helpful Change By: Gregory Boissinot (14/Oct/12 2:51 PM) Status: Open InProgress 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
[JIRA] (JENKINS-14053) Being able to read environment variables in dos-trigger would be helpful
Gregory Boissinot edited a comment on JENKINS-14053 Being able to read environment variables in dos-trigger would be helpful Could you test the ScriptTrigger plugin? It is supposed to meet all dos-trigger features (and more). Additionally, environment variables are supposed to be handle very 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
[JIRA] (JENKINS-14739) EnvInject params are overwritten by default string params
Gregory Boissinot commented on JENKINS-14739 EnvInject params are overwritten by default string params I'm afraid I can't solve this issue. Please help me by providing more information or further investigation? 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
[JIRA] (JENKINS-15400) pipeline plugin shows global passwords from 'EnvInject' plugin on build card as common env
Gregory Boissinot commented on JENKINS-15400 pipeline plugin shows global passwords from EnvInject plugin on build card as common env EnvInject is not aimed at being intrusive. I understand the compatibility issue between these two plugins. The only solution for me to check parameter type from the build-pipeline plugin. 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
[JIRA] (JENKINS-15429) Envinqect plugin not allowing proporties with \u0027 to be added
Gregory Boissinot commented on JENKINS-15429 Envinqect plugin not allowing proporties with \u0027 to be added Please could you check again? I tried it and all is OK. 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
[JIRA] (JENKINS-15429) Envinqect plugin not allowing proporties with \u0027 to be added
Gregory Boissinot started work on JENKINS-15429 Envinqect plugin not allowing proporties with \u0027 to be added Change By: Gregory Boissinot (14/Oct/12 3:31 PM) Status: Open InProgress 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
[JIRA] (JENKINS-15473) Jenkins forgets about old builds under IO pressure
Eric Fleischman commented on JENKINS-15473 Jenkins forgets about old builds under IO pressure Perhaps related to this recent feature? https://issues.jenkins-ci.org/browse/JENKINS-8754 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
[JIRA] (JENKINS-166) Some CVS/SVN changes might not be visible to users
Michael Clarke resolved JENKINS-166 as Fixed Some CVS/SVN changes might not be visible to users I believe this is fixed (it works in the CVS plugin at least). SCM plugins can either do their polling as part of the checkout activity or following checkout. If there is an error during checkout which the plugin doesn't handle then the build is marked as failed and then it's down to the SCM plugin to work out what to do on the next build. CVS checks for changes and generate changelogs since the start time of the last successful build, other SCM plugins (Perforce, GIT, clearcase etc) may work differently but that would have to be raised as issues against those specific components Change By: Michael Clarke (14/Oct/12 4:34 PM) Status: Open Resolved Assignee: MichaelClarke Resolution: Fixed 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
[JIRA] (JENKINS-34) Provide Code Backout command in Hudson
Michael Clarke closed JENKINS-34 as Wont Fix Provide Code Backout command in Hudson Neither link provided works anymore. Given no-one has chased this, I'm closing it as Won't fix, although am happy for it to be re-opened and assigned to a specific plugin if the feature is still needed Change By: Michael Clarke (14/Oct/12 4:38 PM) Status: Open Closed Assignee: KohsukeKawaguchi MichaelClarke Resolution: WontFix 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
[JIRA] (JENKINS-41) email notification could provide more information about unstable build
Michael Clarke resolved JENKINS-41 as Fixed email notification could provide more information about unstable build This feature is available through email-ext plugin Change By: Michael Clarke (14/Oct/12 4:40 PM) Status: Open Resolved Assignee: MichaelClarke Resolution: Fixed 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
[JIRA] (JENKINS-242) Make path to cvs configurable
Michael Clarke resolved JENKINS-242 as Fixed Make path to cvs configurable cvs-plugin now uses a pure java implementation so doesn't require users to have cvs installed on their Jenkins machine. The other problem referred to about timestamps has also been resolved but should have been raised as a separate issue to give it visibility Change By: Michael Clarke (14/Oct/12 4:53 PM) Status: Reopened Resolved Assignee: MichaelClarke Resolution: Fixed 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
[JIRA] (JENKINS-267) suggest the name for tagging a build
Michael Clarke resolved JENKINS-267 as Fixed suggest the name for tagging a build Most (if not all) SCMs suggest a tag name based on build number. If this is not the case then open an issue against the relevant component Change By: Michael Clarke (14/Oct/12 4:56 PM) Status: Open Resolved Assignee: MichaelClarke Resolution: Fixed 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
[JIRA] (JENKINS-286) more flexible settings for SCM changelog computation
Michael Clarke resolved JENKINS-286 as Wont Fix more flexible settings for SCM changelog computation CVS supports checking out multiple modules and will generate changelogs for all of them. This should prevent the need for using scrips to checkout other files. Change By: Michael Clarke (14/Oct/12 4:58 PM) Status: Open Resolved Assignee: MichaelClarke Resolution: WontFix 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
[JIRA] (JENKINS-287) Incremental build support
Michael Clarke resolved JENKINS-287 as Fixed Incremental build support This has been fixed in CVS plugin - there's an option to clean on failed checkout which wipes out the workspace and retries the checkout. Not sure about other SCM plugins, but if they're needed then please open a separate issue against the relevant components. Change By: Michael Clarke (14/Oct/12 5:05 PM) Status: Reopened Resolved Assignee: MichaelClarke Resolution: Fixed 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
[JIRA] (JENKINS-346) many schedules per project
Michael Clarke commented on JENKINS-346 many schedules per project Can this not be done using the conditional build-step plugin? 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
[JIRA] (JENKINS-15457) Passwords leaked in logs
Gregory Boissinot started work on JENKINS-15457 Passwords leaked in logs Change By: Gregory Boissinot (14/Oct/12 6:50 PM) Status: Open InProgress 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
[JIRA] (JENKINS-15457) Passwords leaked in logs
Gregory Boissinot commented on JENKINS-15457 Passwords leaked in logs Could give the plugins list you know where it is managed correctly? 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
[JIRA] (JENKINS-15035) cobertura plugin don't validate report files and later fail to parse them
Yury Zaytsev commented on JENKINS-15035 cobertura plugin dont validate report files and later fail to parse them Same here, upgrade from 1.6 to 1.7 broke all my builds publishing Cobertura reports, downgrade fixed it again. There is something wrong with your check, please fix it! My reports start like this: ?xml version="1.0" ? !DOCTYPE coverage SYSTEM 'http://cobertura.sourceforge.net/xml/coverage-03.dtd' coverage branch-rate="0" line-rate="0.6683" timestamp="1350243774936" version="3.5" !-- Generated by coverage.py: http://nedbatchelder.com/code/coverage -- packages 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
[JIRA] (JENKINS-15457) Passwords leaked in logs
aristedes commented on JENKINS-15457 Passwords leaked in logs Here is the output from a similar run of our maven plugin: [INFO] --- maven-release-plugin:2.1:prepare (default-cli) @ services --- [INFO] Verifying that there are no local modifications... [INFO] ignoring changes on: pom.xml.next, release.properties, pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag [INFO] Executing: /bin/sh -c cd /var/hudson/workspace/onCourse-services svn --username andrey --password '*' --no-auth-cache --non-interactive status [INFO] Working directory: /var/hudson/workspace/onCourse-services [INFO] Ignoring SNAPSHOT depenedencies and plugins ... 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
[JIRA] (JENKINS-15457) Passwords leaked in logs
aristedes edited a comment on JENKINS-15457 Passwords leaked in logs Here is the output from a similar run of the maven plugin: [INFO] --- maven-release-plugin:2.1:prepare (default-cli) @ services --- [INFO] Verifying that there are no local modifications... [INFO] ignoring changes on: pom.xml.next, release.properties, pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag [INFO] Executing: /bin/sh -c cd /var/hudson/workspace/onCourse-services svn --username andrey --password '*' --no-auth-cache --non-interactive status [INFO] Working directory: /var/hudson/workspace/onCourse-services [INFO] Ignoring SNAPSHOT depenedencies and plugins ... 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
[JIRA] (JENKINS-10577) Builds fails with JDK_Installed\jdk.exe error in both 1.423 and 1.424 versions
kokawa assigned JENKINS-10577 to Kohsuke Kawaguchi Builds fails with JDK_Installed\jdk.exe error in both 1.423 and 1.424 versions you intended to assign to kohsuke kawaguchi, maybe. Change By: kokawa (14/Oct/12 11:30 PM) Assignee: kokawa KohsukeKawaguchi 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
[JIRA] (JENKINS-15496) Add Local module directory field like Subversion plugin
apgray updated JENKINS-15496 Add Local module directory field like Subversion plugin Change By: apgray (15/Oct/12 12:02 AM) Attachment: AddLocalModuleDirectoryField.jpg 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
[JIRA] (JENKINS-12009) Downstream projects links disappeared
Daniel Beck commented on JENKINS-12009 Downstream projects links disappeared This is probably duplicated by 13502. Could you verify my analysis there, i.e. that it's related to missing read permissions for the downstream jobs? 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
[JIRA] (JENKINS-15496) Add Local module directory field like Subversion plugin
samngms commented on JENKINS-15496 Add Local module directory field like Subversion plugin Please see if my understanding is correct. For example, if the source directory is "c:\project1\component1\folder1", it may checkout to path "C:\xx\yy\" If the "local_module_directory" is "folder2", then it will checkout to path "c:\xx\yy\folder2", am I correct? If the "local_module_directory" is undefined, then it will checkout to path "c:\xx\yy\folder1", am I correct? If the "local_module_directory" is ".", then it will checkout to path "c:\xx\yy", same as before, am I correct? But for backward compatibility, I think I would change the implementation to if "local_module_directory" is not defined, it will just checkout to "c:\xx\yy" (same as ".") 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
[JIRA] (JENKINS-15517) Findbugs total issue is not displaying properly
King Hpd created JENKINS-15517 Findbugs total issue is not displaying properly Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core Created: 15/Oct/12 2:06 AM Description: In Findbugs log it is displaying the number of warnings and when we add the total warnings then it comes more than 2000 but in findbugs report it is displayed as 1490 FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_BasicSmsReceiver_src_BasicSmsReceiver_intermediates_classes.jar_findbugs.xml of module with 4 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Bluetooth_src_Bluetooth_intermediates_classes.jar_findbugs.xml of module with 56 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Browser_src_Browser_intermediates_classes.jar_findbugs.xml of module with 161 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Calculator_src_Calculator_intermediates_classes.jar_findbugs.xml of module with 48 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Calendar_src_Calendar_intermediates_classes.jar_findbugs.xml of module with 135 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Camera_src_Camera_intermediates_classes.jar_findbugs.xml of module with 92 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_CellBroadcastReceiver_src_CellBroadcastReceiver_intermediates_classes.jar_findbugs.xml of module with 11 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_CertInstaller_src_CertInstaller_intermediates_classes.jar_findbugs.xml of module with 12 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Contacts_src_Contacts_intermediates_classes.jar_findbugs.xml of module with 220 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Email_src_Email_intermediates_classes.jar_findbugs.xml of module with 284 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Exchange_src_Exchange_intermediates_classes.jar_findbugs.xml of module with 237 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Gallery2_src_Gallery2_intermediates_classes.jar_findbugs.xml of module with 145 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_Gallery_src_Gallery_intermediates_classes.jar_findbugs.xml of module with 20 warnings. FINDBUGS Successfully parsed file /home/y00213920/.jenkins/jobs/Agent_Test_Google_Bugfix_Create/workspace/findbugsreport/Agent_Test_Google_Bugfix_Create/135/packages_apps_HTMLViewer_src_HTMLViewer_intermediates_classes.jar_findbugs.xml of module with 2 warnings. FINDBUGS Successfully parsed file
[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result
kevincai created JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result Issue Type: Bug Assignee: stephenconnolly Components: cobertura Created: 15/Oct/12 3:19 AM Description: Get following error message with Cobertura-1.7 version. Downgrade to 1.5 works fine. Publishing Cobertura coverage report... FATAL: Unable to find coverage results hudson.util.IOException2: remote file operation failed: /home/jenkins/squeeze-amd64/workspace/trogdor/arch/amd64/dist/Debian-6.0 at hudson.remoting.Channel@2c3525fc:seblddev-debian-squeeze-amd64 at hudson.FilePath.act(FilePath.java:835) at hudson.FilePath.act(FilePath.java:821) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:335) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@7dc8e850 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:662) at hudson.FilePath.act(FilePath.java:828) ... 11 more Caused by: java.io.NotSerializableException: hudson.plugins.cobertura.CoberturaPublisher at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) ... 14 more Environment: Jenkins-1.466.2, Cobertura-1.7 Project: Jenkins Priority: Major Reporter: kevincai 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
[JIRA] (JENKINS-15490) checkstyle plugin does not work in the latest version of Jenkins
Justin Ye commented on JENKINS-15490 checkstyle plugin does not work in the latest version of Jenkins I created a empty project with our enterprise parent pom and it has the same problem but when the pom is empty, the issue is gone. So I remove the config item one by one to see which one is the cause and it turns out the config below: build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav-jackrabbit/artifactId version1.0/version /extension /extensions /build Just add this part into an empty pom will cause this issue. Using latest version 2.2 still cause 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
[JIRA] (JENKINS-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
Kevin Chiu commented on JENKINS-13871 Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Same issue here. This is a very common case for worklfows that want to have a better utilization of nodes with the same type. 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
[JIRA] (JENKINS-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
Kevin Chiu edited a comment on JENKINS-13871 Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Same issue here. This is a also a very common case for common step for workflows in which multiple instants of job will be executed on the node. 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
[JIRA] (JENKINS-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
Kevin Chiu edited a comment on JENKINS-13871 Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Same issue here. This is also a very common case when common/shared step is created for workflows in which multiple instants of job will be executed on the node. 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
[JIRA] (JENKINS-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
Kevin Chiu edited a comment on JENKINS-13871 Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Same issue here. This is also a very common case when commonly used step is created for workflows in which multiple instants of job will be executed on the same node. 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
