[JIRA] (JENKINS-33756) Job is run twice on first slave using label parameter
Title: Message Title Jason Stanley commented on JENKINS-33756 Re: Job is run twice on first slave using label parameter Also hitting this problem on Jenkins ver. 2.121.2 plugin version 1.7.2 Red Hat 7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-19197) Plug-in does not support matrix builds
Title: Message Title Jason Stanley commented on JENKINS-19197 Re: Plug-in does not support matrix builds Problem still exists with Jenkins version 1.615 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29883) set-build-description no longer appends descriptions.
Title: Message Title Jason Stanley created an issue Jenkins / JENKINS-29883 set-build-description no longer appends descriptions. Issue Type: Bug Assignee: Unassigned Components: cli Created: 10/Aug/15 5:54 PM Environment: CentOS 6.5 Jenkins 1.615 Labels: set-build-description cli Priority: Major Reporter: Jason Stanley After upgrading from 1.594 to 1.615, if you run the command set-build-description, it will no longer append a new description if an existing description exists. Before the upgrade if I ran the set-build-description command 4 times, each time adding a number, the job description would say: 1 2 3 4 After the upgrade, the job description now looks like this; 4
[JIRA] [core] (JENKINS-29071) Jenkins not following symlink of archived directory since upgrade to 1.615
Title: Message Title Jason Stanley created an issue Jenkins / JENKINS-29071 Jenkins not following symlink of archived directory since upgrade to 1.615 Issue Type: Bug Assignee: Unassigned Attachments: screenshots.docx Components: core Created: 24/Jun/15 6:28 PM Environment: CentOS 6.5 Jenkins 1.615 Labels: core archive artifact symlink Priority: Major Reporter: Jason Stanley In my environment, to save disk space, I move a directory that is an archive onto another file server and create a symlink pointing to this location. This was working fine using version 1.594. I just upgraded from 1.594 to 1.615
[JIRA] [extended-choice-parameter] (JENKINS-23739) Builds fail after upgrading Extended Choice Parameter plugin from version 0.28 to 0.34, due to delimiter missing.
Jason Stanley created JENKINS-23739 Builds fail after upgrading Extended Choice Parameter plugin from version 0.28 to 0.34, due to delimiter missing. Issue Type: Bug Affects Versions: current Assignee: vimil Attachments: screenshots.docx Components: extended-choice-parameter Created: 10/Jul/14 10:53 AM Description: After upgrading the Extended Choice Parameter plugin from version 0.28 to 0.34 my builds are failing due to the parameters being passed no longer are separated by a comma. See attachment of screenshot detailing issue. Environment: CentOS 6.5 server. Jenkins 1.570 Project: Jenkins Priority: Major Reporter: Jason Stanley This message is automatically generated by JIRA. 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] [extended-choice-parameter] (JENKINS-23739) Builds fail after upgrading Extended Choice Parameter plugin from version 0.28 to 0.34, due to delimiter missing.
Jason Stanley commented on JENKINS-23739 Builds fail after upgrading Extended Choice Parameter plugin from version 0.28 to 0.34, due to delimiter missing. Isn't the default a comma? According to the help information when you click on the question mark. Inserts this value between selections when the parameter is a multi-select. The default when empty is ',' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23730) Upgraded Email-ext plugin to version 2.38.1, now build log attachments are truncated to 10,000 lines.
Jason Stanley created JENKINS-23730 Upgraded Email-ext plugin to version 2.38.1, now build log attachments are truncated to 10,000 lines. Issue Type: Bug Affects Versions: current Assignee: Alex Earl Attachments: build-2.38.1.zip, log-2.36.zip Components: email-ext Created: 09/Jul/14 5:21 PM Description: Using Jenkins version 1.570, I upgraded the email-ext plugin from version 2.36 to version 2.38.1. Now the build log attachments I get in the email are truncated to only contain the first 1 lines. See the attached logs, one from build running 2.36 and 2.38.1. Environment: CentOS 6.5 server, Jenkins version 1.570 Project: Jenkins Priority: Major Reporter: Jason Stanley This message is automatically generated by JIRA. 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-20708) Upgraded to 1.540, when a new job is created via the CLI using the copy-job command, the Build with Parameters button is not available
Jason Stanley created JENKINS-20708 Upgraded to 1.540, when a new job is created via the CLI using the copy-job command, the Build with Parameters button is not available Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 21/Nov/13 8:28 PM Description: I just upgraded to version 1.540. Linux server. Problem: New jobs do not include the "Build with Parameters" link when created via the CLI. Here is the command I use to create the new job. java -jar jenkins-cli.jar -s http://usmar-jenkins:8081 copy-job BUILD_TEMPLATE NEW_BUILD --username build --password-file /home/build/jenkins/jenkinsPassword.txt If I create the job in the web interface via the copy option, the "Build with Parameters" link exists. If I execute the "Reload Configuration from Disk" the "Build with Parameters" link appears from the job created from the CLI. Environment: Linux CentOS 6.2 Project: Jenkins Priority: Major Reporter: Jason Stanley This message is automatically generated by JIRA. 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/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Jason Stanley commented on JENKINS-15156 Builds disappear from build history after completion I have encountered this same problem. Jenkins 1.499 Server CentOS 6.2 Restarting Jenkins shows missing builds. This message is automatically generated by JIRA. 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/groups/opt_out.
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley commented on JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. In this case, the upstream job was not run on the master but a slave. If you look at the screenshot of the job output, you will see the value of NODE_LABELS is not master, but the name of the slave which the job is running on. All of the other environment variables are correctly passed to the downstream job except this 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
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley updated JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. As you can see, I have $NODE_LABELS as a predefined parameter. Change By: Jason Stanley (06/Nov/12 9:16 PM) Attachment: Upstreamjobpredefinedparameters.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley created JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Issue Type: Bug Assignee: huybrechts Attachments: Upstream job predefined parameters.jpg Components: parameterized-trigger Created: 06/Nov/12 9:14 PM Description: The value of "master" gets passed to the down stream job when you define NODE_LABELS in the Predefined parameters section of an upstream job. See attached screenshot showing the "Predefined parameters section" of the upstream job and the console output of the downstream job. Environment: Jenkins version 1.482 running on CentOS 5.8 Project: Jenkins Priority: Major Reporter: Jason Stanley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley commented on JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Please ignore first screenshot showing Predefined parameters section as the $NL was set incorrectly, it is now just NL=$NODE_LABELS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley updated JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. You can see the value for Node Label is "master". This is incorrect, see next screenshot for environment variable output from upstream build. Change By: Jason Stanley (06/Nov/12 9:24 PM) Attachment: Downstreamprojectconsoleoutput..jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley updated JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Correct NODE_LABEL value from upstream build. Change By: Jason Stanley (06/Nov/12 9:28 PM) Attachment: NODE_LABELvaluefromupstreambuild..jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14336) Too many open files upon HTTP listener init or shutdown
Jason Stanley commented on JENKINS-14336 Too many open files upon HTTP listener init or shutdown Also on 1.482 running on CentOS release 5.8 Oct 22, 2012 12:07:23 PM winstone.Logger logInternal SEVERE: Error during HTTP listener init or shutdown java.net.SocketException: Too many open files at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375) at java.net.ServerSocket.implAccept(ServerSocket.java:470) at java.net.ServerSocket.accept(ServerSocket.java:438) at winstone.HttpListener.run(HttpListener.java:136) at java.lang.Thread.run(Thread.java:679) Oct 22, 2012 12:42:40 PM hudson.model.Run execute This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15130) BuildTrigger ambiguous
Jason Stanley commented on JENKINS-15130 BuildTrigger ambiguous Apparently, I did not upgrade to 2.16 but 2.15. After installing 2.16, the error is gone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15130) BuildTrigger ambiguous
Jason Stanley reopened JENKINS-15130 BuildTrigger ambiguous This problem still persists with the 2.16 plugin version. I am using Jenkins version 1.482. Here is the stack trace: Status Code: 500 Exception: java.lang.IllegalArgumentException: BuildTrigger is ambiguous; matches both hudson.plugins.parameterizedtrigger.BuildTrigger and hudson.tasks.BuildTrigger Stacktrace: javax.servlet.ServletException: java.lang.IllegalArgumentException: BuildTrigger is ambiguous; matches both hudson.plugins.parameterizedtrigger.BuildTrigger and hudson.tasks.BuildTrigger at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] (JENKINS-15130) BuildTrigger ambiguous
Jason Stanley updated JENKINS-15130 BuildTrigger ambiguous Here is a screenshot of what I still see after upgrading to 2.16 version of plugin. Change By: Jason Stanley (11/Oct/12 3:02 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10197) Matrix jobs default to locked (and are difficult to delete)
[
https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159623#comment-159623
]
Jason Stanley commented on JENKINS-10197:
-
This problem also occurs on Jenkins version 1.445.
Matrix jobs default to locked (and are difficult to delete)
-
Key: JENKINS-10197
URL: https://issues.jenkins-ci.org/browse/JENKINS-10197
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: 1.418, 1.434
Reporter: Tom Rini
Assignee: abayer
Priority: Critical
With a matrix job now when it completes it defaults to being a keep forever
type build. Only by deleting the current job can a previous job be deleted,
in some cases.
{noformat}
(09:36:12 AM) Tartarus: kohsuke: With matrix jobs and 1.418 I'm seeing all of
my jobs default to being locked, didn't see this with 1.409, any ideas?
(09:36:32 AM) kohsuke: probably related to the partial rebuild support. Any
ticket for this?
(09:36:54 AM) Tartarus: Hadn't filed one yet
(09:37:18 AM) kohsuke: Would you please? I don't think I can get it right
now, but I don't want to forget
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
