[JIRA] [junit-plugin] (JENKINS-31926) Jenkins doesn't display graph for test suites, before all tests successfully pass
Title: Message Title Nickolay Rumyantsev commented on JENKINS-31926 Re: Jenkins doesn't display graph for test suites, before all tests successfully pass I made some experiments and for me it seems that the trend graph on the main page is not shown when: Last build has a failed test In the build history there is no consequently reachable build result with this test passed. By consequently reachable I mean that every build without Test results (i.e. failed on git checkout) stops the algorithm from traversing deeper. This is actually really annoying, especially for Jenkins Pipeline: In some cases when the build failed early (preparation or compilation phase) I don't want to run unit tests. I configure the script to avoid JUnit publishing in this case this always causes the trend not to be shown. The graph permalink that I embed on my wiki pages becomes unavailable too. My setup: jenkins 1.639 Jenkins Workflow 1.12 JUnit plugin 1.10 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
[JIRA] [junit-plugin] (JENKINS-31926) Jenkins doesn't display graph for test suites, before all tests successfully pass
Title: Message Title Nickolay Rumyantsev updated an issue Jenkins / JENKINS-31926 Jenkins doesn't display graph for test suites, before all tests successfully pass Change By: Nickolay Rumyantsev Priority: Minor Major 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] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Philipp Kyeck commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Having the same problems and can confirm, that it is only when your key is passphrase protected. Without passphrase everything is working as expected. Jenkins v1.625.3, Ubuntu 14.04, java version 1.7.0_91 OpenJDK Runtime Environment 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] [p4-plugin] (JENKINS-31862) "Build Now" should trigger Perforce polling
Title: Message Title Andrew Barnish commented on JENKINS-31862 Re: "Build Now" should trigger Perforce polling As far as we can tell this latest change has fixed the issue. We cannot be 100% sure, because the original problem was intermittent. But I think you can close this ticket. Many thanks 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] [summary_report-plugin] (JENKINS-30146) Plugin is hanging builds when running concurrently
Title: Message Title deruyter resolved as Fixed Fixed in version 1-14 Jenkins / JENKINS-30146 Plugin is hanging builds when running concurrently Change By: deruyter Status: In Progress Resolved Resolution: Fixed 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] [reverse-proxy-auth-plugin] (JENKINS-32663) Jenkins instance is not loading after patch upgrade
Title: Message Title Mariska Tallandtree commented on JENKINS-32663 Re: Jenkins instance is not loading after patch upgrade We have the same problem. Jenkins 1.625.3, apache 2.4. Downgrading to reverse proxy 1.4.0 solved the issue. 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] [summary_report-plugin] (JENKINS-30717) summary report href not working properly when choosing "show on project page"
Title: Message Title deruyter started work on JENKINS-30717 Change By: deruyter Status: Open In Progress 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] [summary_report-plugin] (JENKINS-30717) summary report href not working properly when choosing "show on project page"
Title: Message Title deruyter assigned an issue to deruyter Jenkins / JENKINS-30717 summary report href not working properly when choosing "show on project page" Change By: deruyter Assignee: deruyter 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] [embeddable-build-status-plugin] (JENKINS-32683) build status badge link missing for lhs menu for pipeline multibranch jobs/builds
Title: Message Title Jacob Blain Christen updated an issue Jenkins / JENKINS-32683 build status badge link missing for lhs menu for pipeline multibranch jobs/builds Change By: Jacob Blain Christen Environment: Jenkins: 1.625.3/1.642.1* embeddable-build-status @ 1.8* workflow-multibranch @ 1.13 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] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Dario Griffo commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Florian Doersch Arnt Witteveen I have been running again builds for 4 hours without any disconnection. My "fix": stop using the slave windows service and run this as a scheduled task running a bat file. First I downloaded the slave.jar and slave-agent.jnlp into an empty folder (C:\Jenkins). Created the following .bat in that folder cd C:\Jenkins java -jar slave.jar -jnlpUrl http:/MY_JENKINS_URL/computer/MY_SLAVE_NAME/slave-agent.jnlp -secret MYSECRET That last line is the one in the agent page Create a scheduled task to run at startup with same credentials as the uninstall windows slave service. So far, no disconnections, when I used to have them every 4~5 minutes. 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] [credentials-plugin] (JENKINS-25874) Maven Project plugin to use Credentials plugin
Title: Message Title
Jochen Hinrichsen commented on JENKINS-25874
Re: Maven Project plugin to use Credentials plugin
Give $ {env.PASSWORD}
a try. Note the env qualifier.
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] [build-failure-analyzer-plugin] (JENKINS-32686) Limit Scan by Job Label, Job Type, Name Etc.
Title: Message Title Kenneth Baltrinic created an issue Jenkins / JENKINS-32686 Limit Scan by Job Label, Job Type, Name Etc. Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 29/Jan/16 1:12 PM Priority: Major Reporter: Kenneth Baltrinic We know that certain types of failures are only going to occur on certain kinds of jobs. Especially when a mulit-line can is required, it is ideal if we an limit what jobs are scanned for a particular cause. Obvious ways to limit a job scanning are as follows: By job label. By Name (regex pattern match against name) By job Type (maven, free style, etc.) By what folder or view the job appears in. Some of these ideas are harder to implement than others and probably deserve their own ticket. The first two are easy and likely give the most ROI.
[JIRA] [summary_report-plugin] (JENKINS-19475) Hudson Summary Display Plugin not found by plugin Manager
Title: Message Title deruyter commented on JENKINS-19475 Re: Hudson Summary Display Plugin not found by plugin Manager The best solution is to uninstall the Hudson Summary Display Plugin and install the new one 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] [embeddable-build-status-plugin] (JENKINS-32683) build status badge link missing for lhs menu for pipeline multibranch jobs/builds
Title: Message Title Jacob Blain Christen created an issue Jenkins / JENKINS-32683 build status badge link missing for lhs menu for pipeline multibranch jobs/builds Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: duplicated-menu-items.png, missing-badge-link.png Components: embeddable-build-status-plugin, workflow-plugin Created: 29/Jan/16 10:50 AM Environment: Jenkins: 1.625.3/1.642.1 * embeddable-build-status@1.8 * workflow-multibranch@1.13 Priority: Minor Reporter: Jacob Blain Christen embeddable-build-status seems incompatible with pipeline-multibranch for branch job menus no build status link is rendered missing-badge-link.png for branch build menus the "Polling Log", "Git Build Data", "Tags", "Rebuild", and "Pipeline Steps" links are rendered
[JIRA] [summary_report-plugin] (JENKINS-30072) Summary Display Plugin Content Cut Off By Footer On The Job Page
Title: Message Title deruyter assigned an issue to deruyter This is probably due to the fixed size which is assigned to the display page. I'll try to make it dynamic. Jenkins / JENKINS-30072 Summary Display Plugin Content Cut Off By Footer On The Job Page Change By: deruyter Assignee: deruyter 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] [embeddable-build-status-plugin] (JENKINS-32683) build status badge link missing for lhs menu for pipeline multibranch jobs/builds
Title: Message Title Jacob Blain Christen updated an issue Jenkins / JENKINS-32683 build status badge link missing for lhs menu for pipeline multibranch jobs/builds Change By: Jacob Blain Christen Labels: embeddable-build-status plugin workflow 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] [summary_report-plugin] (JENKINS-30072) Summary Display Plugin Content Cut Off By Footer On The Job Page
Title: Message Title deruyter started work on JENKINS-30072 Change By: deruyter Status: Open In Progress 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] [summary_report-plugin] (JENKINS-30146) Plugin is hanging builds when running concurrently
Title: Message Title deruyter closed an issue as Fixed Fixed in summary_report-1.14 released on 29th of January 2016 Jenkins / JENKINS-30146 Plugin is hanging builds when running concurrently Change By: deruyter Status: Resolved Closed 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] [credentials-binding-plugin] (JENKINS-24805) Mask credentials in Build Log
Title: Message Title Jochen Hinrichsen commented on JENKINS-24805 Re: Mask credentials in Build Log Jesse, i'm looking for just this particular workaround until this issue is resolved. My jobs are not using credentials as parameters, but the credentialsBinding DSL/ "Build environment -> Bindings" setup. My combination of Jenkins Credentials Binding Plugin and Mask Passwords plugin (LTS/ latest/ latest) shows credential passwords. Could you please elaborate on what you did to mask those? Any insights greatly appreciated. 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-32684) Improve test coverage of CLI command 'console'
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-32684 Improve test coverage of CLI command 'console' Issue Type: Improvement Assignee: Pavel Janoušek Components: cli Created: 29/Jan/16 12:56 PM Priority: Major Reporter: Pavel Janoušek Improve test coverage of CLI command console represented by ConsoleCommand class. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-failure-analyzer-plugin] (JENKINS-32685) Faster Mult-Line Scanning
Title: Message Title Kenneth Baltrinic created an issue Jenkins / JENKINS-32685 Faster Mult-Line Scanning Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 29/Jan/16 1:04 PM Priority: Major Reporter: Kenneth Baltrinic Presently multi-line scanning is very processor intensive. I think this is because we are trying to do a single regex using the multi-line modifier across the entire log. Given that log files, unlike human written text only break lines in usually known locations, almost all places where a multi-line scan is needed, we know already where the line breaks will be. Because of this, a different, faster approach may be possible. Instead of using a single multi-line regex, we can scan for multiple single line regexes that are expected to appear in order. So we perform the first single line scan, if we get a hit, starting with that line we continue to scan the file for the next pattern and so on, if we get to the end of the file w/o finding the last pattern, we have no match. Does this make sense? Seems it should be no slower that the current single line scan.
[JIRA] [job-dsl-plugin] (JENKINS-31786) Add support for Confluence Publisher Plugin
Title: Message Title
Marcel Birkner commented on JENKINS-31786
Re: Add support for Confluence Publisher Plugin
Until this has been implemented I created an example Job DSL configure block that you can use as a template: See https://gist.github.com/marcelbirkner/0a4959e74c0c806c00f8
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
/**
* Jenkins Job DSL configure block for Confluence Publisher
* Open Feature Request, see https://issues.jenkins-ci.org/browse/JENKINS-31786
*
* siteName = Link to your Confluence Installation
* spaceName = Confluence Space
* pageName = Confluence Page Name
*
*/
job('confluence-publisher-job') {
configure { project ->
project / publishers << 'com.myyearbook.hudson.plugins.confluence.ConfluencePublisher' {
siteName 'confluence.company.com'
attachArchivedArtifacts 'false'
buildIfUnstable 'false'
spaceName 'TEST'
pageName 'Jenkins Confluence Publisher Integration Test'
editors {
'com.myyearbook.hudson.plugins.confluence.wiki.editors.PrependEditor' {
generator(class: "com.myyearbook.hudson.plugins.confluence.wiki.generators.PlainTextGenerator") {
text 'Jenkins Publisher Job Build Number: $BUILD_NUMBER'
}
}
'com.myyearbook.hudson.plugins.confluence.wiki.editors.AppendEditor' {
generator(class: "com.myyearbook.hudson.plugins.confluence.wiki.generators.PlainTextGenerator") {
text 'Jenkins Publisher Job Build Number: $BUILD_NUMBER'
}
}
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this
[JIRA] [summary_report-plugin] (JENKINS-30146) Plugin is hanging builds when running concurrently
Title: Message Title deruyter assigned an issue to deruyter Jenkins / JENKINS-30146 Plugin is hanging builds when running concurrently Change By: deruyter Assignee: deruyter 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] [summary_report-plugin] (JENKINS-30146) Plugin is hanging builds when running concurrently
Title: Message Title deruyter started work on JENKINS-30146 Change By: deruyter Status: Open In Progress 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] [credentials-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title Doru Cailean commented on JENKINS-24750 Re: Cannot find user credentials when job is triggered with parameters The security constraints do make sense, but I can think of a lot of cases where allowing the user that triggered the job to access its own credentials would be useful. In the case of the Authorize Project Plugin, specifying a user ID also allows one to select a 'No need for re-authentication' option. Their documentation warns about the security threats by saying: This can threaten your Jenkins security. Be careful to use. Do not require authentication in the next configuration if the User ID is not changed. Use this feature carefully, for a malicious user can run unintended commands without authentication by changing configuration of the project. You should also watch CONFIGURE privilege for this project is granted only to proper users. This does not work when configuring via REST/CLI. So, in the flow that we are discussing, by explicitly specifying the user id which has access to the desired credentials AND also checking 'No need for re-authentication' presents another security threat, albeit a different one. However, this is agreed by the administrator or the user configuring the job since he or she actively checks that box. If the malicious user J.Random.User would have permissions to add a job in downstream (even if it were hidden), that means he could also take advantage of the previously described threat. Following the same thought pattern, it would make sense to have a similar logic allowed for the 'Run as the user who triggered the build.' option. Just a thought. 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
[JIRA] [packaging] (JENKINS-32687) Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key.
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-32687 Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key. Change By: James Nord Assignee: Kohsuke Kawaguchi James Nord 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] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title Jesse Glick commented on JENKINS-26522 Re: Annotated block/stage status A related request was for a stage to be marked with a custom icon, to indicate what kind of stage this way, or to add some key/value pairs such as name of environment we deployed to. 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] [packaging] (JENKINS-32687) Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key.
Title: Message Title James Nord created an issue Jenkins / JENKINS-32687 Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key. Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 29/Jan/16 3:42 PM Priority: Major Reporter: James Nord the publish scripts have hard coded KK's sun PGP key. They should use the keys from credentials and not be hard coded so that you can publish packages signed by other people or corporations. Add Comment
[JIRA] [packaging] (JENKINS-32687) Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key.
Title: Message Title James Nord started work on JENKINS-32687 Change By: James Nord Status: Open In Progress 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] [script-security-plugin] (JENKINS-32688) workflow scripts can't use String.replaceFirst( string, string )
Title: Message Title Michael Scharp updated an issue Jenkins / JENKINS-32688 workflow scripts can't use String.replaceFirst( string, string ) Change By: Michael Scharp Priority: Minor Major 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] [script-security-plugin] (JENKINS-32688) workflow scripts can't use String.replaceFirst( string, string )
Title: Message Title
Michael Scharp updated an issue
Jenkins / JENKINS-32688
workflow scripts can't use String.replaceFirst( string, string )
Change By:
Michael Scharp
script-security 1.18{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int replaceFirst java.lang.String java.lang.String }}eg: {{someString. substring replaceFirst ( 10 );}}workaround: {{someString.substring( 10 "a" , someString.length( "b" ) ) ;}} which is slightly annoying and makes the Jenkinsfile more verbose than necessary.Related to: https://issues.jenkins-ci.org/browse/JENKINS-29541
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] [jenkins-tracker] (JENKINS-31647) Options to Ignore changes in Externals, But need externals during checkout.
Title: Message Title Ilayda Akinalan updated an issue Jenkins / JENKINS-31647 Options to Ignore changes in Externals, But need externals during checkout. Change By: Ilayda Akinalan Comment: Hi Daniel,could you take a look at this please?Thanks,Ilayda 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] [script-security-plugin] (JENKINS-32688) workflow scripts can't use String.replaceFirst( string, string )
Title: Message Title Michael Scharp created an issue Jenkins / JENKINS-32688 workflow scripts can't use String.replaceFirst( string, string ) Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 29/Jan/16 4:29 PM Labels: workflow Priority: Minor Reporter: Michael Scharp script-security 1.18 org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int eg: someString.substring( 10 ); workaround: someString.substring( 10, someString.length() ); which is slightly annoying and makes the Jenkinsfile more verbose than necessary. Related to: https://issues.jenkins-ci.org/browse/JENKINS-29541
[JIRA] [pretested-integration-plugin] (JENKINS-32360) Configuration option to mention ready branch name in commit message (our case 14095)
Title: Message Title Lars Kruse updated an issue Jenkins / JENKINS-32360 Configuration option to mention ready branch name in commit message (our case 14095) Change By: Lars Kruse This is a feature.But what's the problem it solves?As a _bla bla ha_ I want to _bla bla bla ha_ so that _bla bla bal_I'm just saying the I's not clear what the problem is: Why should the branch be mentioned in the commit message - it's not (that normal) to put a branch name in a commit message. Personally I never do it - but I rarely (as in "haven't yet") seen any other developers do it either.Let's get a description of the problem we're trying to solve, and then lets see somebody actually watch or vote for this issue, before we hit the keyboard! 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] [build-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Patrice Matignon commented on JENKINS-30426 Re: Allow overwrite of aliases This issue is affecting my set up and I would like to see this fix being released. Anyway I can help ? 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] [build-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Patrice Matignon edited a comment on JENKINS-30426 Re: Allow overwrite of aliases This issue is affecting my set up and I would like to see this fix being released. Anyway Is thee any way that I can help ? 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] [ansicolor-plugin] (JENKINS-24387) Support parsing output of $(tput sgr0)
Title: Message Title Adrian Bridgett commented on JENKINS-24387 Re: Support parsing output of $(tput sgr0) FYI this now appears to be fixed 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] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Vanista Herion commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials The workaround is not quite enough for us; when switching repos for a tag build, the externals are not checked out/updated properly. 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] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Maciej Jaros commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials I think I know a way to reproduce this bug. Repo structure: trunk\i18n\translations.xml trunk\java\somefolder\i18n <- relative external (..\..\i18n) Jobs: I. Update i18n: 1. checkout trunk\i18n\ 2. make some changes to translations.xml 3. svn commit (through shell) II. Build project 1. checkout trunk\java\ (I think actual building is not required) III. Update job (run one-by-one) 1. Run Update i18n job (blocking). 2. Run Build job. This fails every time for me. With Alexander Dvorsky fix it seems to work fine. 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] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Nickolay Rumyantsev commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Might this be connected with JENKINS-31926 ? 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] [pretested-integration-plugin] (JENKINS-31128) Add Matrix Project compatibility (investigate) (our case 13748)
Title: Message Title Lars Kruse closed an issue as Fixed Jenkins / JENKINS-31128 Add Matrix Project compatibility (investigate) (our case 13748) Change By: Lars Kruse Status: Resolved Closed 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] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Francis Upton commented on JENKINS-32690 Re: Cannot manually provision new slave if one already exists Yes, this is a side effect of the change to use previously provisioned stopped instances that are already there, so I would expect this behavior and in fact call it a feature. Can you explain why it's a problem? 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Craig Rodrigues commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin AbstractProject should be replaced by Job in the ghprb plugin for workflow compatibility. See: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md 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] [core] (JENKINS-26466) Split node monitors from core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26466 Re: Split node monitors from core Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/59540fa2a399a431ed6fbaee7072515b763fd632 Log: Merge pull request #1983 from batmat/JENKINS-26466-decouple-AbstractProject-from-DiskSpaceMonitor JENKINS-26466 Decouple AbstractProject from DiskSpaceMonitor Compare: https://github.com/jenkinsci/jenkins/compare/452b6fd740d4...59540fa2a399 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] [core] (JENKINS-26466) Split node monitors from core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26466 Re: Split node monitors from core Code changed in jenkins User: Baptiste Mathus Path: core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/dad9cb6e6defb60bcd714cb5f8e0c7fe2423e1c9 Log: JENKINS-26466 Decouple AbstractProject from DiskSpaceMonitor This modification is one of the preliminary steps to the full plugin extraction later (see JIRA above). Basically reverts a8c3a031c. 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] [build-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Oliver Gondža resolved as Fixed Version 0.4 was released, sorry for the delay. Jenkins / JENKINS-30426 Allow overwrite of aliases Change By: Oliver Gondža Status: Open Resolved Resolution: Fixed 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] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Robert Pilachowski commented on JENKINS-32690 Re: Cannot manually provision new slave if one already exists There are couple of reasons why I would like to be able to create a new slaves when I already a slave, either active or stopped: I have a single active slave and none in the stopped state, but I know that soon there will be a need for several more. And to create an slave from scratch take a significant period of time. I want to start a few new slaves so I am ready for the work. I am making changes to an existing slave definition, and I want to test them out to see if they work, but still leave the existing slaves incase there is a problem with my changes. I could copy the existing definition, but that is not easy the moment. 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] [workflow-plugin] (JENKINS-32691) Hard to find "Click here to forcibly terminate running steps"
Title: Message Title Craig Rodrigues created an issue Jenkins / JENKINS-32691 Hard to find "Click here to forcibly terminate running steps" Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 30/Jan/16 4:46 AM Priority: Minor Reporter: Craig Rodrigues Hi, I recently had a pipeline running, and had to terminate it from the web interface by clicking on the red "X" icon. The build did not terminate. At this point, I had to go to: https://jenkins.freebsd.org/job/FreeBSD_HEAD/75/console then I had to scroll all the way to the bottom, and click on: Click here to forcibly terminate running steps It took me a long time to figure out that this link even existed. Can this link be put in a better place? The current behavior is not intuitive at all from a UI perspective. Add Comment
[JIRA] [core] (JENKINS-26466) Split node monitors from core
Title: Message Title dogfood commented on JENKINS-26466 Re: Split node monitors from core Integrated in jenkins_main_trunk #4434 JENKINS-26466 Decouple AbstractProject from DiskSpaceMonitor (Revision dad9cb6e6defb60bcd714cb5f8e0c7fe2423e1c9) Result = SUCCESS batmat : dad9cb6e6defb60bcd714cb5f8e0c7fe2423e1c9 Files : core/src/main/java/hudson/model/AbstractProject.java 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] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Maciej Jaros edited a comment on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials I think I know a way to reproduce this bug.Repo structure:trunk\i18n\translations.xmltrunk\java\somefolder\i18n <- relative external (..\..\i18n)Jobs:I. Update i18n:1. checkout trunk\i18n\2. make some changes to translations.xml3. svn commit (through shell)II. Build project1. checkout trunk\java\(I think actual building is not required)III. Update job (run one-by-one)1. Run Update i18n job (blocking).2. Run Build job.This fails every time for me when running Build job immediately after Update job . Also note that if no changes are made in Update job then Build job works fine. With Alexander Dvorsky fix it seems to work works fine in both cases . I see no changes in build details and SVN version doesn't include the external, but I don't think it ever did anyway. 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] [packaging] (JENKINS-31074) packaging for mac/unix not tolerant of spaces in cwd.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31074 Re: packaging for mac/unix not tolerant of spaces in cwd. Code changed in jenkins User: James Nord Path: deb/publish/publish.sh rpm/publish/publish.sh suse/publish/publish.sh http://jenkins-ci.org/commit/packaging/209b56507ff9c86212a38706eb259f0c5263a05f Log: Merge pull request #40 from abayer/jenkins-31074-mk2 JENKINS-31074 - more attempts Compare: https://github.com/jenkinsci/packaging/compare/535886b09197...209b56507ff9 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] [sidebar-link-plugin] (JENKINS-32312) Add support for workflow jobs
Title: Message Title steve sides commented on JENKINS-32312 Re: Add support for workflow jobs This would be nice to have back. 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] [sidebar-link-plugin] (JENKINS-32312) Add support for workflow jobs
Title: Message Title steve sides edited a comment on JENKINS-32312 Re: Add support for workflow jobs +1 This would be nice to have back. 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] [packaging] (JENKINS-31074) packaging for mac/unix not tolerant of spaces in cwd.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31074 Re: packaging for mac/unix not tolerant of spaces in cwd. Code changed in jenkins User: Andrew Bayer Path: deb/publish/publish.sh rpm/publish/publish.sh suse/publish/publish.sh http://jenkins-ci.org/commit/packaging/79ac89ec7a73e0a07cf285ded82af12ca1dffa33 Log: JENKINS-31074 Tweaks to quoting/string contents. 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] [packaging] (JENKINS-32516) branding.py will error on any variable set to ""
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-32516 branding.py will error on any variable set to "" Change By: James Nord Status: Resolved Closed 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] [core] (JENKINS-32689) Load statistics graph don't show the correct number of executors
Title: Message Title Roland Asmann created an issue Jenkins / JENKINS-32689 Load statistics graph don't show the correct number of executors Issue Type: Bug Assignee: Unassigned Attachments: Jenkins Load 1.png, Jenkins Load 2.png Components: core Created: 29/Jan/16 7:51 PM Environment: Master: Ubuntu14 Slaves: Ubuntu12 / Windows Priority: Minor Reporter: Roland Asmann I just set up a new Jenkins and was checking out how the load was during our nightly builds, when I noticed that the graph is missing 2 executors. Playing with shutting down the slaves it appears to be the executors on the master that are not included in the graph. I am showing the graph for the whole installation, not for any specific node. I must say that checking the graph for the master only actually does show 2 executors! Please check the attached screenshots. On the screenshot with the running project, you can actually see the graph is going down – this
[JIRA] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting
Title: Message Title Martin Weber assigned an issue to Martin Weber Jenkins / JENKINS-32657 cmakebuilder should allow cmake scripting Change By: Martin Weber Assignee: Martin Weber 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] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Robert Pilachowski created an issue Jenkins / JENKINS-32690 Cannot manually provision new slave if one already exists Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 29/Jan/16 8:37 PM Environment: Jenkins: 1.634 ec2-plugin: 1.31 Priority: Minor Reporter: Robert Pilachowski In version 1.29, I could manually provision a new slave if I was below the instance cap by clicking the button on the Manage Nodes page. In version 1.31, clicking the button takes me to the status page of an existing ec2 slave node. Add Comment
[JIRA] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number
Title: Message Title Alexander Komarov commented on JENKINS-27958 Re: Cannot reset the next build number Maninder Singh, is this still an issue? If so, can you provide detailed steps to reproduce? 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] [next-build-number-plugin] (JENKINS-27185) nextbuildnumber plugin should allow alpha-numberic values
Title: Message Title Alexander Komarov closed an issue as Won't Fix The NextBuildNumber plugin sets the jenkins internal next build number value. This number is numeric by design. Jenkins / JENKINS-27185 nextbuildnumber plugin should allow alpha-numberic values Change By: Alexander Komarov Status: Open Closed Assignee: Dean Yu Alexander Komarov Resolution: Won't Fix 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
[JIRA] [packaging] (JENKINS-32687) Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32687 Re: Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key. Code changed in jenkins User: James Nord Path: bin/branding.list branding/jenkins.mk branding/test.mk credentials/README.md credentials/test.ascii.key credentials/test.mk deb/publish/contents/jenkins-ci.org.key deb/publish/gen.rb deb/publish/publish.sh rpm/publish/gen.rb rpm/publish/jenkins-ci.org.key rpm/publish/publish.sh suse/publish/jenkins-ci.org.key suse/publish/publish.sh test/provision/deb.sh test/provision/rpm.sh http://jenkins-ci.org/commit/packaging/d12c7e152707af955dd2ae29052010602ee31b13 Log: JENKINS-32687 Use a configurable publiv key for repos. THis introduceds a new branding variable "ORGANIZATION" that will be used to compute the name of the key. The key used will be taken from the "GPG_PUBLIC_KEY" variable which needs to be configured in the credentials make file. 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] [packaging] (JENKINS-32687) Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32687 Re: Packaging allows the use of other pgp keys for signing but publishing hard codes KK's sun key. Code changed in jenkins User: James Nord Path: bin/branding.list branding/jenkins.mk branding/test.mk credentials/README.md credentials/test.ascii.key credentials/test.mk deb/publish/contents/jenkins-ci.org.key deb/publish/gen.rb deb/publish/publish.sh rpm/publish/gen.rb rpm/publish/jenkins-ci.org.key rpm/publish/publish.sh suse/publish/jenkins-ci.org.key suse/publish/publish.sh test/provision/deb.sh test/provision/rpm.sh http://jenkins-ci.org/commit/packaging/002489ba96977cb5f531d4e1d711c1219abbc7f5 Log: Merge pull request #42 from jtnord/configurableKey JENKINS-32687 Use a configurable public key for repos. Compare: https://github.com/jenkinsci/packaging/compare/209b56507ff9...002489ba9697 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] [ansicolor-plugin] (JENKINS-31029) no known implementation of class jenkins.tasks.SimpleBuildWrapper
Title: Message Title davidkarlsen assigned an issue to Daniel Doubrovkine Jenkins / JENKINS-31029 no known implementation of class jenkins.tasks.SimpleBuildWrapper Change By: davidkarlsen Assignee: davidkarlsen Daniel Doubrovkine 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.
