[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak edited a comment on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around Thanks Awesome, thanks [~danielbeck], that's exactly what I did. The latest Build Monitor picks up the crumb name from CrumbIssuer::getCrumbRequestField so it should be a more appropriate solution :-) 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around Thanks Daniel Beck, that's exactly what I did. The latest Build Monitor picks up the crumb name from CrumbIssuer::getCrumbRequestField so it should be a more appropriate solution 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak edited a comment on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around [~jknurek] - Fixed in Build Monitor 1.9+build.201604300128, which you can [download from my Jenkins CI server]( here| https://smartcode-opensource.ci.cloudbees.com/job/build-monitor/37/artifact/build-monitor-plugin/target/build-monitor-plugin.hpi ) ] before it hits the official update centre. 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around J Knurek - Fixed in Build Monitor 1.9+build.201604300128, which you can [download from my Jenkins CI server](https://smartcode-opensource.ci.cloudbees.com/job/build-monitor/37/artifact/build-monitor-plugin/target/build-monitor-plugin.hpi) before it hits the official update centre. 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-26481) Mishandling of binary methods accepting Closure
Title: Message Title
Patrick Ranspach commented on JENKINS-26481
Re: Mishandling of binary methods accepting Closure
Can we add this to the epic: 2.0: Pipeline as Code? This seems very important to using Groovy in a pipeline as code. It can be easily reproduced and blocks dependable groovy functionality.
Also relevant labels: 2.0, 2.0-planned, testfest, windows, workflow
Maybe also related, I'm only able to access closure arguments within returned closures if I copy the argument:
def test = { name ->
def path = 'services/' + name
return { _ ->
println(name)
// .. do something
}
}
will print the same 'name' with this code:
def options = [];
['test', 'test1', 'test2'].each {
iter ->
options << test(iter)
}
options.each {it()}
return options
In a Jenkins Pipeline I have to save the argument, like:
def test = { arg ->
def name = arg;
def path = 'services/' + name
return { _ ->
println(name)
// .. do something
}
}
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] [nunit-plugin] (JENKINS-27043) NUnit plugin fails while converting to JUnit XML
Title: Message Title Jonathan Fletcher commented on JENKINS-27043 Re: NUnit plugin fails while converting to JUnit XML Now that NUnit3 is released, is there a plan for fixing this? We recently upgraded from NUnit to NUnit3 and the XUnit plugin stopped working for us. 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Daniel Beck commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around Jan Molak which replaced the hard-coded '.crumb' header with 'Jenkins-Crumb', that's why they no longer match. The crumb name has been configurable since 1.310 (hudson.security.csrf.requestfield), and that was necessary for anyone running Jenkins behind nginx, as it dropped the .crumb header ( JENKINS-12875 ). So we renamed the default to something nginx accepts. Maybe it's a good idea to check which crumb name is used by Jenkins in your plugin to adapt to user configuration. 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around Daniel Beck Build Monitor has supported CSRF protection since its early days The problem is caused by change https://github.com/jenkinsci/jenkins/compare/4649e04cbe58...a87c38c5052c , which replaced the hard-coded '.crumb' header with 'Jenkins-Crumb', that's why they no longer match. I can work around that in Build Monitor. J Knurek you can watch the progress of this issue on github at https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/215, which is the official issue tracker for Build Monitor. Thanks! Jan 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak updated an issue Jenkins / JENKINS-12875 "No valid crumb was included in the request" errors all around Change By: Jan Molak Comment: Hey Daniel and thanks for your suggestion about Build Monitor not handling the CSRF protection option. The CSRF protection option works perfectly fine with Build Monitor on Jenkins 1.x. Has anything changed regarding CSRF and the Crumb/.crumb headers handling on Jenkins 2.0? I'd be grateful for suggestions.Kind regards,Jan (author of Build Monitor) 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-pipeline-plugin] (JENKINS-33935) Can't rerun a build
Title: Message Title Harry Soehalim commented on JENKINS-33935 Re: Can't rerun a build Ran into the same issue with the versions: build-pipeline-plugin: 1.5.2 jenkins CI: 2.0 Could someone plz take a look at this issue? 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-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jan Molak commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around Hey Daniel and thanks for your suggestion about Build Monitor not handling the CSRF protection option. The CSRF protection option works perfectly fine with Build Monitor on Jenkins 1.x. Has anything changed regarding CSRF and the Crumb/.crumb headers handling on Jenkins 2.0? I'd be grateful for suggestions. Kind regards, Jan (author of Build Monitor) 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-34506) successful parallel stages marked as failed
Title: Message Title Sam Van Oort resolved as Won't Fix Unfortunately, as currently implemented, stage steps cannot be used correctly within parallel blocks. This is a limitation of how stages are implemented in the pipeline, not the UI itself. You may use a stage that contains parallel blocks, however (in which case the stage will show as successful if and only if all parallel components succed). Since it's a fairly common assumption, there's a mention within the in the Pipeline Stage View limitations/usage notes on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin There is work in progress to provide a new step that can be used within parallel blocks to mark their progress: https://issues.jenkins-ci.org/browse/JENKINS-26107 Please see also: https://issues.jenkins-ci.org/browse/JENKINS-33185 which is planned work to offer better visualization of parallel branches within a stage (there are multiple people including me working towards that, but it is complex and will take a while to implement). Jenkins / JENKINS-34506 successful parallel stages marked as failed Change By: Sam Van Oort Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34506) successful parallel stages marked as failed
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-34506 successful parallel stages marked as failed Change By: Sam Van Oort Assignee: Antonio Muñiz Sam Van Oort 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-34507) failed execution in a new node during a parallel step is incorrectly displayed
Title: Message Title Sam Van Oort resolved as Won't Fix Unfortunately, as currently implemented, stage steps cannot be used correctly within parallel blocks. This is a limitation of how stages are implemented in the pipeline, not the UI itself. You may use a stage that contains parallel blocks, however (in which case the stage will show as successful if and only if all parallel components succed). Since it's a fairly common assumption, there's a mention within the in the Pipeline Stage View limitations/usage notes on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin There is work in progress to provide a new step that can be used within parallel blocks to mark their progress: https://issues.jenkins-ci.org/browse/JENKINS-26107 Please see also: https://issues.jenkins-ci.org/browse/JENKINS-33185 which is planned work to offer better visualization of parallel branches within a stage (there are multiple people including me working towards that, but it is complex and will take a while to implement). Jenkins / JENKINS-34507 failed execution in a new node during a parallel step is incorrectly displayed Change By: Sam Van Oort Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title Sam Van Oort commented on JENKINS-34212 Re: Visualization shows stage failed when an exception is caught Hi Michael, Please, can you provide a sample pipeline that reproduces this issue? I suspect this is a result of limitations in how the pipeline is currently scanned for errors (which should be addressed by https://issues.jenkins-ci.org/browse/JENKINS-34038 since the implementation is being completely replaced with a more robust algorithm). However, I would like to confirm this and have a test case I can use to verify. 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-34212) Visualization shows stage failed when an exception is caught
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-34212 Visualization shows stage failed when an exception is caught Change By: Sam Van Oort Component/s: pipeline-stage-view-plugin Component/s: pipeline-view-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] [pipeline-stage-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-34212 Visualization shows stage failed when an exception is caught Change By: Sam Van Oort Assignee: Sergei Egorov Sam Van Oort 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-34507) failed execution in a new node during a parallel step is incorrectly displayed
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-34507 failed execution in a new node during a parallel step is incorrectly displayed Change By: Sam Van Oort Assignee: Antonio Muñiz Sam Van Oort 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] [cmakebuilder-plugin] (JENKINS-29142) look for MSVC 15.x toolchain
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29142 Re: look for MSVC 15.x toolchain Code changed in jenkins User: 15knots Path: src/main/resources/hudson/plugins/cmake/CmakeBuilder/help-generator.html http://jenkins-ci.org/commit/cmakebuilder-plugin/bfe1506a258e61d1fa6ed1a8905d7317500b7669 Log: FIXED JENKINS-29142 (cannot be fixed, but mention 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] [core] (JENKINS-34342) Remove version from X-Hudson and X-Jenkins headers
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-34342 Re: Remove version from X-Hudson and X-Jenkins headers Owen Wood I agree with Daniel Beck, What is the motivation to do that? I agree with removing X-Hudson because it should be deprecated. 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-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Jacob Keller commented on JENKINS-32479 Re: multiple git repositories sometimes fail to checkout some of them into subdirectory An alternative would be to implement getModuleRoots for the Git Plugin to return the actual root when Git is using the extension, and then order checkouts based on this. I am thinking this is simpler and will try to implement this. 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-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Jacob Keller assigned an issue to Jacob Keller Jenkins / JENKINS-32479 multiple git repositories sometimes fail to checkout some of them into subdirectory Change By: Jacob Keller Assignee: Jacob Keller 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-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Jacob Keller commented on JENKINS-32479 Re: multiple git repositories sometimes fail to checkout some of them into subdirectory So the recursive delete call was originally added since "git clone" does not let you clone into a non-empty directory. The root of this problem is due to how MultiSCM orders its checkouts, and there is no (obvious) way to tell which repositories belong in which directories from within the MultiSCM plugin, as this is part of the Git plugin settings. In addition, we can't really depend on a specific ordering from within the MultiSCM plugin, and we can't reliably remove the restriction that the work space be empty. I believe the problem is that MultiSCM should be made aware of the "checkout to separate directory" option, and indeed should actually implement it itself, since it is a very common or obvious problem when using multiple repositories. That would avoid the issues here without having to remove the constraint (which probably affects other SCMs as well!) 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] [clover-plugin] (JENKINS-34010) Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS
Title: Message Title Robert Miesen commented on JENKINS-34010 Re: Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS I've done some more digging and it appears that this happens when a clover.xml file is corrupt or invalid. So the root cause appears to be that the clover plugin doesn't gracefully handle cases where the processing of the clover.xml file fails when preparing the trend graph. 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] [clover-plugin] (JENKINS-34010) Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS
Title: Message Title Robert Miesen updated an issue Jenkins / JENKINS-34010 Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS Change By: Robert Miesen Comment: I've done some more digging and it appears that this happens when a clover.xml file is corrupt or invalid.So the root cause appears to be that the clover plugin doesn't gracefully handle cases where the processing of the clover.xml file fails when preparing the trend graph. 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] [clover-plugin] (JENKINS-34010) Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS
Title: Message Title Robert Miesen commented on JENKINS-34010 Re: Trend graph no longer works after upgrading Jenkins from 1.625.2 LTS to 1.642.2 LTS I've done some more digging and it appears that this happens when a clover.xml file is corrupt or invalid. So the root cause appears to be that the clover plugin doesn't gracefully handle cases where the processing of the clover.xml file fails when preparing the trend graph. 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-33885) Multibranch Pipeline projects do not expose build status
Title: Message Title Jesse Glick commented on JENKINS-33885 Re: Multibranch Pipeline projects do not expose build status I have no idea what cc.xml is or what it is being generated by, but AFAIK there is nothing missing in Pipeline or multibranch per se. As you can see from your screenshot, the weather icon does represent the aggregate status of the branch projects inside the folder, just like it would for any other folder. Perhaps this just boils down to some old tool not being folder-aware. 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-33885) Multibranch Pipeline projects do not expose build status
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33885 Multibranch Pipeline projects do not expose build status Change By: Jesse Glick Labels: folders multibranch 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] [radiatorview-plugin] (JENKINS-33645) Multibranch Pipelines do not show up in Radiator Views
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33645 Multibranch Pipelines do not show up in Radiator Views Change By: Jesse Glick Labels: multibranch 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] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title Jesse Glick commented on JENKINS-26522 Re: Annotated block/stage status Another example use case is that github-branch-source could look for the resulting status notes and publish them to the GH Status API, so you would be able to see progress of your build in different sections right in a pull request. 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 Lev Mishin commented on JENKINS-34512 Re: error in build-name-setter plugin - Set build name I'll check it soon, could you also provide job configuration please? 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-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title John Long commented on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable I was really surprised that this was not implemented. This lack will make it very hard to integrate into some of our reporting systems and probably will delay our adoption of the Pipelines. It's a shame, I really like them. 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-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Jacob Keller commented on JENKINS-32479 Re: multiple git repositories sometimes fail to checkout some of them into subdirectory I found the root cause of the issue is due to lines 453 in the Git-client plugin, it runs a recursive "delete workspace" command, and so entirely depending on the ordering of the repositories the Multiple SCM plugin will fail. I don't even think the options are necessary to use, since a checkout -f will overwrite any files to begin with, and the only other option is implementing our own "clean" setup which would be more expensive than just relying on the clean extension. 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] [gitlab-plugin] (JENKINS-34515) NPE in ActionResolver.onPost
Title: Message Title John Casebolt updated an issue Jenkins / JENKINS-34515 NPE in ActionResolver.onPost Change By: John Casebolt Environment: Desktop: MacOS 10.11.4, Chrome latest. Jenks server: Jenkins 2.0 on RHEL 6 with Java 1.8.0_91, git/gitlab (version 1.2.0) /gitlab hook plugins, various other plugins. GitLab version 8.7.0-ee on RHEL 7. When trying to use the new-ish (not the Deprecated version) Jenkins CI integration from GitLab to kick off a Jenks job on a push, I get a stack trace (file attached) in the jenks error log and an "Internal Server Error" message back in GitLab.Prior to upgrading to Jenkins 2.0 and the new version of the GitLab Jenks plugin, all was working great for months on end. I was able to get the integration to work if I rolled back the gitlab plugin to version 1.1.32. 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-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman commented on JENKINS-34498 Re: Jenkins 2.0 "out of the box" plugins failed to install I'm changing it to major because it basically invalidates the 2.0 experience. Without those plugins Jenkins is just the same as the old 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] [core] (JENKINS-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman updated an issue Jenkins / JENKINS-34498 Jenkins 2.0 "out of the box" plugins failed to install Change By: Igor Koyfman 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Brantone commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 There are a few assumptions in there ... would prefer explicit confirmation. 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Brantone assigned an issue to Brantone Jenkins / JENKINS-31712 Use SCM from another project is removed after upgrading to 1.5.1 Change By: Brantone Assignee: huybrechts Brantone 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] [gitlab-plugin] (JENKINS-34515) NPE in ActionResolver.onPost
Title: Message Title John Casebolt updated an issue Jenkins / JENKINS-34515 NPE in ActionResolver.onPost Change By: John Casebolt When trying to test use the new-ish (not the Deprecated version) Jenkins CI integration from GitLab to kick off a Jenks job on a push, I get a stack trace (file attached) in the jenks error log and a an "Internal Server Error" message back in GitLab.Prior to upgrading to Jenkins 2.0 and the new version of the GitLab Jenks plugin, all was working great for months on end. 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] [gitlab-plugin] (JENKINS-34515) NPE in ActionResolver.onPost
Title: Message Title John Casebolt created an issue Jenkins / JENKINS-34515 NPE in ActionResolver.onPost Issue Type: Bug Assignee: Robin Müller Attachments: jenkins.log Components: gitlab-plugin Created: 2016/Apr/29 5:34 PM Environment: Desktop: MacOS 10.11.4, Chrome latest. Jenks server: Jenkins 2.0 on RHEL 6 with Java 1.8.0_91, git/gitlab/gitlab hook plugins, various other plugins. GitLab version 8.7.0-ee on RHEL 7. Labels: gitlab Priority: Major Reporter: John Casebolt When trying to test the new-ish Jenkins CI integration from GitLab to kick off a Jenks job on a push, I get a stack trace (file attached) in the jenks error log and a "Internal Server Error" message back in GitLab. Prior to upgrading to Jenkins 2.0 and the new
[JIRA] [gerrit-trigger-plugin] (JENKINS-34514) NPE if job is marked as parameterized with no parameters
Title: Message Title
Will Saxon updated an issue
Jenkins / JENKINS-34514
NPE if job is marked as parameterized with no parameters
Change By:
Will Saxon
If a build is marked as "This build is parameterized" but has no defined parameters, the Gerrit Trigger cannot trigger it. An NPE gets logged:{noformat}Apr 29, 2016 12:22:28 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener onTriggeredINFO: Project [Some_Build_Project] triggered by Gerrit: [PatchsetCreated: Change-Id for #43226: Idde0e7ec2fa298b9f5fb9ee59f63af390699fedb PatchSet: 1]Apr 29, 2016 12:22:28 PM com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListenersSEVERE: When notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@19fdac1f about event: PatchsetCreated: Change-Id for #43226: Idde0e7ec2fa298b9f5fb9ee59f63af390699fedb PatchSet: 1Apr 29, 2016 12:22:28 PM com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListenersSEVERE: Notify-error:java.lang.NullPointerExceptionat com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.getDefaultParametersValues(EventListener.java:278)at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.createParameters(EventListener.java:252)at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.schedule(EventListener.java:182)at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.schedule(EventListener.java:158)at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.gerritEvent(EventListener.java:100)at com.sonymobile.tools.gerrit.gerritevents.GerritHandler.notifyListener(GerritHandler.java:328)at com.sonymobile.tools.gerrit.gerritevents.GerritHandler.notifyListeners(GerritHandler.java:296)at com.sonyericsson.hudson.plugins.gerrit.trigger.JenkinsAwareGerritHandler.notifyListeners(JenkinsAwareGerritHandler.java:77)at com.sonymobile.tools.gerrit.gerritevents.workers.AbstractGerritEventWork.perform(AbstractGerritEventWork.java:46)at com.sonymobile.tools.gerrit.gerritevents.workers.AbstractJsonObjectWork.perform(AbstractJsonObjectWork.java:77)at com.sonymobile.tools.gerrit.gerritevents.workers.StreamEventsStringWork.perform(StreamEventsStringWork.java:67)at com.sonymobile.tools.gerrit.gerritevents.workers.EventThread.run(EventThread.java:66)at com.sonyericsson.hudson.plugins.gerrit.trigger.SystemEventThread.run(SystemEventThread.java:66){noformat} Even after fixing the job (by deselecting the parameters option), manual trigger via 'query and trigger Gerrit patchsets' doesn't work for the specific patchset generating the NPE. Nothing happens. A new patchset is required to get the trigger to work.
[JIRA] [gerrit-trigger-plugin] (JENKINS-34514) NPE if job is marked as parameterized with no parameters
Title: Message Title Will Saxon created an issue Jenkins / JENKINS-34514 NPE if job is marked as parameterized with no parameters Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Apr/29 4:50 PM Environment: Gerrit 2.12.2, Jenkins 1.651.1, Gerrit Trigger 2.20.0 Priority: Minor Reporter: Will Saxon If a build is marked as "This build is parameterized" but has no defined parameters, the Gerrit Trigger cannot trigger it. An NPE gets logged: Apr 29, 2016 12:22:28 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener onTriggered INFO: Project [Some_Build_Project] triggered by Gerrit: [PatchsetCreated: Change-Id for #43226: Idde0e7ec2fa298b9f5fb9ee59f63af390699fedb PatchSet: 1] Apr 29, 2016 12:22:28 PM com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListeners SEVERE: When notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@19fdac1f about event: PatchsetCreated: Change-Id for #43226: Idde0e7ec2fa298b9f5fb9ee59f63af390699fedb Pa tchSet: 1 Apr 29, 2016 12:22:28 PM com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListeners SEVERE: Notify-error: java.lang.NullPointerException at
[JIRA] [metrics-plugin] (JENKINS-34491) Fix PCT against 2.0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34491 Re: Fix PCT against 2.0 Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/metrics-plugin/2ae5ec4ceac6edbe79c51ef35f5b316c5edf1389 Log: Merge pull request #23 from andresrc/JENKINS-34491 JENKINS-34491 Fix PCT against core 2.0 Compare: https://github.com/jenkinsci/metrics-plugin/compare/612944c5209c...2ae5ec4ceac6 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] [metrics-plugin] (JENKINS-34491) Fix PCT against 2.0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34491 Re: Fix PCT against 2.0 Code changed in jenkins User: Andres Rodriguez Path: pom.xml http://jenkins-ci.org/commit/metrics-plugin/70925d4d3cb94b0d7f59eab7bf4cee05658ccd4a Log: JENKINS-34491 Fix PCT against core 2.0 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] [scoverage-plugin] (JENKINS-24806) Scoverage: iFrames blocked by many server setups
Title: Message Title WynX Alucard commented on JENKINS-24806 Re: Scoverage: iFrames blocked by many server setups Same here, had to work around it by modifying the headers. 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] [scoverage-plugin] (JENKINS-24803) Scoverage shouldn't load external static content
Title: Message Title WynX Alucard commented on JENKINS-24803 Re: Scoverage shouldn't load external static content Same here. Serving Jenkins over HTTPS gives a lot of problems with this plugin that pulls in many external resources. I'd recommend to distribute the scripts and stylesheets with the plugin if at all possible. At least the following: http://yui.yahooapis.com/pure/0.3.0/pure-min.css Available on https as well (I use CSP upgrade-insecure-requests): ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js cdnjs.cloudflare.com/ajax/libs/jquery.tablesorter/2.20.1/css/theme.default.min.css cdnjs.cloudflare.com/ajax/libs/jquery.tablesorter/2.20.1/js/jquery.tablesorter.min.js netdna.bootstrapcdn.com/bootstrap/3.0.3/css/bootstrap.min.css netdna.bootstrapcdn.com/bootstrap/3.0.3/js/bootstrap.min.js 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] [global-build-stats-plugin] (JENKINS-10563) NoSuchElementException when no job is created
Title: Message Title David Hinske closed an issue as Fixed Jenkins / JENKINS-10563 NoSuchElementException when no job is created Change By: David Hinske 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] [global-build-stats-plugin] (JENKINS-10607) Jenkins jobs hang when finished
Title: Message Title David Hinske closed an issue as Fixed Jenkins / JENKINS-10607 Jenkins jobs hang when finished Change By: David Hinske 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] [testng-plugin] (JENKINS-34513) Don't mark skipped testng tests as a failed build
Title: Message Title Wilson Davis created an issue Jenkins / JENKINS-34513 Don't mark skipped testng tests as a failed build Issue Type: Bug Assignee: Nalin Makar Components: testng-plugin Created: 2016/Apr/29 4:03 PM Environment: Jenkins 1.629, CentOS-07, Java 8, testNG 1.1 Priority: Minor Reporter: Wilson Davis I am running some testNG tests on Jenkins, but there are tests I have to skip every time through a SkipException. This causes my build to be marked as a failure and shows a red icon next to it. Is there a way to not mark testNG skips as a failure? Add Comment
[JIRA] [global-build-stats-plugin] (JENKINS-9088) Global Build Stats graphing should stack the statuses in a different order
Title: Message Title David Hinske closed an issue as Fixed Jenkins / JENKINS-9088 Global Build Stats graphing should stack the statuses in a different order Change By: David Hinske 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] [global-build-stats-plugin] (JENKINS-7476) v0.4 : Jelly Exception thrown on the "install" tab in plugin manager
Title: Message Title David Hinske closed an issue as Fixed Jenkins / JENKINS-7476 v0.4 : Jelly Exception thrown on the "install" tab in plugin manager Change By: David Hinske 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] [acceptance-test-harness] (JENKINS-34411) Horizontal scrolling & overflow issues
Title: Message Title
Andres Rodriguez updated an issue
Jenkins / JENKINS-34411
Horizontal scrolling & overflow issues
Change By:
Andres Rodriguez
Summary:
Horizontal scrolling & overflow issues
Tests using matrix authorization (or permissions tables similar to the used in this configuration) are presenting some issues relates to scrolling.I have only been able to reproduce it in Mac (in a Linux VM seems to work) but when clicking in permissions outside the current view, the scrolling the element is not checked (but no error is launched), causing the test to fail downstream when the expected permission is not set. Besides, tests in which elements with specific overflow styles (such as the "Add Credentials Dialog", used for example in {{CreateSlaveTest#newSlave}} are also problematic.
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 created an issue Jenkins / JENKINS-34512 error in build-name-setter plugin - Set build name Issue Type: Bug Assignee: Lev Mishin Components: build-name-setter-plugin Created: 2016/Apr/29 2:56 PM Priority: Minor Reporter: Devesh Kumar I recently upgraded my Jenkins from 1.543 to Jenkins 2 and build-name-setter plugin automatically got upgraded from 1.3 to 1.6.5. However the build fails, here are the logs: 16:52:02 Set build name. 16:52:02 New build name is '#553' 16:52:02 Variable with name 'BUILD_DISPLAY_NAME' already exists, current value: '#553', new value: '#553' OS: Windows Server 2008 R2 Ent./64 bit Jenkins - 2.0 - Only Master no Slave Java - 7 (7_49) build-name-setter-plugin version: 1.6.5 Installed Jenkins directly using installer tried multiple browsers Chrome, Firefox I reverted the plugin to old version 1.3 and it works well with Jenkins 2.0. Add Comment
[JIRA] [antisamy-markup-formatter-plugin] (JENKINS-34511) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez started work on JENKINS-34511 Change By: Armando Fernandez 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] [antisamy-markup-formatter-plugin] (JENKINS-34511) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez assigned an issue to Armando Fernandez Jenkins / JENKINS-34511 Migrate to 2.x parent pom Change By: Armando Fernandez Assignee: Jesse Glick Armando Fernandez 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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Faheem Nadeem edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Hi I have some jenkinfiles which worked perfectly when I just copied them to a simple pipeline job. After shifting to a multibranch or jenkinsfile from scm all of them get a rejected access exception, which makes sense due to groovy sand boxing{code:java}ERROR: Failed: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap{code}on a command, which is just parsing an xml from a get with curl{code:java}13:55:28 + xmllint --xpath string(//action/cause/shortDescription) JENKINS_REST_API_RESULTS[Pipeline] readFile[Pipeline] error[Pipeline] echo{code}My problem is I have admin privileges for jenkins. I also have permission to read/RunScripts in Overall, but I still don't see an approval request for "java.util.HashMap" in scriptApproval section. At one point I had approvals due to my testing but , which I accepted. But now what ever I try e.g. moving the job a simple pipeline enabling sandboxing, creating a multibranch, loading the jenkinsfile through scm, nothing triggers a script approval for "java.util.HashMap". Which To top it all I removed the previously approved requests and now even they are not triggered :( Interestingly, I am not even sure why I require because approvals as I am the admin my self, who is creating these jobs. And I see no way to whitelist certain methods my self, until or unless as [~hrmpw] mentioned to create a plugin and install it. Is there any solution for this currently. And I totally vote for a disabled or a limited sandboxed environment, with the choice easily accessible from the configuration.
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] [global-build-stats-plugin] (JENKINS-7240) Don't provide link to console in build search results if build informations have been deleted
Title: Message Title David Hinske closed an issue as Fixed not available builds are not getting displayed Jenkins / JENKINS-7240 Don't provide link to console in build search results if build informations have been deleted Change By: David Hinske Status: Resolved Closed Assignee: Frédéric Camblor David Hinske 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] [antisamy-markup-formatter-plugin] (JENKINS-34511) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-34511 Migrate to 2.x parent pom Issue Type: Improvement Assignee: Jesse Glick Components: antisamy-markup-formatter-plugin Created: 2016/Apr/29 2:15 PM Priority: Minor Reporter: Armando Fernandez Migrate to 2.x parent pom Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title Faheem Nadeem commented on JENKINS-28178 Re: Option to disable sandbox in CpsScmFlowDefinition Hi I have some jenkinfiles which worked perfectly when I just copied them to a simple pipeline job. After shifting to a multibranch or jenkinsfile from scm all of them get a rejected access exception, which makes sense due to groovy sand boxing ERROR: Failed: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap on a command, which is just parsing an xml from a get with curl 13:55:28 + xmllint --xpath string(//action/cause/shortDescription) JENKINS_REST_API_RESULTS [Pipeline] readFile [Pipeline] error [Pipeline] echo My problem is I have admin privileges for jenkins. I also have permission to read/RunScripts in Overall, but I still don't see an approval request for "java.util.HashMap" in scriptApproval section. At one point I had approvals due to my testing but now what ever I try e.g. moving the job a simple pipeline enabling sandboxing, creating a multibranch, loading the jenkinsfile through scm, nothing triggers a script approval for "java.util.HashMap". Which I am not even sure I require because I am the admin my self, who is creating these jobs. And I see no way to whitelist certain methods my self, until or unless as Patrick Wolf mentioned to create a plugin and install it. Is there any solution for this currently. And I totally vote for a disabled or a limited sandboxed environment, with the choice easily accessible from the configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [rundeck-plugin] (JENKINS-34510) Very long Jenkins startup time with a vast number of Rundeck jobs
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-34510 Very long Jenkins startup time with a vast number of Rundeck jobs Issue Type: Bug Assignee: Vincent Behar Components: rundeck-plugin Created: 2016/Apr/29 1:21 PM Environment: Jenkins 1.642.3 rundeck-plugin 3.5.2 Priority: Major Reporter: Marcin Zajączkowski Having Jenkins instance with a vast number of rundeck jobs Jenkins startup time increases dramatically. With 1500+ rundeck jobs on very strong AWS instance Jenkins starts up over 30 minutes. That number of jobs can be easy to achieve having automatically generated (e.g. with Jenkins JobDSL) deployment pipelines for multiple products deployed in multiple countries. After the analyze it turned out that rundeck-plugin makes a hit to Rundeck about job details for every runcked job in Jenkins (in RundeckJobProjectLinkerAction to display details on a build page). It can take some time, especially if Rundeck is configured to use H2 DB. In many cases number of distinct jobs in Rundeck is very limited (e.g. several) - they are prameterized. Having it cached reduce number all calls dramatically. In our case for 1500+ rundeck jobs (several distinct rundeck jobs) the startup time was reduced from over 30 minutes to less than 30 seconds .
[JIRA] [categorized-view-plugin] (JENKINS-29273) Column misalignment from indentation is too severe
Title: Message Title Arno Moonen assigned an issue to Arno Moonen Jenkins / JENKINS-29273 Column misalignment from indentation is too severe Change By: Arno Moonen Assignee: Arno Moonen 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-34509) Allow InputStep.id to start with a lowercase letter
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-34509 Allow InputStep.id to start with a lowercase letter Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/29 12:42 PM Priority: Minor Reporter: Jesse Glick As per this change, the id of an input step must start with a capital letter. Fine enough for computed IDs, but very confusing for an explicitly specified ID. The reasoning was so that getDynamic would not be ambiguous. But I think this would be fixed more easily by deprecating getDynamic, using getExecution, and making this code append execution/ to the base URL. Add Comment
[JIRA] [categorized-view-plugin] (JENKINS-29273) Column misalignment from indentation is too severe
Title: Message Title Arno Moonen commented on JENKINS-29273 Re: Column misalignment from indentation is too severe I'm working on a fix (see this branch in my fork on GitHub). I hope to finish it within a few weeks. 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-33870) Add possibility to correct manual input
Title: Message Title Jesse Glick resolved as Won't Do CloudBees Jenkins Enterprise has a checkpoint step that does essentially what you are requesting, though the usual use case is a bit different. Jenkins / JENKINS-33870 Add possibility to correct manual input Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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] [xunit-plugin] (JENKINS-21234) [xUnit] [ERROR] - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read xml file
Title: Message Title espenalb commented on JENKINS-21234 Re: [xUnit] [ERROR] - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read xml file Same here. Any chance of getting this fixed? What is really strange is that I observe the following: Three identical Jenkins nodes running on the same Windows7x64 machine (Jenkins 2.0) Master is on a Ubuntu server. The nodes have identical setup, except of course that they all execute in different holders on the hard-drive. I start three integrationtest jobs (NUnit), one on each node. The first node completes with [MOCKTESTS] [xUnit] [INFO] - Starting to record. [MOCKTESTS] [xUnit] [INFO] - Processing NUnit-Version N/A (default) [MOCKTESTS] [xUnit] [INFO] - [NUnit-Version N/A (default)] - 1 test report file(s) were found with the pattern '**/NUnit*.xml' relative to 'j:\jenkins-slave\MsBuild\workspace\Windows-feature\Win--795-s-n-over-isa' for the testing framework 'NUnit-Version N/A (default)'. [MOCKTESTS] [xUnit] [ERROR] - The plugin hasn't been performed correctly: remote file operation failed: j:\jenkins-slave\MsBuild\workspace\Windows-feature\Win--795-s-n-over-isa at hudson.remoting.Channel@1fefd624:build01-MsBuild: java.io.IOException: java.io.IOException: Failed to read j:\jenkins-slave\MsBuild\workspace\Windows-feature\Win--795-s-n-over-isa\generatedJUnitFiles\NUnit\TEST-1668962269.xml The next node finishes a little time later: [SENSORSIMULATOR] [xUnit] [INFO] - Starting to record. [SENSORSIMULATOR] [xUnit] [INFO] - Processing NUnit-Version N/A (default) [SENSORSIMULATOR] [xUnit] [INFO] - [NUnit-Version N/A (default)] - 1 test report file(s) were found with the pattern '**/NUnit*.xml' relative to 'J:\jenkins-slave\SensorSimulator1\workspace\Windows-feature\Win--795-s-n-over-isa' for the testing framework 'NUnit-Version N/A (default)'. [SENSORSIMULATOR] [xUnit] [INFO] - Check 'Failed Tests' threshold. [SENSORSIMULATOR] [xUnit] [INFO] - Check 'Skipped Tests' threshold. [SENSORSIMULATOR] [xUnit] [INFO] - Setting the build status to FAILURE [SENSORSIMULATOR] [xUnit] [INFO] - Stopping recording. and then the third node: [SYSTEMTEST] [xUnit] [INFO] - Starting to record. [SYSTEMTEST] [xUnit] [INFO] - Processing NUnit-Version N/A (default) [SYSTEMTEST] [xUnit] [INFO] - [NUnit-Version N/A (default)] - 1 test report file(s) were found with the pattern '**/NUnit*.xml' relative to 'J:\jenkins-slave\SystemTest01\workspace\Windows-feature\Win--795-s-n-over-isa' for the testing framework 'NUnit-Version N/A (default)'. [SYSTEMTEST] [xUnit] [INFO] - Check 'Failed Tests' threshold. [SYSTEMTEST] [xUnit] [INFO] - Check 'Skipped Tests' threshold. [SYSTEMTEST] [xUnit] [INFO] - Setting the build status to FAILURE [SYSTEMTEST] [xUnit] [INFO] - Stopping recording. There are no failing tests - I assume the
[JIRA] [core] (JENKINS-34494) Enable disabled (transitive) dependencies when installing a new plugin
Title: Message Title Daniel Beck assigned an issue to Keith Zantow Jenkins / JENKINS-34494 Enable disabled (transitive) dependencies when installing a new plugin Change By: Daniel Beck Assignee: Keith Zantow 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-34494) Enable disabled (transitive) dependencies when installing a new plugin
Title: Message Title Daniel Beck started work on JENKINS-34494 Change By: Daniel Beck 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] [core] (JENKINS-34494) Enable disabled (transitive) dependencies when installing a new plugin
Title: Message Title
Daniel Beck edited a comment on JENKINS-34494
Re: Enable disabled (transitive) dependencies when installing a new plugin
Steps to reproduce:* Install 1.653* Create a freestyle job* Update all plugins* Restart* Disable Subversion and SCM API plugin* Shut down* Start 2.0 on same Jenkins home* 'Finish upgrade'* (GHOF and Pipeline:Groovy will fail to load)* RestartResult:{noformat}hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237)Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1020) at jenkins.model.Jenkins.(Jenkins.java:864) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:225)Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8 moreCaused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at hudson.ExtensionList.get(ExtensionList.java:171) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1690) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34494) Enable disabled (transitive) dependencies when installing a new plugin
Title: Message Title Daniel Beck commented on JENKINS-34494 Re: Enable disabled (transitive) dependencies when installing a new plugin Steps to reproduce: Install 1.653 Create a job Update all plugins Restart Disable SCM API plugin Shut down Start 2.0 on same Jenkins home 'Finish upgrade' (GHOF and Pipeline:Groovy will fail to load) Restart Result: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1020) at jenkins.model.Jenkins.(Jenkins.java:864) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8
[JIRA] [_unsorted] (JENKINS-34504) Jenkins got unusable after upgrading to 2.0 version
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-34504 Jenkins got unusable after upgrading to 2.0 version Change By: Daniel Beck 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] [active-directory-plugin] (JENKINS-34508) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-34508 Migrate to 2.x parent pom Issue Type: Improvement Assignee: Armando Fernandez Components: active-directory-plugin Created: 2016/Apr/29 10:42 AM Priority: Minor Reporter: Armando Fernandez Migrate to 2.x parent pom. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [active-directory-plugin] (JENKINS-34508) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez started work on JENKINS-34508 Change By: Armando Fernandez 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] [_unsorted] (JENKINS-34504) Jenkins got unusable after upgrading to 2.0 version
Title: Message Title Alex Al commented on JENKINS-34504 Re: Jenkins got unusable after upgrading to 2.0 version Thanks you for much, Daniel for the hint. I removed all *.jpi.disabled from plugins directory and Jenkins is up again. 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] [rebuild-plugin] (JENKINS-19910) Support rebuilding projects using maven metadata plugin
Title: Message Title Sylvain Mougenot reopened an issue Using rebuild for a moment it worked fine until I add parameters from maven-metadata_plugin. Might be specific to that plugin Parameter everest_version_CLASSIFIER was "blank" in the first build. The build ran fine I wanted to relaunch with the same parameter using rebuild The new build failed with this stacktrace FATAL: Null value not allowed as an environment variable: everest_version_CLASSIFIER java.lang.IllegalArgumentException: Null value not allowed as an environment variable: everest_version_CLASSIFIER at hudson.EnvVars.put(EnvVars.java:356) at eu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterValue.buildEnvVars(MavenMetadataParameterValue.java:80) at hudson.model.ParameterValue.buildEnvironment(ParameterValue.java:174) at hudson.model.ParametersAction.buildEnvVars(ParametersAction.java:89) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:950) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1046) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) versions : component version jenkins 1.642.2 maven-metadata_plugin 1.4.1 rebuild-plugin 1.25
[JIRA] [global-build-stats-plugin] (JENKINS-11925) Global Build Stats Search - Add times to the start and end date criteria
Title: Message Title David Hinske assigned an issue to David Hinske Jenkins / JENKINS-11925 Global Build Stats Search - Add times to the start and end date criteria Change By: David Hinske Assignee: Frédéric Camblor David Hinske 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-34507) failed execution in a new node during a parallel step is incorrectly displayed
Title: Message Title
J Knurek created an issue
Jenkins / JENKINS-34507
failed execution in a new node during a parallel step is incorrectly displayed
Issue Type:
Bug
Assignee:
Antonio Muñiz
Attachments:
Screen Shot 2016-04-29 at 11.50.29.png, Screen Shot 2016-04-29 at 11.50.47.png
Components:
pipeline-stage-view-plugin
Created:
2016/Apr/29 9:55 AM
Priority:
Critical
Reporter:
J Knurek
When parallel steps use a new node, and throws an error, the Stage View displays the wrong stage as failing
example pipeline:
try{
parallel a: {
execute_function('A')
}, b: {
execute_function('B')
}, c: {
execute_function('C')
},
failFast: false
} finally {
stage 'Cleanup'
echo "done with all"
}
def execute_function(name){
try {
stage "${name}"
node {
if(name == 'B'){ echo "FAILING HERE"; error 'died' }
else if (name == 'A') { echo "sleeping"; sleep 25; }
echo "future steps"
}
} catch(e) {
echo "error: ${e.toString()}"; throw e
}
}
here's a snippet of the
[JIRA] [_unsorted] (JENKINS-34504) Jenkins got unusable after upgrading to 2.0 version
Title: Message Title Daniel Beck commented on JENKINS-34504 Re: Jenkins got unusable after upgrading to 2.0 version Jenkins.log should help. And my wild guess is JENKINS-34494, for which we have a fix in the pipeline. 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] [categorized-view-plugin] (JENKINS-29273) Column misalignment from indentation is too severe
Title: Message Title Arno Moonen commented on JENKINS-29273 Re: Column misalignment from indentation is too severe I see the same "annoying" behavior. Would be nice if I could disable the indentation all together. 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-34506) successful parallel stages marked as failed
Title: Message Title
J Knurek created an issue
Jenkins / JENKINS-34506
successful parallel stages marked as failed
Issue Type:
Bug
Assignee:
Antonio Muñiz
Attachments:
Screen Shot 2016-04-29 at 10.47.52.png
Components:
pipeline-stage-view-plugin
Created:
2016/Apr/29 9:03 AM
Priority:
Major
Reporter:
J Knurek
This somewhat relates to JENKINS-33840 but the problem is that the stages that run in parallel, and/or finish after a failure get marked as "failed"
example pipeline:
stage 'parallel'
def error;
node {
try {
parallel(
b: { stage 'b'; error 'died' },
c: { stage 'c'; echo 'c' },
// this branch takes longer than b and c
a: { stage 'a'; sleep 25; echo'a' },
failFast: false
)
} finally {
stage 'Cleanup'
echo "done with all"
}
}
Expected behavior is that stage 'b' is marked as failure, the build is marked as failure, and all other stages are executed successfully. But as you can see in the screenshot, 'a' and 'Cleanup' are marked as 'failed'
NOTE:
[JIRA] [maven-metadata-plugin] (JENKINS-34505) Choosing version and classifier
Title: Message Title Sylvain Mougenot created an issue Jenkins / JENKINS-34505 Choosing version and classifier Issue Type: New Feature Assignee: Gesh Markov Components: maven-metadata-plugin Created: 2016/Apr/29 8:45 AM Priority: Minor Reporter: Sylvain Mougenot In the configuration we can set (hardcode) the classifier for the artifact. Would be nice if we could choose both version and classifier in the parameter combo. My use case is : we deploy in a testing environment (for non automated test) users are expected to test a particular 'candidate' version among several (available at the moment) same artifact (group id, artifact id, version) with different classifier according to actual feature we try to deploy (ex : eu.group.id:artifact:1.2.3-SNAPSHOT:fix-3210)
[JIRA] [parameterized-trigger-plugin] (JENKINS-34474) Upgrade parameterized trigger plugin to 2.x parent pom
Title: Message Title Armando Fernandez started work on JENKINS-34474 Change By: Armando Fernandez 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] [github-branch-source-plugin] (JENKINS-34259) Some links in multibranch projects are broken
Title: Message Title Manuel Jesús Recena Soto closed an issue as Fixed This fix has been included in branch-api-1.7. Jenkins / JENKINS-34259 Some links in multibranch projects are broken Change By: Manuel Jesús Recena Soto Status: In Progress 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] [credentials-plugin] (JENKINS-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title Armando Fernandez resolved as Done Jenkins / JENKINS-33863 Upgrade Credentials Plugin to new plugin parent pom Change By: Armando Fernandez 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] [_unsorted] (JENKINS-34504) Jenkins got unusable after upgrading to 2.0 version
Title: Message Title
Alex Al created an issue
Jenkins / JENKINS-34504
Jenkins got unusable after upgrading to 2.0 version
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
_unsorted
Created:
2016/Apr/29 8:22 AM
Environment:
Ubuntu 15.10
Priority:
Blocker
Reporter:
Alex Al
Here is what I get on main page after upgrading to Jenkins 2.0 and installing required plugins ("completing 2.0 version installation").
hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1020) at jenkins.model.Jenkins.(Jenkins.java:864) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at
[JIRA] [credentials-plugin] (JENKINS-31863) Sort Credentials list by name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31863 Re: Sort Credentials list by name Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/5c5fe9064e4d6be5b2ae4148e7997d31265868e7 Log: Merge pull request #42 from AndraeRay/sort-credential-selection JENKINS-31863 Sort Credential select list by credenial name Compare: https://github.com/jenkinsci/credentials-plugin/compare/1928c6c3b6d8...5c5fe9064e4d 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-31863) Sort Credentials list by name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31863 Re: Sort Credentials list by name Code changed in jenkins User: Andrae Raymond Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/4dd03c4a06fdc7cbc2c214a14c08dd9079bec15a Log: JENKINS-31863 - removed sorting distinction between upper and lowecase 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-31863) Sort Credentials list by name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31863 Re: Sort Credentials list by name Code changed in jenkins User: Andrae Raymond Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/93e7492d6ab9d9342db577afa6a47dd70de8d982 Log: JENKINS-31863 - minor fix changed tabs to spaces 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-31863) Sort Credentials list by name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31863 Re: Sort Credentials list by name Code changed in jenkins User: Andrae Raymond Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/68dc8c9607ec66f474824ec0489a38c205bfdd18 Log: JENKINS-31863 Sort Credential select list by credenial name 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-31863) Sort Credentials list by name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31863 Re: Sort Credentials list by name Code changed in jenkins User: Andrae Raymond Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/86c7b57a81e2552c1f8f8aacecfe24b47ffdb215 Log: JENKINS-31863 Made comparator class implement serializable due to BugFind Warning 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-31863) Sort Credentials list by name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31863 Re: Sort Credentials list by name Code changed in jenkins User: Andrae Raymond Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/1228f43a50d7b547755a49a2852b4a736d1943ec Log: JENKINS-31863 Made comparator class implement serializable due to BugFind Warning 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-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Armando Fernandez Path: pom.xml src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java http://jenkins-ci.org/commit/credentials-plugin/98945c79f60bd680a34c56f0b6caab7665e9134c Log: JENKINS-33863 Bump parent pom to 2.6. Fix FindBugs errors when built against 2.0-rc-1 baseline 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-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Armando Fernandez Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsScope.java src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java src/main/java/com/cloudbees/plugins/credentials/NameWith.java src/main/java/com/cloudbees/plugins/credentials/common/AbstractIdCredentialsListBoxModel.java src/main/java/com/cloudbees/plugins/credentials/common/IdCredentials.java http://jenkins-ci.org/commit/credentials-plugin/32f1a1e74534e34d6ef71221caf3859bb13e3cd3 Log: JENKINS-33863 Fix javadoc errors 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-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Stephen Connolly Path: pom.xml src/findbugs/excludesFilter.xml src/main/java/com/cloudbees/plugins/credentials/CredentialsScope.java src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java src/main/java/com/cloudbees/plugins/credentials/NameWith.java src/main/java/com/cloudbees/plugins/credentials/common/AbstractIdCredentialsListBoxModel.java src/main/java/com/cloudbees/plugins/credentials/common/IdCredentials.java src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/action.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/FileOnMasterKeyStoreSource/config.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/UploadedKeyStoreSource/Upload/complete.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/UploadedKeyStoreSource/Upload/index.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/UploadedKeyStoreSource/config.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/Messages_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials.jelly src/main/resources/index.jelly http://jenkins-ci.org/commit/credentials-plugin/c5f3e77d7cd26ef8355d433d75602706c827a50a Log: Merge pull request #44 from armfergom/JENKINS-33863 JENKINS-33863 Upgrade to plugin parent pom 2.4 Compare: https://github.com/jenkinsci/credentials-plugin/compare/49a06e8c166a...c5f3e77d7cd2 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
[JIRA] [credentials-plugin] (JENKINS-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Armando Fernandez Path: pom.xml http://jenkins-ci.org/commit/credentials-plugin/22867c36913919e5b32731c37a00c1a52afb7cf9 Log: JENKINS-33863 Remove unnecessary properties. 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-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Armando Fernandez Path: src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/action.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/FileOnMasterKeyStoreSource/config.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/UploadedKeyStoreSource/Upload/complete.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/UploadedKeyStoreSource/Upload/index.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/UploadedKeyStoreSource/config.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/Messages_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials.jelly src/main/resources/index.jelly http://jenkins-ci.org/commit/credentials-plugin/6750b736bfc32b193f02384702ace0154402ef01 Log: JENKINS-33863 Fix injected tests 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-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Armando Fernandez Path: pom.xml src/findbugs/excludesFilter.xml http://jenkins-ci.org/commit/credentials-plugin/a8ed6e3321012a1a0c0d3109e8ada731ec75816d Log: JENKINS-33863 No need to have the windbags exclusions 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-33863) Upgrade Credentials Plugin to new plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33863 Re: Upgrade Credentials Plugin to new plugin parent pom Code changed in jenkins User: Armando Fernandez Path: pom.xml http://jenkins-ci.org/commit/credentials-plugin/5aa556d789ece6272ea70260f7305d0d087cb99f Log: JENKINS-33863 Upgrade to new parent pom 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-commons-plugin] (JENKINS-34503) Add username/password support for docker registry
Title: Message Title Gijs Kunze created an issue Jenkins / JENKINS-34503 Add username/password support for docker registry Issue Type: New Feature Assignee: Jesse Glick Components: docker-commons-plugin, docker-workflow-plugin Created: 2016/Apr/29 8:09 AM Labels: workflow docker Priority: Minor Reporter: Gijs Kunze Currently with the docker workflow plugin you have to specify credentials, however in our case we're using the AWS's container registry which don't have fixed credentials. Instead, you can use an AWS api call to retrieve temporary credentials (valid 12 hours). Ideally, a three-parameter withRegistry (registry, username, password) would allow us to log in with these kinds of credentials. Add Comment
[JIRA] [github-branch-source-plugin] (JENKINS-34259) Some links in multibranch projects are broken
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34259 Re: Some links in multibranch projects are broken Code changed in jenkins User: recena Path: src/main/java/jenkins/branch/BaseEmptyView.java http://jenkins-ci.org/commit/branch-api-plugin/c0b4d479a0b5871a69e13e9c7181b9a2e2756460 Log: JENKINS-34259 Disable Edit View option in EmptyViews 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-34259) Some links in multibranch projects are broken
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34259 Re: Some links in multibranch projects are broken Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/BaseEmptyView.java src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java http://jenkins-ci.org/commit/branch-api-plugin/e5363900cc94bff2674adee2f59f3ff6d2cd5d00 Log: Merge pull request #38 from recena/JENKINS-34259 JENKINS-34259 Some links are broken in the Welcome page Compare: https://github.com/jenkinsci/branch-api-plugin/compare/3e8a70c387fb...e5363900cc94 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.
