[JIRA] (JENKINS-40549) Unable to use Parameter filters in copy artifacts if parameter values contain commas
Title: Message Title Alan Birtles commented on JENKINS-40549 Re: Unable to use Parameter filters in copy artifacts if parameter values contain commas changing this regex https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/java/hudson/plugins/copyartifact/ParametersBuildFilter.java#L48 to "(.?)=((\".?\"(,|$))|(([^,]*)(,|$)))" would allow commas inside quoted values 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-40549) Unable to use Parameter filters in copy artifacts if parameter values contain commas
Title: Message Title Alan Birtles created an issue Jenkins / JENKINS-40549 Unable to use Parameter filters in copy artifacts if parameter values contain commas Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 2016/Dec/19 5:38 PM Priority: Minor Reporter: Alan Birtles I have a project with a parameter whose value contains commas, it doesn't seem to be possible to specify the value of this parameter in the Parameter filters field of the copy artifact plugin. It would be nice if there was a way of escaping commas, e.g.: "A=a,B=b\,c,C=d" would evaluate to "A=a", "B=b,c" and "C=d" Add Comment
[JIRA] [scm-sync-configuration-plugin] (JENKINS-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Alan Birtles commented on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Yes I am seeing the same issue on OSX 10.10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Title: Message Title Alan Birtles commented on JENKINS-21640 Re: scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0 and broken again in 1.613, svn 2.5 and scm 0.0.8 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] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Alan Birtles
created JENKINS-28011
Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Issue Type:
Bug
Assignee:
Unassigned
Components:
copyartifact-plugin
Created:
20/Apr/15 9:13 AM
Description:
When changing the configuration of any job which uses the copy artifact plugin I receive the following stack trace, other jobs can be reconfigured successfully.
Looking at thejob configuration they were last updated with version 1.32.1 of the plugin.
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact from {"projectName":"TestJob","":"0","selector":{"stableOnly":false,"kind":""},"filter":"build_results/TestJob/**","excludes":"","target":"TargetDir/Executables","parameters":"","flatten":false,"optional":true,"fingerprintArtifacts":true,"stapler-class":"hudson.plugins.copyartifact.CopyArtifact","$class":"hudson.plugins.copyartifact.CopyArtifact"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
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:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607
Alan Birtles commented on JENKINS-27708 Concurrent build limits not honored on Jenkins 1.607 Did this make it into 1.610? 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] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 all working for me as well with jeninks 1.607, svn 2.5 and scm 0.0.8 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] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles
edited a comment on JENKINS-21640
scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0
I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/*
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job
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] [subversion-plugin] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)
Alan Birtles commented on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) just had a similar issue, in our case we had the svn url defined as http://server:80/svn/repo, I think the svn checkout strips out the port number then the polling thinks that the workspace doesn't contain the same working copy. 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] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles
commented on JENKINS-21640
scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0
I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job
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] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from
Alan Birtles commented on JENKINS-17680 Upgrade to new Copy Artifacts version erases all job names to copy from I've upgraded from 1.25 to 1.27 and it seems to automatically perform the upgrade when a project is built. Unfortunately I modified a few jobs before they were built so encountered this 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-10628) SCM build trigger not working correctly with variables in SVN URL
Alan Birtles commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Any chance of getting Bela's patch merged in to Jenkins? 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-13793) Build isn't triggered after reboot
Alan Birtles created JENKINS-13793: -- Summary: Build isn't triggered after reboot Key: JENKINS-13793 URL: https://issues.jenkins-ci.org/browse/JENKINS-13793 Project: Jenkins Issue Type: Bug Components: buildresult-trigger Environment: Mac OS X Jenkins 1.463 buildresult-trigger 0.6 Reporter: Alan Birtles Priority: Minor After rebooting jenkins the buildresult-trigger won't trigger a build. In our setup we use the buildresult-trigger to run a nightly test suite only after a build has happened during the day. If the server is rebooted then builds will not be triggered on the first night and will only be triggered on the second night if another build has happened during the second day. The polling log on the first night says that the monitored build didn't exist before. I guess this is because the plugin has no persistance? This means that after installing updates or new plugins our tests wont run for at least a day. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
