[JIRA] [core] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
swapnil soor commented on JENKINS-26257 ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException Hi Daniel, Thanks for the pointer, I have installed the VersionColumn Plugin, and its not complaining for any of the slave jars, so I believe that's not the issue. Moreover, when I am trying a release build, I am executing it on master server only where Jenkins is installed and not using any slave. When I did further analysis between various build jobs I have, found a pattern that its causing this exception only for the job which is having a heavy maven build in terms of modules, which takes almost an hour for us to get all the modules built, may be it has some relation with timing or some threading issue in the core part of code which is leading to this error. Just wanted to share my analysis, might give you some clue to diagnose the problem. Thanks! Regards, Swapnil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fstrigger-plugin] (JENKINS-23073) Jobs stop polling for file changes after 1-2 builds
ting lu commented on JENKINS-23073 Jobs stop polling for file changes after 1-2 builds I have met the same problem in ScriptTrigger - Poll with a shell or batch script Polling has not run yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Tom Brus commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We have the same problem as Henri Gomez above: ...This client is too old to work with the working copy... But the circumstances are slightly different: I just upgraded the svn plugin from 2.4.5 to 2.5 my jobs that do not use a fresh workspace for svn work fine my jobs that use a fresh copy fail as mentioned above svn repos are taken from a dir on the same machine that runs jenkins (file:://...) svn version installed on the machine is 1.7.9 in jenkins/configure the Subversion Workspace Version is set to 1.7 Even completely cleaning the workspace (including removing the .svn dir) does not solve this issue. I did not revert to 2.4.5 yet, but I guess that will solve it. I also expect that upgrading the svn version on the machine to 1.8 will solve it. When I do an 'svn status' on the dir on the disk from a shell I get the same error message. So my conclusion is that the working dir is created by the plugin as a 1.8 dir and then the locally installed svn (1.7.9) can not deal with that. So the plugin does not seem to listen to the setting Subversion Workspace Version which is set to 1.7. Does this help? I will go back to 2.4.5 until this is solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26305) Updating maven jobs that are running causes them to think modules are not built
Lorenz Bateman created JENKINS-26305 Updating maven jobs that are running causes them to think modules are not built Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 06/Jan/15 9:58 AM Description: If the seed job runs and updates a maven job that is already executing then all modules that have not built for that job are marked as 'not built' which then causes those artifacts to not be fingerprinted correctly. Looking at the console output for the job, it continues to execute correctly, but something about updating the job from the seed job causes it to break. Project: Jenkins Priority: Major Reporter: Lorenz Bateman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-25433) Xcodebuild sigining fails
lacostej commented on JENKINS-25433 Xcodebuild sigining fails @Reinhard, you're right... WRT rejection, I've found: "Do not use the --resource-rules flag or ResourceRules.plist. They have been obsoleted and will be rejected." under https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG205 That's bad. I reported Apple bug #19384243 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22118) Unable to tag build due to lack of credentials
Roman Pickl commented on JENKINS-22118 Unable to tag build due to lack of credentials any update on this one? (2.5 is available now) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
SCM/JIRA link daemon commented on JENKINS-25588 Integrate vSphere Cloud plugin with Credentials plugin (auth options) Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/vSphereCloud.java http://jenkins-ci.org/commit/vsphere-cloud-plugin/4d74a1d4b274495e3d56b63b3ef0a8ef39beae8b Log: JENKINS-25588 - Fix the error with vSphereInstance() setup. I forgot to remove vcHost usage in previous commits. Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
SCM/JIRA link daemon commented on JENKINS-25588 Integrate vSphere Cloud plugin with Credentials plugin (auth options) Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/org/jenkinsci/plugins/vSphereCloud/config.jelly http://jenkins-ci.org/commit/vsphere-cloud-plugin/3667afe1236c896b389fcdd043180cc063a7d298 Log: JENKINS-25588 - Fixed the "Test Connection" validation handler Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
SCM/JIRA link daemon commented on JENKINS-25588 Integrate vSphere Cloud plugin with Credentials plugin (auth options) Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/vSphereCloud.java src/main/java/org/jenkinsci/plugins/vsphere/tools/VSphere.java http://jenkins-ci.org/commit/vsphere-cloud-plugin/7a73a674e3424cadd84dbcc99b61d2c66a6659c4 Log: JENKINS-25588 - Improve error checks for missing host/username Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/3667afe1236c^...7a73a674e342 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-5463) Matrix parent build should indicate the failed builds
Oliver Gondža resolved JENKINS-5463 as Fixed Matrix parent build should indicate the failed builds Matrix project prints "$COMBINATION completed with result $RESULT" for quite some time. Fixed. Change By: Oliver Gondža (06/Jan/15 8:35 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Luc Sarzyniec commented on JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves Hello, what's the status of this bug please ? I've tried the version 0.3.2 (jenkins 1.596) and it do not seems to be fixed ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
Dave Taddei created JENKINS-26303 Not compatible with Subversion plugin 2.5 Issue Type: Bug Assignee: Kevin Bell Attachments: multiplescmexception.txt Components: multiple-scms-plugin Created: 06/Jan/15 8:57 AM Description: The latest update of the Subversion plugin causes a class cast exception in the Multiple SCM plugin. If subversion is selected as one of the SCM sources in the multiple scm plugin a class cast exception generates the attached logs when updating or checking out new code. For the moment we have rolled back our Subversion plugin to 2.4.5 to work around this issue. Environment: Jenkins 1.596, Subversion Plugin 2.5 Project: Jenkins Labels: plugin exception Priority: Major Reporter: Dave Taddei This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-15404) Failure when setting up metric goals in cobertura plugin
Joshua Gudmundson commented on JENKINS-15404 Failure when setting up metric goals in cobertura plugin Can confirm still issue in Jenkins 1.580.2, With plugin version 1.9.6. My Report: classes: 100%, conditionals: 89%, flies: 100%, Lines: 76%, packages: 100% Also tried: -Setting bad = 50 causes the same thing to happen even tho lines are above the threshold. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25869) Jenkins is getting crashed and shutting down once in a while
Vamsi Hari commented on JENKINS-25869 Jenkins is getting crashed and shutting down once in a while Thanks Daniel for your help, I will try removing all the proxy related environment variables and restarting the Jenkins container(Tomcat) and let you know about the result. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25192) Trigger are always run after finalize
Nicolas De Loof commented on JENKINS-25192 Trigger are always run after finalize Indeed, as the trigger is executed after workspace has been released, access to property files is not possible to collect parameters. So such a file need to be archived and retrieved as a build artifact. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26302) REGRESSION: Node environment doesn't work
Orgad Shaneh created JENKINS-26302 REGRESSION: Node environment doesnt work Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Jan/15 8:13 AM Description: Overriding PATH in slave environment settings worked until 1.595. In 1.596 it is broken. Environment: v1.596, master is on Windows, slave is linux Project: Jenkins Labels: slave Priority: Critical Reporter: Orgad Shaneh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Clifford Sanders commented on JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 I'm not sure if this is related: I have configured my jobs to fail on timeout. This works in the freestyle project but not in the Maven project. The Maven type build is marked as 'aborted' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Henri Gomez commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Darren I got errors even after cleaning workspace and using fresh copy. Subversion Plugin fetch contents in SVN 1.8 whereas I defined to use SVN 1.7. Some part of SVN operation respect 1.7 config but .svn is performed in 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25514) FutureImpl does not cancel it`s start future
SCM/JIRA link daemon commented on JENKINS-25514 FutureImpl does not cancel it`s start future Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/queue/FutureImpl.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/5bfaca449ce3b6edbf39a3f623bc8ce62411b37e Log: Merge pull request #1472 from jbaranov/JENKINS-25514 JENKINS-25514 Fixed lock case in FutureImpl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25514) FutureImpl does not cancel it`s start future
SCM/JIRA link daemon commented on JENKINS-25514 FutureImpl does not cancel it`s start future Code changed in jenkins User: Eugene Baranov Path: core/src/main/java/hudson/model/queue/FutureImpl.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/3edae667b3955a561296a23122f86b35ec928a98 Log: JENKINS-25514 Fixed lock case in FutureImpl when some other process is waiting for build in queue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26306) Disabled scrollbars since upgrading to jenkins 1.596
Manni Heumann created JENKINS-26306 Disabled scrollbars since upgrading to jenkins 1.596 Issue Type: Bug Assignee: Unassigned Attachments: jenkins-scrollbars.png Components: core Created: 06/Jan/15 10:57 AM Description: Since I updated my Jenkins installations to 1.596, all html pages display a disabled horizontal scrollbar. This is a waste of screen real estate and a visual distraction. On some, short, pages, I also get a disabled vertical scrollbar. Please never display disabled scrollbars. Project: Jenkins Priority: Minor Reporter: Manni Heumann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey reopened JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I would like to see this issue reopened and the original change reverted. It is not possible to use the current variable with the sonar plugin: sonar.branch=$GIT_BRANCH breaks as the branch must be a branch, not an append of GIT_REMOTE and GIT_BRANCH. The documentation even says that this variable, called GIT_BRANCH, contains the remote and the branch separated by a slash. If you need the remote add a new variable called GIT_REMOTE please. There are many situations where string manipulation is not available and so expecting me to split on slash is not reasonable and not possible. Change By: Tim Pizey (06/Jan/15 11:10 AM) Resolution: WontFix Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-26235) Tab customizations
Ulli Hafner commented on JENKINS-26235 Tab customizations Changing the tab titles shouldn't be complicated. All hard-coded strings in main.jelly should be replaced by a method call on instance of AnnotationContainer (as this is already done for the package/module name header). Then individual plug-ins can override TabDetail class (e.g. this is done in tasks or dry plug-in). Interested in providing a pull request? Adding additional tabs is not that easy. Here I need to investigate in more detail on how this can be achieved... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26113) REST api needed to get individual warnings values, not combined ones
Ulli Hafner commented on JENKINS-26113 REST api needed to get individual warnings values, not combined ones That should be feasible. Interested in providing a pull request? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25192) Trigger are always run after finalize
SCM/JIRA link daemon commented on JENKINS-25192 Trigger are always run after finalize Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/77355b70a0904a5fae3655dd2a63492b95d869b5 Log: FIXED JENKINS-25192 rely on archived artifacts to trigger (parameterized) build fallback to workspace for backward compatibility This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25192) Trigger are always run after finalize
SCM/JIRA link daemon resolved JENKINS-25192 as Fixed Trigger are always run after finalize Change By: SCM/JIRA link daemon (06/Jan/15 11:18 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [findbugs-plugin] (JENKINS-25977) Make FindBugsPublisher a SimpleBuildStep
Ulli Hafner commented on JENKINS-25977 Make FindBugsPublisher a SimpleBuildStep Does this mean that there will be an additional type (besides the publisher and reporter) or should the existing publisher use the new parent class? Can I use a SimpleBuildStep also in Maven jobs, or is the MavenReporter type still required? Is there already an example around that I can look at? Is such a change transparent for users that have existing publishers in their configuration (config.xml) or do I need to provide a migration to update all existing jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey updated JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH Change By: Tim Pizey (06/Jan/15 11:30 AM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey started work on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH Change By: Tim Pizey (06/Jan/15 11:30 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25192) Trigger are always run after finalize
SCM/JIRA link daemon commented on JENKINS-25192 Trigger are always run after finalize Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/2c782fd693e30dda3edb439c4b4ed41d82e6cbcb Log: Merge pull request #80 from jenkinsci/JENKINS-25192 FIXED JENKINS-25192 rely on archived artifacts Compare: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/666e72e5a740...2c782fd693e3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25514) FutureImpl does not cancel it`s start future
Oliver Gondža resolved JENKINS-25514 as Fixed FutureImpl does not cancel it`s start future Change By: Oliver Gondža (06/Jan/15 11:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Kevin Burge commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH While I was able to work around this issue (using CMake and Regular Expressions), as an end user, I can see Tim Pizey's point and agree. Another possibility is to add a variable in addition to GIT_REMOTE that has today's GIT_BRANCH value, like GIT_REF, or GIT_UPSTREAM_BRANCH or something like that. So, if anyone is depending on the current logic, they can simply rename the the variable they are referencing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26307) CPS Groovy collection.find() returns Boolean
Kenneth Baltrinic
created JENKINS-26307
CPS Groovy collection.find() returns Boolean
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
06/Jan/15 12:08 PM
Description:
To demonstrate the issue createa new workflow job with the following script:
def str="1:one|2:two|3:three"
def i = "2"
def opts = str.split(/\|/)
def opt = opts.find { o - o.contains("${i}:") }
echo "len: ${opts.length}"
echo "opt: ${opt}"
The output of which is
Started by user anonymous
Running: Print Message
len: 3
Running: Print Message
opt: false
Running: End of Workflow
Finished: SUCCESS
Note the value returned for opt. It appears that the current behavior of find in cps is to return the result of the closure for the first element in the collection.
Environment:
Workflow 1.1 and Jenkins 1.596
Project:
Jenkins
Priority:
Major
Reporter:
Kenneth Baltrinic
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25514) FutureImpl does not cancel it`s start future
dogfood commented on JENKINS-25514 FutureImpl does not cancel it`s start future Integrated in jenkins_main_trunk #3915 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Luc Sarzyniec stopped work on JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves Change By: Luc Sarzyniec (06/Jan/15 12:45 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Luc Sarzyniec started work on JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves Change By: Luc Sarzyniec (06/Jan/15 12:45 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pretested-integration-plugin] (JENKINS-25873) Extend version number with git SHA (our case 12396)
Bue Petersen resolved JENKINS-25873 as Fixed Extend version number with git SHA (our case 12396) For the latest release you will see that the version is "2.2.0 (060cf)". This is okay for now, though the short SHA isn't strictly necessary for releases but more important for snapshots. Few other plugins, also uses custom version numbers. Change By: Bue Petersen (06/Jan/15 1:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [promoted-builds-plugin] (JENKINS-14890) Force Promotion and Re-execute promotion should be configured by project-based matrix separately
Guillaume Paradis assigned JENKINS-14890 to Guillaume Paradis Force Promotion and Re-execute promotion should be configured by project-based matrix separately Change By: Guillaume Paradis (06/Jan/15 2:40 PM) Assignee: OHTAKETomohiro GuillaumeParadis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-14890) Force Promotion and Re-execute promotion should be configured by project-based matrix separately
Guillaume Paradis assigned JENKINS-14890 to OHTAKE Tomohiro Force Promotion and Re-execute promotion should be configured by project-based matrix separately Sorry, it got assigned to me by error. Change By: Guillaume Paradis (06/Jan/15 2:41 PM) Assignee: GuillaumeParadis OHTAKETomohiro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)
Bue Petersen resolved JENKINS-25546 as Fixed Support individual git scm configuration part in the Multi SCMs plugin (our case 12287) Change By: Bue Petersen (06/Jan/15 2:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-pipeline-plugin] (JENKINS-23828) Build Pipeline View doesn't show build user id on Downstream Projects
Gilad Judes commented on JENKINS-23828 Build Pipeline View doesnt show build user id on Downstream Projects this happens in other "pipeline" plugins (i.e. Delivery Pipeline Plugin) when setting up a manual step - the user logs in and press the | (play) button the build status in jenkins shows "Started by anonymous user" while the build xml (e.g. /var/lib/jenkins/jobs/Product-1.0.6-promote-to-QA/builds/22/build.xml) au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView_-MyUserIdCause plugin="build-pipeline-plugin@1.4.5" userIdgilad/userId user fullNameGilad Judes/fullName properties BTW we are working with Active Directory authentication This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25959) Post-buid steps is executed though master is integration branch (our case 12427)
Bue Petersen resolved JENKINS-25959 as Fixed Post-buid steps is executed though master is integration branch (our case 12427) Change By: Bue Petersen (06/Jan/15 2:56 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-26309) Custom Commit message for git publisher
Layton Whiteley created JENKINS-26309 Custom Commit message for git publisher Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 06/Jan/15 3:23 PM Description: Is there a way to append/add a custom commit message when pushing commits from jenkins. Currently, im not seeing a way to do this. If there is a way and im not seeing it, please point it out. If not, this would be a good feature an eg. use case would be to add ci skip tags to the description of the commit to stop recursive builds when doing a git push from jenkins. Environment: all Project: Jenkins Priority: Minor Reporter: Layton Whiteley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26310) notifyCommit URL responds with No Git consumers using SCM API
Oded Arbel created JENKINS-26310 notifyCommit URL responds with No Git consumers using SCM API Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 06/Jan/15 3:29 PM Description: According to the documentation, to get the git plugin to start a build without polling, one needs to set up a post-commit hook to send an HTTP request to `/notifyCommit`. In my tests, I always get the response No Git consumers using SCM API plugin for: g...@bitbucket.org:mycompany/myproject.git even though the URL submitted was copy-pasted from the job configuration screen Environment: Jenkins version 1.595 Project: Jenkins Labels: plugin Priority: Minor Reporter: Oded Arbel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25886) Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)
Bue Petersen resolved JENKINS-25886 as Fixed Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401) Change By: Bue Petersen (06/Jan/15 2:50 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)
Bue Petersen resolved JENKINS-25960 as Fixed MultiScm configurations does not resolve corret git-client (our case 12426) Change By: Bue Petersen (06/Jan/15 2:59 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert
created JENKINS-26308
LoadRunner Scenario Always Times Out
Issue Type:
Bug
Assignee:
Ofir Shaked
Components:
hp-application-automation-tools-plugin
Created:
06/Jan/15 3:20 PM
Description:
Simple Loadrunner scenario always times out when ran through Jenkins. The test runs fine when started within Loadrunner. Have tried on multiple machines in the same environment and found this issue. Though on my own personal machine it works fine.
LoadRunner Settings are set to default:
Controller Polling Interval - 30
Scenario Execution Timeout - 10
Errors To Ignore - none
Below is the console output:
Building in workspace C:\Program Files (x86)\Jenkins\jobs\Testing\workspace
workspace $ "C:\Program Files (x86)\Jenkins\jobs\Testing\workspace\HpToolsLauncher.exe" -paramfile props05012015172238713.txt
"Started..."
1 tests found:
C:\Users\Downloads\Scenario1.lrs
05/01/2015 17:22:39 Running: C:\Users***\Downloads\Scenario1.lrs
Cleaning up the environment...
Preparing scenario C:\Users***\Downloads\Scenario1.lrs for execution.
Load Generator localhost connected
Starting scenario...
Error: Scenario Execution timeout (29 seconds) passed.
Error: Scenario Execution timeout ({0} seconds) passed.
Scenario C:\Users***\Downloads\Scenario1.lrs ended.
Analyzing results...
Error: Timeout for Analysis passed.
Analysis Results:
SLA report:
Full Name : Errors Per Second
Measurement : ErrorsPerSecond
CriteriaMeasurement Value : RunningVusers
LoadThresholds value :
status : Passed
Error(s) summary:
0 ignored , 0 errors
Test PASSED
Test result: Passed
05/01/2015 17:24:26 Test complete: C:\Users***\Downloads\Scenario1.lrs
---
Cleaning up the environment...
Run status: Job succeeded, total tests: 1, succeeded: 1, failures: 0, errors: 0
Passed : C:\Users\Downloads\Scenario1.lrs
Report archiving mode is set to: DONT_ARCHIVE_TEST_REPORT
Finished: SUCCESS
Environment:
Jenkins 1.596
LoadRunner 11.52
HP Application Automation Tools 3.0.6
Windows server 2008
Java 6 update 38
Project:
Jenkins
Labels:
jenkins
plugin
timeout
loadrunner
Priority:
Major
Reporter:
Connor Gilbert
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Florent Poinsaut commented on JENKINS-12523 Could not initialize class org.libvirt.Connect Hello, Does this issue have another workaround that downgrade Jenkins or use SSH ? If not, I could fork this plugin but I lack of information to upgrade it. Can someone help me to realize this work ? Thanks in advance. Regards, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26311) Warning plugin archives do not exist
Lance Johnston created JENKINS-26311 Warning plugin archives do not exist Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 06/Jan/15 7:21 PM Description: The warnings plugin does not exist in the plugins download site at "https://updates.jenkins-ci.org/download/plugins/". It does exist at "https://updates.jenkins-ci.org/latest/warnings.hpi", but no releases other than latest appear to be available. Project: Jenkins Labels: plugin plugins Priority: Minor Reporter: Lance Johnston This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-26004) Priority option in multijob projects
Mathieu Cantin commented on JENKINS-26004 Priority option in multijob projects Please provide more informations or exemple. Yes, with multijob (and Trigger/call builds on other projects) there are possibility to create a deadlock. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26306) Disabled scrollbars since upgrading to jenkins 1.596
Alex Lombardi edited a comment on JENKINS-26306 Disabled scrollbars since upgrading to jenkins 1.596 This scrollbar issue is also affecting the jenkins Plugin admin page and hides the OK button under the toolbar if your list of avialable plugins to update is too long (can't scroll down). If you click the blue section on the the toolbar you can get it to update, but it is not intuitive that that is possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25474) MultiJob Plugin not recognizing job failures for continuation condition
Mathieu Cantin closed JENKINS-25474 as Fixed MultiJob Plugin not recognizing job failures for continuation condition Change By: Mathieu Cantin (06/Jan/15 7:30 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman created JENKINS-26312 No save button on the job configuration page Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Jan/15 7:57 PM Description: In 1.596 there is no save button on the job configuration page. Cannot modify any jobs. Project: Jenkins Priority: Blocker Reporter: Igor Koyfman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-26251) Groovy Postbuild plugin shows error in project configuration
Marlen Ablaev commented on JENKINS-26251 Groovy Postbuild plugin shows error in project configuration Yes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26307) CPS Groovy collection.find() returns Boolean
Jesse Glick assigned JENKINS-26307 to Kohsuke Kawaguchi CPS Groovy collection.find() returns Boolean Change By: Jesse Glick (06/Jan/15 8:43 PM) Assignee: JesseGlick KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert
updated JENKINS-26308
LoadRunner Scenario Always Times Out
Change By:
Connor Gilbert
(06/Jan/15 7:59 PM)
Description:
SimpleLoadrunnerscenarioalwaystimesoutwhenranthroughJenkins.ThetestrunsfinewhenstartedwithinLoadrunner.Havetriedonmultiplemachinesinthesameenvironmentandfoundthisissue.Thoughonmyownpersonalmachineitworksfine.LoadRunnerSettingsaresettodefault:ControllerPollingInterval-30ScenarioExecutionTimeout-10ErrorsToIgnore-noneBelowistheconsoleoutput
(noticethetimeoutoccurringat29seconds.Thisisconsistentalongallattempts)
:BuildinginworkspaceC:\ProgramFiles(x86)\Jenkins\jobs\Testing\workspace[workspace]$C:\ProgramFiles(x86)\Jenkins\jobs\Testing\workspace\HpToolsLauncher.exe-paramfileprops05012015172238713.txtStarted...1testsfound:C:\Users\*\Downloads\Scenario1.lrs05/01/201517:22:39Running:C:\Users\\Downloads\Scenario1.lrsCleaninguptheenvironment...PreparingscenarioC:\Users\\Downloads\Scenario1.lrsforexecution.LoadGeneratorlocalhostconnectedStartingscenario...Error:ScenarioExecutiontimeout(29seconds)passed.Error:ScenarioExecutiontimeout({0}seconds)passed.ScenarioC:\Users\\Downloads\Scenario1.lrsended.Analyzingresults...Error:TimeoutforAnalysispassed.AnalysisResults:SLAreport:FullName:ErrorsPerSecondMeasurement:ErrorsPerSecondCriteriaMeasurementValue:RunningVusersLoadThresholdsvalue:status:PassedError(s)summary:0ignored,0errorsTestPASSEDTestresult:Passed05/01/201517:24:26Testcomplete:C:\Users\\Downloads\Scenario1.lrs---Cleaninguptheenvironment...Runstatus:Jobsucceeded,totaltests:1,succeeded:1,failures:0,errors:0Passed:C:\Users\*\Downloads\Scenario1.lrsReportarchivingmodeissetto:DONT_ARCHIVE_TEST_REPORTFinished:SUCCESS
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24272) jnlp slaves fail to reconnect when master is restarted
SCM/JIRA link daemon commented on JENKINS-24272 jnlp slaves fail to reconnect when master is restarted Code changed in jenkins User: Richard Mortimer Path: core/src/main/java/jenkins/slaves/restarter/JnlpSlaveRestarterInstaller.java http://jenkins-ci.org/commit/jenkins/ea6baf9a103b841ec99dd1c2a9aac85fe6d8d29f Log: FIXES JENKINS-24272 jnlp slaves fail to reconnect when master is restarted During master restart only attempt to reconnect the slave after the master has finished restarting. (cherry picked from commit 48e19c58f9e2caa998d0942417d58679f5ce47f0) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25989) No wrap up(not in multiple lines) of too long list of slaves at label page
SCM/JIRA link daemon commented on JENKINS-25989 No wrap up(not in multiple lines) of too long list of slaves at label page Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Computer/index.jelly core/src/main/resources/hudson/model/Label/index.jelly http://jenkins-ci.org/commit/jenkins/2172503f3ce2acf1dd9fb95891e41441bff5197f Log: FIXED JENKINS-25989 Allow breaking label and node lists (cherry picked from commit 2820e59202975ce8ad302e4a0b0e17c07e4c40cf) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
SCM/JIRA link daemon commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java test/src/test/java/hudson/model/RunMapTest.java http://jenkins-ci.org/commit/jenkins/14d676bb15dbf8ddc3208bd8a80033e831756d49 Log: FIXED JENKINS-25788 RunMap.remove was always returning false, even when the Run was in fact removed. (cherry picked from commit ce94579c50621990517c86120236ee9a1d0490da) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders The font change was not incidental; it was filed as a specific issue Right, I meant that the layout issue may not be a direct result of the font changes only, but rather interaction of font change and layout change, or layout change only. They were both merged into the same release IIRC. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Mathieu Cantin commented on JENKINS-18567 Add Watch button to Job summary screen I have try this feature and it was good. But I don't understand why when I add a trigger on "Watch Job", I have the choice of who I would send a mail (developers, recipient list, culprits...). I think that is not usefull and this feature would just add me as receiver list. Doesn't work, if we have no authentification on jenkins (exemple, a test instance). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders Thanks, Dan, for that good info. I'll recommend we hold off on our upgrade until February. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders A lot more than font was changed, so this may be incidental. The font change was not incidental; it was filed as a specific issue (JENKINS-23840) separate from the other UI changes. The change submitter also specifically increased the font size. It appears, however, that Marlene's and my complaints about the formatting of columns are not related to the font change, but rather to the UI redesign, probably pull request 1310, which changed the way tables are rendered. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (06/Jan/15 8:01 PM) Description: In1.596thereisnosavebuttononthejobconfigurationpage.Cannotmodifyanyjobs. Revertingto1.594gotthebuttonback. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25636) multijob does not finish if phase contains same job multiple times
Mathieu Cantin closed JENKINS-25636 as Fixed multijob does not finish if phase contains same job multiple times Change By: Mathieu Cantin (06/Jan/15 7:28 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh-slaves-plugin] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Oliver Gondža commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG Rejected for 1.580.3. Removing lts-candidate label entirely, as this will be part of next LTS line anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-19360) Missing classname when used with reports generated from VSTest.Console.exe
SCM/JIRA link daemon commented on JENKINS-19360 Missing classname when used with reports generated from VSTest.Console.exe Code changed in jenkins User: Ivo Bellin Salarin Path: pom.xml src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java src/test/resources/hudson/plugins/mstest/mstest_vs_2012.trx src/test/resources/hudson/plugins/mstest/mstest_vs_2012.xml http://jenkins-ci.org/commit/mstest-plugin/0f2aa07d0fa905819d21997b2595eec54c5fdc88 Log: Merge pull request #3 from iansul/master JENKINS-19360 - Fix for mstest problems with trx files genereated by vstest.console.exe Compare: https://github.com/jenkinsci/mstest-plugin/compare/e11a4dc2471a...0f2aa07d0fa9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19031) com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1
SCM/JIRA link daemon commented on JENKINS-19031 com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1 Code changed in jenkins User: Christoph Kutzinski Path: pom.xml http://jenkins-ci.org/commit/instant-messaging-parent-plugin/3c2666d51c523325621b025c4971232143a8b1f0 Log: Update to Jenkins 1.565 because of JENKINS-19031 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders There were changes since then to how the build history looks, and adapts to longer text in the description, build name, and/or badges, which were long-standing problems (screen shots e.g. on https://github.com/jenkinsci/jenkins/pull/1470). I don't think these are eligible for LTS backport though (even if -IRC- long build names or badges don't break and overlap the main panel). You'll need for the next major LTS.1 release that should arrive in February. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI
Daniel Beck commented on JENKINS-25971 Job list and console output are not properly aligned in the new UI Tom's fix is in 1.596. Does this issue still occur in that version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [redmine-plugin] (JENKINS-8760) detail information for commit messages are missed in changes
Roman Pickl commented on JENKINS-8760 detail information for commit messages are missed in changes if I understand Larry's comment at https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin correctly i came up with a fix for this https://github.com/jenkinsci/redmine-plugin/pull/17 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl commented on JENKINS-18567 Add Watch button to Job summary screen Since I'm am reusing the UI for the trigger setup, the selection of recipients is still there, but only the person who is setting up the trigger will be emailed. If there is no authentication, how would the plugin know who to send the email to? The user would be Anonymous without login. The feature requires authentication in order to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26306) Disabled scrollbars since upgrading to jenkins 1.596
Alex Lombardi commented on JENKINS-26306 Disabled scrollbars since upgrading to jenkins 1.596 This scrollbar issue is also affecting the jenkins Plugin admin page and hides the OK button under the toolbar. If you click the blue section on the the toolbar you can get it to update, but it is not intuitive that that is possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-25977) Make FindBugsPublisher a SimpleBuildStep
Jesse Glick commented on JENKINS-25977 Make FindBugsPublisher a SimpleBuildStep should the existing publisher use the new parent class? The existing publisher can just implement SimpleBuildStep. Can I use a SimpleBuildStep also in Maven jobs, or is the MavenReporter type still required? I do not know much about MavenReporter, and anyway it seems to be unused in findbugs-plugin. If there is a BuildStep registered as an extension and it happens to implement SimpleBuildStep, it will be usable from a workflow, otherwise not. Is there already an example around that I can look at? https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md#build-steps-and-post-build-actions Is such a change transparent for users that have existing publishers in their configuration Sure, you should not need to change the name of the class. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()
kutzi commented on JENKINS-6560 Plugin should use project.getFullDisplayName() instead of project.getName() Should be fixed in version 1.32 of the instant-messaging plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Alexander Bertram
created JENKINS-26313
Workflow script fails if CPS-transformed methods are called from constructors
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
06/Jan/15 9:53 PM
Description:
When a CPS-transformed method is called from a Groovy class constructor, the CpsCallableInvocation is not caught and aborts the build.
Here is a minimally-reproducible test case:
class B {
static def sqr(x) { x*x }
}
class A {
A(y) {
B.sqr(y)
}
}
def a = new A(42)
The resulting CpsCallableInvocation is not caught and the build aborts:
Running: End of Workflow
com.cloudbees.groovy.cps.impl.CpsCallableInvocation
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71)
at org.codehaus.groovy.runtime.callsite.ConstructorSite.callConstructor(ConstructorSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:54)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:198)
at B.sqr(WorkflowScript)
at B$sqr.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at A.init(WorkflowScript:11)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:54)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.constructorCall(DefaultInvoker.java:20)
at WorkflowScript.run(WorkflowScript:15)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:90)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:76)
at sun.reflect.GeneratedMethodAccessor498.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:267)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:70)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:176)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:174)
at
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl commented on JENKINS-18567 Add Watch button to Job summary screen You don't configure the job's notifications, it only subscribes you. If you are anonymous, then it doesn't allow you to watch a job. I don't want to have a separate UI for this vs. the normal configuration. so maybe I can set some variable to remove those items in the watch area. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()
SCM/JIRA link daemon commented on JENKINS-6560 Plugin should use project.getFullDisplayName() instead of project.getName() Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/im/bot/CurrentlyBuildingCommand.java http://jenkins-ci.org/commit/instant-messaging-plugin/4ca5e97cfdd01ab23e7301f66cfa3471f8a17d3e Log: Use FullDisplayName for 'cb' command, too, if available JENKINS-6560 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26307) CPS Groovy collection.find() returns Boolean
Alexander Bertram commented on JENKINS-26307 CPS Groovy collection.find() returns Boolean Think I beat you to it by a few hours https://issues.jenkins-ci.org/browse/JENKINS-26300 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5135) Adopt ?jelly escape-by-default='true'? everywhere
SCM/JIRA link daemon commented on JENKINS-5135 Adopt ?jelly escape-by-default=true? everywhere Code changed in jenkins User: Mark Waite Path: src/main/resources/hudson/plugins/git/ChangelogToBranchOptions/config.jelly src/main/resources/hudson/plugins/git/GitBranchTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/digest.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/index.jelly src/main/resources/hudson/plugins/git/GitPublisher/config.jelly src/main/resources/hudson/plugins/git/GitRevisionBuildParameters/config.jelly src/main/resources/hudson/plugins/git/GitRevisionTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitSCM/config.jelly src/main/resources/hudson/plugins/git/GitSCM/global.jelly src/main/resources/hudson/plugins/git/GitSCM/project-changes.jelly src/main/resources/hudson/plugins/git/GitTagAction/tagForm.jelly src/main/resources/hudson/plugins/git/UserMergeOptions/config.jelly src/main/resources/hudson/plugins/git/browser/AssemblaWeb/config.jelly src/main/resources/hudson/plugins/git/browser/BitbucketWeb/config.jelly src/main/resources/hudson/plugins/git/browser/CGit/config.jelly src/main/resources/hudson/plugins/git/browser/FisheyeGitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitBlitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitLab/config.jelly src/main/resources/hudson/plugins/git/browser/GitList/config.jelly src/main/resources/hudson/plugins/git/browser/GitWeb/config.jelly src/main/resources/hudson/plugins/git/browser/GithubWeb/config.jelly src/main/resources/hudson/plugins/git/browser/Gitiles/config.jelly src/main/resources/hudson/plugins/git/browser/GitoriousWeb/config.jelly src/main/resources/hudson/plugins/git/browser/KilnGit/config.jelly src/main/resources/hudson/plugins/git/browser/Phabricator/config.jelly src/main/resources/hudson/plugins/git/browser/RedmineWeb/config.jelly src/main/resources/hudson/plugins/git/browser/RhodeCode/config.jelly src/main/resources/hudson/plugins/git/browser/Stash/config.jelly src/main/resources/hudson/plugins/git/browser/ViewGitWeb/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPath/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPaths/config.jelly src/main/resources/hudson/plugins/git/util/BuildData/index.jelly src/main/resources/hudson/plugins/git/util/BuildData/summary.jelly src/main/resources/index.jelly src/main/resources/jenkins/plugins/git/GitSCMSource/config-detail.jelly http://jenkins-ci.org/commit/git-plugin/07defeb47056a90a591d21c18b3fc77691527d0c Log: Escape jelly output by default - see JENKINS-5135 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5135) Adopt ?jelly escape-by-default='true'? everywhere
SCM/JIRA link daemon commented on JENKINS-5135 Adopt ?jelly escape-by-default=true? everywhere Code changed in jenkins User: Mark Waite Path: src/main/resources/hudson/plugins/git/ChangelogToBranchOptions/config.jelly src/main/resources/hudson/plugins/git/GitBranchTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/digest.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/index.jelly src/main/resources/hudson/plugins/git/GitPublisher/config.jelly src/main/resources/hudson/plugins/git/GitRevisionBuildParameters/config.jelly src/main/resources/hudson/plugins/git/GitRevisionTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitSCM/config.jelly src/main/resources/hudson/plugins/git/GitSCM/global.jelly src/main/resources/hudson/plugins/git/GitSCM/project-changes.jelly src/main/resources/hudson/plugins/git/GitTagAction/tagForm.jelly src/main/resources/hudson/plugins/git/UserMergeOptions/config.jelly src/main/resources/hudson/plugins/git/browser/AssemblaWeb/config.jelly src/main/resources/hudson/plugins/git/browser/BitbucketWeb/config.jelly src/main/resources/hudson/plugins/git/browser/CGit/config.jelly src/main/resources/hudson/plugins/git/browser/FisheyeGitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitBlitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitLab/config.jelly src/main/resources/hudson/plugins/git/browser/GitList/config.jelly src/main/resources/hudson/plugins/git/browser/GitWeb/config.jelly src/main/resources/hudson/plugins/git/browser/GithubWeb/config.jelly src/main/resources/hudson/plugins/git/browser/Gitiles/config.jelly src/main/resources/hudson/plugins/git/browser/GitoriousWeb/config.jelly src/main/resources/hudson/plugins/git/browser/KilnGit/config.jelly src/main/resources/hudson/plugins/git/browser/Phabricator/config.jelly src/main/resources/hudson/plugins/git/browser/RedmineWeb/config.jelly src/main/resources/hudson/plugins/git/browser/RhodeCode/config.jelly src/main/resources/hudson/plugins/git/browser/Stash/config.jelly src/main/resources/hudson/plugins/git/browser/ViewGitWeb/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPath/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPaths/config.jelly src/main/resources/hudson/plugins/git/util/BuildData/index.jelly src/main/resources/hudson/plugins/git/util/BuildData/summary.jelly src/main/resources/index.jelly src/main/resources/jenkins/plugins/git/GitSCMSource/config-detail.jelly http://jenkins-ci.org/commit/git-plugin/f297338702395e53f2f4db8d9070de15bc770890 Log: Escape jelly output by default - see JENKINS-5135 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-26235) Tab customizations
Steve Springett commented on JENKINS-26235 Tab customizations I looked into what it would take to make the labels configurable and it appears to be more complex than I thought. When the labels are rendered, it's done so when the AnnotationContainer is of type JavaProject, not TabDetail. JavaProject is constructed by BuildResult so it appears the custom label definitions would need to be defined here. Replacing the hard-coded strings in main.jelly is simple enough. The Dependency-Check Jenkins plugin which uses analysis-core, already overrides TabDetail. But by the time it's called, the text to be rendered for the tabs has already been determined. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8
Daniel Spilker commented on JENKINS-25643 Not able to use example build.gradle file with Java 8 Will be fixed in the next release. https://github.com/jenkinsci/gradle-jpi-plugin/pull/37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookie to be saved when configuring trend graphs
Ulli Hafner commented on JENKINS-25917 Spaces in URL (from project name or view) cause invalid cookie to be saved when configuring trend graphs I see. Since you already found the problematic statement: are you interested in providing a fix as pull request? I currently quite busy with other work... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Kanstantsin Shautsou commented on JENKINS-18567 Add Watch button to Job summary screen My idea was to allow subscribe yourself, not allow somebody to configure job's notifications. If you are anonymous, then doesn't allow to subscribe. (developers, recipient list, culprits...) - should not be available here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Alexander Bertram commented on JENKINS-26313 Workflow script fails if CPS-transformed methods are called from constructors There is a workaround: annotate sqr() with @com.cloudbees.groovy.cps.NonCPS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Daniel Beck commented on JENKINS-26312 No save button on the job configuration page Is the Simple Theme Plugin installed? If so, disable it, or remove the custom CSS/JS assignments from global configuration. Disable Greasemonkey or any similar browser-specific custom JS/CSS insertions. Please provide a screen shot showing the full browser window including scroll bar. Does this only occur on long job configuration pages that exceed the window height (i.e. where scrolling is needed)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Jesse Glick assigned JENKINS-26313 to Kohsuke Kawaguchi Workflow script fails if CPS-transformed methods are called from constructors I wonder if this is even fixable. Change By: Jesse Glick (06/Jan/15 10:35 PM) Assignee: JesseGlick KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (07/Jan/15 1:49 AM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Igor Koyfman commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden This also happens on other pages with buttons at the bottom, e.g. the system configuration page, the plugin installation page, etc. The zoom in/zoom out workaround works for all. The CSS workaround with the Simple Theme Plugin mentioned above didn't work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin incorrectly adds trailing slash to repository URLs containing property reference(s) when polling
Ron MacNeil
updated JENKINS-26315
Git plugin incorrectly adds trailing slash to repository URLs containing property reference(s) when polling
Change By:
Ron MacNeil
(07/Jan/15 3:10 AM)
Description:
WeuseaglobalpropertycalledRepoRoottospecifywhereourGitrepositorieslive,soourrepositoryURLslooksimilarto:${RepoRoot}/RepoA.git${RepoRoot}/RepoB.gitTheseresolvecorrectlywhenthejobactuallyruns,butwereseeingerrorssimilartothefollowinginourpollinglog:{code}Fetchingupstreamchangesfrom${RepoRoot}/RepoA.gitgit.exe--version#timeout=10git.exe-ccore.askpass=truefetch--tags--progress${RepoRoot}/RepoA.git+refs/heads/*:refs/remotes/origin/*FATAL:hudson.plugins.git.GitException:Failedtofetchfrom${RepoRoot}/RepoA.githudson.util.IOException2:hudson.plugins.git.GitException:Failedtofetchfrom${RepoRoot}/RepoA.git athudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:518) athudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) athudson.scm.SCM.poll(SCM.java:397) atorg.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:92) athudson.scm.SCM.poll(SCM.java:397) athudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1462) athudson.model.AbstractProject._poll(AbstractProject.java:1433) athudson.model.AbstractProject.poll(AbstractProject.java:1344) athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)Causedby:hudson.plugins.git.GitException:Failedtofetchfrom${RepoRoot}/RepoA.git athudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:695) athudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:598) athudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:516) ...16moreCausedby:hudson.plugins.git.GitException:Commandgit.exe-ccore.askpass=truefetch--tags--progress${RepoRoot}/RepoA.git+refs/heads/*:refs/remotes/origin/*returnedstatuscode128:stdout:stderr:fatal:repositoryhttps://github.com/Foo/RepoA.git/notfound atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) athudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:693) ...18moreDone.Took2.3sec{code}
IfIhard-codethereporootratherthanusetheglobalpropertyreference,pollingworks.SoitseemsasthoughtheresadifferenceinthehandlingofrepositoryURLsbetweenpollingforchangesandactuallypullingchangesduringjobexecution.
Thanksfolks,loveyourwork.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin can't handle property references in repository URLs when polling
Ron MacNeil updated JENKINS-26315 Git plugin cant handle property references in repository URLs when polling Change By: Ron MacNeil (07/Jan/15 3:25 AM) Summary: Gitplugincanthandle repositoryURLscontaining propertyreferences inrepositoryURLs whenpolling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26310) notifyCommit URL responds with No Git consumers using SCM API
Mark Waite resolved JENKINS-26310 as Not A Defect notifyCommit URL responds with No Git consumers using SCM API Per the commit message, that is an expected message. You can confirm that the notifyCommit had the expected result by reviewing the git polling log immediately after a notifyCommit. It should report the polling time in the polling log and that time should be very near the time of the poll. Change By: Mark Waite (07/Jan/15 3:52 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Jackey Cheung commented on JENKINS-26280 Missing Integrate Branch from feature branch builds There is only one branch. History: I've created a dev (not dev1) branch back then, and couldn't see the Integrate button. So I've deleted it, and do it again, created the dev1 branch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I uninstalled the Simple Theme Plugin, and I'm using Chrome. I don't have any jobs that fit on one screen. Also, I checked in IE and there is no Save or Apply button there either. I don't have Firefox. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds I did some investigation and I found that Integration Action does not work if the feature branch job has more that one Subversion modules. If the job that builds your feature branch has more than one module. Then it is the cause of this issue. I just wanted to confirm that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin can't handle repository URLs containing property references when polling
Ron MacNeil updated JENKINS-26315 Git plugin cant handle repository URLs containing property references when polling Change By: Ron MacNeil (07/Jan/15 3:24 AM) Summary: GitplugincanthandlerepositoryURLscontainingproperty reference(s) references whenpolling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I zoomed out the browser until it got so small the job did fit on one screen, and the buttons did show up then. So I guess that's a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Nathan Smith created JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 07/Jan/15 1:43 AM Description: Use a Tag in the Branch Specifier. Polling on the remote repo will occur. It will run git ls-remote -h MY_REMOTE MY_TAG This will result in nothing returned from the remote repository. git ls-remote has a --tags option which will return the SHA of the Tag. Polling is enabled because the Job also checkouts an SVN repository using the Jenkins Multiple SCMs plugin which doesn't refer to a tag. Environment: Jenkins 1.584 Jenkins Git Plugin 2.3.1 Jenkins Multiple SCMs plugin 0.3 Project: Jenkins Priority: Major Reporter: Nathan Smith This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman commented on JENKINS-26312 No save button on the job configuration page I zoomed out the screen until it got so small the job did fit on one screen, and the buttons did show up then. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
