[JIRA] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Daniel Beck commented on JENKINS-25481 API call results empty waring messages BTW best practice is to use the tree parameter to prune nodes that aren't needed rather than depth (once the structure is known). 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Beck commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection cepnyci: The stream header is in hex digits and equals ASCII 'nloa'. Does that tell you anything? Jan Hollevoet: What did you use before? Disabled or dynamic port? 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-25261) Missing dependency on RPM package
Daniel Beck commented on JENKINS-25261 Missing dependency on RPM package Could you check whether Jenkins runs in headless mode on your box? Configured in /etc/sysconfig/jenkins, see: https://github.com/jenkinsci/jenkins/blob/master/rpm/SOURCES/jenkins.sysconfig.in#L37 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] [jabber-plugin] (JENKINS-25505) After Upgrade jenkins to 1.587 cannot send message with jabber
kutzi commented on JENKINS-25505 After Upgrade jenkins to 1.587 cannot send message with jabber What are the previous and current version of the jabber-plugin (the plugin doesn't get automatically updated if Jenkins is)? Is _xmpp-client._tcp.jabber.peykasa.ir the correct name of your Jabber server? What happens if you try to resolve the name (i.e. nslookup) from the shell on the Jenkins host? 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-25488) New UI wastes horizontal space
Daniel Beck updated JENKINS-25488 New UI wastes horizontal space Change By: Daniel Beck (08/Nov/14 9:25 AM) Labels: user-experience 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-25490) Slave JLNP client stops working with "Unable to launch the application" when master is stopped
Daniel Beck commented on JENKINS-25490 Slave JLNP client stops working with "Unable to launch the application" when master is stopped To clarify, the Linux slave has a UI and you're launching it using the Start button on the slave's index page on the Jenkins UI? 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] [jobconfighistory-plugin] (JENKINS-25456) POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'
Daniel Beck commented on JENKINS-25456 POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml' Jake: What happens on a pristine instance without Job Config History? Does the config.xml for the job exist before and after you POST? 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
Daniel Beck commented on JENKINS-25474 MultiJob Plugin not recognizing job failures for continuation condition Jira is an issue tracker, not a support site. If you're asking for advice, try #jenkins on Freenode, or the jenkinsci-users mailing list. 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-25490) Slave JLNP client stops working with "Unable to launch the application" when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with "Unable to launch the application" when master is stopped That is correct, yes. We don't have it running as service via upstart. 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-25479) Multi-configuration project jobs cannot be opened if the multijob has been opened from some view
Daniel Beck commented on JENKINS-25479 Multi-configuration project jobs cannot be opened if the multijob has been opened from some view Core changed consistent with documented behavior of Item.getUrl() for JENKINS-19310, comments in JENKINS-23583 link to discussion and advice how to fix. 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-24764) Tabs are wrapping on narrow screens
Daniel Beck updated JENKINS-24764 Tabs are wrapping on narrow screens Change By: Daniel Beck (08/Nov/14 9:48 AM) Labels: user-experience 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] [active-directory-plugin] (JENKINS-22727) AD plugin times out for large user/group membership
Daniel Beck commented on JENKINS-22727 AD plugin times out for large user/group membership Try connecting to the global catalog if you're not. There's an advanced option on /configureSecurity named 'Group Looking Strategy', try both values to see if that changes anything. 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] [icon-shim-plugin] (JENKINS-25498) Inappropriate use of GString
Daniel Beck updated JENKINS-25498 Inappropriate use of GString Change By: Daniel Beck (08/Nov/14 9:50 AM) Component/s: icon-shim-plugin Component/s: core 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Jan Hollevoet commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Daniel, I was using the dynamic port setting. Yesterday, I saw it once again on 480 launches of the cli: Nov 7, 2014 7:06:12 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://192.168.100.61:8080/cli java.io.IOException: Unexpected termination of the channel I am also using the ip address instead of the hostname for the Jenkins server. Not sure whether that helped. 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-25490) Slave JLNP client stops working with "Unable to launch the application" when master is stopped
Daniel Beck commented on JENKINS-25490 Slave JLNP client stops working with "Unable to launch the application" when master is stopped Please try the workaround of using the java ... command line call in a terminal on the slave instead. 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] [cloudbees-folder-plugin] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Daniel Beck commented on JENKINS-25330 Folders should offer to use a hash for workspace path (like matrix does) Ali Raza: Any news? 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Jan Hollevoet edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Daniel, I was using the dynamic port setting. Yesterday, I saw it once again on 480 launches of the cli: Nov 7, 2014 7:06:12 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://192.168.100.61:8080/cli java.io.IOException: Unexpected termination of the channel I am also using the ip address instead of the hostname for the Jenkins server. Not sure whether that helped. And hudson.diyChunking = false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-25500) Cannot save the job after removing Groovy build step
Daniel Beck commented on JENKINS-25500 Cannot save the job after removing Groovy build step Cannot reproduce on 1.586. Create freestyle project, add a Groovy build step with inline script "println 'Hello World'", Save, Configure, delete the build step, Save, everything works. 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-22769) ListView's ItemListener runs with user privileges, might miss affected views
SCM/JIRA link daemon commented on JENKINS-22769 ListView's ItemListener runs with user privileges, might miss affected views Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Fingerprint.java core/src/main/java/hudson/model/ListView.java core/src/main/java/hudson/model/listeners/ItemListener.java core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/8478e24609d407268bd579609bf0ce3ad395a046 Log: [FIXED JENKINS-25400] Rework fix of JENKINS-22769 (c04cdcd) to put the burden on each listener to impersonate ACL.SYSTEM if it needs to. (cherry picked from commit a6a3d5e1660735edc18d331500f7ce9850fbc724) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/be835bfcfb17...8478e24609d4 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-25400) Job owned by SYSTEM instead of creator when 'Setup after creation' used
SCM/JIRA link daemon commented on JENKINS-25400 Job owned by SYSTEM instead of creator when 'Setup after creation' used Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Fingerprint.java core/src/main/java/hudson/model/ListView.java core/src/main/java/hudson/model/listeners/ItemListener.java core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/8478e24609d407268bd579609bf0ce3ad395a046 Log: [FIXED JENKINS-25400] Rework fix of JENKINS-22769 (c04cdcd) to put the burden on each listener to impersonate ACL.SYSTEM if it needs to. (cherry picked from commit a6a3d5e1660735edc18d331500f7ce9850fbc724) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/be835bfcfb17...8478e24609d4 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-21224) Catch all errors thrown by listeners
SCM/JIRA link daemon commented on JENKINS-21224 Catch all errors thrown by listeners Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/listeners/ItemListener.java http://jenkins-ci.org/commit/jenkins/b70313476a86813417b9197555780622cf5170b8 Log: JENKINS-21224 Defend against exceptions in listeners, for now just for ItemListener. java.lang.RuntimeException: Unable to copy /…/jobs/…/config.xml at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndCopyConfig(FileHistoryDao.java:252) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewItem(FileHistoryDao.java:238) at hudson.plugins.jobConfigHistory.JobConfigHistoryJobListener.onCreated(JobConfigHistoryJobListener.java:31) at hudson.model.listeners.ItemListener.fireOnCreated(ItemListener.java:161) at jenkins.model.Jenkins.putItem(Jenkins.java:2483) at … Caused by: java.io.FileNotFoundException: /…/jobs/…/config.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:120) at hudson.plugins.jobConfigHistory.FileHistoryDao.copyConfigFile(FileHistoryDao.java:178) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndCopyConfig(FileHistoryDao.java:250) ... 108 more (cherry picked from commit 6825121f06d6427304fd5149531216ecae6fdf93) 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
SCM/JIRA link daemon commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG Code changed in jenkins User: Oliver Gondža Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/8fbd44db2b2ebf81947a6c3c5861bc30b48cc775 Log: Revert "[FIXED JENKINS-20108]" This reverts commit 68eb26633b1c042d90a426efac7b6e60dd4b2ede. 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-22769) ListView's ItemListener runs with user privileges, might miss affected views
SCM/JIRA link daemon commented on JENKINS-22769 ListView's ItemListener runs with user privileges, might miss affected views Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/listeners/ItemListener.java test/src/test/java/hudson/model/ListViewTest.java http://jenkins-ci.org/commit/jenkins/0efd811adb89769c8a6180e33e3d06d755bca4b5 Log: [FIXED JENKINS-22769] ItemListener callbacks should run as SYSTEM since they sometimes do ACL-checked calls. (cherry picked from commit c04cdcd9f717ddcd3e8c9dbe86cb353c14ae511e) 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] [ssh-slaves-plugin] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Daniel Beck commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG This caused JENKINS-25241 so unfit for LTS. 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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Alexander Obuhovich
commented on JENKINS-25481
API call results empty waring messages
That's better, 10x. I've just specified {{?tree=warnings[*]}} and got only needed info.
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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Ulli Hafner commented on JENKINS-25481 API call results empty waring messages Maybe we should improve the inline documentation of the remote API with some examples. Currently there is just a note that the parameter tree is available... 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-25501) Results not being propagated to ENV variables
Ulli Hafner commented on JENKINS-25501 Results not being propagated to ENV variables Did you use the name as ENV variable or as token with the https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+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] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Ulli Hafner edited a comment on JENKINS-25501 Results not being propagated to ENV variables Did you use it as ENV variable or as token with the https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Daniel Beck commented on JENKINS-25481 API call results empty waring messages Ulli: The entire section "Controlling the amount of data you fetch" is about the tree parameter. 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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Ulli Hafner
commented on JENKINS-25481
API call results empty waring messages
Ah, thanks. Didn't see that. Just noted the section in the top of the help about the JSON explanation ("Access the same data as JSON for _javascript_-based access. tree may be used."). Maybe we should link to the bottom here, too (like in the XML section). I stopped reading after the note with the link to the Wiki page with further information. I hope that other users are not as blind while reading
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-client-plugin] (JENKINS-25506) Git client plugin version not found
Dylan Johnson created JENKINS-25506 Git client plugin version not found Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 08/Nov/14 3:40 PM Description: Installing the Git Client Plugin from the Jenkins UI and from a Chef jenkins_plugin resource provider fails with the following exception: `Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/git-client/1.11.1/git-client.hpi` There is a `/latest` dir and a `1.11.0` dir at that URL, but no `1.11.1` Environment: Jenkins 1.588, OS X Project: Jenkins Labels: version installation missing Priority: Blocker Reporter: Dylan Johnson 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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Alexander Obuhovich commented on JENKINS-25481 API call results empty waring messages Fact, that "tree" parameter can be used in JSON was a surprise to me as well. Also nowhere mentioned that if you pass "*" instead of node name you get all content, e.g. "warnings[*]". 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] [cli] (JENKINS-18627) NullPointerException in Jenkins CLI
Oleg Nenashev resolved JENKINS-18627 as Fixed NullPointerException in Jenkins CLI Fixed in jenkins-1.588 and 1.565.1 https://github.com/jenkinsci/jenkins/commit/b2730f3d31da93a45c7321962141c6f1bc360937 Change By: Oleg Nenashev (08/Nov/14 4:04 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] [mercurial-plugin] (JENKINS-25507) mercurial 1.51 release links broken at http://updates.jenkins-ci.org/download/plugins/mercurial/
Thien Nguyen created JENKINS-25507 mercurial 1.51 release links broken at http://updates.jenkins-ci.org/download/plugins/mercurial/ Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 08/Nov/14 4:09 PM Description: The permalink references http://mirrors.jenkins-ci.org/plugins/mercurial/1.51/mercurial.hpi which is returning a 404: Not Found The requested URL /plugins/mercurial/1.51/mercurial.hpi was not found on this server. Apache/2.2.14 (Ubuntu) Server at mirrors.jenkins-ci.org Port 80 Project: Jenkins Priority: Major Reporter: Thien Nguyen 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] [cli] (JENKINS-21209) any cli command fails with exception
Oleg Nenashev resolved JENKINS-21209 as Duplicate any cli command fails with exception No response from the requester. The issue has a similar stacktrace as JENKINS-20128, the referenced core version is affected by the issue. Closing as a duplicate Change By: Oleg Nenashev (08/Nov/14 4:11 PM) Status: Open Resolved Resolution: Duplicate 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] [cli] (JENKINS-23755) Misleading exception from cli command create-job
Oleg Nenashev resolved JENKINS-23755 as Not A Defect Misleading exception from cli command create-job No response from the requester; not a defect IMO Change By: Oleg Nenashev (08/Nov/14 4:12 PM) Status: Open Resolved Resolution: Not A Defect 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] [github-plugin] (JENKINS-25312) GitHubCommitNotifier: Make the build result configurable on commit update failure
SCM/JIRA link daemon commented on JENKINS-25312 GitHubCommitNotifier: Make the build result configurable on commit update failure Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java http://jenkins-ci.org/commit/github-plugin/06b886a4eda250392eb272ee3c8a1dbb2de15fa3 Log: JENKINS-25312 - Prevent NPE if build has not been finished yet May appear if somebody calls the publisher using AnyBuildStep Signed-off-by: Oleg Nenashev 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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Daniel Beck commented on JENKINS-25481 API call results empty waring messages Yep, JENKINS-16395 was implemented in https://github.com/stapler/stapler/commit/bcb1ab27fa0751a0a9904e41107628f12c0c73c3 without corresponding documentation in Jenkins. I'll look into adding 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] [groovy-plugin] (JENKINS-25500) Cannot save the job after removing Groovy build step
vjuranek resolved JENKINS-25500 as Cannot Reproduce Cannot save the job after removing Groovy build step obviously some issue in my dev environment (when plugin run via mvn hpi:run). Cannot reproduce on regular Jenkins as well. Daniel Beck thanks for looking. Change By: vjuranek (08/Nov/14 6:47 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-25455) Code input field is too small
vjuranek commented on JENKINS-25455 Code input field is too small radiobox makes this element invisible and when CodeMirror computes height of the element it's zero (as element is not visible). Also gutter gets somehow broken during making it invisible and visible process. IMHO proper fix is PR #1460, however, to fix it soon (and for older Jenkins core version), I decided to pre-select StringScriptSource by default when adding new step and thus make it visible at the beginning. 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-25455) Code input field is too small
SCM/JIRA link daemon resolved JENKINS-25455 as Fixed Code input field is too small Change By: SCM/JIRA link daemon (08/Nov/14 7:04 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] [core] (JENKINS-25455) Code input field is too small
SCM/JIRA link daemon commented on JENKINS-25455 Code input field is too small Code changed in jenkins User: Vojtech Juranek Path: src/main/resources/hudson/plugins/groovy/Groovy/config.jelly src/main/resources/hudson/plugins/groovy/form/multi-hetero-radio.jelly http://jenkins-ci.org/commit/groovy-plugin/f91e2194790deb576acbe792dcec1c90a0071d2b Log: [FIXED JENKINS-25455] Show StringScriptSource by default and thus avoid zero height of the textarea 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] [buildresult-trigger-plugin] (JENKINS-20700) Build Result Trigger plugin only sparks job intermittently
Chase Sterling commented on JENKINS-20700 Build Result Trigger plugin only sparks job intermittently I'm having similar trouble, but the trigger never seems to go for me. I just get "Recording context. Check changes in next poll." every run. 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] [mercurial-plugin] (JENKINS-25507) mercurial 1.51 release links broken at http://updates.jenkins-ci.org/download/plugins/mercurial/
Daniel Beck resolved JENKINS-25507 as Not A Defect mercurial 1.51 release links broken at http://updates.jenkins-ci.org/download/plugins/mercurial/ Not a problem with the Mercurial plugin but the Jenkins project infrastructure. This particular issue is known (no tracking issue though) so should be resolved soon. Change By: Daniel Beck (08/Nov/14 9:13 PM) Status: Open Resolved Resolution: Not A Defect 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-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Or Shachar commented on JENKINS-25253 When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build. Thanks for the workaround... I bet there's a simple mistake in one on the conditions in the code that causes it. I'll try to dig in... Thanks! 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-25508) Git plugin doesn't parse changelog (false "First time build")
Or Shachar
created JENKINS-25508
Git plugin doesn't parse changelog (false "First time build")
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
08/Nov/14 9:47 PM
Description:
The job is triggered because of SCM change:
Poll log
[poll] Last Built Revision: Revision 3281126a340c0e863f12c11a7f9ccd31bceb587a (origin/master)
[git] $ sh -e /DATA/jenkins/app-data/tools/git/hudson598255919908413882.sh
> git ls-remote -h [CENSURED] master # timeout=10
[poll] Latest remote head revision is: e72acfe796b818f51ba549991a8f1876657d8986
Done. Took 0.32 sec
Changes found
But in the git log we see that it skips changelog becuase of "First time build" -falsely:
Run log
16:27:52 > /usr/bin/git checkout -f e72acfe796b818f51ba549991a8f1876657d8986
16:27:55 > /usr/bin/git rev-list 3281126a340c0e863f12c11a7f9ccd31bceb587a # timeout=10
16:27:55 First time build. Skipping changelog.
Looking at the current code of Git Plugin I see there's some kind of condition on "exclusion" but I've yet understood what sets it:
from GitSCM.java
private void computeChangeLog(GitClient git, Revision revToBuild, TaskListener listener, BuildData previousBuildData, FilePath changelogFile, BuildChooserContext context) throws IOException, InterruptedException {
Writer out = new OutputStreamWriter(changelogFile.write(),"UTF-8");
boolean executed = false;
ChangelogCommand changelog = git.changelog();
changelog.includes(revToBuild.getSha1());
try {
boolean exclusion = false;
ChangelogToBranch changelogToBranch = getExtensions().get(ChangelogToBranch.class);
if (changelogToBranch != null) {
listener.getLogger().println("Using 'Changelog to branch' strategy.");
changelog.excludes(changelogToBranch.getOptions().getRef());
exclusion = true;
} else {
for (Branch b : revToBuild.getBranches()) {
Build lastRevWas = getBuildChooser().prevBuildForChangelog(b.getName(), previousBuildData, git, context);
if (lastRevWas != null && git.isCommitInRepo(lastRevWas.getSHA1())) {
changelog.excludes(lastRevWas.getSHA1());
exclusion = true;
}
}
}
if (!exclusion) {
// this is the first time we are building this branch, so there's no base line to compare against.
// if we force the changelog, it'll contain all the changes in the repo, which is not what we want.
listener.getLogger().println("First time build. Skipping changelog.");
} else {
changelog.to(out).max(MAX_CHANGELOG).execute();
executed = true;
}
} catch (GitException ge) {
ge.printStackTrace(listener.error("Unable to retrieve changeset"));
} finally {
if (!executed) changelog.abort();
IOUtils.closeQuietly(out);
}
}
I might take the task to fix it on my own - but maybe for some of you it may be obvious...
Environment:
Jenkins 1.565.2
Git-Client 1.11.0
Git plugin 2.2.7
SCM-API 0.2
SSH credentials 1.10
Credentials 1.18
Both master and slave works on RHEL 6.3 with Java 7u51
Project:
Jenkins
Labels:
git
git-client
changelog
Priority:
Minor
Reporter:
Or Shachar
This message is automatic
[JIRA] [git-plugin] (JENKINS-25508) Git plugin doesn't parse changelog (false "First time build")
Or Shachar
updated JENKINS-25508
Git plugin doesn't parse changelog (false "First time build")
Change By:
Or Shachar
(08/Nov/14 9:48 PM)
Description:
The job is triggered because of SCM change:{code:title=Poll log|borderStyle=solid}[poll] Last Built Revision: Revision 3281126a340c0e863f12c11a7f9ccd31bceb587a (origin/master)[git] $ sh -e /DATA/jenkins/app-data/tools/git/hudson598255919908413882.sh > git ls-remote -h [CENSURED] master # timeout=10[poll] Latest remote head revision is: e72acfe796b818f51ba549991a8f1876657d8986Done. Took 0.32 secChanges found{code}But in the
run
git log we see that it skips changelog becuase of "First time build" -falsely:{code:title=Run log|borderStyle=solid}16:27:52 > /usr/bin/git checkout -f e72acfe796b818f51ba549991a8f1876657d898616:27:55 > /usr/bin/git rev-list 3281126a340c0e863f12c11a7f9ccd31bceb587a # timeout=1016:27:55 First time build. Skipping changelog.{code}Looking at the current code of Git Plugin I see there's some kind of condition on "exclusion" but I've yet understood what sets it:{code:java|title=from GitSCM.java} private void computeChangeLog(GitClient git, Revision revToBuild, TaskListener listener, BuildData previousBuildData, FilePath changelogFile, BuildChooserContext context) throws IOException, InterruptedException {Writer out = new OutputStreamWriter(changelogFile.write(),"UTF-8");boolean executed = false;ChangelogCommand changelog = git.changelog();changelog.includes(revToBuild.getSha1());try {boolean exclusion = false;ChangelogToBranch changelogToBranch = getExtensions().get(ChangelogToBranch.class);if (changelogToBranch != null) {listener.getLogger().println("Using 'Changelog to branch' strategy.");changelog.excludes(changelogToBranch.getOptions().getRef());exclusion = true;} else {for (Branch b : revToBuild.getBranches()) {Build lastRevWas = getBuildChooser().prevBuildForChangelog(b.getName(), previousBuildData, git, context);if (lastRevWas != null && git.isCommitInRepo(lastRevWas.getSHA1())) {changelog.excludes(lastRevWas.getSHA1());exclusion = true;}}}if (!exclusion) {// this is the first time we are building this branch, so there's no base line to compare against.// if we force the changelog, it'll contain all the changes in the repo, which is not what we want.listener.getLogger().println("First time build. Skipping changelog.");} else {changelog.to(out).max(MAX_CHANGELOG).execute();executed = true;}} catch (GitException ge) {ge.printStackTrace(listener.error("Unable to retrieve changeset"));} finally {if (!executed) changelog.abort();IOUtils.closeQuietly(out);}}{code}I might take the task to fix it on my own - but maybe for some of you it may be obvious...
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-client-plugin] (JENKINS-25506) Git client plugin version not found
Mark Waite resolved JENKINS-25506 as Not A Defect Git client plugin version not found There was an infrastructure issue 8 Nov 2014 (and possibly a day or two earlier) which caused the mirrors site to not mirror content. Kohsuke Kawaguchi reported that he was working on it that same day. Update worked for me about 9 hours after the initial failure report. Believed to be fixed. In any case, not an issue with the git client plugin. Change By: Mark Waite (08/Nov/14 10:59 PM) Status: Open Resolved Resolution: Not A Defect 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-client-plugin] (JENKINS-25506) Git client plugin version not found
Mark Waite closed JENKINS-25506 as Not A Defect Git client plugin version not found Change By: Mark Waite (08/Nov/14 10:59 PM) Status: Resolved Closed 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] [flexible-publish-plugin] (JENKINS-22187) Add support of multiple actions inside the condition
SCM/JIRA link daemon commented on JENKINS-22187 Add support of multiple actions inside the condition Code changed in jenkins User: ikedam Path: src/test/java/org/jenkins_ci/plugins/flexible_publish/AggregationRecorder.java src/test/java/org/jenkins_ci/plugins/flexible_publish/ConfigurationTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisherTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/MatrixAggregationTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/TriggerTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/testutils/AggregationRecorder.java src/test/java/org/jenkins_ci/plugins/flexible_publish/testutils/FileWriteBuilder.java src/test/resources/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisherTest/testMigrationFrom0_12/config.xml src/test/resources/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisherTest/testMigrationFrom0_12/jobs/migration_from_0.12/config.xml http://jenkins-ci.org/commit/flexible-publish-plugin/b598099d41c701977bb9273aff645fe9879a482f Log: JENKINS-22187 Added tests for multiple actions. 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] [flexible-publish-plugin] (JENKINS-22187) Add support of multiple actions inside the condition
SCM/JIRA link daemon commented on JENKINS-22187 Add support of multiple actions inside the condition Code changed in jenkins User: ikedam Path: src/test/java/org/jenkins_ci/plugins/flexible_publish/MatrixAggregationTest.java http://jenkins-ci.org/commit/flexible-publish-plugin/b8813b5a9032edbe5912aad23752bfb8e81f06f2 Log: JENKINS-22187 wrong Action name in tests. 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] [flexible-publish-plugin] (JENKINS-22187) Add support of multiple actions inside the condition
SCM/JIRA link daemon commented on JENKINS-22187 Add support of multiple actions inside the condition Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java src/main/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisher.java src/main/resources/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher/config.jelly http://jenkins-ci.org/commit/flexible-publish-plugin/a8f232f9a7fa7dcacdd7bdddc0e214231ec1871a Log: [FIXED JENKINS-22187] Supports multiple actions for a condition. 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] [flexible-publish-plugin] (JENKINS-22187) Add support of multiple actions inside the condition
SCM/JIRA link daemon commented on JENKINS-22187 Add support of multiple actions inside the condition Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java src/main/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisher.java src/main/resources/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher/config.jelly src/test/java/org/jenkins_ci/plugins/flexible_publish/AggregationRecorder.java src/test/java/org/jenkins_ci/plugins/flexible_publish/ConfigurationTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisherTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/MatrixAggregationTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/TriggerTest.java src/test/java/org/jenkins_ci/plugins/flexible_publish/testutils/AggregationRecorder.java src/test/java/org/jenkins_ci/plugins/flexible_publish/testutils/FileWriteBuilder.java src/test/resources/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisherTest/testMigrationFrom0_12/config.xml src/test/resources/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisherTest/testMigrationFrom0_12/jobs/migration_from_0.12/config.xml http://jenkins-ci.org/commit/flexible-publish-plugin/50f89c1d261d2483117126c723e5fb785f58 Log: Merge pull request #6 from ikedam/feature/JENKINS-22187_MultipleActions JENKINS-22187 Support multiple actions Compare: https://github.com/jenkinsci/flexible-publish-plugin/compare/6b9f980f351e...50f89c1d261d 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] [flexible-publish-plugin] (JENKINS-22187) Add support of multiple actions inside the condition
SCM/JIRA link daemon resolved JENKINS-22187 as Fixed Add support of multiple actions inside the condition Change By: SCM/JIRA link daemon (09/Nov/14 12:21 AM) Status: In Progress 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] [authorize-project-plugin] (JENKINS-25403) Plugins should switch to '$class' from 'stapler-class' and 'kind'
ikedam commented on JENKINS-25403 Plugins should switch to '$class' from 'stapler-class' and 'kind' https://github.com/ikedam/stapler/tree/stapler-parent-1.233-JENKINS-25403 https://github.com/ikedam/jenkins/tree/jenkins-1.588-JENKINS-25403 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] [authorize-project-plugin] (JENKINS-25403) Plugins should switch to '$class' from 'stapler-class' and 'kind'
SCM/JIRA link daemon commented on JENKINS-25403 Plugins should switch to '$class' from 'stapler-class' and 'kind' Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java http://jenkins-ci.org/commit/flexible-publish-plugin/319e7add1b70b41017dbdc1cf9ad30a7238f3195 Log: Merge pull request #5 from mattmoor/master JENKINS-25403 Add support for upcoming $class annotation change Compare: https://github.com/jenkinsci/flexible-publish-plugin/compare/50f89c1d261d...319e7add1b70 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] [authorize-project-plugin] (JENKINS-25403) Plugins should switch to '$class' from 'stapler-class' and 'kind'
SCM/JIRA link daemon commented on JENKINS-25403 Plugins should switch to '$class' from 'stapler-class' and 'kind' Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java http://jenkins-ci.org/commit/flexible-publish-plugin/8f952fcdfe26c460494eeb42bc744bc3d64e727a Log: JENKINS-25403 Fixed the error message for no $class or stapler-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] [authorize-project-plugin] (JENKINS-25403) Plugins should switch to '$class' from 'stapler-class' and 'kind'
ikedam updated JENKINS-25403 Plugins should switch to '$class' from 'stapler-class' and 'kind' Change By: ikedam (09/Nov/14 3:11 AM) Component/s: flexible-publish-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] [flexible-publish-plugin] (JENKINS-22187) Add support of multiple actions inside the condition
ikedam closed JENKINS-22187 as Fixed Add support of multiple actions inside the condition Fixed in 0.13. It will be available in a day. Please try that. Change By: ikedam (09/Nov/14 3:19 AM) Status: Resolved Closed 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] [flexible-publish-plugin] (JENKINS-22188) Multiple capability (as conditional steps plugin as single and multiple)
ikedam closed JENKINS-22188 as Duplicate Multiple capability (as conditional steps plugin as single and multiple) Fixed in 0.13. It will be available in a day. Please try that. Change By: ikedam (09/Nov/14 3:20 AM) Status: Resolved Closed Assignee: bap ikedam 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] [flexible-publish-plugin] (JENKINS-25017) BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501
ikedam closed JENKINS-25017 as Fixed BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501 Fixed in 0.13. It will be available in a day. Please try that. Change By: ikedam (09/Nov/14 3:20 AM) Status: Resolved Closed 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] [flexible-publish-plugin] (JENKINS-21497) Combining with xUnit Plugin cause "Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher"
ikedam closed JENKINS-21497 as Won't Fix Combining with xUnit Plugin cause "Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher" Fixed in 0.13. It will be available in a day. Please try that. Change By: ikedam (09/Nov/14 3:20 AM) Status: Resolved Closed 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] [flexible-publish-plugin] (JENKINS-21345) Filter action list on matrix jobs
ikedam closed JENKINS-21345 as Not A Defect Filter action list on matrix jobs Fixed in 0.13. It will be available in a day. Please try that. Change By: ikedam (09/Nov/14 3:20 AM) Status: Resolved Closed Assignee: ikedam 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-25414) Allow remote polling if multiple repositories but single branch defined
SCM/JIRA link daemon resolved JENKINS-25414 as Fixed Allow remote polling if multiple repositories but single branch defined Change By: SCM/JIRA link daemon (09/Nov/14 5:04 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-25414) Allow remote polling if multiple repositories but single branch defined
SCM/JIRA link daemon commented on JENKINS-25414 Allow remote polling if multiple repositories but single branch defined Code changed in jenkins User: Wannes Sels Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/0c250cd1c53e351f119b819c879290ce111cd5ef Log: Allow remotePolling on single (qualified) branch with multiple repositories [FIXED JENKINS-25414] 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-25414) Allow remote polling if multiple repositories but single branch defined
SCM/JIRA link daemon commented on JENKINS-25414 Allow remote polling if multiple repositories but single branch defined Code changed in jenkins User: Wannes Sels Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/c82b8e888a5810189e7c641e846468954d41ad4c Log: Allow remotePolling on single (qualified) branch with multiple repositories [FIXED JENKINS-25414] 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.
