[JIRA] (JENKINS-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42383 Re: Maven and javadoc Plugin dependencies are not required when using reflection Code changed in jenkins User: Victor Martinez Path: pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GradleWrapperChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/HardcodedScriptChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JavadocChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/ccaba773360c7e3c2ab0aa0ac6fe07f922d6390b Log: JENKINS-42383 Removed dependent plugins (#16) JENKINS-42383 Removed dependent plugins 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-35447) bug on moveing pipeline projects into folder
Title: Message Title
ilya rosman edited a comment on JENKINS-35447
Re: bug on moveing pipeline projects into folder
I can add some details.I found the same issue and googled this bug looking forjava.io.FileNotFoundException: lastUnstableBuild (No such file or directory)First of all this issue is reproducible for the latest 5.18 folder_plugin versionThe root of this issue is the following.Let's assume we have the following job structure:{code}ubuntu@ubuntu-xenial:~$ ls -l /var/lib/jenkins/jobs/XXX/builds/total 40drwxr-xr-x 2 1002 1002 4096 Feb 14 09:55 327drwxr-xr-x 4 1002 1002 4096 Feb 14 10:14 328drwxr-xr-x 4 1002 1002 4096 Feb 15 10:57 329drwxr-xr-x 4 1002 1002 4096 Feb 17 08:29 330drwxr-xr-x 4 1002 1002 4096 Feb 17 09:18 331drwxr-xr-x 4 1002 1002 4096 Feb 20 13:55 332drwxr-xr-x 4 1002 1002 4096 Feb 22 15:29 333drwxr-xr-x 4 1002 1002 4096 Feb 27 11:18 334lrwxrwxrwx 1 1002 10023 Feb 14 09:55 lastFailedBuild -> 327lrwxrwxrwx 1 1002 10023 Feb 27 11:18 lastStableBuild -> 334lrwxrwxrwx 1 1002 10023 Feb 27 11:18 lastSuccessfulBuild -> 334lrwxrwxrwx 1 1002 10022 Jun 27 2016 lastUnstableBuild -> -1lrwxrwxrwx 1 1002 10023 Feb 14 09:55 lastUnsuccessfulBuild -> 327-rw-r--r-- 1 1002 10020 Jun 27 2016 legacyIds{code}Corresponding links point to existing folders excepting lastUnstableBuild which points to non existing dir for now.It is supposed to be changed when UnstableBuild appears. For example in 332 build versionWe wanna move XXX job to some newly created Test_FolderI used 3 cases how to handle it:1) Using Jenkins GUI2) Using post request curl -L -X POST http://10.229.55.117:8080/job/XXX/move/move?destination=/Test_Folder --user xxx:yyy3) Using groovy script like that{code}def FOLDER_NAME = 'Test_Folder'def JOB_REGEX = 'XXX'import jenkins.*import jenkins.model.*import hudson.*import hudson.model.*jenkins = Jenkins.instancedef folder = jenkins.getItemByFullName(FOLDER_NAME)if (folder == null) { println "ERROR: Folder '$FOLDER_NAME' not found" return}jenkins.items.grep { it.name =~ "${JOB_REGEX}" }.each { job -> println "Moving '$job.name' to '$folder.name'" Items.move(job, folder)}{code}All these methods transform links (lastFailedBuild, lastStableBuild, lastSuccessfulBuild, lastUnsuccessfulBuild) to dirs ( accroding according to the content of 327, 334, 334, 327 correspondingly).In case of lastUnstableBuild -> -1 (points to nothing) it can not be transformed to dir and it is failed.As result moving is broken. Job is copied. Original is not deleted. It is why it can not be copied again (already exist) Copied version has dirs instead of links{code}ubuntu@ubuntu-xenial:~$ ls -l /var/lib/jenkins/jobs/Test_Folder/jobs/XXX/builds/total 56drwxr-xr-x 4 jenkins jenkins 4096 Feb 13 12:17 325drwxr-xr-x 4 jenkins jenkins 4096 Feb 14 09:16 326drwxr-xr-x 2 jenkins jenkins 4096 Feb 14 09:55 327drwxr-xr-x 4 jenkins jenkins 4096 Feb 14 10:14 328drwxr-xr-x 4 jenkins jenkins 4096 Feb 15 10:57 329drwxr-xr-x 4 jenkins jenkins 4096 Feb 17 08:29 330drwxr-xr-x 4 jenkins jenkins 4096 Feb 17 09:18 331drwxr-xr-x 4 jenkins jenkins 4096 Feb 20 13:55 332drwxr-xr-x 4 jenkins jenkins 4096 Feb 22 15:29 333drwxr-xr-x 4 jenkins jenkins 4096 Feb 27 11:18 334drwxr-xr-x 2 jenkins jenkins 4096 Feb 14 09:55 lastFailedBuilddrwxr-xr-x 4 jenkins jenkins 4096 Feb 27 11:18 lastStableBuilddrwxr-xr-x 4 jenkins jenkins 4096 Feb 27 11:18 lastSuccessfulBuilddrwxr-xr-x 2 jenkins jenkins 4096 Feb 14 09:55 lastUnsuccessfulBuild-rw-r--r-- 1 jenkins jenkins0 Jun 27 2016 legacyIds{code}P.s. As we can see, the only 1 safest way for us (to migrate jobs to folders) is using cp -arp copying on jenkins linux master from jobs folder to Name_of_Folder/jobs.
[JIRA] (JENKINS-35447) bug on moveing pipeline projects into folder
Title: Message Title
ilya rosman edited a comment on JENKINS-35447
Re: bug on moveing pipeline projects into folder
I can add some details.I found the same issue and googled this bug looking forjava.io.FileNotFoundException: lastUnstableBuild (No such file or directory)First of all this issue is reproducible for the latest 5.18 folder_plugin versionThe root of this issue is the following.Let's assume we have the following job structure:{code}ubuntu@ubuntu-xenial:~$ ls -l /var/lib/jenkins/jobs/XXX/builds/total 40drwxr-xr-x 2 1002 1002 4096 Feb 14 09:55 327drwxr-xr-x 4 1002 1002 4096 Feb 14 10:14 328drwxr-xr-x 4 1002 1002 4096 Feb 15 10:57 329drwxr-xr-x 4 1002 1002 4096 Feb 17 08:29 330drwxr-xr-x 4 1002 1002 4096 Feb 17 09:18 331drwxr-xr-x 4 1002 1002 4096 Feb 20 13:55 332drwxr-xr-x 4 1002 1002 4096 Feb 22 15:29 333drwxr-xr-x 4 1002 1002 4096 Feb 27 11:18 334lrwxrwxrwx 1 1002 10023 Feb 14 09:55 lastFailedBuild -> 327lrwxrwxrwx 1 1002 10023 Feb 27 11:18 lastStableBuild -> 334lrwxrwxrwx 1 1002 10023 Feb 27 11:18 lastSuccessfulBuild -> 334lrwxrwxrwx 1 1002 10022 Jun 27 2016 lastUnstableBuild -> -1lrwxrwxrwx 1 1002 10023 Feb 14 09:55 lastUnsuccessfulBuild -> 327-rw-r--r-- 1 1002 10020 Jun 27 2016 legacyIds{code}Corresponding links point to existing folders excepting lastUnstableBuild which points to non existing dir for now.It is supposed to be changed when UnstableBuild appears. For example in 332 build versionWe wanna move XXX job to some newly created Test_FolderI used 3 cases how to handle it:1) Using Jenkins GUI2) Using post request curl -L -X POST http://10.229.55.117:8080/job/XXX/move/move?destination=/Test_Folder --user xxx:yyy3) Using groovy script like that{code}def FOLDER_NAME = 'Test_Folder'def JOB_REGEX = 'XXX'import jenkins.*import jenkins.model.*import hudson.*import hudson.model.*jenkins = Jenkins.instancedef folder = jenkins.getItemByFullName(FOLDER_NAME)if (folder == null) { println "ERROR: Folder '$FOLDER_NAME' not found" return}jenkins.items.grep { it.name =~ "${JOB_REGEX}" }.each { job -> println "Moving '$job.name' to '$folder.name'" Items.move(job, folder)}{code}All these methods transform links (lastFailedBuild, lastStableBuild, lastSuccessfulBuild, lastUnsuccessfulBuild) to dirs (according to the content of 327, 334, 334, 327 correspondingly).In case of lastUnstableBuild -> -1 (points to nothing) it can not be transformed to dir and it is failed.As result moving is broken. Job is partially copied. Original is not deleted. It is why it can not be copied again (already exist) Copied version has dirs instead of links . lastUnstableBuild is missed. {code}ubuntu@ubuntu-xenial:~$ ls -l /var/lib/jenkins/jobs/Test_Folder/jobs/XXX/builds/total 56drwxr-xr-x 4 jenkins jenkins 4096 Feb 13 12:17 325drwxr-xr-x 4 jenkins jenkins 4096 Feb 14 09:16 326drwxr-xr-x 2 jenkins jenkins 4096 Feb 14 09:55 327drwxr-xr-x 4 jenkins jenkins 4096 Feb 14 10:14 328drwxr-xr-x 4 jenkins jenkins 4096 Feb 15 10:57 329drwxr-xr-x 4 jenkins jenkins 4096 Feb 17 08:29 330drwxr-xr-x 4 jenkins jenkins 4096 Feb 17 09:18 331drwxr-xr-x 4 jenkins jenkins 4096 Feb 20 13:55 332drwxr-xr-x 4 jenkins jenkins 4096 Feb 22 15:29 333drwxr-xr-x 4 jenkins jenkins 4096 Feb 27 11:18 334drwxr-xr-x 2 jenkins jenkins 4096 Feb 14 09:55 lastFailedBuilddrwxr-xr-x 4 jenkins jenkins 4096 Feb 27 11:18 lastStableBuilddrwxr-xr-x 4 jenkins jenkins 4096 Feb 27 11:18 lastSuccessfulBuilddrwxr-xr-x 2 jenkins jenkins 4096 Feb 14 09:55 lastUnsuccessfulBuild-rw-r--r-- 1 jenkins jenkins0 Jun 27 2016 legacyIds{code}P.s. As we can see, the only 1 safest way for us (to migrate jobs to folders) is using cp -arp copying on jenkins linux master from job
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title wolfs commented on JENKINS-42429 Re: Cannot view dependency of jobs Could you please check if there is some error in the Jenkins log? 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-24453) Jenkins server got blue screen to death
Title: Message Title Oleg Nenashev commented on JENKINS-24453 Re: Jenkins server got blue screen to death Yes, there is a known issue with WinP: https://github.com/kohsuke/winp/issues/22 . This fix has been released in winp-1.24 and then integrated into Jenkins 2.34: https://github.com/jenkinsci/jenkins/commit/63c2f6c5d7d154a3a0f58c54f04f9b1a25ea5385. According to the code the fix has been also backported to Jenkins 2.32.1 though changelogs do not say it explicitly. I will make sure that changelogs get updated. The recommendation is to update the core to the latest LTS 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-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title tawanda minya commented on JENKINS-42408 Re: HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found Awesome thanks guys I had furiously tried googling for solutions to this but was stuck I can still access the config from the administration side so will do that for now Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title tawanda minya closed an issue as Duplicate Thank You Ivan Jenkins / JENKINS-42408 HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found Change By: tawanda minya Status: Resolved Closed 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-42429) Cannot view dependency of jobs
Title: Message Title
Vikas Kumar commented on JENKINS-42429
Re: Cannot view dependency of jobs
Hello wolfs, There is nothing in logs. In Debian, only installing graphviz does the job, looks like I am missing few packages in Alpine.
# docker logs -f jenkins_master
Running from: /usr/share/jenkins/jenkins.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
Mar 02, 2017 8:33:07 AM Main deleteWinstoneTempContents
WARNING: Failed to delete the temporary Winstone file /tmp/winstone/jenkins.war
Mar 02, 2017 8:33:07 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Logging initialized @1612ms
Mar 02, 2017 8:33:08 AM winstone.Logger logInternal
INFO: Beginning extraction from war file
Mar 02, 2017 8:33:08 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Empty contextPath
Mar 02, 2017 8:33:08 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-9.2.z-SNAPSHOT
Mar 02, 2017 8:33:09 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
Mar 02, 2017 8:33:10 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started w.@6e6f2380{/,file:/var/jenkins_home/war/,AVAILABLE}{/var/jenkins_home/war}
Mar 02, 2017 8:33:10 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started ServerConnector@1ca3b418{HTTP/1.1}{0.0.0.0:8080}
Mar 02, 2017 8:33:10 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started @3865ms
Mar 02, 2017 8:33:10 AM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Mar 02, 2017 8:33:10 AM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Mar 02, 2017 8:33:11 AM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Mar 02, 2017 8:33:11 AM jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
INFO: Initializing Bouncy Castle security provider.
Mar 02, 2017 8:33:11 AM jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
INFO: Bouncy Castle security provider initialized.
Mar 02, 2017 8:33:12 AM hudson.plugins.ansicolor.PluginImpl start
INFO: AnsiColor: eliminating boring output (https://github.com/dblock/jenkins-ansicolor-plugin)
Mar 02, 2017 8:33:19 AM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Mar 02, 2017 8:33:19 AM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Mar 02, 2017 8:33:20 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
INFO: Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping
Mar 02, 2017 8:33:21 AM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Mar 02, 2017 8:33:21 AM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Mar 02, 2017 8:33:21 AM jenkins.util.groovy.GroovyHookScript execute
INFO: Executing /var/jenkins_home/init.groovy.d/basic-security.groovy
Mar 02, 2017 8:33:21 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Download metadata
Mar 02, 2017 8:33:21 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Download metadata. 131 ms
Mar 02, 2017 8:33:21 AM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 40338
Mar 02, 2017 8:33:22 AM jenkins.util.groovy.GroovyHookScript execute
INFO: Executing /var/jenkins_home/init.groovy.d/tcp-slave-agent-port.groovy
Mar 02, 2017 8:33:22 AM org.springframework.context.support.AbstractApplicationContext pre
[JIRA] (JENKINS-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title Michael Neale commented on JENKINS-42408 Re: HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found tawanda minya yes sorry about this - snuck into the last beta. I'll see if we can cut one tomorrow as a few people have been bitten by this. 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-41756) Indecently translated main menu items
Title: Message Title Uroš Malenšek commented on JENKINS-41756 Re: Indecently translated main menu items I have created pull request https://github.com/jenkinsci/jenkins/pull/2767. I hope that helps. Do I have to do somethig else or just wait for the next release? 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-33082) Record diagnosis information under an agent disconnection failure
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-33082 Record diagnosis information under an agent disconnection failure Change By: Baptiste Mathus Summary: Record diagnosis information under a slave an agent disconnection failure 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-41756) Indecently translated main menu items
Title: Message Title Oleg Nenashev commented on JENKINS-41756 Re: Indecently translated main menu items My apologies, I have forgotten about this action item. The PR has been integrated, so it will be in the next release. Sadly, seems we cannot backport it to the LTS due to the delay on my side 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-42431) Error: Invalid or corrupt jarfile, during seed job verify
Title: Message Title Bandi Ram Mohan created an issue Jenkins / JENKINS-42431 Error: Invalid or corrupt jarfile, during seed job verify Issue Type: Bug Assignee: Unassigned Components: jenkins-flowdock Created: 2017/Mar/02 9:07 AM Priority: Minor Reporter: Bandi Ram Mohan I have encountered an issue during seed job verify. Error: Invalid or corrupt jarfile /repo/bbijenkins/workspace/job-dsl-verify/fem004-eiffel002/build/job-dsl-core-1.57-standalone.jar 13:16:38 Build step 'Execute shell' marked build as failure Also one more error during the same seed job verify Exception in thread "main" java.lang.reflect.InvocationTargetException 11:47:27 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 11:47:27 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 11:47:27 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 11:47:28 at java.lang.reflect.Method.invoke(Method.java:606) 11:47:28 at com.simontuffs.onejar.Boot.run(Boot.java:313) 11:47:28 at com.simontuffs.onejar.Boot.main(Boot.java:161) 11:47:28 Caused by: javaposse.jobdsl.dsl.DslException: startup failed: 11:47:28 /repo/bbijenkins/workspace/job-dsl-verify/fem004-eiffel002/build/bbi_ci_jobdsl_temp.groovy: 2740: unexpected token: << @ line 2740, column 1. 11:47:28 <<< eb284f825eda554f8c5b9370c37f367c71fab001 11:47:28 ^ 11:47:28 11:47:28 1 error 11:47:28 11:47:28 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Both the errors occured at different time periods. Done some googling but did not find the clue to fix this problem,
[JIRA] (JENKINS-41756) Indecently translated main menu items
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41756 Re: Indecently translated main menu items Code changed in jenkins User: urkon Path: core/src/main/resources/hudson/model/View/sidepanel_sl.properties http://jenkins-ci.org/commit/jenkins/acaf91c585e0b97d2b3dc93ec26f327d0abd9319 Log: Fix JENKINS-41756 - Indecently translated items Removed false and indecently to slovene translated main menu items. 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-41756) Indecently translated main menu items
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41756 Re: Indecently translated main menu items Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/hudson/model/View/sidepanel_sl.properties http://jenkins-ci.org/commit/jenkins/03c58b9c925fc2922fe58aa0e8539683908892d0 Log: Merge pull request #2767 from urkon/patch-1 Fix JENKINS-41756 - Indecently translated items Compare: https://github.com/jenkinsci/jenkins/compare/c63abe3e8cfc...03c58b9c925f 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-42432) All branches (SVN) get built periodically, even if nothing has changed
Title: Message Title Jochen A. Fürbacher created an issue Jenkins / JENKINS-42432 All branches (SVN) get built periodically, even if nothing has changed Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2017/Mar/02 9:34 AM Environment: Jenkins 2.48 / 2.46 Branch API Plugin 2.0.7 Multi-Branch Project Plugin 0.6 SCM API Plugin 2.0.7 Priority: Major Reporter: Jochen A. Fürbacher Hello, when we use the environment as described above, Subversion as Branch Sources and checked "Periodically if not otherwise run" with an interval of 1 minute in the Build Triggers section, all branches get build every minute even if nothing has changed. That happened first after we upgraded the Branch/SCM API to 2.x. With the environment Branch API Plugin 1.5, SCM API Plugin 1.3 and Multi-Branch Project Plugin 0.5.1 only those branches got built periodically, those sources changed. I am not quite sure if this is an issue of Branch API Plugin, SCM API Plugin or Multi-Branch Project Plugin. Add Comment
[JIRA] (JENKINS-33020) ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33020 Re: ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties http://jenkins-ci.org/commit/cloudbees-folder-plugin/9c378bea8901a0fddd0bdcea0783b98dae7d1078 Log: [FIXED JENKINS-40921][FIXED JENKINS-33020] Only display triggers that make sense for a folder computation 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-40921) Build Periodically setting for multibranch pipelines needs clarification
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40921 Re: Build Periodically setting for multibranch pipelines needs clarification Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties http://jenkins-ci.org/commit/cloudbees-folder-plugin/9c378bea8901a0fddd0bdcea0783b98dae7d1078 Log: [FIXED JENKINS-40921][FIXED JENKINS-33020] Only display triggers that make sense for a folder computation 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-40921) Build Periodically setting for multibranch pipelines needs clarification
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40921 Re: Build Periodically setting for multibranch pipelines needs clarification Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/e6ea7d8ceebcc0a95eda7159c402a9d0e01b309b Log: JENKINS-40921 Review comments 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-40921) Build Periodically setting for multibranch pipelines needs clarification
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40921 Re: Build Periodically setting for multibranch pipelines needs clarification Code changed in jenkins User: Stephen Connolly Path: src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/e72a89e4964458ed51a9d0f7d30e8616c750ae95 Log: JENKINS-40921 Add test to verify configuration page for triggers works 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-33020) ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33020 Re: ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/0d35973205f9bf79eee02ba36dc380f02b6ecc0a Log: Merge pull request #89 from stephenc/jenkins-40921 [FIXED JENKINS-40921][FIXED JENKINS-33020] Only display triggers that make sense for a folder computation Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/ea44cb643427...0d35973205f9 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-40921) Build Periodically setting for multibranch pipelines needs clarification
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40921 Re: Build Periodically setting for multibranch pipelines needs clarification Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/0d35973205f9bf79eee02ba36dc380f02b6ecc0a Log: Merge pull request #89 from stephenc/jenkins-40921 [FIXED JENKINS-40921][FIXED JENKINS-33020] Only display triggers that make sense for a folder computation Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/ea44cb643427...0d35973205f9 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/e090ce41073979674cec4774bf9348c2aa74dc25 Log: JENKINS-36121 Save rate limits when processing events 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubConsoleNote.java http://jenkins-ci.org/commit/github-branch-source-plugin/b025751381452800809847d9585f5f356a38d9ac Log: JENKINS-36121 Typos 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/c16c1f4dabbe08feda6f8661772c7bad62334bbf Log: JENKINS-36121 Actually don't even waste the API calls listing repositories for the common event case 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubBuildStatusNotification.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubClosable.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubConsoleNote.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMFile.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMFileSystem.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMProbe.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/8a393a4231a4eda81cd4f931d9bc07804713543d Log: JENKINS-36121 Throttle API usage rather than trip the API limit 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java http://jenkins-ci.org/commit/github-branch-source-plugin/b59c83dbab0ef203bf930e5cbde49796ddc609b9 Log: JENKINS-36121 Clarifying comments 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java http://jenkins-ci.org/commit/github-branch-source-plugin/fcafab8f42b55bcb2dbc6383f7ce01b29810cd98 Log: JENKINS-36121 Review comments 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubBuildStatusNotification.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubClosable.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubConsoleNote.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMFile.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMFileSystem.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMProbe.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/2b7a7f955978c275892c10460d2c4351ff400cb8 Log: Merge pull request #124 from stephenc/jenkins-36121 JENKINS-36121 Do not trip the rate limit Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/1dbf190e3c29...2b7a7f955978 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-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title tawanda minya commented on JENKINS-42408 Re: HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found sweet, thanks for the heads up 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-42433) Allow Scriptler to be used in Post Build
Title: Message Title Lewis England created an issue Jenkins / JENKINS-42433 Allow Scriptler to be used in Post Build Issue Type: Bug Assignee: Dominik Bartholdi Components: scriptler-plugin Created: 2017/Mar/02 9:55 AM Priority: Minor Reporter: Lewis England There are times that we would like to run Scriptler scripts as part of the post-build section of a job. We would like to use Scriptler to report things back to us about the agent without having to run a separate job to hold up the agent for a longer period of time. Add Comment
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-38837 Mutibranch project plugin does not respect "Workspace Root Directory" global configuration Change By: Stephen Connolly Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title Stephen Connolly commented on JENKINS-38837 Re: Mutibranch project plugin does not respect "Workspace Root Directory" global configuration https://github.com/jenkinsci/branch-api-plugin/blob/ec03b429c21e5035b652b624b29b3dee79ffef8a/src/main/java/jenkins/branch/WorkspaceLocatorImpl.java#L71 is where the setting is being ignored CC Jesse Glick 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-42268) Enable Knowledge Database analyser
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42268 Re: Enable Knowledge Database analyser Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/CyclomaticComplexityChecker.java src/main/resources/org/jenkins/ci/plugins/jenkinslint/check/Messages.properties http://jenkins-ci.org/commit/jenkinslint-plugin/519e77a809fbf98823ee6c5ac2d655e3e929ff72 Log: JENKINS-42268 CyclomaticComplexity lint defect initial approach Compare: https://github.com/jenkinsci/jenkinslint-plugin/compare/4c16292a8df7^...519e77a809fb 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-42268) Enable Knowledge Database analyser
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42268 Re: Enable Knowledge Database analyser Code changed in jenkins User: Victor Martinez Path: pom.xml src/test/java/org/jenkins/ci/plugins/jenkinslint/check/CyclomaticComplexityCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/4c16292a8df7d846bf87de2b51bf8cb378254610 Log: JENKINS-42268 Added CyclomaticComplexity test cases (WiP) 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-41806) Error 500 rest call for Item
Title: Message Title Pavel Savshenko commented on JENKINS-41806 Re: Error 500 rest call for Item I see the same exact issue, rest call to: https://jenkins/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26 shows the same stack trace. Stack trace Stack trace io.jenkins.blueocean.commons.stapler.export.NotExportableException: class hudson.model.Result doesn't have @ExportedBean so cannot write hudson.plugins.git.util.Build.buildResult at io.jenkins.blueocean.commons.stapler.export.Model.(Model.java:80) at io.jenkins.blueocean.commons.stapler.export.ModelBuilder.get(ModelBuilder.java:53) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:190) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:280) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:244) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:280) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:223) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:280) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne(Export.java:97) at io.jenkins.blueocean.commons.stapler.Export.serveExposedBean(Export.java:85) at io.jenkins.blueocean.commons.stapler.Export.doJson(Export.java:30) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:59) at org.kohsuke.stapler.Htt
[JIRA] (JENKINS-41806) Error 500 rest call for Item
Title: Message Title
Pavel Savshenko edited a comment on JENKINS-41806
Re: Error 500 rest call for Item
I see the same exact issue , ; in fact I have never seen the dashboard (e.g https://jenkins/blue/pipelines). The rest call is made to to : https://jenkins/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26 shows the same stack trace.{code:title=Stack trace|Language=java|collapse=true}Stack traceio.jenkins.blueocean.commons.stapler.export.NotExportableException: class hudson.model.Result doesn't have @ExportedBean so cannot write hudson.plugins.git.util.Build.buildResult at io.jenkins.blueocean.commons.stapler.export.Model.(Model.java:80) at io.jenkins.blueocean.commons.stapler.export.ModelBuilder.get(ModelBuilder.java:53) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:190) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:280) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:244) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:280) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:223) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:280) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:140) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne(Export.java:97) at io.jenkins.blueocean.commons.stapler.Export.serveExposedBean(Export.java:85) at io.jenkins.blueocean.commons.stapler.Export.doJson(Export.java:30) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:59) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:127) at org.kohsuke.sta
[JIRA] (JENKINS-35447) bug on moveing pipeline projects into folder
Title: Message Title ilya rosman commented on JENKINS-35447 Re: bug on moveing pipeline projects into folder Some addition from my side. First of all I want to apologize for not finding that before. I just understood that the root of wrong behavior during links copying is invalid ownership U can see it from my previous comment. Historically job (which I'm trying to move) was migrated from some another server. And during migration (archiving, copying, unpacking) ownership was lost (1002 1002 instead of jenkins jenkins) I fixed that in my filesystem and everything is fine for now. sudo chown -R jenkins:jenkins jobs/XXX So I even do not know is it a bug or not. Should system check/repair ownership... 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-41512) CSS width problem with credentials dropdown
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41512 Re: CSS width problem with credentials dropdown Code changed in jenkins User: Stephen Connolly Path: src/main/resources/lib/credentials/select/select.css http://jenkins-ci.org/commit/credentials-plugin/7a413bd933ce8e3edb1f991f138cc27bfd284d6d Log: JENKINS-41512 Use @media query to scale select max-width 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-41904) NPE when selecting a scan credential for GitHub SCM on Pipeline Libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41904 Re: NPE when selecting a scan credential for GitHub SCM on Pipeline Libraries Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/dc13e7a53b4ff1bda2a1eeed547f510ebfdefb2d Log: [FIXED JENKINS-41904] NPE from GitHubSCMSource$DescriptorImpl.doCheckScanCredentialsId when there is no contextual SCMSourceOwner. 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-42434) Support git parameter
Title: Message Title Mondane Woodworker created an issue Jenkins / JENKINS-42434 Support git parameter Issue Type: Improvement Assignee: Unassigned Attachments: image-2017-03-02-11-17-56-890.png Components: blueocean-plugin Created: 2017/Mar/02 10:20 AM Labels: plugin blueocean git-parameter input Priority: Minor Reporter: Mondane Woodworker In Jenkins 2, I have installed https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin and in the default interface all works well. When using blue ocean, no inputs are shown for the plugin, instead a message is shown: > No component found for type PT_BRANCH_TAG.What's the best method to support such inputs? Add Comment
[JIRA] (JENKINS-41512) CSS width problem with credentials dropdown
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41512 Re: CSS width problem with credentials dropdown Code changed in jenkins User: Stephen Connolly Path: src/main/resources/lib/credentials/select/select.css http://jenkins-ci.org/commit/credentials-plugin/d8a11ad108ad3b5e66c83401fcf212297092efd4 Log: Merge pull request #80 from stephenc/jenkins-41512 JENKINS-41512 Use @media query to scale select max-width Compare: https://github.com/jenkinsci/credentials-plugin/compare/51583db72282...d8a11ad108ad 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-42435) Add support for Blue Ocean
Title: Message Title Mondane Woodworker created an issue Jenkins / JENKINS-42435 Add support for Blue Ocean Issue Type: Improvement Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2017/Mar/02 10:22 AM Priority: Minor Reporter: Mondane Woodworker Currently, it's not possible to use Blue Ocean with Git Parameter plugin, the following is shown: > No component found for type PT_BRANCH_TAG. Perhaps the Git Paramater Plugin can be changed do only use default inputs? Add Comment Th
[JIRA] (JENKINS-42434) Support git parameter in Blue Ocean
Title: Message Title Mondane Woodworker updated an issue Jenkins / JENKINS-42434 Support git parameter in Blue Ocean Change By: Mondane Woodworker Summary: Support git parameter in Blue Ocean 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-42435) Add support for Blue Ocean to Git Parameter plugin
Title: Message Title Mondane Woodworker updated an issue Jenkins / JENKINS-42435 Add support for Blue Ocean to Git Parameter plugin Change By: Mondane Woodworker Summary: Add support for Blue Ocean to Git Parameter plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title davida2009 commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hi Stephen Please will you summarize the state of this issue? Does the merge of the pull request mean that this change is now in Jenkins? Does it mean that the concerns about long path names are mitigated? Where would the user set the path length? Sorry for the many questions but this issue spans lots of Jira issues and is hard to track by the uninformed. Thanks David 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-42433) Allow Scriptler to be used in Post Build
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42433 Allow Scriptler to be used in Post Build Change By: Dominik Bartholdi Issue Type: Bug New Feature 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-41806) Error 500 rest call for Item
Title: Message Title James Dumay commented on JENKINS-41806 Re: Error 500 rest call for Item Thanks for the info. We are going to have a fix for this in rc1 shortly. 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-24453) Jenkins server got blue screen to death
Title: Message Title Peter p55p commented on JENKINS-24453 Re: Jenkins server got blue screen to death Thank you Oleg for your quick response. We will do the upgrade and will let you know if the issue reoccur. 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-42415) s3upload can't find file - Unable to calculate MD5 hash
Title: Message Title Thorsten Hoeger commented on JENKINS-42415 Re: s3upload can't find file - Unable to calculate MD5 hash Hi, sorry for any problems this is causing. I will try to locate the error and test it on Windows. I tested it only on Mac and Linux but will setup a Windows box. 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-42189) Groovy 2.4.8 interoperability issues
Title: Message Title Emmanuel Debanne updated an issue Jenkins / JENKINS-42189 Groovy 2.4.8 interoperability issues When testing groovy 2.4.8, we needed to restart twice Jenkins. We already provided a screenshot corresponding to the first restart on on the 18th. I add an attachment with the thread dump of the second restart on 21th in case it helps to investigate the deadlock. The job names have been replaced by 'AJOB'. Change By: Emmanuel Debanne Attachment: 20170221_thread_dump.html.htm 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 optio
[JIRA] (JENKINS-42189) Groovy 2.4.8 interoperability issues
Title: Message Title Emmanuel Debanne edited a comment on JENKINS-42189 Re: Groovy 2.4.8 interoperability issues When testing groovy 2.4.8, we needed to restart twice Jenkins. We already provided a screenshot corresponding to the first restart on on the 18th. I add an attachment with the thread dump of the second restart on the 21th in case , hoping it helps will help to investigate the deadlock. The job names have been replaced by 'AJOB'. 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-11241) AccuRev: reduce load and increase speed for SCM polling
Title: Message Title Arno Moonen commented on JENKINS-11241 Re: AccuRev: reduce load and increase speed for SCM polling What we currently have looks a bit like this: Depot Libraries LIB-A LIB-B Firmware PRODUCT-A PRODUCT-A-WIP PRODUCT-A workspace for Jenkins PRODUCT-A workspace user 1 PRODUCT-A workspace user 2 PRODUCT-B PC Utilities UTIL-A UTIL-B Libraries are generally pieces of firmware used by multiple products, via include / exclude rules. I would like to get rid of the workspace for Jenkins CI, because this only adds additional work when adding a new product to the CI environment. It would also be nice if the workspaces get automatically checked, so I can work on a specific issue/feature in there (or I might add an additional stream for that, on the same level as the workspaces currently are). Using Jenkinsfile would be nice, but if I remember correctly this file still needs to be in the root of the repository, which would not be practical for us. For example, for PRODUCT-A, we have a directory product\PRODUCT-A in which the makefile and other project specific files are located. To me this would be the ideal location for a Jenkinsfile, but the open source version of Jenkins does not allow me to specify a search location (again, if I remember correctly).
[JIRA] (JENKINS-42094) [Artifactory] Publishing Docker Build-Info requires
Title: Message Title Sergey Kulanov commented on JENKINS-42094 Re: [Artifactory] Publishing Docker Build-Info requires Roman Gurevitch, I've investigated a little. I don't use automatic certificate generation. I've found the issue, that in my case certificate was not encrypted, I've checked the code and find out the in case of automatic generation private key is encrypted https://github.com/jenkinsci/artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/pipeline/docker/proxy/CertManager.java#L45 So the solution was to encrypt my pkey: # encrypt with password: AES-128-CBC ssh-keygen -p -f jfrog.proxy.key Probably this should be somehow reflected in documentation 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-42436) Jenkins Installation fails when no internet access is available.
Title: Message Title Stuart Milton created an issue Jenkins / JENKINS-42436 Jenkins Installation fails when no internet access is available. Issue Type: Task Assignee: Unassigned Attachments: jenkins_log.txt Components: core Created: 2017/Mar/02 11:16 AM Environment: NO INTERNET CONNECTION Jenkins 2.32.3.war RHEL 6.7 Oracle JDK 1.8.0_51 We are using the Tanuki Service Wrapper to start Jenkins from the bare war file. Labels: installationWizard offline Priority: Major Reporter: Stuart Milton Hi, We are using Jenkins as an deployment automation server within a secure environment that does not have internet connection. The setup process currently hangs after I paste in the Administration password. In the past, there was now the ability to select the 'Install No Plugins' option, which I gather has now been removed - and I assume that this is what is causing the issue. I've included the log but there is not a huge amount in there. Is there an up-to-date guide on how to install the latest Jenkins in an offline environment? Many Thanks, Stuart
[JIRA] (JENKINS-42436) Jenkins Installation fails when no internet access is available.
Title: Message Title Stuart Milton updated an issue Jenkins / JENKINS-42436 Jenkins Installation fails when no internet access is available. Change By: Stuart Milton Issue Type: Task Bug 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-42437) Increase functional test coverage
Title: Message Title Evaristo Gutierrez created an issue Jenkins / JENKINS-42437 Increase functional test coverage Issue Type: Task Assignee: Evaristo Gutierrez Components: plain-credentials-plugin Created: 2017/Mar/02 11:49 AM Priority: Minor Reporter: Evaristo Gutierrez Increase coverage for: System scoped credentials. Personal scoped credentials. Domains. Add Comment
[JIRA] (JENKINS-42437) Increase functional test coverage
Title: Message Title Evaristo Gutierrez started work on JENKINS-42437 Change By: Evaristo Gutierrez Status: Open In Progress 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Stephen Connolly commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Released as 2.0.4-beta-1 and available via the experimental update center. Assuming our (CloudBees) soak tests and any other community contributed test results are successful, this should be released to the general update center in the next couple of days. This is your last chance to provide feedback before this is incorporated into a mainline release 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-42437) Increase functional test coverage
Title: Message Title Evaristo Gutierrez updated JENKINS-42437 Jenkins / JENKINS-42437 Increase functional test coverage Change By: Evaristo Gutierrez Status: In Progress Review 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-41470) trigger a build failed with "build job:"
Title: Message Title
Ihor Antonov updated an issue
Jenkins / JENKINS-41470
trigger a build failed with "build job:"
Change By:
Ihor Antonov
Comment:
I have the same issue with {{build}} - none of documentation examples work +WHEN WORKS:+Pipeline - 2.4Pipeline Basic steps 2.3Pipeline BuildStep 2.4Pipeline Groovy 2.24+WHEN DOES NOT WORK:+Pipeline - 2.5Pipeline Basic steps 2.4Pipeline BuildStep 2.4Pipeline Groovy 2.28==={quote}Hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: build.call() is applicable for argument types: (java.util.LinkedHashMap) values: [[job:Vagrant, parameters:[@string(name=component,value=comp1), ...]]]Possible solutions: call(), wait(), any(), wait(long), main([Ljava.lang.String;), any(groovy.lang.Closure) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:64) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:18) at testVagrant.call(/var/jenkins_home/jobs/CertaScale/jobs/onboarding/branches/develop/builds/97/libs/certa/vars/testVagrant.groovy:10) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor259.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor261.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor261.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:60) at com.c
[JIRA] (JENKINS-41470) trigger a build failed with "build job:"
Title: Message Title Ihor Antonov commented on JENKINS-41470 Re: trigger a build failed with "build job:" Hey, Hubert Li, I had the same problem. Check your library. Most likely you have build.groovy file under /var that conflicts by name with Pipeline DSL build. Just rename it 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-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title
Thorsten Meinl commented on JENKINS-42405
Re: Lots of remote channel errors with pipelines and Windows slaves
After I figured out to turn on more logging messages, I got this: {{could not check C:\Users\jenkins\slave\workspace\r-WGI6TZZNQOBAAHSSLVRBWLNOVFN3FM5CSX5AJTOHIS4QEFKE2BPA@2 java.io.IOException: Remote call on Channel to /172.17.xxx.xxx failed at hudson.remoting.Channel.call(Channel.java:830) at org.jenkinsci.plugins.durabletask.ProcessLiveness._isAlive(ProcessLiveness.java:77) at org.jenkinsci.plugins.durabletask.ProcessLiveness.isAlive(ProcessLiveness.java:59) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.exitStatus(BourneShellScript.java:198) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:307) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:276) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.durabletask.ProcessLiveness$LibC at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:98) at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:91) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Thread.java:745) at ..remote call to Channel to /172.17.xxx.xxx(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) ... 12 more }}
Add Comment
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title
Thorsten Meinl edited a comment on JENKINS-42405
Re: Lots of remote channel errors with pipelines and Windows slaves
After I figured out to turn on more logging messages, I got this:{{ could not check C:\Users\jenkins\slave\workspace\r-WGI6TZZNQOBAAHSSLVRBWLNOVFN3FM5CSX5AJTOHIS4QEFKE2BPA@2java.io.IOException: Remote call on Channel to /172.17.xxx.xxx failed at hudson.remoting.Channel.call(Channel.java:830) at org.jenkinsci.plugins.durabletask.ProcessLiveness._isAlive(ProcessLiveness.java:77) at org.jenkinsci.plugins.durabletask.ProcessLiveness.isAlive(ProcessLiveness.java:59) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.exitStatus(BourneShellScript.java:198) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:307) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:276) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.durabletask.ProcessLiveness$LibC at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:98) at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:91) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Thread.java:745) at ..remote call to Channel to /172.17.xxx.xxx(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) ... 12 more}}
Add Comment
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title
Thorsten Meinl edited a comment on JENKINS-42405
Re: Lots of remote channel errors with pipelines and Windows slaves
After I figured out to turn on more logging messages, I got this:{ { noformat} could not check C:\Users\jenkins\slave\workspace\r-WGI6TZZNQOBAAHSSLVRBWLNOVFN3FM5CSX5AJTOHIS4QEFKE2BPA@2java.io.IOException: Remote call on Channel to /172.17.xxx.xxx failed at hudson.remoting.Channel.call(Channel.java:830) at org.jenkinsci.plugins.durabletask.ProcessLiveness._isAlive(ProcessLiveness.java:77) at org.jenkinsci.plugins.durabletask.ProcessLiveness.isAlive(ProcessLiveness.java:59) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.exitStatus(BourneShellScript.java:198) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:307) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:276) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.durabletask.ProcessLiveness$LibC at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:98) at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:91) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Thread.java:745) at ..remote call to Channel to /172.17.xxx.xxx(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) ... 12 more {noformat } }
Add Comment
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title
Thorsten Meinl edited a comment on JENKINS-42405
Re: Lots of remote channel errors with pipelines and Windows slaves
After I figured out how to turn on more logging messages, I got this:{noformat}could not check C:\Users\jenkins\slave\workspace\r-WGI6TZZNQOBAAHSSLVRBWLNOVFN3FM5CSX5AJTOHIS4QEFKE2BPA@2java.io.IOException: Remote call on Channel to /172.17.xxx.xxx failed at hudson.remoting.Channel.call(Channel.java:830) at org.jenkinsci.plugins.durabletask.ProcessLiveness._isAlive(ProcessLiveness.java:77) at org.jenkinsci.plugins.durabletask.ProcessLiveness.isAlive(ProcessLiveness.java:59) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.exitStatus(BourneShellScript.java:198) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:307) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:276) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.durabletask.ProcessLiveness$LibC at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:98) at org.jenkinsci.plugins.durabletask.ProcessLiveness$Liveness.call(ProcessLiveness.java:91) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Thread.java:745) at ..remote call to Channel to /172.17.xxx.xxx(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) ... 12 more{noformat}
Add Comment
[JIRA] (JENKINS-39621) Pipeline job loop after polling always find changes
Title: Message Title Martin Sander commented on JENKINS-39621 Re: Pipeline job loop after polling always find changes Mike Neary: You are checking out two different branches of the same repository, which confuses Jenkins: Found 6 remote heads on ssh://g...@bitbucket.foo:7999/ba/myservice.git [poll] Latest remote head revision on refs/heads/BRANCH-49 is: 2a04...53f1 - already built by 4 ... Found 6 remote heads on ssh://g...@bitbucket.foo:7999/ba/myservice.git [poll] Latest remote head revision on refs/heads/master is: 4a03...1f79 This caused the problem for us, try to organize the code in a way that you don't require this - seems that right now this is the only workaround. 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-41470) trigger a build failed with "build job:"
Title: Message Title Hubert Li closed an issue as Fixed Jenkins / JENKINS-41470 trigger a build failed with "build job:" Change By: Hubert Li Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42438) Wrong JUnit test duration shown in classes list
Title: Message Title Nitzan Yemal created an issue Jenkins / JENKINS-42438 Wrong JUnit test duration shown in classes list Issue Type: Bug Assignee: Unassigned Attachments: Class.png, Package.png, Tests.png Components: junit-plugin Created: 2017/Mar/02 12:59 PM Environment: jenkins 2.32.1 junit-plugin 1.20 Labels: junit test-results Priority: Major Reporter: Nitzan Yemal Hi, The Junit test result showing all the class time duration as 1 sec while the class can take less or more then 1 sec in total. The example job is Android tests job (using Gradle). Package time and individual test time duration result are good. Thanks, Nitzan
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY updated JENKINS-41662 Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Tom FENNELLY Status: In Progress Review 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-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY commented on JENKINS-41662 Re: Proceed button fails (investigate) PR: https://github.com/jenkinsci/blueocean-plugin/pull/875 io.jenkins.blueocean.rest.impl.pipeline.InputStepImpl has some unusual code, resetting the ID of the underlying pipeline InputStep instance to a random ID. The result of this ... two browsers load the same input step ... the first browser is screwed because the id it is using to submit against no longer corresponds to a valid ID because the load from the second browser caused it to be changed via io.jenkins.blueocean.rest.impl.pipeline.InputStepImpl. 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-41773) Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null)
Title: Message Title ikedam commented on JENKINS-41773 Re: Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null) > due to getBuildSelectors returning null Maybe. It means Jenkins#getDescriptorList returns null. It's really strange and I have no idea why it happens, anyway... 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-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY commented on JENKINS-41662 Re: Proceed button fails (investigate) I would have thought it was a total no-no for Blue Ocean code to be modifying underlying object model data in this way. The side effects of changes like this would surely have to be pretty bad. 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
It seems as if jenkins doesn't properly detect the PID of the process: It tries to build a commandline like that: [pid 6503] execve("/usr/bin/docker", ["docker", "exec", "e58e441dbf413c4180bca9f3e8db816eed1f3d985c21036fd93d9c970174141d", "env", "ps", "-o", "pid=", "7"], [/* 15 vars */] which will always produce an empty result, since it should be "pid=7" instead
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-42432) All branches (SVN) get built periodically, even if nothing has changed
Title: Message Title
Jochen A. Fürbacher updated an issue
Jenkins / JENKINS-42432
All branches (SVN) get built periodically, even if nothing has changed
Change By:
Jochen A. Fürbacher
Hello,when we use the environment as described above, Subversion as Branch Sources and checked "Periodically if not otherwise run" with an interval of 1 minute in the Build Triggers section, all branches get build every minute even if nothing has changed.That happened first after we upgraded the Branch/SCM API to 2.x. With the environment Branch API Plugin 1.5, SCM API Plugin 1.3 and Multi-Branch Project Plugin 0.5.1 only those branches got built periodically, those sources changed.I am not quite sure if this is an issue of Branch API Plugin, SCM API Plugin or Multi-Branch Project Plugin. EDIT: This happens only if "Discard old builds" as property is chosen for Branch Sources (not for Build Configuration).Project log says:{code:java}Checking candidate branch /branches/xyz@509884Met criteriaTakeover for MMTest » xyz by source #1 from source that no longer existsBranch reopened: xyz (509884)Scheduled build for branch: xyz{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42432) All branches (SVN) get built periodically, even if nothing has changed (discard old builds)
Title: Message Title Jochen A. Fürbacher updated an issue Jenkins / JENKINS-42432 All branches (SVN) get built periodically, even if nothing has changed (discard old builds) Change By: Jochen A. Fürbacher Summary: All branches (SVN) get built periodically, even if nothing has changed (discard old builds) 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-42393) Temporary files should not be created in the bundles root directory under JENKINS_HOME
Title: Message Title Baptiste Mathus updated JENKINS-42393 Jenkins / JENKINS-42393 Temporary files should not be created in the bundles root directory under JENKINS_HOME Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42430) Waiting on scanning for 'pick one' flow is too slow
Title: Message Title Cliff Meyers commented on JENKINS-42430 Re: Waiting on scanning for 'pick one' flow is too slow Yes, the UI waits of the org folder scanning to complete. It's pretty slow even with an org with a modest number of repos. 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-42439) Fix PCT for 2.32.3
Title: Message Title Evaristo Gutierrez started work on JENKINS-42439 Change By: Evaristo Gutierrez Status: Open In Progress 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-32616) p4 plugin should support for multibranch pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32616 Re: p4 plugin should support for multibranch pipelines Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/scm/BranchesScmSource.java src/main/java/org/jenkinsci/plugins/p4/scm/StreamsScmSource.java src/main/resources/org/jenkinsci/plugins/p4/scm/BranchesScmSource/config-detail.jelly src/main/resources/org/jenkinsci/plugins/p4/scm/BranchesScmSource/help-includes.html src/main/resources/org/jenkinsci/plugins/p4/scm/StreamsScmSource/config-detail.jelly src/main/resources/org/jenkinsci/plugins/p4/scm/StreamsScmSource/help-includes.html http://jenkins-ci.org/commit/p4-plugin/55b956effa5aaaeec496873e988698e371c6a62d Log: Help for MultiBranch include field and update BETA label. JENKINS-32616 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-42439) Fix PCT for 2.32.3
Title: Message Title Evaristo Gutierrez created an issue Jenkins / JENKINS-42439 Fix PCT for 2.32.3 Issue Type: Task Assignee: Evaristo Gutierrez Components: structs-plugin Created: 2017/Mar/02 2:37 PM Priority: Minor Reporter: Evaristo Gutierrez junit dependency needs to be bumped. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42440) Job directory is empty when using pipeline multi-branch
Title: Message Title
Bijoy Thomas created an issue
Jenkins / JENKINS-42440
Job directory is empty when using pipeline multi-branch
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
JenkinsConsoleLog.txt
Components:
pipeline
Created:
2017/Mar/02 2:47 PM
Environment:
OS: Linux 3.14.34-27.48.amzn1.x86_64 Java: 1.7.0_85 (OpenJDK Runtime Environment) Jenkins: 2.32.2 (Installed via yum) Plugins: Pipeline: 2.4 Multi-Branch Project Plugin: 0.5.1 Lockable Resources Plugin: 1.11.1 GitHub Branch Source Plugin: 2.0.3 GitHub plugin: 1.26.0
Priority:
Minor
Reporter:
Bijoy Thomas
We have a multi-branch pipeline setup with our repo in GitHub. Since yesterday, we started noticing that new branches created in GitHub were not passing the build because, of the three directories that get created for the build, the @script dir has the sources, the @tmp is also present but the actual workspace directory is just empty. So, in our case, DebugTool-SomeRandomNum directory is just empty DebugTool-SomeRandomNum@script dirctory has the sources This started happening yesterday. For the other 4 branches (that we already had in GitHub when setting up the multi-branch pipeline), I see that the both the workspace and workspace@script dir have sources in them. For now, I have a rather crude way of getting around this properties([disableConcurrentBuilds()]) node { env.BUILDSPACE = pwd() echo "BUILDSPACE is $ {env.BUILDSPACE}" // check to see if sources are available in current dir. Else switch to @script dir if (fileExists('package.json')) { echo 'package.json exists' } else { echo '
[JIRA] (JENKINS-42415) s3upload can't find file - Unable to calculate MD5 hash
Title: Message Title Jon Hermansen commented on JENKINS-42415 Re: s3upload can't find file - Unable to calculate MD5 hash Thorsten Hoeger I believe this effects Linux too. I was seeing the issue yesterday with a Linux master + slaves. 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-42440) Job directory is empty when using pipeline multi-branch
Title: Message Title
Bijoy Thomas updated an issue
Jenkins / JENKINS-42440
Job directory is empty when using pipeline multi-branch
Change By:
Bijoy Thomas
We have a multi-branch pipeline setup with our repo in GitHub. Since yesterday, we started noticing that new branches created in GitHub were not passing the build because, of the three directories that get created for the build, the @script dir has the sources, the @tmp is also present but the actual workspace directory is just empty. So, in our case, DebugTool-SomeRandomNum directory is just emptyDebugTool-SomeRandomNum@script dirctory has the sourcesThis started happening yesterday. For the other 4 branches (that we already had in GitHub when setting up the multi-branch pipeline), I see that the both the workspace and workspace@script dir have sources in them.For now, I have a rather crude way of getting around this {code:java} properties([disableConcurrentBuilds()])node { env.BUILDSPACE = pwd()echo "BUILDSPACE is ${env.BUILDSPACE}"// check to see if sources are available in current dir. Else switch to @script dir if (fileExists('package.json')) {echo 'package.json exists' } else {echo 'No package.json. Switching to script dir'env.BUILDSPACE = "${env.BUILDSPACE}" + '@script'echo "BUILDSPACE is ${env.BUILDSPACE}" } stage "Build Step"sh '''cd ${BUILDSPACE}#Do stuff here'''} {code} I have attached the console log from the failed build (sanitized to remove actual GitHub URL info).It says that its "Running on master in /var/lib/jenkins/workspace/ZULUSCHED_DebugTool-6RUZGOFIV76HNXGYFRPCOHJUYYIS5YA2O7JZQWZG2RYSCS4XFCJQ"but then that directory is just empty
Add Comment
[JIRA] (JENKINS-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Flemming Steffensen commented on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Issue confirmed to still exist on SCM Sync Configuration 0.0.10, installed on Windows server 2012. Any progress or even ETA on a fix? Any hints to how we (the community) can assist debugging this issue? 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Flemming Steffensen edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Issue confirmed to still exist on SCM Sync Configuration 0.0.10 , installed on Windows server 2012 R2, Jenkins 2 . 4.8, LTS, Subversion plugin 2.71, SCM API Plugin 2.0.8 Any progress or even ETA on a fix?Any hints to how we (the community) can assist debugging this issue? 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Flemming Steffensen edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Issue confirmed to still exist on SCM Sync Configuration 0.0.10Windows 2012 R2, Jenkins 2.4.8, LTS, Subversion plugin 2.71, SCM API Plugin 2.0.8Any progress or even ETA on a fix?Any hints to how we (the community) can assist debugging this issue? 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-40599) AD descriptor saved without any domain make Jenkins not to start
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40599 Re: AD descriptor saved without any domain make Jenkins not to start Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java http://jenkins-ci.org/commit/active-directory-plugin/d36ab0a200ec12b8213fc439819aa10db751a13c Log: JENKINS-40599 Not throw any Exception in case there is not any domain configured on the descriptor 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-41311) NPE in CleanupJobsOnDelete
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41311 Re: NPE in CleanupJobsOnDelete Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/plugins/pipeline/milestone/MilestoneStepExecution.java http://jenkins-ci.org/commit/pipeline-milestone-step-plugin/7ecb946d1c54ed15a8f4bb9848cfaa9da7c6086f Log: [FIXED JENKINS-41311] Fix NPE in CleanupJobsOnDelete.onDeleted 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-40599) AD descriptor saved without any domain make Jenkins not to start
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40599 Re: AD descriptor saved without any domain make Jenkins not to start Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java http://jenkins-ci.org/commit/active-directory-plugin/079bd37c7744af09d371083fa06c857299b9053f Log: Merge pull request #58 from fbelzunc/JENKINS-40599 JENKINS-40599 Not throw any Exception in case there is not any domain configured in the descriptor Compare: https://github.com/jenkinsci/active-directory-plugin/compare/fac8df0c7686...079bd37c7744 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
It seems as if jenkins doesn't properly detect the PID of the process:It tries to build a commandline like that: [pid 6503] execve("/usr/bin/docker", ["docker", "exec", "e58e441dbf413c4180bca9f3e8db816eed1f3d985c21036fd93d9c970174141d", "env", "ps", "-o", "pid=", "7"], [/* 15 vars */] which will always produce an empty result, since it should be "pid=7" instead [edit]if ps is not installed in the container this will fail miserably.
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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick commented on JENKINS-39307 Re: pipeline docker execution aborts without reason Yes you need at least cat and ps in the container. Currently the plugin does not try to verify these prerequisites or provide tailored error messages. 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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39307 pipeline docker execution aborts without reason Change By: Jesse Glick Labels: diagnostics 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-42415) s3upload can't find file - Unable to calculate MD5 hash
Title: Message Title Thorsten Hoeger commented on JENKINS-42415 Re: s3upload can't find file - Unable to calculate MD5 hash I think it does affect slaves in general but works on master nodes. Could anyone with a slave setup try if the attached file solves the problem? 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-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title
Philip Adams commented on JENKINS-41214
Re: bitbucket branch source plugin notifies wrong repository
Hey, We've been experiencing a similar issue (on Jenkins 2.32.2) - in our case we are using a custom recognizer and a groovy library from the workflow global libs plugin. All of our notifications are going to the repository of the included library, rather than the repository for the job. After poking around it seems like this line: https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L100
BuildData gitBuildData = build.getAction(BuildData.class);
returns the hash of the first thing to be checked out during the build. Usually that's the Jenkinsfile (so it can determine what to do). In our case, it's the pipeline lib. I supect in OP's case it's the git repo of the pipeline script. e.g, in the groovy console, running
job = Jenkins.getInstance().getItemByFullName('test/pipeline-with-jenkinsfile/master')
build = job.getLastBuild()
println(build.getAction(BuildData.class).getLastBuiltRevision())
returns
Revision 1bd16215aa781b6f68045fe2447a5a2221eb4216 (master)
which is the correct sha for the repo, however
job = Jenkins.getInstance().getItemByFullName('test/pipeline-with-customfile/master')
build = job.getLastBuild()
println(build.getAction(BuildData.class).getLastBuiltRevision())
returns
Revision 6e61c4fbec94af6aa47255f7be91f34c978ecf06 (v6)
which is the sha for the groovy library. I can't reproduce without using a custom recogniser since all Jenkinsfile-based pipeline jobs will checkout the Jenkinsfile first. I haven't tried with the Literate plugin but I imagine the same is true there.
[JIRA] (JENKINS-42415) s3upload can't find file - Unable to calculate MD5 hash
Title: Message Title Thorsten Hoeger updated an issue Jenkins / JENKINS-42415 s3upload can't find file - Unable to calculate MD5 hash Change By: Thorsten Hoeger Attachment: pipeline-aws.hpi 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-42042) Ant glob syntax for upload
Title: Message Title Thorsten Hoeger commented on JENKINS-42042 Re: Ant glob syntax for upload Will try to implement this using the S3 TransferManager 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-42439) Fix PCT for 2.32.3
Title: Message Title Evaristo Gutierrez updated JENKINS-42439 Jenkins / JENKINS-42439 Fix PCT for 2.32.3 Change By: Evaristo Gutierrez Status: In Progress Review 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-42441) add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave
Title: Message Title Hubert Li created an issue Jenkins / JENKINS-42441 add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/02 4:05 PM Priority: Critical Reporter: Hubert Li I add Windows 7 slave by launch method "launch slave agents via SSH" Jenkins, my system info is: MINGW32_NT-6.1 WIN7VM06 1.0.17(0.48/3/2) 2011-04-24 23:39 i686 Msys and I got the following error: [03/02/17 16:35:13] [SSH] Opening SSH connection to WIN7VM06:22. [03/02/17 16:35:14] [SSH] Authentication successful. [03/02/17 16:35:18] [SSH] The remote users environment is: ALLUSERSPROFILE='C:\ProgramData' ANT_HOME='C:\apache-ant-1.9.3' APPDATA='C:\Users\chunhui.li\AppData\Roaming' BASH=/usr/bin/bash BASH_ARGC=() BASH_ARGV=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]="3" [1]="1" [2]="17" [3]="1" [4]="release" [5]="i686-pc-msys") BASH_VERSION='3.1.17(1)-release' BITVISESFSDLL=1988-43C8DDE8-B5059B29-598EC7DD BZR_PROGRESS_BAR=none BZR_REMOTE_PATH=/data/cmsadmin/environment/release/MScms/Environment_latest/bzr COMMONPROGRAMFILES='C:\Program Files (x86)\Common Files' COMMONPROGRAMFILES(X86)='C:\Program Files (x86)\Common Files' COMMONPROGRAMW6432='C:\Program Files\Common Files' COMPUTERNAME=WIN7VM06 COMSPEC='C:\Windows\system32\cmd.exe' CVConfigPath=/data/cmsadmin/environment/cmsadmin/CVconfig CV_HOSTTYPE=i686_MINGW32_1.0.17 DIRSTACK=() EUID=500 FP_NO_HOST_CHECK=NO GROUPS=() HISTCONTROL=ignoredups:ignorespace HISTFILE=/data/users/chunhui.li/.bash_history HISTFILESIZE=2000 HISTSIZE=1000 HOME=/data/users/chunhui.li HOMEDRIVE='' HOMEPATH='USERSERVER\homes' HOMESHARE='\\USERSERVER\homes' HOSTNAME=WIN7VM06 HOSTTYPE=i686_MINGW32_1.0.17 IFS=$' \t\n' JAVA_HOME='C:\Program Files\Java\jdk1.7.0_79' LOCALAPPDATA='C:\Users\chunhui.li\AppData\Local' LOGNAME=chunhui.li LOGONSERVER='FILESERVER' LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;
[JIRA] (JENKINS-42441) add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave
Title: Message Title Hubert Li updated an issue Jenkins / JENKINS-42441 add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave Change By: Hubert Li I add Windows 7 slave by launch method "launch slave agents via SSH" in Jenkins, my system info is:MINGW32_NT-6.1 WIN7VM06 1.0.17(0.48/3/2) 2011-04-24 23:39 i686 Msysand I got the following error:[03/02/17 16:35:13] [SSH] Opening SSH connection to WIN7VM06:22.[03/02/17 16:35:14] [SSH] Authentication successful.[03/02/17 16:35:18] [SSH] The remote users environment is:ALLUSERSPROFILE='C:\ProgramData'ANT_HOME='C:\apache-ant-1.9.3'APPDATA='C:\Users\chunhui.li\AppData\Roaming'BASH=/usr/bin/bashBASH_ARGC=()BASH_ARGV=()BASH_EXECUTION_STRING=setBASH_LINENO=()BASH_SOURCE=()BASH_VERSINFO=([0]="3" [1]="1" [2]="17" [3]="1" [4]="release" [5]="i686-pc-msys")BASH_VERSION='3.1.17(1)-release'BITVISESFSDLL=1988-43C8DDE8-B5059B29-598EC7DDBZR_PROGRESS_BAR=noneBZR_REMOTE_PATH=/data/cmsadmin/environment/release/MScms/Environment_latest/bzrCOMMONPROGRAMFILES='C:\Program Files (x86)\Common Files'COMMONPROGRAMFILES(X86)='C:\Program Files (x86)\Common Files'COMMONPROGRAMW6432='C:\Program Files\Common Files'COMPUTERNAME=WIN7VM06COMSPEC='C:\Windows\system32\cmd.exe'CVConfigPath=/data/cmsadmin/environment/cmsadmin/CVconfigCV_HOSTTYPE=i686_MINGW32_1.0.17DIRSTACK=()EUID=500FP_NO_HOST_CHECK=NOGROUPS=()HISTCONTROL=ignoredups:ignorespaceHISTFILE=/data/users/chunhui.li/.bash_historyHISTFILESIZE=2000HISTSIZE=1000HOME=/data/users/chunhui.liHOMEDRIVE='\\'HOMEPATH='USERSERVER\homes'HOMESHARE='\\USERSERVER\homes'HOSTNAME=WIN7VM06HOSTTYPE=i686_MINGW32_1.0.17IFS=$' \t\n'JAVA_HOME='C:\Program Files\Java\jdk1.7.0_79'LOCALAPPDATA='C:\Users\chunhui.li\AppData\Local'LOGNAME=chunhui.liLOGONSERVER='\\FILESERVER'LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35:'MACHTYPE=i686-pc-msysMAKE_MODE=unixMSBUILD_ROOT=/volumes1/build/MSENVIRONMENT_PATH=/data/cmsadmin/environmentMSRELEASE_ROOT=/data/id/releaseMSSITE_NAME=MAPSCAPE_EINDHOVENMSYSTEM=MINGW32NUMBER_OF_PROCESSORS=8OLDPWD=/data/users/hans.vanpinxterenOPTERR=1OPTIND=1OS=Windows_NTOSTYPE=msysPATH='/data/cmsadmin/environment/release/MScms/Environment_latest/i686_MINGW32_1.0.17:/data/cmsadmin/environment/release/MScms/Environment_latest:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/c/cmake-2.8.12.2-win32-x86/bin:/c/Program Files/Java/jdk1.7.0_79/bin:/c/apache-ant-1.9.3/bin:/c/Pro
