[JIRA] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. To be honour, port exposig just occures on any internal redirection. Form save, trailing slash redirection, etc. The redirected version contains internal 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Nope, this didn't help. nginx and jenkins were restarted after setting to be sure After setting X-Forwarded-Port 443 https://build.example.com/ null https 443 8080 Before setting X-Forwarded-Port 443 https://build.example.com:8080/ null https null 8080 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Additionaly, I've tried to update everything at the jenkins host, so jenkins is 1.605 now. And still not 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-27525) Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine
Daniel Beck updated JENKINS-27525 Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine Change By: Daniel Beck (21/Mar/15 8:15 AM) Component/s: core Component/s: maven-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] [description-setter-plugin] (JENKINS-26671) Multiple description setter build steps should append to build description
SCM/JIRA link daemon commented on JENKINS-26671 Multiple description setter build steps should append to build description Code changed in jenkins User: michael1010 Path: .gitignore src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-regexpForFailed.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help.html http://jenkins-ci.org/commit/description-setter-plugin/284925c209ae47a429f821b777ccbc023d652ac1 Log: Merge pull request #6 from michael1010/master JENKINS-26671 Multiple description setter build steps should append JENKINS-16377 help text for "description setter" seems to be incorrect JENKINS-17461 Expose description as an environment variable Compare: https://github.com/jenkinsci/description-setter-plugin/compare/965d2e9d8512...284925c209ae 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] [description-setter-plugin] (JENKINS-16377) help text for description setter seems to be incorrect / misleading
SCM/JIRA link daemon commented on JENKINS-16377 help text for description setter seems to be incorrect / misleading Code changed in jenkins User: michael Path: src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-regexpForFailed.html http://jenkins-ci.org/commit/description-setter-plugin/9ee30931cd776ec46c7c3147b945ff37c4666502 Log: JENKINS-16377 help text for "description setter" seems to be incorrect changed the help text to make it clearer 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] [description-setter-plugin] (JENKINS-17461) Expose description as an environment variable.
SCM/JIRA link daemon commented on JENKINS-17461 Expose description as an environment variable. Code changed in jenkins User: michael1010 Path: .gitignore src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-regexpForFailed.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help.html http://jenkins-ci.org/commit/description-setter-plugin/284925c209ae47a429f821b777ccbc023d652ac1 Log: Merge pull request #6 from michael1010/master JENKINS-26671 Multiple description setter build steps should append JENKINS-16377 help text for "description setter" seems to be incorrect JENKINS-17461 Expose description as an environment variable Compare: https://github.com/jenkinsci/description-setter-plugin/compare/965d2e9d8512...284925c209ae 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] [description-setter-plugin] (JENKINS-17461) Expose description as an environment variable.
SCM/JIRA link daemon commented on JENKINS-17461 Expose description as an environment variable. Code changed in jenkins User: michael Path: src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help.html http://jenkins-ci.org/commit/description-setter-plugin/c8f1b3f353a1a418ac5c5e3e4345aa6c9f70e505 Log: JENKINS-17461 Expose description as an environment variable fixed JENKINS-17461: description is exposed as DESCRIPTION_SETTER_DESCRIPTION environment variable 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Daniel Beck commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. UPD. Display url is set up on `https://build.example.com` as it should. What does that mean? Are you referring to the Jenkins URL option in the global configuration? You haven't answered this question. If you mean something else, check what URL is configured there. In the script console, please also run and provide output for: println org.kohsuke.stapler.Stapler.currentRequest.serverName 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] [description-setter-plugin] (JENKINS-26671) Multiple description setter build steps should append to build description
SCM/JIRA link daemon commented on JENKINS-26671 Multiple description setter build steps should append to build description Code changed in jenkins User: michael Path: .gitignore src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java http://jenkins-ci.org/commit/description-setter-plugin/3b98efa98268f225bfb33fa2cf8d75df23dce75b Log: JENKINS-26671 Multiple description setter build steps should append ... This commit fixes JENKINS-26671: Multiple description setter build steps should append to build description] At the same time it also fixes JENKINS-14198: Ability to append a description to existing description for use with flexible publish 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] [description-setter-plugin] (JENKINS-14198) Ability to append a description to existing description for use with flexible publish
SCM/JIRA link daemon commented on JENKINS-14198 Ability to append a description to existing description for use with flexible publish Code changed in jenkins User: michael Path: .gitignore src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java http://jenkins-ci.org/commit/description-setter-plugin/3b98efa98268f225bfb33fa2cf8d75df23dce75b Log: JENKINS-26671 Multiple description setter build steps should append ... This commit fixes JENKINS-26671: Multiple description setter build steps should append to build description] At the same time it also fixes JENKINS-14198: Ability to append a description to existing description for use with flexible publish 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] [description-setter-plugin] (JENKINS-16377) help text for description setter seems to be incorrect / misleading
SCM/JIRA link daemon commented on JENKINS-16377 help text for description setter seems to be incorrect / misleading Code changed in jenkins User: michael1010 Path: .gitignore src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help-regexpForFailed.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterPublisher/help.html http://jenkins-ci.org/commit/description-setter-plugin/284925c209ae47a429f821b777ccbc023d652ac1 Log: Merge pull request #6 from michael1010/master JENKINS-26671 Multiple description setter build steps should append JENKINS-16377 help text for "description setter" seems to be incorrect JENKINS-17461 Expose description as an environment variable Compare: https://github.com/jenkinsci/description-setter-plugin/compare/965d2e9d8512...284925c209ae 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Also problem exists only for some routers. I.e Going /log - redirects me to :8080/log/ (with trailing slash) Going /systeminfo - succeedes (without trailing slash) Going /pluginManager - redirects me to :8080/pluginManager/ Harder example is /configure. It opens normally, but redirects me to :8080/ (main page with port) on configuration save 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Is it possible just to replace jenkins.war with old one (i.e 1.598) just to check it works? Will I have some compatability issues? 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov edited a comment on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Is it possible just to replace jenkins.war with old one (i.e 1.598) just to check it works? Will I have any compatability issues? 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Daniel Beck commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Is it possible just to replace jenkins.war with old one (i.e 1.598) just to check it works? Downgrading to before 1.600 may fail to load some plugins if Matrix Project Plugin is enabled. Not sure what happens though. I'd just rename JENKINS_HOME temporarily and provide a clean JENKINS_HOME for the 1.598 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov
commented on JENKINS-27468
Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
The main idea, that nginx config was touched several months ago. And anything worked properly more than for a year.
I've updated nginx to the latest versiona available. I've checked that configuration is equal to the link you refer. (first one, second is not applicable as jenkins is not on the same host)
Here it is for you to be sure
server {
listen *:80;
server_name build.example.com build.other.tld;
rewrite ^/(.*) https://build.example.com/$1;
}
server {
listen *:443;
server_name build.example.com build.other.tld;
location / {
proxy_pass http://10.0.0.19:8080/;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host:$proxy_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_redirect http:// https://;
}
client_max_body_size 400m;
ssl on;
ssl_certificate /root/chain/chained/build.example.com.crt;
ssl_certificate_key /root/chain/keys/build.example.com.key;
}
And firstly I've asked about this bug on a Jenkins IRC chat, and `orrc` confirmed that he has the same behavior.
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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Daniel Beck commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. Try proxy_set_header X-Forwarded-Port 443 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Daniel Beck commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. FWIW your comment with the script console output suggests it did work as the "before" state shows that Jenkins adds the port. It really shouldn't redirect to 8080 anymore afterwards though 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. But unfortunately it does I've restarted nginx and jenkins again to be sure. println org.kohsuke.stapler.Stapler.currentRequest.serverName gives me build.example.com I'll try to deploy old version soon, if we can't find other reason for it 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] [klaros-testmanagement-plugin] (JENKINS-15744) Whitespaces at the end of input fields leads to bogus file upload
stolp started work on JENKINS-15744 Whitespaces at the end of input fields leads to bogus file upload Change By: stolp (21/Mar/15 4:36 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] [klaros-testmanagement-plugin] (JENKINS-15744) Whitespaces at the end of input fields leads to bogus file upload
stolp resolved JENKINS-15744 as Fixed Whitespaces at the end of input fields leads to bogus file upload Change By: stolp (21/Mar/15 4:37 PM) 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] [klaros-testmanagement-plugin] (JENKINS-15744) Whitespaces at the end of input fields leads to bogus file upload
stolp assigned JENKINS-15744 to stolp Whitespaces at the end of input fields leads to bogus file upload Change By: stolp (21/Mar/15 4:35 PM) Assignee: stolp 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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Daniel Beck
commented on JENKINS-27468
Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
If that doesn't help, please provide the output of the following script in Manage Jenkins ยป Script Console:
println Jenkins.instance.rootUrlFromRequest
println org.kohsuke.stapler.Stapler.currentRequest.getHeader('X-Forwarded-Host')
println org.kohsuke.stapler.Stapler.currentRequest.getHeader('X-Forwarded-Proto')
println org.kohsuke.stapler.Stapler.currentRequest.getHeader('X-Forwarded-Port')
println org.kohsuke.stapler.Stapler.currentRequest.serverPort
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-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
Pavel Batanov commented on JENKINS-27468 Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs. yes, I refer Jenkins Url there, just mixed up with atlassian terms (it called display url there). I'll try to provide answers for you in a several hours 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-26145) Narrow down github auth scope for user logins
Daniel Beck commented on JENKINS-26145 Narrow down github auth scope for user logins Given that the source code of the plugin is available, isn't this more cosmetic than anything else? 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-27536) Add option for back to normal build result to trigger a build in the Parameterized Trigger Plugin
Karl Weinmeister created JENKINS-27536 Add option for back to normal build result to trigger a build in the Parameterized Trigger Plugin Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger-plugin Created: 21/Mar/15 3:47 PM Description: We have a use case where it would be helpful to trigger another build when the current build is successful after a previous failure. Environment: Jenkins 1.598 Project: Jenkins Priority: Minor Reporter: Karl Weinmeister 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] [klaros-testmanagement-plugin] (JENKINS-15744) Whitespaces at the end of input fields leads to bogus file upload
stolp commented on JENKINS-15744 Whitespaces at the end of input fields leads to bogus file upload Thanks for submitting. 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] [extensible-choice-parameter-plugin] (JENKINS-27528) Implement a XPathChoiceListProvider so that entries could be read from the pom.xml for example
Michael Rumpf
updated JENKINS-27528
Implement a XPathChoiceListProvider so that entries could be read from the pom.xml for example
Change By:
Michael Rumpf
(21/Mar/15 11:01 AM)
Summary:
Implementa
XmlXPathChoiceListProvider
XPathChoiceListProvider
sothatentriescouldbereadfromthepom.xmlforexample
Description:
Havinga
XmlXPathChoiceListProvider
XPathChoiceListProvider
wouldallowtograbcertainentriesfromanXMLfile.InourcasewewanttograballMavenprovileidsbecausethoseprofileidsarethenameoftheenvironmentswhereyoucandeployanartifactto.TheselectedentrycouldlaterbepassedtotheMavenbuildbysomethinglikethat-P${profileId}...Asfilenameanyfileshouldbepossible,relativetothejobsworkspaceroot-notonlypom.xml.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-19384) Adding stdout to be displayed in your test results
Ivo Bellin Salarin reopened JENKINS-19384 Adding stdout to be displayed in your test results Sorry, this is not a duplicate of JENKINS-17506. I'm fixing it now. Change By: Ivo Bellin Salarin (21/Mar/15 1:26 PM) Resolution: Duplicate Status: Resolved 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] [mstest-plugin] (JENKINS-19384) Adding stdout to be displayed in your test results
Ivo Bellin Salarin resolved JENKINS-19384 as Fixed Adding stdout to be displayed in your test results Change By: Ivo Bellin Salarin (21/Mar/15 2:14 PM) Status: Reopened 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] [mstest-plugin] (JENKINS-19384) Adding stdout to be displayed in your test results
SCM/JIRA link daemon commented on JENKINS-19384 Adding stdout to be displayed in your test results Code changed in jenkins User: nilleb Path: src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java src/test/resources/hudson/plugins/mstest/JENKINS-25533+19384.trx src/test/resources/hudson/plugins/mstest/JENKINS-25533+19384.xml src/test/resources/hudson/plugins/mstest/nilleb_HOST18468 2015-03-18 08_03_36.xml http://jenkins-ci.org/commit/mstest-plugin/2b6797a0cc004d7756bcb6d13fbba465389bdac2 Log: FIXED JENKINS-25533FIXED JENKINS-19384 support for output/stdout messages 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] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
SCM/JIRA link daemon commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Code changed in jenkins User: nilleb Path: src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java src/test/resources/hudson/plugins/mstest/JENKINS-25533+19384.trx src/test/resources/hudson/plugins/mstest/JENKINS-25533+19384.xml src/test/resources/hudson/plugins/mstest/nilleb_HOST18468 2015-03-18 08_03_36.xml http://jenkins-ci.org/commit/mstest-plugin/2b6797a0cc004d7756bcb6d13fbba465389bdac2 Log: FIXED JENKINS-25533FIXED JENKINS-19384 support for output/stdout messages 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-27533) Show StdOut/ information from .trx file.
Ivo Bellin Salarin resolved JENKINS-27533 as Fixed Show StdOut/ information from .trx file. fixed by commit http://jenkins-ci.org/commit/mstest-plugin/2b6797a0cc004d7756bcb6d13fbba465389bdac2 Change By: Ivo Bellin Salarin (21/Mar/15 2:15 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] [perforce-plugin] (JENKINS-15315) Slave polling hungup
Alexey Larsky commented on JENKINS-15315 Slave polling hungup Version 1.31 is most stable. 1.33 and 1,34 hungs on slaves periodically. 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-26145) Narrow down github auth scope for user logins
Daniel Beck commented on JENKINS-26145 Narrow down github auth scope for user logins Sure, the plugin should restrict itself to the minimum. But I meant that the impact of any additional permissions can be known with certainty in this case: It's not like you give access to your account to a third party, but to software you run yourself and can read the source code of. Therefore I don't see how this can be classified as anything more severe than Minor. 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Daniel Beck edited a comment on JENKINS-26186 Last Build Trigger Column does not print author name Columns can have configuration. Why not add a checkbox or dropdown menu to configure column behavior (rather than add two different, but similar columns)? Advantages would be that it requires less space in the column selection list in the view configuration, and you can more easily switch from one form to the other. 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-26145) Narrow down github auth scope for user logins
norman richards commented on JENKINS-26145 Narrow down github auth scope for user logins Given that we want this plugin to work for a wide variety of users, (my assumption) shouldn't the default scopes be more reasonable? I'd suggest they should be configurable so that a jenkins installation can chose the permissions appropriate for it's users. 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Daniel Beck commented on JENKINS-26186 Last Build Trigger Column does not print author name Columns can have configuration. Why not add a checkbox or dropdown menu to configure column behavior? 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Baptiste Mathus updated JENKINS-26186 Last Build Trigger Column does not print author name Change By: Baptiste Mathus (21/Mar/15 8:42 PM) Issue Type: Bug Improvement 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Baptiste Mathus commented on JENKINS-26186 Last Build Trigger Column does not print author name OK, the intent was indeed actually to only show the icon (like elsewhere). So that makes the current issue no more a bug, but an improvement request. For me, it's two fold (from a "product" management perspective): either we just close this bug as wontfix because we want to keep the complexity low, or we add a new column variant named for example 'last build trigger - long version' and reintroduce a column with the old behaviour. If we were on a big product, I'd say the first solution may be better. In our case, I suppose the second case is feasible since the codebase is still pretty small. Though we sure want to reuse as much code as possible if we introduce that second column being a 'long' variant of the current one. 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Baptiste Mathus commented on JENKINS-26186 Last Build Trigger Column does not print author name Additional note: for that new column, to not have the issue that led to JENKINS-22557 we certainly want to limit the max number of characters shown to some hard value, and for example show the full version in a title (if there's more). 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-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
Dominik Pich reopened JENKINS-23543 Launchctl does not load Jenkins on OS X 10.10 Yosemite the current installer (on the main page) isn't fixed as of wednesday Change By: Dominik Pich (21/Mar/15 9:31 PM) Resolution: Duplicate Status: Resolved 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] [git-plugin] (JENKINS-27097) wrong timezone reported in changes
Vasili Kvockin commented on JENKINS-27097 wrong timezone reported in changes What is the minimum JDK compatibility level for Jenkins? One of the tests breaks with JDK 1.6 for me. With 1.7 it works. (OSX 10.10.2) Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.444 sec FAILURE! - in hudson.plugins.git.GitChangeSetTest testIsoDate(hudson.plugins.git.GitChangeSetTest) Time elapsed: 1.01 sec ERROR! java.lang.IllegalArgumentException: Illegal pattern character 'X' at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:768) at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:575) at java.text.SimpleDateFormat.init(SimpleDateFormat.java:500) at java.text.SimpleDateFormat.init(SimpleDateFormat.java:475) at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:209) at hudson.plugins.git.GitChangeSetTest.testIsoDate(GitChangeSetTest.java:154) $ java -version java version "1.6.0_65" Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716) Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode) $ java -version java version "1.7.0_21" Java(TM) SE Runtime Environment (build 1.7.0_21-b12) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) 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-27097) wrong timezone reported in changes
Mark Waite edited a comment on JENKINS-27097 wrong timezone reported in changes The Jenkins git plugin is developed, compiled, and tested with JDK 1.7. The building Jenkins wiki page says that JDK 1.6 is required for Jenkins as a whole, but the git plugin is no longer being checked that it compiles with JDK 1.6, or that it runs with JDK 1.6. Since April 2015 is the official end of publicly available patches for JDK 1.7, and since Oracle's last publicly available patch for JDK 1.6 was 1.6.0_45 in April 2013, I hope the community sees that as a reasonable approach. Do you think that JDK 1.6 support is critical for the community of users of the git plugin? We recently had to refine a change so that users of the git plugin running on Red Hat 5 and Red Hat 6 (git versions prior to 1.7.10) would not be disrupted by the assumption of credentials support in command line git. Maybe we'll need to do something similar here, with some form of conditional for JDK 1.6. If so, then I'll adapt the test automation setup I have to include more testing of JDK 1.6 before new plugin versions are released. 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-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Mark Waite commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin I wonder if this is another manifestation of JENKINS-27332 ? You could test that by downgrading your git plugin from 2.3.5 to 2.3.4. There are some other hints in that report of alternatives you may be able to try for the branch specification. 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-27097) wrong timezone reported in changes
Mark Waite commented on JENKINS-27097 wrong timezone reported in changes The Jenkins git plugin is developed, compiled, and tested with JDK 1.7. The building Jenkins wiki page says that JDK 1.6 is required for Jenkins as a whole, but the git plugin is no longer being checked that it compiles with JDK 1.6, or that it runs with JDK 1.6. Since April 2015 is the official end of publicly available patches for JDK 1.7, and since Oracle's last publicly available patch for JDK 1.6 was 1.6.0_45 in April 2013, I hope the community sees that as a reasonable approach. 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-27097) wrong timezone reported in changes
Mark Waite edited a comment on JENKINS-27097 wrong timezone reported in changes The Jenkins git plugin is developed, compiled, and tested with JDK 1.7. The building Jenkins wiki page says that JDK 1.6 is required for Jenkins as a whole, but the git plugin is no longer being checked that it compiles with JDK 1.6, or that it runs with JDK 1.6. Since April 2015 is the official end of publicly available patches for JDK 1.7, and since Oracle's last publicly available patch for JDK 1.6 was 1.6.0_45 in April 2013, I hope the community sees that as a reasonable approach. Do you think that JDk 1.6 support is critical for the community of users of the git plugin? We recently had to refine a change so that users of the git plugin running on Red Hat 5 and Red Hat 6 (git versions prior to 1.7.10) would not be disrupted by the assumption of credentials support in command line git. Maybe we'll need to do something similar here, with some form of conditional for JDK 1.6. 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-27097) wrong timezone reported in changes
Mark Waite edited a comment on JENKINS-27097 wrong timezone reported in changes The Jenkins git plugin is developed, compiled, and tested with JDK 1.7. The building Jenkins wiki page says that JDK 1.6 is required for Jenkins as a whole, but the git plugin is no longer being checked that it compiles with JDK 1.6, or that it runs with JDK 1.6. Since April 2015 is the official end of publicly available patches for JDK 1.7, and since Oracle's last publicly available patch for JDK 1.6 was 1.6.0_45 in April 2013, I hope the community sees that as a reasonable approach. Do you think that JDK 1.6 support is critical for the community of users of the git plugin? We recently had to refine a change so that users of the git plugin running on Red Hat 5 and Red Hat 6 (git versions prior to 1.7.10) would not be disrupted by the assumption of credentials support in command line git. After that, I included Red Hat 5 and Red Hat 6 machines in my test setup. Maybe we'll need to do something similar here, with some form of conditional for JDK 1.6. If so, then I'll adapt the test automation setup I have to include more testing of JDK 1.6 before new plugin versions are released. 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] [extensible-choice-parameter-plugin] (JENKINS-27375) Add options to enable / disable choice providers
ikedam started work on JENKINS-27375 Add options to enable / disable choice providers Change By: ikedam (22/Mar/15 4:35 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.
