[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Doron Shai commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries MOVING TO GITLAB CI - THANKS FOR THE AMAZING SUPPORT 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.178297.1485467365000.7194.1561375441775%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Doron Shai commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries William Brode I do not see that the lightweight checkout actually solve this issue. I do not understand why and how this issue is still open. this is a MAJOR problem with Jenkins 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] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title
Doron Shai edited a comment on JENKINS-41497
Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
I see this issue once again with Jenkins {color:#ff}* 2.107.2 *{color}, on *{color:#14892c}2.107.1{color}* it is working just fine
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Doron Shai updated an issue Jenkins / JENKINS-41497 Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries Change By: Doron Shai Comment: I see this issue again on plugin 2.9 and Jenkins 2.107.2.Does someone knows if this can be solved somehow? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Doron Shai reopened an issue I see this issue once again with Jenkins 2.107.2 Jenkins / JENKINS-41497 Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries Change By: Doron Shai Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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,
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Doron Shai commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries I see this issue again on plugin 2.9 and Jenkins 2.107.2. Does someone knows if this can be solved somehow? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40796) IOException: Failed to write author ERROR when using api/xml
Title: Message Title Doron Shai reopened an issue i thought that this ticket is a duplication of 24317 but this is wrong. Therefore this ticket is relevant Jenkins / JENKINS-40796 IOException: Failed to write author ERROR when using api/xml Change By: Doron Shai Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Title: Message Title Doron Shai commented on JENKINS-24317 Re: Nullpointer Exception on build in version 1.576 can't see output and fails when using api/xml for build url, i get IOException: Failed to write author ERROR with this log java.io.IOException: Failed to write author at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:206) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:276) at hudson.model.Api.doXml(Api.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at
[JIRA] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Title: Message Title Doron Shai reopened an issue Issue is reoccurring when working with Jenkins 2.19.4 / 2.19.1 / 2.7.1 Assembla Auth Plugin 1.11 Credentials Plugin 2.1.10 Ubuntu 16.04 LTS Jenkins / JENKINS-24317 Nullpointer Exception on build in version 1.576 can't see output and fails Change By: Doron Shai Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-24350) NPE/IOException Failed to write author
Title: Message Title Doron Shai updated an issue Jenkins / JENKINS-24350 NPE/IOException Failed to write author Change By: Doron Shai Component/s: assembla-auth Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24350) NPE/IOException Failed to write author
Title: Message Title Doron Shai resolved as Duplicate Jenkins / JENKINS-24350 NPE/IOException Failed to write author Change By: Doron Shai Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24350) NPE/IOException Failed to write author
Title: Message Title Doron Shai reopened an issue Issue is reoccurring when working with Jenkins 2.19.4 / 2.19.1 / 2.7.1 Assembla Auth Plugin 1.11 Credentials Plugin 2.1.10 Ubuntu 16.04 LTS Jenkins / JENKINS-24350 NPE/IOException Failed to write author Change By: Doron Shai Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40796) IOException: Failed to write author ERROR when using api/xml
Title: Message Title Doron Shai closed an issue as Duplicate Jenkins / JENKINS-40796 IOException: Failed to write author ERROR when using api/xml Change By: Doron Shai Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40796) IOException: Failed to write author ERROR when using api/xml
Title: Message Title Doron Shai assigned an issue to Unassigned Jenkins / JENKINS-40796 IOException: Failed to write author ERROR when using api/xml Change By: Doron Shai Summary: NPE on getUserByUsername IOException: Failed to write author ERROR when using api/xml Environment: Jenkins 2. 5 (installed via apt-get upgrade), master only Also: Jenkins 19.4 / 2. 19.1 / 2. 7 (installed via apt-get install) .1 Assembla Auth Plugin 1. 06 11 Credentials Plugin 2. 1. 27 10 Ubuntu 14 16 .04 .4 LTS (GNU/Linux 3.13.0-74-generic x86_64) Assignee: Pavel Dotsulenko Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40796) NPE on getUserByUsername when using api/xml
Title: Message Title Doron Shai created an issue Jenkins / JENKINS-40796 NPE on getUserByUsername when using api/xml Issue Type: Bug Assignee: Pavel Dotsulenko Components: assembla-auth, core Created: 2017/Jan/04 8:48 AM Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Also: Jenkins 2.7 (installed via apt-get install) Assembla Auth Plugin 1.06 Credentials Plugin 1.27 Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) Labels: auth authentication Priority: Major Reporter: Doron Shai Jenkins Authorization is integrated with Assembla's auth. Security Realm uses Assembla Auth Plugin. Jobs finish with FAILURE status with the following error message (always the last item in the console log) : FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken at com.assembla.jenkinsci.plugin.AssemblaSecurityRealm.loadUserByUsername(AssemblaSecurityRealm.java:333) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1050) at hudson.model.User.get(User.java:395) at hudson.model.User.get(User.java:364) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at
[JIRA] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Doron Shai commented on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) When we will have a fix for it? When i downgraded to 2.19.4 i still have this problem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16024) SCM Sync fails to check in any files
Title: Message Title Doron Shai reopened an issue Jenkins / JENKINS-16024 SCM Sync fails to check in any files Change By: Doron Shai Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16024) SCM Sync fails to check in any files
Title: Message Title
Doron Shai edited a comment on JENKINS-16024
Re: SCM Sync fails to check in any files
I have similar issues even that the ticket is closed. When I just started using the plugin it worked for an hour and then, when i deleted a job it stopped working and even worse, When looking at {color:#654982}*_ /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/ _*{color} I can see that all the jobs were disappeared and also from the git repo while they were still avail on the jenkins.I am using SCM-Sync 0.0.10 and Jenkins 2.19.4
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16024) SCM Sync fails to check in any files
Title: Message Title Doron Shai commented on JENKINS-16024 Re: SCM Sync fails to check in any files I have similar issues even that the ticket is closed. When I just started using the plugin it worked for an hour and then, when i deleted a job it stopped working and even worse, When looking at /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/ I can see that all the jobs were disappeared and also from the git repo while they were still avail on the jenkins. I am using SCM-Sync 0.0.10 and Jenkins 2.19.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [scm-sync-configuration-plugin] (JENKINS-32125) New Jobs are not synced to Repo
Title: Message Title Doron Shai created an issue Jenkins / JENKINS-32125 New Jobs are not synced to Repo Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 17/Dec/15 2:31 PM Environment: Jenkins ver. 1.638 SCM Sync Configuration Plugin ver. 0.0.9 Priority: Major Reporter: Doron Shai When i create new Jobs, the plugin is not syncing these new jobs to my repo. Only when I change these jobs (even just disable > enable) then these jobs are synced... Add Comment
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Title: Message Title Doron Shai commented on JENKINS-24686 Re: scm-sync-configuration fails if job name contains whitespace Why this pull request is not part of the 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] [job-dsl-plugin] (JENKINS-31654) Jobs of MultiJob type are not created while jenkins report success
Title: Message Title Doron Shai commented on JENKINS-31654 Re: Jobs of MultiJob type are not created while jenkins report success BINGO - thanks a lot! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31654) Jobs of MultiJob type are not created while jenkins report success
Title: Message Title Doron Shai closed an issue as Not A Defect Jenkins Restart solved the problem Jenkins / JENKINS-31654 Jobs of MultiJob type are not created while jenkins report success Change By: Doron Shai Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31654) Jobs of MultiJob type are not created while jenkins report success
Title: Message Title Doron Shai commented on JENKINS-31654 Re: Jobs of MultiJob type are not created while jenkins report success Here is the exception: createOrUpdateConfig for example Nov 19, 2015 3:54:41 PM WARNING javaposse.jobdsl.plugin.JenkinsJobManagement createNewItem Error writing config for new item example. java.io.IOException: Unable to read /opt/jenkins/jobs/example/config.xml at hudson.XmlFile.read(XmlFile.java:144) at hudson.model.Items.load(Items.java:319) at hudson.model.ItemGroupMixIn$4.call(ItemGroupMixIn.java:264) at hudson.model.ItemGroupMixIn$4.call(ItemGroupMixIn.java:262) at hudson.model.Items.whileUpdatingByXml(Items.java:95) at hudson.model.ItemGroupMixIn.createProjectFromXML(ItemGroupMixIn.java:262) at jenkins.model.Jenkins.createProjectFromXML(Jenkins.java:3039) at javaposse.jobdsl.plugin.JenkinsJobManagement.createNewItem(JenkinsJobManagement.java:529) at javaposse.jobdsl.plugin.JenkinsJobManagement.createOrUpdateConfig(JenkinsJobManagement.java:135) at javaposse.jobdsl.dsl.JobManagement$createOrUpdateConfig.call(Unknown Source) at javaposse.jobdsl.plugin.InterruptibleJobManagement.createOrUpdateConfig(InterruptibleJobManagement.groovy:44) at javaposse.jobdsl.dsl.DslScriptLoader.extractGeneratedJobs(DslScriptLoader.java:150) at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngineForParent(DslScriptLoader.java:88) at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngine(DslScriptLoader.java:132) at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:220) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) 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:381) Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: com.tikal.jenkins.plugins.multijob.MultiJobProject at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at
[JIRA] [job-dsl-plugin] (JENKINS-31654) Jobs of MultiJob type are not created while jenkins report success
Title: Message Title
Doron Shai created an issue
Jenkins / JENKINS-31654
Jobs of MultiJob type are not created while jenkins report success
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
19/Nov/15 1:56 PM
Environment:
Jenkins ver. 1.609.2 Plugin Job DSL 1.40
Priority:
Minor
Reporter:
Doron Shai
I am trying to create a MultiJob Job using DSL, and it even that the log say everything is Green, the Job is not created.
Any Idea?
multiJob('example') {
steps {
phase('Second') {
phaseJob('JobZ') {
parameters {
propertiesFile('my1.properties')
}
}
}
}
}
the log of the Build is:
Building in workspace /opt/jenkins/workspace/CreateMJ
Processing provided DSL script
Existing items:
GeneratedJob{name='example'}
Finished: SUCCESS
[JIRA] [job-dsl-plugin] (JENKINS-31654) Jobs of MultiJob type are not created while jenkins report success
Title: Message Title Doron Shai commented on JENKINS-31654 Re: Jobs of MultiJob type are not created while jenkins report success Tested it also on Jenkins ver. 1.638 and there it is wokring. 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] [gerrit-trigger-plugin] (JENKINS-27873) Gerrit trigger to support custom labels
Title: Message Title Doron Shai commented on JENKINS-27873 Re: Gerrit trigger to support custom labels Very important Feature 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-25484) Add support for multijob to retry only failed portions of a matrix build.
Title: Message Title Doron Shai commented on JENKINS-25484 Re: Add support for multijob to retry only failed portions of a matrix build. from my end, support for retry when child job is called and failed is really needed. at the moment if i will call job X from a MulltiJob and X will fail from some silly reason which will not happen again / will re happen just few times, a retry of X will not be known by the Multijob Father. When i say retry of Child Job i mean to use the Naginator plugin (https://wiki.jenkins-ci.org/display/JENKINS/Naginator+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] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Doron Shai edited a comment on JENKINS-18125 Changelog empty or contains all changes looks like no one is on it as last comment is 1 year a go. Same error also on my Server. the PR are always empty. For me it is really bad since I use the incremental build of maven jobs and it needs this delta data 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] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Doron Shai commented on JENKINS-18125 Changelog empty or contains all changes Same error also on my Server. the PR are always empty. For me it is really bad since I use the incremental build of maven jobs and it needs this delta data 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] [gerrit-trigger-plugin] (JENKINS-25428) Pending Gerrit Job details overlay the whole jenkins screen
Doron Shai created JENKINS-25428 Pending Gerrit Job details overlay the whole jenkins screen Issue Type: Bug Assignee: rsandell Attachments: GERRIT.jpg Components: gerrit-trigger-plugin Created: 04/Nov/14 10:07 AM Description: When there are pending Jobs with Gerrit event Listener the Gerrit Job details of the pending build overlay the whole jenkins screen in a way that is really disturbing. Environment: Jenkins ver. 1.588 Gerrit 2.11.1 Linux RHEL 6.5 Project: Jenkins Priority: Critical Reporter: Doron Shai 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] [gerrit-trigger-plugin] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai resolved JENKINS-24948 as Fixed Git/Gerrit environment Variables are not available in Maven projects Change By: Doron Shai (04/Nov/14 10:10 AM) Status: Open Resolved Resolution: Fixed 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects it was not released yet 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects is there a planned fix for this issue? 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects for the job that use git poll to trigger build i get these results, and i am able to get the params using echo but it should be avaialbe as out of the box as it is in other job types like Multijob 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] [git] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
Doron Shai commented on JENKINS-23606 Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits Also here this issue is a real problem 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
Doron Shai closed JENKINS-24924 as Not A Defect Gerrit trigger is not wokring with Maven Projects My mistake Change By: Doron Shai (05/Oct/14 12:22 PM) Status: Resolved Closed 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
Doron Shai reopened JENKINS-24924 Gerrit trigger is not wokring with Maven Projects of-course it is possible to add the Trigger to the Job configuration - but when doing so the job is not triggered Change By: Doron Shai (01/Oct/14 10:26 AM) Resolution: NotADefect Status: Resolved Reopened 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai created JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Issue Type: Bug Assignee: rsandell Components: gerrit-trigger, git Created: 01/Oct/14 10:32 AM Description: In Maven project when the trigger is set to Poll git SCM or Gerrit trigger the Git/Gerrit parameters are not part of the maven project environment Variables as they are in freestyle projects and Multijob Projects. i am refering to these environment Variables: GERRIT_EVENT_TYPE GERRIT_CHANGE_URL GERRIT_BRANCH GERRIT_CHANGE_OWNER_EMAIL GERRIT_CHANGE_SUBJECT GIT_COMMIT GIT_URL GIT_BRANCH Environment: Jenkins 1.581 GT 2.11.1 Git 2.2.6 Project: Jenkins Labels: plugin maven git gerrit Priority: Major Reporter: Doron Shai 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] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Doron Shai commented on JENKINS-14193 EnvInject doesnt pass variables defined in prebuild step if maven project is used Any estimation if this issue will be fixed and when? it is quite an annoying bug 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] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
Doron Shai created JENKINS-24924 Gerrit trigger is not wokring with Maven Projects Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 30/Sep/14 9:50 AM Description: I am Jenkins(1.581) and the Gerrit Trigger(2.11.1) to launch builds from Gerrit in order to verify code. This is working fine as long as the project in Jenkins is configured as a "Free style" project. However, When I'm using the "Build a maven2/3 project" option in order to take advantage of maven specific properties which I can't get from the "Free style" option. For some reason, Jenkins doesn't seem to trigger builds using this option. Nothing at all happens when I submit code to Gerrit which under normal circumstances should be picked up. I'm actually wondering if the Gerrit trigger is meant to work with Jenkins projects configured as a maven2/3 job or maybe it is the case that I can only use the Free style option in order to do this. Please make it work See discussion here (http://stackoverflow.com/questions/10609598/how-to-trigger-maven-specific-job-in-jenkins-with-gerrit Environment: Jenkins 1.581 Gerrit Plugin 2.11.1 Project: Jenkins Priority: Critical Reporter: Doron Shai 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] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support
Doron Shai commented on JENKINS-18361 Provide build report API support This is Super important in order to make this Plugin the standard way of running multiple jobs. At the moment, If i want to have a report that is calculated at the end of the MultiJob Project i have to do some magics which are very ugly. I hope that you will manage to provide such an ability soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support
Doron Shai edited a comment on JENKINS-18361 Provide build report API support This is Super important in order to make this Plugin the standard way of running multiple jobs. At the moment, If i want to have a report that is calculated at the end of the MultiJob Project i have to do some magics which are very ugly. The main reason is that in order to display build results of inner jobs, i have to know the build number of this jobs. At the moment there is no nice way to do so. I hope that you will manage to provide such an ability soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17710) Windows: Using Shallow Clone cause a git fatal error - pack has 1 unresolved delta (index-pack failed)
Doron Shai created JENKINS-17710 Windows: Using Shallow Clone cause a git fatal error - pack has 1 unresolved delta (index-pack failed) Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 23/Apr/13 5:29 AM Description: When i use the Shallow clone option in a Job that use the git plugin, i get the following Error: ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "C:\Program Files (x86)\Git\bin\git.exe fetch -t origin +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: fatal: pack has 1 unresolved delta fatal: index-pack failed removing the shallow clone option and then everything works good. Environment: Git Plugin 1.3.0, Jenkins 1.505, Windows 2008 Project: Jenkins Labels: git Priority: Major Reporter: Doron Shai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:391)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?ownerId=doronshaiavatarId=11478;
alt= height=48 width=48 border=0 align=left style=padding:0;margin:
0 16px 16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=doronshai
id=email_doronshai
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=doronshai;
style=color:#355564;Doron Shai/a
reopened img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
href='https://issues.jenkins-ci.org/browse/JENKINS-5537'JENKINS-5537/a
/div
[JIRA] (JENKINS-14955) Wrong links created on summary on a multijob execution
Doron Shai commented on JENKINS-14955 Wrong links created on summary on a multijob execution Any chance this will be solved? I believe this is a small fix for a really annoying bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16058) [Email-Ext] Not able to use a parameter that i define in the Job
Doron Shai
created JENKINS-16058
[Email-Ext] Not able to use a parameter that i define in the Job
Issue Type:
Bug
Affects Versions:
current
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
06/Dec/12 3:15 PM
Description:
Hello,
At the end of my Job that I set a post build step that will send a mail.
This mail format is HTML and I am trying to use few variables.
I am able to use Tokens such: $PROJECT_NAME, $BUILD_NUMBER, $BUILD_STATUS but when I want to use a System Variable then i get nothing. (This variable is being set at the beginning of the Job using the "This build is parameterized"
The system Variable name is JobBranch and I already tried to call it in all the ways i know:
${ENV, JobBranch}
${ENV, %JobBranch%}
%JobBranch%
$JobBranch
for all of these i get nothing (It is actually print this text as it is ...)
What i am doing wrong?
Doron
Environment:
Win Server 2008 R2, Jenkins 1.7
Project:
Jenkins
Labels:
email
email-ext
token
Priority:
Major
Reporter:
Doron Shai
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16058) [Email-Ext] Not able to use a parameter that i define in the Job
Doron Shai
closed JENKINS-16058 as Not A Defect
[Email-Ext] Not able to use a parameter that i define in the Job
Managed to find the answer after some more digging in the Net.
the way to use this Token is ${ENV,var="variable_name"}
I found the answer Here
Change By:
Doron Shai
(06/Dec/12 3:25 PM)
Status:
Open
Closed
Fix Version/s:
current
Resolution:
NotADefect
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14952) Downstream job build links are broken when jenkins is not hosted on the root context
Doron Shai commented on JENKINS-14952 Downstream job build links are broken when jenkins is not hosted on the root context Same issue as https://issues.jenkins-ci.org/browse/JENKINS-14955 and https://issues.jenkins-ci.org/browse/JENKINS-15965 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15965) Currently building links point to wrong downstream projects when concurent builds are active
Doron Shai commented on JENKINS-15965 Currently building links point to wrong downstream projects when concurent builds are active Duplicated with https://issues.jenkins-ci.org/browse/JENKINS-14955 and https://issues.jenkins-ci.org/browse/JENKINS-14952 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16048) MultiJob Detailed Table is missing when non valid MultiJob phase exits
Doron Shai created JENKINS-16048 MultiJob Detailed Table is missing when non valid MultiJob phase exits Issue Type: Task Affects Versions: current Assignee: Unassigned Attachments: B.jpg Components: jenkins-multijob-plugin Created: 05/Dec/12 4:04 PM Description: Once there is a non valid MultiJob Phase (i.e. with a Jub name that doesn't exists), the MultiJob Detailed Table (See Image) is missing. In this case, I think that the plugin should do 1 of the following: 1. When a job is not valid, the save button should be disabled / error message will be displayed to the user after click on save (so it will not be saved in this way). OR 2. An error message should be displayed instead of the missing table. Due Date: 20/Feb/13 12:00 AM Environment: Win Server 2008, Jenkins 1.490, MultiJob 1.7 Fix Versions: current Project: Jenkins Labels: plugin jenkins multi-job Priority: Major Reporter: Doron Shai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15965) Currently building links point to wrong downstream projects when concurent builds are active
Doron Shai commented on JENKINS-15965 Currently building links point to wrong downstream projects when concurent builds are active You are right This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16013) [jenkins-multijob-plugin] Use custom workspace is not working with the MultiJob Plugin
Doron Shai updated JENKINS-16013 [jenkins-multijob-plugin] Use custom workspace is not working with the MultiJob Plugin Change By: Doron Shai (03/Dec/12 12:32 PM) Summary: [jenkins-multijob-plugin] UsecustomworkspaceisnotworkingwiththeMultiJobPlugin Component/s: jenkins-multijob-plugin Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15094) Multijob with use of parameter from type “File Parameter” all Executors are becoming Dead (!)
Doron Shai commented on JENKINS-15094 Multijob with use of parameter from type “File Parameter” all Executors are becoming Dead (!) This issue is a real pain since when using the MultiJob Plugin there is no real way to use the Parametrized Build Plugin and therefore passing parameters from MultiJob Phase to another MultiJob Phase is not possible. 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
