[JIRA] [core] (JENKINS-35206) NullPointerException on startup after update from 2.5 to 2.6
Title: Message Title
Axel Behrens commented on JENKINS-35206
Re: NullPointerException on startup after update from 2.5 to 2.6
Keith Zantow, this is only a test instance running on my laptop (Windows 7 x64). I've installed v2.0 from scratch, added a handful of plugins and created some jobs. I automatically updated pretty much to every new release until 2.6.
This is my config.xml if that helps:
jenkins.diagnostics.SecurityIsOffMonitor
1.0
RESTART
2
NORMAL
true
false
${ITEM_ROOTDIR}/workspace
${ITEM_ROOTDIR}/builds
0
All
false
false
All
0
Cheers
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] [testng-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed
Title: Message Title pavan pothnis closed an issue as Not A Defect Trying to solve this issue with JENKINS-35254. Thanks Tom. Jenkins / JENKINS-35169 Jenkins "Job status" shows success even if it has many / all test cases failed Change By: pavan pothnis Status: Open Closed Resolution: Not A Defect 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] [git-plugin] (JENKINS-35248) Additional Behaviours not saved when Jenkins updated
Title: Message Title Mark Waite resolved as Duplicate JENKINS-33695 and JENKINS-33564 both are duplicates of this bug Jenkins / JENKINS-35248 Additional Behaviours not saved when Jenkins updated Change By: Mark Waite Status: Open Resolved Resolution: Duplicate 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] [testng-plugin] (JENKINS-35254) Thresholds to mark build unstable
Title: Message Title pavan pothnis created an issue Jenkins / JENKINS-35254 Thresholds to mark build unstable Issue Type: Improvement Assignee: Nalin Makar Attachments: TestNGConfigaration.PNG Components: testng-plugin Created: 2016/Jun/01 5:04 AM Environment: Windows 7 , Jenkins version 2.6 Labels: configuration plugin jenkins Priority: Critical Reporter: pavan pothnis Hi All, I am using TestNg plugin to for Publishing the Results in post Build Actions and having hard time configuring Thresholds for marking Build Unstable / failed. Reason is pretty simple so as solution should be, As of now I can either set threshold mode 1.Number of Tests
[JIRA] [git-plugin] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Mark Waite commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. There is an article on stackoverflow.com which seems to indicate this is a known limitation of either pipeline or the git plugin. Sorry, but I'm not sure which is expected to provide that. 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-35253) Whitelist Groovy capitalize method from String for sandbox
Title: Message Title Greg Pagendam-Turner updated an issue Jenkins / JENKINS-35253 Whitelist Groovy capitalize method from String for sandbox Change By: Greg Pagendam-Turner Component/s: script-security-plugin Component/s: groovy-plugin 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] [groovy-plugin] (JENKINS-35253) Whitelist Groovy capitalize method from String for sandbox
Title: Message Title
Greg Pagendam-Turner created an issue
Jenkins / JENKINS-35253
Whitelist Groovy capitalize method from String for sandbox
Issue Type:
Improvement
Assignee:
vjuranek
Components:
groovy-plugin
Created:
2016/Jun/01 4:35 AM
Priority:
Minor
Reporter:
Greg Pagendam-Turner
I get the following error when trying to pipeline build:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods capitalize java.lang.String
It's triggered by the code in my pipeline definition:
def branchToBuild = "$ {env.JOB_NAME}
".tokenize('-').last() def dockerTaskBranch = branchToBuild.capitalize()
The capitalize method should be safe enough to call from the sandbox
Add Comment
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33498) Improve full screen view of pipeline stage view
Title: Message Title Sam Van Oort resolved as Done This was released with v1.4 - discussion of a full layout redesign to do dynamic sizing of columns is moving to separate JIRA to facilitate tracking. Jenkins / JENKINS-33498 Improve full screen view of pipeline stage view Change By: Sam Van Oort Status: In Progress Resolved Resolution: Done 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] [pipeline-stage-view-plugin] (JENKINS-33498) Improve full screen view of pipeline stage view
Title: Message Title Sam Van Oort commented on JENKINS-33498 Re: Improve full screen view of pipeline stage view John Ament and Ken Lamb I agree that it would have value to support dynamic column widths, however I think due to the complexity of the layout change that's probably out of scope for the original JIRA. I've created JENKINS-35252 for layout redesigns as a separate RFE - let's move discussion there. 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] [pipeline-stage-view-plugin] (JENKINS-35252) Allow full screen mode to dynamically grow and shrink stage cell width
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-35252 Allow full screen mode to dynamically grow and shrink stage cell width Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Jun/01 4:20 AM Labels: ux Priority: Minor Reporter: Sam Van Oort Offshoot of JENKINS-33498: taking things a step further, it would be good to use dynamic column width for stage cells, permitting them to grow if screen width is available to better accomodate content. As starting points: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/ui/src/main/js/view/templates/pipeline-staged.less#L239 This sets the width of table cells (even if max-width is set, they don't grow). This sets the overall width of the table cells in view, as does the line below it: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/ui/src/main/js/view/templates/pipeline-staged.hbs#L4 Which is unfortunately hardcoded in JS to give 10em to each stage: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/ui/src/main/js/view/pipeline-staged.js#L60
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Ben Hines great. Yes the aim is to have a regular UC release - it could be the experimental update center at first. The problem with downloads is the installation of transitive dependencies. There is also jenkinsci/blueocean on docker hub as a docker image to try (nightly- ish). 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] [git-plugin] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title
feng yu edited a comment on JENKINS-35230
Re: The environment variables of git plugin not working in pipeline script.
Thank you. I've tried your solutions, but all of them still not working.I can use the "GIT_*" variables in the free style jobs. such as :{code}branch to be published: ${GIT_BRANCH}rev: ${GIT_COMMIT}commit user: ${GIT_AUTHOR_NAME}<${GIT_AUTHOR_EMAIL}>changelog:${CHANGES, showPaths=true} {code}But all the variables above cannot use be used in pipeline script.
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] [git-plugin] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title
feng yu commented on JENKINS-35230
Re: The environment variables of git plugin not working in pipeline script.
Thank you. I've tried your solutions, but all of them still not working.
I can use the "GIT_*" variables in the free style jobs. such as :
branch to be published: ${GIT_BRANCH}
rev: ${GIT_COMMIT}
commit user: ${GIT_AUTHOR_NAME}<${GIT_AUTHOR_EMAIL}>
changelog:
${CHANGES, showPaths=true}
But all the variables above cannot use in pipeline script.
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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines closed an issue as Not A Defect Jenkins / JENKINS-35195 Unable to run Blue Ocean within tomcat Change By: Ben Hines Status: Resolved Closed Assignee: Tom FENNELLY Ben Hines 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Thanks , Adrian. Got it working! It seems maven not creating a blueocean-plugin.jpi for me, but this was because i had a couple failing tests. After fixing the tests and a minor build issue with my environment, it packaged installed the blueocean.hpi and put it in the local mvn repo. Indeed it would be nice if there were a nightly binary build set up somewhere (preferably to an update center, but raw downloads would be fine too) that we could test with, but i'd also like to get it building and deployed into a separate Jenkins instance so we can potentially contribute. I'll close this 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines resolved as Not A Defect Jenkins / JENKINS-35195 Unable to run Blue Ocean within tomcat Change By: Ben Hines Status: Open Resolved Resolution: Not A Defect 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-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name
Title: Message Title Devesh Kumar commented on JENKINS-34512 Re: error in build-name-setter plugin - Set build name Yes the build fails and it happens with all my jobs which uses this plugin version. I was able to get a successful build after reverting to the mentioned version. 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] [blueocean-plugin] (JENKINS-35236) Pagination for Summary tabs
Title: Message Title Michael Neale assigned an issue to Paul Dragoonis Jenkins / JENKINS-35236 Pagination for Summary tabs Change By: Michael Neale Assignee: Paul Dragoonis 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] [blueocean-plugin] (JENKINS-35236) Pagination for Summary tabs
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-35236 Pagination for Summary tabs Change By: Michael Neale Assignee: Michael Neale 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title
Luigi Tagliamonte edited a comment on JENKINS-35242
Re: Upgraded to new AWS-SDK plugin, jenkins would not start.
got the same issue, I solved manually installing the prev version:go in JENKINS_HOME/plugins and performing the following commands:{code}mv aws-java-sdk aws-java-sdk.oldmv aws-java-sdk.bak aws-java-sdk.bak.oldmv aws-java-sdk.jpi aws-java-sdk.jpi.oldwget http://updates.jenkins-ci.org/download/plugins/aws-java-sdk/1.10.45/aws-java-sdk.hpichown jenkins:jenkins aws-java-sdk.hpichmod 775 aws-java-sdk.hpiservice restart jenkins{code}
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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Luigi Tagliamonte commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. got the same issue, I solved manually installing the prev version: go in JENKINS_HOME/plugins and performing the following commands: mv aws-java-sdk aws-java-sdk.old mv aws-java-sdk.bak aws-java-sdk.bak.old mv aws-java-sdk.jpi aws-java-sdk.jpi.old wget http://updates.jenkins-ci.org/download/plugins/aws-java-sdk/1.10.45/aws-java-sdk.hpi chown jenkins:jenkins aws-java-sdk.hpi chmod 775 aws-java-sdk.hpi service restart jenkins 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] [durable-task-plugin] (JENKINS-27617) Isolate durable task in a dedicated process group
Title: Message Title Jesse Glick commented on JENKINS-27617 Re: Isolate durable task in a dedicated process group By depending on net.java.dev.jna:jna-platform:4.1.0 we could call Kernel32.INSTANCE.CreateProcess with WinBase.CREATE_NEW_PROCESS_GROUP. Would it 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] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-35251 Provide different strategies for repositories and branches / pull request Change By: Allan BURDAJEWICZ Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/ branchs branches /pr are never discarded.Discussed solutions would be to either:* Add the option to Delete items regardless of the Discard Policy* Adapt/re-think the Orphaned Item Strategy* Add the option to Delete items* Provide another Strategy 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke edited a comment on JENKINS-33952 Re: "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Neven,Definitely agree that it looks like something is wonky. Can you throw the "Test Statistics Grid" up on your dashboard, and show me the result of that? It shows all the individual jobs being tallied up, and that might help diagnose the issue. I don't see anywhere in the code where there should be an issue specific to never-passed jobs, so I'd like to try and get more data. UPDATE: I went through your latest screenshot, and it doesn't look like the "successful" tests for those two jobs are being included in the chart either.Is there anything special about those jobs? What plugin is publishing those test results? 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] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-35251 Provide different strategies for repositories and branches / pull request Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Jun/01 1:19 AM Priority: Major Reporter: Allan BURDAJEWICZ Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/branchs/pr are never discarded. Discussed solutions would be to either: Adapt/re-think the Orphaned Item Strategy Add the option to Delete items Provide another Strategy
[JIRA] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke commented on JENKINS-33952 Re: "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Curtis, Regarding the Grid, what type of tests are being published? I fixed an issue with the TAP plugin where it wasn't publishing its results in a way that the grid liked. I'd recommend opening a separate defect report for that one, tied to whatever test tool is trying to publish results. You can reference https://issues.jenkins-ci.org/browse/JENKINS-22016 which was the fix for the TAP plugin. 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke commented on JENKINS-33952 Re: "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Neven, Definitely agree that it looks like something is wonky. Can you throw the "Test Statistics Grid" up on your dashboard, and show me the result of that? It shows all the individual jobs being tallied up, and that might help diagnose the issue. I don't see anywhere in the code where there should be an issue specific to never-passed jobs, so I'd like to try and get more data. 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] [jobconfighistory-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Bing Shiao commented on JENKINS-33111 Re: jobconfighistory-plugin does not track credential.xml changes Jochen A. Fürbacher, the content of credentials.xml is cryptic to some extend; being able to see which credential item was changed (add/delete/update) in the JobConfigHistory page is good enough for me. Thanks a lot. 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] [git-plugin] (JENKINS-35248) Additional Behaviours not saved when Jenkins updated
Title: Message Title Beau Henderson commented on JENKINS-35248 Re: Additional Behaviours not saved when Jenkins updated The downgrade button is offering 2.4.3 so that looks like the culprit. We've hit on this issue previously when updating / restarting jenkins so I'm guessing we've had 2.4.3 for some time and only just bumped up to 2.4.4. AFAIK checkout to sub directory and possibly git sub-module behaviour was impacted. I don't know if we're using anything else. 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] [git-plugin] (JENKINS-35248) Additional Behaviours not saved when Jenkins updated
Title: Message Title Mark Waite commented on JENKINS-35248 Re: Additional Behaviours not saved when Jenkins updated The 2.4.3 version of the plugin was only available for about 7 days (19 Mar 2016 - 24 Mar 2016) before it was superseded by the 2.4.4 version. I would be surprised if you were running 2.4.3, since it was replaced over two months ago by 2.4.4. You should be able to see check enough of the plugin installation history from your "Manage Plugins" section called "Installed Plugins". If git plugin 2.4.3 was on your system prior to 2.4.4, it will be listed with a large button "Downgrade to 2.4.3" on the line for the git plugin. If the version number in the "Downgrade to " button is not 2.4.3 (possibly 2.4.2 or 2.4.1 or 2.4.0), then you probably never had 2.4.3 on your Jenkins server. If you never had 2.4.3 on your machine, then I don't have any good suggestions for the cause of the problem you're seeing. Are there specific additional behaviors which are not preserved, or is it all additional behaviors that are not preserved? 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] [git-plugin] (JENKINS-35248) Additional Behaviours not saved when Jenkins updated
Title: Message Title Beau Henderson commented on JENKINS-35248 Re: Additional Behaviours not saved when Jenkins updated We're on 2.4.4 at present. It looks like the git module was updated along with jenkins so I'm assuming this was a result of the 2.4.3 bug then ? 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] [role-strategy-plugin] (JENKINS-35250) Help text for slave roles mentions project names
Title: Message Title Phillip Kuhrt created an issue Jenkins / JENKINS-35250 Help text for slave roles mentions project names Issue Type: Bug Assignee: Oleg Nenashev Attachments: 2016-06-01 01_16_30-Jenkins.png Components: role-strategy-plugin Created: 2016/May/31 11:22 PM Environment: Jenkins 2.6, Plugin 2.2.0 Priority: Trivial Reporter: Phillip Kuhrt Was probably introduced in JENKINS-18748 : The help box for slave roles under http://jenkins.example.com:8080/role-strategy/manage-roles shows "The pattern is used to match project names. This means that the permissions you are assigning to this role will only be valid for project having a name matching this pattern."; I suppose the text should reference "slave names" / "node names"?
[JIRA] [workflow-plugin] (JENKINS-35245) Pipeline SCM Step Plugin does not use the same git commit for the pipeline
Title: Message Title Sebastien Vas updated an issue Jenkins / JENKINS-35245 Pipeline SCM Step Plugin does not use the same git commit for the pipeline Change By: Sebastien Vas Component/s: workflow-plugin Component/s: pipeline-utility-steps-plugin 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] [docker-build-publish-plugin] (JENKINS-35000) Docker build on linux slave fails due to '\' backslash
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35000 Re: Docker build on linux slave fails due to '\' backslash Code changed in jenkins User: Mark Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java http://jenkins-ci.org/commit/docker-build-publish-plugin/46d450db5a3e057f26f580a4a311764ea1efcff4 Log: JENKINS-35000 Incorrect file backslash when slave is linux (#42) Incorrect file backslash when slave is linux and master is windows 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] [docker-build-publish-plugin] (JENKINS-35000) Docker build on linux slave fails due to '\' backslash
Title: Message Title Carlos Sanchez closed an issue as Fixed Merged, thanks Jenkins / JENKINS-35000 Docker build on linux slave fails due to '\' backslash Change By: Carlos Sanchez Status: Open Closed 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] [active-directory-plugin] (JENKINS-35249) Security update 1.651.2 breaks LDAP/AD look up
Title: Message Title Roberto Sanchez created an issue Jenkins / JENKINS-35249 Security update 1.651.2 breaks LDAP/AD look up Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin, ldap-plugin Created: 2016/May/31 10:51 PM Environment: Debian Wheezy 7.10, OpenJDK 7u101, AD Plugin 1.46, LDAP Plugin 1.12 Priority: Blocker Reporter: Roberto Sanchez After I updated to 1.651.2 I started seeing failures that appear similar to those in JENKINS-34775 . Reverting to earlier versions of the AD and LDAP plugins doesn't resolve the issue. Only reverting to 1.651.1 got things working again. I initially added my stack trace as a comment to JENKINS-34775 , but I was told there that this was a different issue and to create a new issue. BUILD SUCCESSFUL Total time: 5 minutes 23 seconds Sending e-mails to: b...@example.com t...@example.com FATAL: Failed to retrieve user information for Bill S. Preston; nested exception is javax.naming.NamingException:
[JIRA] [workflow-plugin] (JENKINS-28673) ISE from BuildTriggerListener.onDeleted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28673 Re: ISE from BuildTriggerListener.onDeleted Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerListener.java src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepRestartTest.java src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepTest.java http://jenkins-ci.org/commit/pipeline-build-step-plugin/c869245bed52a6b0b9c35e9a38f4c6d3f843a1ff Log: [FIXED JENKINS-28673] ISE after deleting a downstream build. 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-28673) ISE from BuildTriggerListener.onDeleted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28673 Re: ISE from BuildTriggerListener.onDeleted Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerListener.java src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepRestartTest.java src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepTest.java http://jenkins-ci.org/commit/pipeline-build-step-plugin/3e7943a4afc873b1355eb9f406e82ad0e05dea24 Log: Merge pull request #2 from jglick/ISE-< /a> JENKINS-28673 JENKINS-28673 ISE after deleting a downstream build Compare: https://github.com/jenkinsci/pipeline-build-step-plugin/compare/a850c28adbe2...3e7943a4afc8 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-28673) ISE from BuildTriggerListener.onDeleted
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28673 ISE from BuildTriggerListener.onDeleted Change By: SCM/JIRA link daemon 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] [git-plugin] (JENKINS-35248) Additional Behaviours not saved when Jenkins updated
Title: Message Title Mark Waite commented on JENKINS-35248 Re: Additional Behaviours not saved when Jenkins updated That is quite surprising. What version of the git plugin are you using? There was a known problem in git plugin 2.4.3 (fixed in 2.4.4) which caused it to fail to preserve the configuration across saves (and Jenkins server restarts). It might have also shown as a failure to save configuration across upgrade. See JENKINS-33695 and JENKINS-33564 for the descriptions of that bug. 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop edited a comment on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. Hmmm... how did you roll back? I just manually installed version 1.10.42 from [here|http://updates.jenkins-ci.org/download/plugins/aws-java-sdk/] and it just destroyed my aws configuration! Now nothing will build. Any ideas? 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop updated an issue Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would not start. Change By: jake bishop Priority: Major Critical 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. Hmmm... how did you roll back? I just manually installed version 1.10.42 from here and it just destroyed my aws configuration! Any ideas? 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Joe Arasin commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. jake bishop I was able to rollback to the previous version of the aws sdk plugin, and then I was able to get things rolling again. It'd probably be useful to get your setup and try to figure out what the common element is in our stacks. 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] [git-plugin] (JENKINS-35248) Additional Behaviours not saved when Jenkins updated
Title: Message Title Beau Henderson created an issue Jenkins / JENKINS-35248 Additional Behaviours not saved when Jenkins updated Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/May/31 10:28 PM Environment: Version 2.7 Labels: plugin jenkins git-plugin Priority: Minor Reporter: Beau Henderson When Jenkins is updated we seem to be loosing any additional behaviours that were configured within the git plugin component of our jobs. These need to be manually reconfigured.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. We have this issue too, any workarounds? 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] [git-plugin] (JENKINS-35247) Move git/svn steps out of workflow-scm-steps
Title: Message Title Jesse Glick started work on JENKINS-35247 Change By: Jesse Glick 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] [git-plugin] (JENKINS-35247) Move git/svn steps out of workflow-scm-steps
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-35247 Move git/svn steps out of workflow-scm-steps Issue Type: Bug Assignee: Jesse Glick Components: git-plugin, subversion-plugin, workflow-plugin Created: 2016/May/31 10:06 PM Priority: Major Reporter: Jesse Glick Arnaud Héritier pointed out that when installing recommended plugins in Jenkins 2, sometimes the git step does not work in Pipeline builds until after a restart. This is because when workflow-scm-step is loaded, git might not yet be installed, so GitStep.DescriptorImpl would be skipped. If later in the same session git is installed, this extension is not revisited. Simpler to keep the SCM-specific steps in the corresponding plugins. Add Comment
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-script.html src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/block.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/help.html src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/help.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/html.groovy src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/index.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/sidepanel.jelly src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/272fc16d274522efb08371cc9c7c0f8a1305305d Log: Merge branch 'master' into JENKINS-34064 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.
[JIRA] [core] (JENKINS-19508) Replace @Extension(optional=true) and optional dependencies with bridge plugins
Title: Message Title Jesse Glick commented on JENKINS-19508 Re: Replace @Extension(optional=true) and optional dependencies with bridge plugins Another problem is that an optional extension which is initially broken due to a missing optional dependency does not get added when that dependency is installed—you have to restart Jenkins. 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] [htmlpublisher-plugin] (JENKINS-32026) HTML publisher 1.9 broken since Jenkins 1.625.3
Title: Message Title Daniel Beck resolved as Fixed This issue has been resolved. HTML Publisher itself failed to show the iframe at all, which this issue is about. What's left is covered by https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy Jenkins / JENKINS-32026 HTML publisher 1.9 broken since Jenkins 1.625.3 Change By: Daniel Beck Status: Reopened 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] [git-plugin] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jan Prach commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields This has quadratic memory complexity for modern workflows! Nicolas De Loof any progress fixing this upstream? Can I help? Thank you for the workaround Scott Hebert! This is very bad. It renders jenkins unusable. In our case jenkins lazy.BuildReference took 95% heap. But actually 91% heap is the git.util.BuildData. Those builds are by default hold as soft references. It sounds good. Problem is once those deserialized build.xml files take more than a heap it will deserialize gigabytes of data on every job view. It will not OOM because it is freeing those softreferences within a single request. But it can be extremely slow. It can read GB of data on every request. It is not ok. It cause timeouts and get progressively worse with every branch and/or every record in job history. I would be surprised if some (many) people would not leave jenkins for this issue. It is not easy to say for most people why page load takes 20 seconds or more. 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-34887) PingFailureAnalyzer NPE
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-34887 PingFailureAnalyzer NPE Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-7443) Feature to delete the user setting of trend graph preserved in the cookie.
Title: Message Title Ulli Hafner resolved as Won't Fix You can remove cookies in your browser. Jenkins / JENKINS-7443 Feature to delete the user setting of trend graph preserved in the cookie. Change By: Ulli Hafner Status: Open Resolved 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 options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-9284) Compiler Warning Plugin - Ignore Warnings by type in place of or addition to by file regex
Title: Message Title Ulli Hafner resolved as Fixed Filtering by message is implemented already. Jenkins / JENKINS-9284 Compiler Warning Plugin - Ignore Warnings by type in place of or addition to by file regex Change By: Ulli Hafner 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] [analysis-core-plugin] (JENKINS-10596) Improve handling of source code files with duplicate relative path names
Title: Message Title Ulli Hafner resolved as Fixed See JENKINS-32150 . Jenkins / JENKINS-10596 Improve handling of source code files with duplicate relative path names Change By: Ulli Hafner Status: Reopened 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] [checkstyle-plugin] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Title: Message Title Ulli Hafner resolved as Won't Fix I think maven 2 should not be supported anymore. Jenkins / JENKINS-15490 Analysis parsers don't work with maven 2 jobs Change By: Ulli Hafner Status: Open Resolved 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 options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33237) Failure to check out commit from a closed & reopened PR
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-33237 Failure to check out commit from a closed & reopened PR Change By: Patrick Wolf Labels: 2.0 Followup 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] [findbugs-plugin] (JENKINS-12330) Occasionally,collecting findbugs analysis files will take very long time, event two more hours.
Title: Message Title Ulli Hafner resolved as Cannot Reproduce Jenkins / JENKINS-12330 Occasionally,collecting findbugs analysis files will take very long time, event two more hours. Change By: Ulli Hafner Status: Reopened Resolved Resolution: Cannot 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] [warnings-plugin] (JENKINS-15801) Allow root of relative paths to be specified
Title: Message Title Ulli Hafner resolved as Fixed Hopefully the fix for JENKINS-32150 is useful here, too. Jenkins / JENKINS-15801 Allow root of relative paths to be specified Change By: Ulli Hafner 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] [analysis-core-plugin] (JENKINS-17062) TrendGraph Returns 500 NoClassDefFoundError org/joda/time/LocalDate
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-17062 TrendGraph Returns 500 NoClassDefFoundError org/joda/time/LocalDate Change By: SCM/JIRA link daemon 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] [analysis-core-plugin] (JENKINS-17062) TrendGraph Returns 500 NoClassDefFoundError org/joda/time/LocalDate
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17062 Re: TrendGraph Returns 500 NoClassDefFoundError org/joda/time/LocalDate Code changed in jenkins User: Ulli Hafner Path: pom.xml http://jenkins-ci.org/commit/analysis-core-plugin/fc27890b7d3a5ab8bb1a282514f11022313e8a20 Log: [FIXED JENKINS-17062] Added transitive dependency of optional plugin. 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] [checkstyle-plugin] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Title: Message Title Ulli Hafner resolved as Fixed SAX property is not overwritten anymore by the plugin. Jenkins / JENKINS-19932 Publish FindBugs/Checkstyle from slave failed Change By: Ulli Hafner Status: Reopened 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] [checkstyle-plugin] (JENKINS-24942) Trend graphs are not shown for some projects
Title: Message Title Ulli Hafner resolved as Cannot Reproduce Jenkins / JENKINS-24942 Trend graphs are not shown for some projects Change By: Ulli Hafner Status: Open Resolved Resolution: Cannot 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] [analysis-core-plugin] (JENKINS-25905) Parameterized view on Warnings trend
Title: Message Title Ulli Hafner resolved as Incomplete Jenkins / JENKINS-25905 Parameterized view on Warnings trend Change By: Ulli Hafner Status: Open Resolved Resolution: Incomplete 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] [warnings-plugin] (JENKINS-29203) StyleCop warnings are counted twice
Title: Message Title Ulli Hafner resolved as Won't Fix You can exclude certain warnings by a regexp (based on the message). Jenkins / JENKINS-29203 StyleCop warnings are counted twice Change By: Ulli Hafner Status: Open Resolved 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 options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-29871) NullPointerException after parsing error file
Title: Message Title Ulli Hafner resolved as Cannot Reproduce I can't reproduce this. If this is a bug then it is located in core. Jenkins / JENKINS-29871 NullPointerException after parsing error file Change By: Ulli Hafner Status: Open Resolved Resolution: Cannot 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] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32150 Re: Cannot resolve relative filenames referencing parent directory Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/ParserResult.java src/test/java/hudson/plugins/analysis/core/ParserResultTest.java http://jenkins-ci.org/commit/analysis-core-plugin/cfdaa8f4b476425d505150999af4d4c34231b302 Log: [FIXED JENKINS-32150] Remove whole path before ../ 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] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32150 Cannot resolve relative filenames referencing parent directory Change By: SCM/JIRA link daemon Status: Reopened 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] [htmlpublisher-plugin] (JENKINS-32026) HTML publisher 1.9 broken since Jenkins 1.625.3
Title: Message Title Andru Cherny reopened an issue My Jenkins ver. 1.651.2 and HTML Publisher plugin - 1.11 Bug exsist. Jenkins / JENKINS-32026 HTML publisher 1.9 broken since Jenkins 1.625.3 Change By: Andru Cherny Resolution: Fixed Status: Resolved Reopened 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] [kubernetes-plugin] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-35246 Kubernetes nodes not getting deleted when a pipeline job fails Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/May/31 8:50 PM Priority: Minor Reporter: Alvaro Lobato When you run a failing pipeline job the kubernetes node responsible for doing the job does not get properly deleted and after a while appears as suspended. These are the logs when the node ab1c5bc857e82 was being deleted and it didn't: May 18, 2016 4:18:41 PM FINER hudson.slaves.NodeProvisioner$2 run Queue length 0 is less than the available capacity 0. No provisioning strategy required May 18, 2016 4:18:41 PM FINER hudson.slaves.NodeProvisioner$2 run Queue length 0 is less than the available capacity 0. No provisioning strategy required May 18, 2016 4:18:41 PM FINER hudson.slaves.NodeProvisioner$2 run Queue length 0 is less than the available capacity 0. No provisioning strategy required May 18, 2016 4:18:41 PM FINER hudson.slaves.NodeProvisioner$2 run Queue length 0 is less than the available capacity 0. No provisioning strategy required May 18, 2016 4:18:41 PM FINER hudson.slaves.NodeProvisioner$2 run Queue length 0 is less than the available capacity 0. No provisioning strategy required May 18, 2016 4:18:41 PM FINER hudson.slaves.NodeProvisioner$2 run Queue length 0 is less than the available capacity 0. No provisioning strategy required May 18, 2016 4:18:48 PM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate
[JIRA] [workflow-plugin] (JENKINS-26055) DurableTaskStep
Title: Message Title Jimmy Ray commented on JENKINS-26055 Re: DurableTaskStep So, I have a similar need here. I wrote and published the Consul KV Builder Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Consul-KV-Builder+Plugin) that allows jobs to be configured to Read/Write/Delete Key/Value data from/to Hashicorp Consul servers. In the READ mode, the configured build step reads data from Consul and writes ENV variables. So, that currently cannot work with SimpleBuildStep. I am looking into alternatives with SimpleBuildWrapper, but I don't know if that will work either. 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] [htmlpublisher-plugin] (JENKINS-32026) HTML publisher 1.9 broken since Jenkins 1.625.3
Title: Message Title Andru Cherny updated an issue Jenkins / JENKINS-32026 HTML publisher 1.9 broken since Jenkins 1.625.3 Change By: Andru Cherny Attachment: снимок265.png 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-33048) add ability to archive artifacts only on FAILURE
Title: Message Title Pavel Kudrys commented on JENKINS-33048 Re: add ability to archive artifacts only on FAILURE Hi, I'm looking for such option (to archive artifacts only for FAILED builds) as well. Most of my Jenkins jobs are in fact automated tests, for which I don't really need to save 'success' artifacts (reports). Currently, there is no such option and stored artifacts make my jobs bloated with unnecessary files (only small fraction of daily test fail). Any chance to have such option? Thank you in advance! 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] [pipeline-utility-steps-plugin] (JENKINS-35245) Pipeline SCM Step Plugin does not use the same git commit for the pipeline
Title: Message Title
Sebastien Vas created an issue
Jenkins / JENKINS-35245
Pipeline SCM Step Plugin does not use the same git commit for the pipeline
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2016/May/31 8:29 PM
Priority:
Critical
Reporter:
Sebastien Vas
I have a pipeline set where I want to test every commit. The pipeline basically builds some binaries and docker images and test them in some end to end test. While in reality I am doing stuff in parallel, the pipeline can be summarized in something like that: node { checkout scm // Build binary }
node { checkout scm // Build docker ... }
node { checkout scm // Run test .. }
What I noticed is that, whenever a new commit is created on the git repo after my build started and before it finishes, it will be used whenever I do a new checkout scm in my pipeline.
So basically what I expect is: 1. Jenkins triggers a build for sha 1234 2. Build binary at sha 1234 3. Build docker at sha 1234 4. Run test at sha 1234
but what s happening is: 1. Jenkins triggers a build for sha 1234 2. Build binary at sha 1234 3. Build docker at sha 1234 (1235 is pushed to the repo) 4. Run test at sha 1235
This is from my point of view a critical bug, because I cannot guarantee that my pipeline is using the same commit, which is a point of a pipeline.
Here is beginning of the sample output: (first checkout from master) > git
[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-34847) Missing parameters
Title: Message Title Daniel Barcay commented on JENKINS-34847 Re: Missing parameters This bug caught my team when attempting an upgrade to Jenkins. I had to rollback. Definitely a blocker bug, and needs to be addressed ASAP, since I can't find a workaround. 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] [hp-application-automation-tools-plugin] (JENKINS-35106) HP ALM plugin fails to find junit results file
Title: Message Title mpendas resolved as Fixed Thank you for the response. I was expecting the plugin to look for the result file in the workspace directory of the job, not the build directory. I was assuming the same behavior as the junit plugin. I see now that this plugin uses the results of the junit plugin not that actual junit file produced by a given test framework. I think if you were a bit more explicit about that in the help available in the jenkins job configuration, it would avoid this question in the future. Again thanks for the help and for writing the plugin! Jenkins / JENKINS-35106 HP ALM plugin fails to find junit results file Change By: mpendas 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"
[JIRA] [warnings-plugin] (JENKINS-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title Ulli Hafner resolved as Cannot Reproduce See: https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/lastCompletedBuild/testReport/plugins/WarningsPluginTest/should_find_warnings_without_sleep/ Jenkins / JENKINS-32191 workflow plugin does not provide console to warnings plugin, sleep required Change By: Ulli Hafner Status: Open Resolved Resolution: Cannot 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] [github-oauth-plugin] (JENKINS-34894) Jenkins github oAuth breaks UI in anonymous login
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-34894 Jenkins github oAuth breaks UI in anonymous login Change By: Sam Gleske 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] [github-oauth-plugin] (JENKINS-34894) Jenkins github oAuth breaks UI in anonymous login
Title: Message Title Sam Gleske commented on JENKINS-34894 Re: Jenkins github oAuth breaks UI in anonymous login Great! Thanks for reporting back everyone. 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] [external-workspace-manager-plugin] (JENKINS-35244) [EWM] Implement the exws step
Title: Message Title Alexandru Somai started work on JENKINS-35244 Change By: Alexandru Somai 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] [external-workspace-manager-plugin] (JENKINS-35244) [EWM] Implement the exws step
Title: Message Title Alexandru Somai created an issue Jenkins / JENKINS-35244 [EWM] Implement the exws step Issue Type: New Feature Assignee: Alexandru Somai Components: external-workspace-manager-plugin Created: 2016/May/31 7:54 PM Priority: Major Reporter: Alexandru Somai Implement the 'exws' step. Take into consideration both the Node configuration and the Template definition in the Jenkins global config. Add Comment This message was sent by
[JIRA] [github-oauth-plugin] (JENKINS-34894) Jenkins github oAuth breaks UI in anonymous login
Title: Message Title Ronald Gundlach-Chmara commented on JENKINS-34894 Re: Jenkins github oAuth breaks UI in anonymous login UI elements now showing up correctly when not logged in. WIth 0.24. 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 Alexander Obuhovich commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" I've asked DevOps team to do the upgrade and what they did is downloaded RPM package by hand and installed it. Now I can confirm, that issue (with ssh-agent) is indeed solved for me as well. 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Joe Arasin commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. That is without the new version of the plugin installed. 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Felipe Santos edited a comment on JENKINS-34896 Re: Not retrieving teams I did another checks and I see some users that authorization works and teams are not shown in user details, and they are not admins.Some are private org members, some are not, I could not identify a pattern yet.I use the Role-based Authorization Strategy plugin, and some teams are not identified !http://imageshack.com/a/img922/2889/LjFBK8.png! A An user with this team already logged in 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Felipe Santos edited a comment on JENKINS-34896 Re: Not retrieving teams I did another checks and I see some users that authorization works and teams are not shown in user details, and they are not admins.Some are private org members, somo some are not, I could not identify a pattern yet.I use the Role-based Authorization Strategy plugin, and some teams are not identified !http://imageshack.com/a/img922/2889/LjFBK8.png!A user with this team already logged in 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Felipe Santos edited a comment on JENKINS-34896 Re: Not retrieving teams I did another checks and I see some users that authorization works and teams are not shown in user details, and they are not admins.Some are private org members, somo are not, I could not identify a pattern yet.I use the Role-based Authorization Strategy plugin, and some teams are not identified !http://imageshack.com/a/img922/2889/LjFBK8.png! A user with this team already logged in< /span> 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Felipe Santos commented on JENKINS-34896 Re: Not retrieving teams I did another checks and I see some users that authorization works and teams are not shown in user details, and they are not admins. Some are private org members, somo are not, I could not identify a pattern yet. I use the Role-based Authorization Strategy plugin, and some teams are not identified 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Sam Gleske commented on JENKINS-34896 Re: Not retrieving teams Are there any differences between those accounts that you can see or tell? e.g. is their org membership private or open between the two? Any difference you can think of that will help me to replicate it. 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] [parameterized-trigger-plugin] (JENKINS-34954) Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin
Title: Message Title James Murphy commented on JENKINS-34954 Re: Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin Hi, I think I am hitting the same issue. I am using Jenkins for our Continuous Integration Pipeline and over the weekend the Jenkins Master upgraded itself from 1.651.1 to 1.651.2, and several of our jobs that are using the parameterized trigger plugin are now failing. While I can revert back to 1.651.1, I am wondering what the solution going forward should be? Right now I have a shell script that runs in JobA, it creates a bunch of variables (for example, location to some of the build artifacts stored on an external file server) and pipes them to a file that I later pass to JobB using "Parameters from properties file". This works extremely well for us because we don't necessarily need to create the parameters in JobB before hand, as long as JobA passes them in via the properties file. Since I see there appear to be several people hitting the same issue with the parameterized trigger pluggin after upgrade to 1.651.2 or greater, I am wondering if there will be some fix to revert back the requirement that the job that is being triggered must pre-define/declare the parameters before they can be passed in? 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] [core] (JENKINS-35243) ItemGroup.getUrlChildPrefix not honored by views
Title: Message Title Jesse Glick commented on JENKINS-35243 Re: ItemGroup.getUrlChildPrefix not honored by views See symptom in JENKINS-32178 . 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-35243) ItemGroup.getUrlChildPrefix not honored by views
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-35243 ItemGroup.getUrlChildPrefix not honored by views Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/31 6:28 PM Labels: folders multibranch Priority: Minor Reporter: Jesse Glick View.getJob(String} works for URL binding only in case ItemGroup.getUrlChildPrefix returns "job". It would be nicer to allow "item", "branch", etc. to be used, but these do not get URL-bound. Perhaps View.getDynamic(String) needs to consider the prefix? (AbstractFolder could do the same, though it is expected that a subclass overriding getUrlChildPrefix would add a static binding getter.) According to AbstractItem.getShortUrl, the prefix may be ".", which is to say no prefix at all. This is used by MatrixProject and others, though I suspect never for a TopLevelItem child.
[JIRA] [core] (JENKINS-35190) Improper PingThread handling
Title: Message Title Jesse Glick commented on JENKINS-35190 Re: Improper PingThread handling Remoting PR merged but as yet unreleased. I guess standard practice is to mark this fixed once core picks up that release? 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-35190) Improper PingThread handling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35190 Re: Improper PingThread handling Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/remoting/PingThread.java http://jenkins-ci.org/commit/remoting/1fc3c930647fd9352c857fdd247c7d9b252dbc94 Log: JENKINS-35190 Added some logging. 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-35190) Improper PingThread handling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35190 Re: Improper PingThread handling Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/remoting/Launcher.java src/main/java/hudson/remoting/PingThread.java http://jenkins-ci.org/commit/remoting/59e33a4a6592bdf9c680fbeeaf4cc679a2a2 Log: Merge pull request #85 from jglick/PingThread-JENKINS-35190 JENKINS-35190 PingThread fixes Compare: https://github.com/jenkinsci/remoting/compare/c0cf33130ae5...59e33a4a6592 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-35190) Improper PingThread handling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35190 Re: Improper PingThread handling Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/remoting/Launcher.java http://jenkins-ci.org/commit/remoting/7ff0a9ae79eb897bb70d9a88296985f5b67b3c81 Log: JENKINS-35190 Turning off redundant PingThread from Launcher. Also using new onDead overload. 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-24631) Credentials store API cannot browse into domains
Title: Message Title Jesse Glick started work on JENKINS-24631 Change By: Jesse Glick 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-24631) Credentials store API cannot browse into domains
Title: Message Title Jesse Glick reopened an issue JIRA link daemon again thinking that filing a PR from origin is the same as merging it… Jenkins / JENKINS-24631 Credentials store API cannot browse into domains Change By: Jesse Glick Resolution: Fixed Status: Resolved Reopened 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-24631) Credentials store API cannot browse into domains
Title: Message Title Jesse Glick updated JENKINS-24631 Jenkins / JENKINS-24631 Credentials store API cannot browse into domains Change By: Jesse Glick Status: Reopened Open 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.
