[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley commented on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Jonas Hanschke, you can check my ongoing PR (https://github.com/jenkinsci/git-client-plugin/pull/433, branch is based on v2.8.1), and recompile/install the plugin while change is being reviewed and integrated by Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.570.1566898861158%40Atlassian.JIRA.
[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Helloalso facing this issue in some cases where files where modified/added into source branch of PR.Any idea when/if LFS credentials support will be added to the merge portion of the git plugin? Maybe at least providing some implementation guidance for a future contributionBR Edit: [https://github.com/jenkinsci/git-client-plugin/pull/433] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.2307.1560853501215%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Helloalso facing this issue in some cases where files where modified/added into source branch of PR.Any idea when/if LFS credentials support will be added to the merge portion of the git plugin? Maybe at leat least providing some implementation guidance for a future contributionBR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.25250.1560266641018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Geoffroy Jabouley commented on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command Hello also facing this issue in some cases where files where modified/added into source branch of PR. Any idea when/if LFS credentials support will be added to the merge portion of the git plugin? Maybe at leat providing some implementation guidance for a future contribution BR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183359.1498813755000.24984.1560246420425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56789) Add support for Matrix Aggregation
Title: Message Title Geoffroy Jabouley created an issue Jenkins / JENKINS-56789 Add support for Matrix Aggregation Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2019-03-28 09:09 Environment: Jenkins LTS 1.207.3 GitHub plugin 1.29.4 Flexible Publish plugin 0.15.2 Priority: Major Reporter: Geoffroy Jabouley Plugin is not supporting Matrix Aggregation, when activated through the Flexible Publish, i got the following message: [Never seen - one hopes :-)] WARNING: Condition for Matrix Aggregation is configured for Set GitHub commit status (universal) which does not support aggregation It can be helpfull when working with Matrix jobs, let's say you have 20 config per build then you could only post back to GitHub the overall build result from the parent job. Add Comment
[JIRA] (JENKINS-44657) Build history not copied after renaming the job's parent folder when using custom build directories
Title: Message Title Geoffroy Jabouley commented on JENKINS-44657 Re: Build history not copied after renaming the job's parent folder when using custom build directories We are still facing this issue using LTS 2.107.3 Could you point us to the LTS version which support this renaming feature without loss of history? BR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [startup-trigger-plugin] (JENKINS-32659) Cannot start a job located in a Folder
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-32659 Re: Cannot start a job located in a Folder I've added a link to the PR fixing this issue. Sadly this plugin does not seem to get to much attention, it's been a month since the PR is waiting for feedbacks 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy What was at the beginning a simple patch supposed to fix a regression introduced in march 2015 (it's been a year now!) still cannot be mainlined because someone has decided instead to include it in a much wider story/task of implementing JNLP3 support. Why not keeping the scope of this fix simple? 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Hello do you think this fix will make its way to a jenkins 1.X LTS release before jenkins 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] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax I can manage the PR on monday, if you're ok with the fix: remove L183 to L185 of ScmContext.groovy What about extending a little bit the checks on test case "call git scm methods" to ensure defaults values for all fields? 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] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax Thanks for your answers the test case "call git scm methods" does not seem to check anything but the remote and branch fields. https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmContextSpec.groovy#L1173 But i'm not familiar with groovy testing. 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] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax Maybe the default value shall be set to false here:https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitContext.groovy#L118 Or this line is wrong:https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ScmContext.groovy#L184 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] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax Maybe the default value shall be set to false here: https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitContext.groovy#L118 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] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title
Geoffroy Jabouley created an issue
Jenkins / JENKINS-33482
Git scm option "Create tag for each build" is activated by default for oneliner syntax
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
11/Mar/16 1:57 PM
Environment:
jenkins 1.596.3 LTS job-dsl plugin 1.39 git plugin 2.4.0
Priority:
Major
Reporter:
Geoffroy Jabouley
scm {
git {
remote {
url ('ssh://blabla')
}
}
}
set by defaut option "Create Tags for each build" to false (true in the build.xml)
scm {
git ('ssh://blabla')
}
Activates the option by default (false in the build.xml)
Unless specified, i think the option shall be deactivated by default for all syntaxes.
[JIRA] [xunit-plugin] (JENKINS-32920) Support for url for stylesheet in Custom Tool
Title: Message Title Geoffroy Jabouley created an issue Jenkins / JENKINS-32920 Support for url for stylesheet in Custom Tool Issue Type: Improvement Assignee: Gregory Boissinot Components: xunit-plugin Created: 12/Feb/16 4:20 PM Environment: Jenkins LTS 1.596.3 xunit 1.100 Priority: Major Reporter: Geoffroy Jabouley When using the Custom Tool option, it is mandatory to provide a custom stylesheet to convert unit tests results to Junit format. By following the documentation, we stored the xsl file in $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl And we configured the plugin with a custom tool stylesheet pointing to $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl This is not working when building on a slave machine, as the path $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl is not relevant on a slave (only for the master) What about supporting URL instead, so using $JENKINS_URL/userContent/cunit/cunit-to-junit.xsl could work.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy thanks for clarification. The sooner the better 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Just for clarification: how do we set the proxy exclusion list with this patch? Is the environment variable "no_proxy" enought, or do we have to provide a "-Dhttp.nonProxyHosts" java system property when starting the jenkins slave? Looking forward a new release in a LTS 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] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Title: Message Title Geoffroy Jabouley commented on JENKINS-25111 Re: Ability to Copy Artifacts from a Phase Job Hi will this feature support multijob of multijob? Lets say i have the following job organization: multiJobA --> PhaseA1 --> jobA1 --> PhaseA2 --> MultijobB --> PhaseB1 > jobB1 I need to retrieve an artefact from jobA1 in jobB1. We currently pass the JOBA1_BUILD_NUMBER variable as parameter of MultijobB. Any change to use this new functionality with our use case? Add Comment
[JIRA] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Title: Message Title
Geoffroy Jabouley edited a comment on JENKINS-25111
Re: Ability to Copy Artifacts from a Phase Job
Hiwill this feature support multijob of multijob?Lets say i have the following job organization: {noformat} multiJobA|--> PhaseA1|--> jobA1|--> PhaseA2 |--> MultijobB multijobB |--> PhaseB1 |> jobB1 {noformat} I need to retrieve an artefact from jobA1 in jobB1.We currently pass the JOBA1_BUILD_NUMBER variable as parameter of MultijobB.Any change to use this new functionality with our use case?
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] [startup-trigger-plugin] (JENKINS-32659) Cannot start a job located in a Folder
Title: Message Title Geoffroy Jabouley created an issue Jenkins / JENKINS-32659 Cannot start a job located in a Folder Issue Type: Bug Assignee: ashlux Components: startup-trigger-plugin Created: 27/Jan/16 10:16 PM Environment: jenkins lts 1.596.3 startup-trigger-plugin 2.4 Priority: Major Reporter: Geoffroy Jabouley During Jenkins boot, if a job located in a Folder (Folder plugin) is configured to be executed, the startup-trigger-plugin does not "see" it, so nothing is executed. Would be glad to do the PR, if somebody can point me to some resources to support Folder plugin. Add Comment
[JIRA] [multijob-plugin] (JENKINS-32034) Multijob does not detect if a phase job is cancelled while in build queue
Title: Message Title
Geoffroy Jabouley created an issue
Jenkins / JENKINS-32034
Multijob does not detect if a phase job is cancelled while in build queue
Issue Type:
Bug
Assignee:
Unassigned
Components:
multijob-plugin
Created:
11/Dec/15 2:47 PM
Environment:
Jenkins 1.596.3 lts multijob 1.18
Priority:
Critical
Reporter:
Geoffroy Jabouley
Whenever a Multijob is running, if one of its phase job is aborded while in build queue, the multijob never detects the cancellation and is stuck infinitely.
Step to reproduce (very easy): 1) create 1 freestyleJob, configure it to run on a slave label which does not exist (so it will stay in queue forever) 2) create 1 multijob, add a phase which trigger the freestyleJob 3) Start the multijob 4) manually abord the freestyleJob while it is in queue
Expected: multijob detects the cancellation, and act as configured in the case of an aborded job ("Abort all other job" config)
Result: multijob does not detect the cancellation, and is running forever.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Hellocould this issue fix be included in the incoming LTS version?Regads 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Hello could this issue be included in the incoming LTS version? Regads 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] [logfilesizechecker-plugin] (JENKINS-30797) Activate the plugin at Jenkins Global level (not per job)
Title: Message Title Geoffroy Jabouley created an issue Jenkins / JENKINS-30797 Activate the plugin at Jenkins Global level (not per job) Issue Type: Improvement Assignee: Stefan Brausch Components: logfilesizechecker-plugin Created: 05/Oct/15 1:52 PM Environment: logfilesizechecker-plugin:1.2 Priority: Minor Reporter: Geoffroy Jabouley Could it be possible to enable this feature at Jenkins instance level? I would like to add such "watchdog" for all my jenkins jobs (past/present/future), but relying on the user to activate this option in the job configuration page does not seems reliable. On the global configuration page, in the section "Abort Build if log file gets too big", a tickbox to activate the feature for all jobs and another to "fail the build"
[JIRA] [core] (JENKINS-30634) Add HTML anchor to each section of configuration pages (master + jobs)
Title: Message Title Geoffroy Jabouley created an issue Jenkins / JENKINS-30634 Add HTML anchor to each section of configuration pages (master + jobs) Issue Type: Improvement Assignee: Unassigned Components: core Created: 24/Sep/15 4:47 PM Labels: anchor Priority: Minor Reporter: Geoffroy Jabouley It could be nice to be able to refer to each configuration sections of Jenkins or a Job using HTML anchor. An example: Accessing the "Subversion" configuration part of the global configure page of Jenkins using /configure#Subversion Use Case: I am writing an embedded user guide of a Jenkins instance, which sits in the userContent folder. I am able to generate a custom user guide per instance, so any links in the doc point to a valid url of the instance. But when describing global configuration, i am just able to say: "go to /configure and search for Subversion". I would prefer writing: "go to /configure#Subversion
[JIRA] [job-dsl-plugin] (JENKINS-27921) Multijob generation failed when upgrading from 1.29 to 1.32
Geoffroy Jabouley commented on JENKINS-27921 Multijob generation failed when upgrading from 1.29 to 1.32 Hi Daniel Thanks a lot for the explanation. Is this still a regression in the job-dsl plugin, as it was doing fine in prior versions without the "delegate.job" call? Or is this behavior the correct one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27921) Multijob generation failed when upgrading from 1.29 to 1.32
Geoffroy Jabouley
created JENKINS-27921
Multijob generation failed when upgrading from 1.29 to 1.32
Issue Type:
Bug
Assignee:
Daniel Spilker
Attachments:
jobdsl-multijob-groovyloop.txt
Components:
job-dsl-plugin
Created:
13/Apr/15 4:05 PM
Description:
I am using jobdsl plugin to generate a multijob.
The included code snippet works well with v1.29.
It uses a configuration.txt file in the workspace containing several 3-uples data: name,path,config
It then iterates on each uple and add the corresponding job to the multijob phase.
When upgrading to 1.32 (to get support for Multijob 'ALWAYS' continuation condition), i am facing 2 deprecation warnings AND the following error:
Processing provided DSL script
Warning: job is deprecated (DSL script, line 3)
Warning: name is deprecated (DSL script, line 4)
FATAL: No signature of method: javaposse.jobdsl.dsl.jobs.FreeStyleJob.prop() is applicable for argument types: (java.lang.String, java.lang.String) values: RELEASE_BUILD_NUMBER, ${RELEASE_BUILD_NUMBER}]
Possible solutions: grep(), dump(), grep(java.lang.Object), wait(), any(), find()
groovy.lang.MissingMethodException: No signature of method: javaposse.jobdsl.dsl.jobs.FreeStyleJob.prop() is applicable for argument types: (java.lang.String, java.lang.String) values: [RELEASE_BUILD_NUMBER, ${RELEASE_BUILD_NUMBER}
Possible solutions: grep(), dump(), grep(java.lang.Object), wait(), any(), find()
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:78)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
at script142894070212564931370$_run_closure1_closure3_closure6_closure7_closure8.doCall(script142894070212564931370.groovy:29)
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 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.Closure.call(Closure.java:415)
at groovy.lang.Closure.call(Closure.java:428)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.with(DefaultGroovyMethods.java:196)
at org.codehaus.groovy.runtime.dgm$926.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoMetaMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:313)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:64)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:69)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at javaposse.jobdsl.dsl.JobParent.processJob(JobParent.groovy:73)
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 org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:272)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:52)
at
[JIRA] [repo-plugin] (JENKINS-26836) Add support for workflow plugins
Geoffroy Jabouley created JENKINS-26836 Add support for workflow plugins Issue Type: New Feature Assignee: Unassigned Components: repo-plugin Created: 06/Feb/15 3:54 PM Description: It would be nice to use the repo-plugin as a scm step in a Workflow job type. Currently, the repo-plugin does not support Workflow. Here is a link with actions to take on the source code to enable such support: https://github.com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md#supporting-workflow-from-an-scm-plugin A bump in the Jenkins version would be necessary, at least to the 1.580.1 LTS. Project: Jenkins Labels: workflow Priority: Major Reporter: Geoffroy Jabouley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-24382) Convert cunit XML to junit XML in xUnit plugin
Geoffroy Jabouley commented on JENKINS-24382 Convert cunit XML to junit XML in xUnit plugin Hello there is an available xsl style sheet that do pretty much the job: https://bitbucket.org/mcdeck/cunit-to-junit/src/3cd904af25d1a8d5da490737a68395ac646f6b42/cunit-to-junit.xsl To use it, follow the guideline here: https://github.com/shawnliang/cunit-to-junit (Xunit report -- custom tool -- set CUnit file pattern and specify the custom stylesheet) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
