[JIRA] [copyartifact-plugin] (JENKINS-31247) Copyartifact: more integration with workflow
Title: Message Title ikedam commented on JENKINS-31247 Re: Copyartifact: more integration with workflow Is it possible to simplify also selector like this ? copyartifact projectName: 'test', filter: '**/*', selector: StatusBuildSelector(false) 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] [flexible-publish-plugin] (JENKINS-31229) Flexible publisher does not properly consider 'dynamic' RunCondition for MatrixBuild aggregation
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-31229 Flexible publisher does not properly consider 'dynamic' RunCondition for MatrixBuild aggregation Change By: ikedam Assignee: bap ikedam 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] [flexible-publish-plugin] (JENKINS-31229) Flexible publisher does not properly consider 'dynamic' RunCondition for MatrixBuild aggregation
Title: Message Title ikedam commented on JENKINS-31229 Re: Flexible publisher does not properly consider 'dynamic' RunCondition for MatrixBuild aggregation The condition is evaluated only once when a build starts. It decides whether to run all the aggregation process including startBuild: called when a parent build start. endRun: called when a each child finishes. endBuild: called when a parent build finishes. This also means a following problem: you cannot use axes values in conditions for aggregation. I'll consoder to add an options for each steps. 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-31247) Copyartifact: more integration with workflow
Title: Message Title ikedam commented on JENKINS-31247 Re: Copyartifact: more integration with workflow Thanks. It sounds better to wait JENKINS-29922. Are there already steps called with code blocks? (like if-statements) I plan to introduce a build filter that users can declare with groovy scripts (integrating with script-security) in a future release, and want to see if I can make it easier to use that in workflow jobs. 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-31247) Copyartifact: more integration with workflow
Title: Message Title
ikedam commented on JENKINS-31247
Re: Copyartifact: more integration with workflow
Thanks. I found out documents and examples for passing code blocks.
Creating a block-scoped step
TimeoutStep.java
TimeoutStepExecution.java
TimeoutStepTest.java
It may be written like this:
copyartifact projectName: 'upstream' {
return run.resuli.isBetterOrEquals(Result.SECCESS);
}
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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title ikedam assigned an issue to ikedam Naginator looks check only the global permission, not a permission for that project. It's an issue only for role-strategy, also for any strategies defining permissions for projects (such as [matrix-authhttps://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin]). Scheduled for the next release (0.16.1 or 0.17) Jenkins / JENKINS-31318 Retry button invisible with "Build" project role Change By: ikedam Component/s: role-strategy-plugin Assignee: Nicolas De Loof ikedam 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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title ikedam edited a comment on JENKINS-31318 Re: Retry button invisible with "Build" project role Naginator looks check only the global permission, not a permission for that project.It's an issue only for role-strategy, also for any strategies defining permissions for projects (such as [matrix-authhttps://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin]).Scheduled for the next release ( 0 1 .16.1 or 0 1 .17) 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] [naginator-plugin] (JENKINS-26637) naginator doesn't apply regexp to multi-configuration child builds
Title: Message Title ikedam closed an issue as Fixed Fixed in 1.16. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-26637 naginator doesn't apply regexp to multi-configuration child builds Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-17626) Retry count resets when job with other parameters is successful
Title: Message Title ikedam closed an issue as Fixed Fixed in 1.16. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-17626 Retry count resets when job with other parameters is successful Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-23984) Conditional rerun (or Naginator plugin doesn't work with Flexible Publish)
Title: Message Title ikedam closed an issue as Fixed Fixed in naginator-1.16. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-23984 Conditional rerun (or Naginator plugin doesn't work with Flexible Publish) Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-26118) Naginator restarted build without any reason
Title: Message Title ikedam assigned an issue to Kanstantsin Shautsou Naginator-1.14 outputs diagnostic logs: https://github.com/jenkinsci/naginator-plugin/pull/13 Please let me know: Whether the problem still reproduces Log outputs when the problem occurs Jenkins / JENKINS-26118 Naginator restarted build without any reason Change By: ikedam Assignee: Nicolas De Loof Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title ikedam assigned an issue to stephenconnolly Reproduced in my environment. This looks an issue of credentials-plugin. Credentials plugin doesn't use the authorization decided when the build starts by authorize-project. Instead, it uses "default authorization", which means the autorization that can be decided only with the project configuration itself, without contexts like who triggered the build. This looks intended limitation of credentials-plugin: https://github.com/jenkinsci/credentials-plugin/blob/credentials-1.16.1/src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java#L807 // we use the default authentication of the job as those are the only ones that can be configured // if a different strategy is in play it doesn't make sense to consider the run-time authentication // as you would have no way to configure it Jenkins / JENKINS-24750 Cannot find user credentials when job is triggered with parameters Change By: ikedam Component/s: credentials-plugin Component/s: ssh-agent-plugin Component/s: authorize-project-plugin Assignee: stephenconnolly
[JIRA] [credentials-plugin] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Title: Message Title ikedam commented on JENKINS-24750 Re: Cannot find user credentials when job is triggered with parameters It's not strange, and looks rather an intended behavior of credentials plugin. Consider a case that you are an administrator, and developers can't modify configurations of builds. Once you configures the project with Run as Specific user, the authorization is always same however developers teigger a build. But if you configures the project with Run as User who Triggered, the authorization can be different depending on who triggered the build. Credentials plugin doesn't allow the latter case, and it does't work. 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-20546) Preserve symlinks when copying artifacts
Title: Message Title ikedam commented on JENKINS-20546 Re: Preserve symlinks when copying artifacts Just unchecking "Fingerprint Artifacts" should never affect handling symlinks. It looks another issue, and please create a new ticket with details, such as environments, steps to reproduce and console outputs. 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] [flexible-publish-plugin] (JENKINS-31410) Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-31410 Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed Change By: ikedam Assignee: bap ikedam 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] [flexible-publish-plugin] (JENKINS-31410) Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed
Title: Message Title ikedam commented on JENKINS-31410 Re: Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed It's not a bug. Some post-build steps require the last build finished. Flexible-publish also requires that when embedding those post-build steps. And flexible-publish doesn't require that if none of embedded post-build steps require that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-31342) Build Timeout doesn't work with Build Flow Plugin
Title: Message Title ikedam resolved as Duplicate Duplicates JENKINS-16455 Jenkins / JENKINS-31342 Build Timeout doesn't work with Build Flow Plugin Change By: ikedam Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-31410) Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed
Title: Message Title ikedam resolved as Not A Defect Jenkins / JENKINS-31410 Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed Change By: ikedam Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-31569) Should be able to use a 'Run parameter' to select build to copy from
Title: Message Title ikedam resolved as Duplicate Duplicates JENKINS-21519. Jenkins / JENKINS-31569 Should be able to use a 'Run parameter' to select build to copy from Change By: ikedam Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-21519) Copy Artifacts plugin should support build selector from Run Parameter
Title: Message Title
ikedam closed an issue as Won't Fix
I saw that the way Stefan Seidel described works as expected. (The documented expressions are ${BUILD_SELECTOR_JOBNAME} and ${BUILD_SELECTOR_NUMBER}).
Won't fix.
Jenkins / JENKINS-21519
Copy Artifacts plugin should support build selector from Run Parameter
Change By:
ikedam
Status:
Open Closed
Resolution:
Won't Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout-plugin] (JENKINS-31627) Memory leak in build-timeout-plugin when used with NoActivityTimeOutStrategy
Title: Message Title ikedam closed an issue as Fixed Released 1.15.1 including the fix. It will be available in the update center in a day. Jenkins / JENKINS-31627 Memory leak in build-timeout-plugin when used with NoActivityTimeOutStrategy Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-31563) Latest successful artifact cannot be copied from Maven build
Title: Message Title ikedam commented on JENKINS-31563 Re: Latest successful artifact cannot be copied from Maven build I couldn't get how to reproduce the problem. How do you archive artifacts in job1? "lastSuccessfulBuild" is build #510? Are there files in D:\jenkins\jobs\job1\modules\my.package$myapp\builds\510\archive ? 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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title ikedam commented on JENKINS-31318 Re: Retry button invisible with "Build" project role https://github.com/jenkinsci/naginator-plugin/pull/22 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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title ikedam started work on JENKINS-31318 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title ikedam started work on JENKINS-24903 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title ikedam assigned an issue to ikedam https://github.com/jenkinsci/naginator-plugin/pull/23 Jenkins / JENKINS-24903 Unabortable builds due to catastrophic backtracking regular _expression_ Change By: ikedam Assignee: Nicolas De Loof ikedam 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] (JENKINS-16168) Cannot specify a build with parameters containing slash("/")
Yasuyuki IKEDA
created JENKINS-16168
Cannot specify a build with parameters containing slash("/")
Issue Type:
Bug
Assignee:
Unassigned
Components:
copyartifact
Created:
19/Dec/12 1:24 PM
Description:
In a following case, Copy Artifact fails to find the build to copy.
In confituration: specify Project name filtering with a build parameters, using variables.
In build: use variables containing slash("/").
For instance:
Configure Project name to "SomeParameterizedJob/BRANCH=${value1}"
Run build with setting value1 to "origin/develop"
Even if there is a build with BRANCH=origin/develop in SomeParameterizedJob, this results in a following failure:
Unable to find project for artifact copy: SomeParameterizedJob/BRANCH=origin/master
This seems caused for Copy Artifact uses the LAST slash to devide the Project name parameter to the job name and the filter parametes (In CopyArtifact.JobResolver, using lastIndexOf).
So "SomeParameterizedJob/BRANCH=origin/master" is devided into "SomeParameterizedJob/BRANCH=origin" and "master".
Job names never contain slashes, and how about replaces lastIndexOf to indexOf to use the FIRST slash to devide the project name?
Environment:
Windows XP
Jenkins 1.494
Copy Artifact 1.25
Project:
Jenkins
Priority:
Major
Reporter:
Yasuyuki IKEDA
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-15156) Builds disappear from build history after completion
Yasuyuki IKEDA commented on JENKINS-15156 Builds disappear from build history after completion builds.dir of new created MatrixConfiguration is always set to null. This causes Jenkins fail to load builds of configurations from the disk (AbstractLazyLoadRunMap.load). MatrixConfiguration.builds (that is AbstractProject.builds) is initialized with new RunMap(), which sets builds.dir to null. When the configuration is load from the disk, builds is correctly initialized and dir is set. When new MatrixConfiguration is created (including the case a new axis is added), MatrixConfiguration.onLoad nor MatrixConfiguration.onCreatedFromScratch seem not called. It may concerned with this 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/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
ikedam commented on JENKINS-15156 Builds disappear from build history after completion As described above, this problem seems to be fixed in 1.505 (with 42ee6113b7beff8dccba48593cefe0ad23636051). But I am so annoyed with this problem that I wrote a plugin to fix the problem in multi-configuration projects. https://github.com/ikedam/quickfix15156 This may be useful for those that want to fix this problem immediately, or those that do not want to update Jenkins in some reasons. 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] [build-timeout] (JENKINS-22984) Allow Build-Timeout to exclude SVN sync time
ikedam commented on JENKINS-22984 Allow Build-Timeout to exclude SVN sync time build-timeout-plugin starts its timer after SCM checkout and pre-build phase. It should never cause timeout during SCM checkout. Please report more details about the problem you are facing. 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] [build-timeout] (JENKINS-22984) Allow Build-Timeout to exclude SVN sync time
ikedam commented on JENKINS-22984 Allow Build-Timeout to exclude SVN sync time Timestampler plugin will help you. You can see what operation take time with timastamps in a log. Update the summary and description when you find the root cause. 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] [build-timeout] (JENKINS-23018) Absolute build timeout doesn't stop the build
ikedam commented on JENKINS-23018 Absolute build timeout doesn't stop the build Build-timeout plugin starts its timer AFTER scm phase. And so it never catches timeout of SCM. 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam assigned JENKINS-23012 to ikedam Build-timeout plugin causes builds to slow Change By: ikedam (15/May/14 1:13 PM) Assignee: Kohsuke Kawaguchi ikedam 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam commented on JENKINS-23012 Build-timeout plugin causes builds to slow As those synchronized methods are called at the start and the end of builds, I don't think they cause being slow. Rather, changes to watch log outputs may cause the problem. https://github.com/jenkinsci/build-timeout-plugin/commit/2129c5d8fc4a9d9432cf95ce34ce522e646eb3ff#diff-891dfa43e0d85dea7162d46b430299d7R184 I want to make some testing versions to identify the cause. But I'm not sure how to reproduce the problem. Can you try testing versions if I provide? 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam commented on JENKINS-23012 Build-timeout plugin causes builds to slow I agree that it's risky to install testing versions to the production environmtnt. I'm not so sure what the root cause is and how to fix that. I'll try to reproduce it in my local enviroment. Please let me know followings: OS of the master node and slave nodes. Outline of your build process. For example, running maven, running gcc, or running other native process. I think whether builds are performed in Java or native processes can affect this problem. How much log outputs? I think the size of whole log and the time builds take will be helpful. I think much log outputs may trigger the problem. Can you see what process gets slow in builds? If building processes outputs timestamps, please compare them before and after downgrading build-timeout plugin. If you installed Timestampler plugin, please compare timestamps in console outputs. Timestamps logged with timestampler-plugin may differ from the activity of the building process as they can be buffered and delayed. If you don't have timestamper-plugin installed, you'd better not install that as that plugin also captures log output and may cause the same problem. I think there are following possible causes to slow builds: Native processes lauched in builds get slow. Like processes launched with "Execute shell". I don't think Jenkins cannot affect native processes as they should be completely separated by OS. But slowed log output can flood output buffers of processes and may cause the processes hold for a while. Jenkins takes much time to proceed build steps. In this case, native processes don't get slow. Jenkins takes much time to start and stop builds. This can be caused by synchronized. 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam
commented on JENKINS-23012
Build-timeout plugin causes builds to slow
Thanks for information.
I tried to reproduce the problem using native processes and I think I could.
I continue the investigation.
How I reproduce:
Installed build-timeout-plugin 1.13
Create a free style project with "Execute a shell":
#!/bin/bash
for i in $(seq 300); do
for j in $(seq 65535); do
echo ${i} ${j}
done
done
I tested this on Windows 8, using cygwin for 64 bit.
Run a build with and without "Abort the build if it's stuck".
"Absolute" Timeout strategy with 30 minutes.
Result:
Condition
Duration
Without build-timeout
10 minutes
With build-timeout
12 minutes
and I found that the duration gets 32 minutes if I enabled timestamper-plugin...Amazing.
I do have some data captured in a database about those builds. That's data like job-name, build-number, result, build-duration, and interestingly, excerpts from the logs for failed/aborted builds.
If that contains amount of logs, I want to know whether amount of logs affects how much builds get slow.
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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam commented on JENKINS-23012 Build-timeout plugin causes builds to slow I identified the cause is watching log output. Condition Duration Without build-timeout 10 minutes With build-timeout 12 minutes With build-timeout disabling log watching 10 minutes 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam commented on JENKINS-23012 Build-timeout plugin causes builds to slow https://github.com/jenkinsci/build-timeout-plugin/pull/26 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] [build-timeout] (JENKINS-20164) Plugins Build-timeout and FSTrigger cannot be used in the same job
ikedam commented on JENKINS-20164 Plugins Build-timeout and FSTrigger cannot be used in the same job https://github.com/jenkinsci/build-timeout-plugin/pull/27 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] [parameterized-trigger] (JENKINS-23053) Allow Parameter interpolation for job name
ikedam commented on JENKINS-23053 Allow Parameter interpolation for job name Same request to JENKINS-11280 ? 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] [parameterized-trigger] (JENKINS-23084) Support absolute file paths in "Parameters from properties file"
ikedam created JENKINS-23084 Support absolute file paths in "Parameters from properties file" Issue Type: Improvement Assignee: ikedam Components: parameterized-trigger Created: 18/May/14 6:27 AM Description: "Parameters from properties file" is designed to work with "Comma seperated list of paths to file(s) in the workspace that contains the parameters for the new project." There look cases to use a file out of workspaces. Project: Jenkins Priority: Major Reporter: ikedam 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] [parameterized-trigger] (JENKINS-23084) Support absolute file paths in "Parameters from properties file"
ikedam commented on JENKINS-23084 Support absolute file paths in "Parameters from properties file" https://github.com/jenkinsci/parameterized-trigger-plugin/pull/66 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] [parameterized-trigger] (JENKINS-22281) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 - offending parameter not identified
ikedam commented on JENKINS-22281 FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 - offending parameter not identified https://github.com/jenkinsci/parameterized-trigger-plugin/pull/67 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] [parameterized-trigger] (JENKINS-16679) project run gets hung up, when run simultaneously
ikedam commented on JENKINS-16679 project run gets hung up, when run simultaneously This may be fixed in Jenkins-1.558, hudson-remoting 2.36. https://github.com/jenkinsci/remoting/commit/6d0d5dea26c5f619164ade791a26a5c7c8dc50ea https://github.com/jenkinsci/jenkins/commit/75447b57b655e38fdb48f1e854a4b287071342cf#diff-600376dffeb79835ede4a0b285078036 Please report if it reproduces after that version. 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] [parameterized-trigger] (JENKINS-15476) "Block until the triggered projects finish their builds" doesn't notify upstream project when complete.
ikedam commented on JENKINS-15476 "Block until the triggered projects finish their builds" doesn't notify upstream project when complete. This may be fixed in Jenkins-1.558, hudson-remoting 2.36. https://github.com/jenkinsci/remoting/commit/6d0d5dea26c5f619164ade791a26a5c7c8dc50ea https://github.com/jenkinsci/jenkins/commit/75447b57b655e38fdb48f1e854a4b287071342cf#diff-600376dffeb79835ede4a0b285078036 Please report if it reproduces after that version. 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam commented on JENKINS-23012 Build-timeout plugin causes builds to slow Do you have any special advice I should pass on to my Jenkins users regarding their behavior to avoid slow builds? As this is a problem of the plugin, there's nothing users must do. But the investigation I did indicates followings: Fast and much log outputs can have builds slow. Decreasing log outputs may quicken your builds. Outputting logs to a file and archiving that as a artifact may work, but it should depend on CPU, network bandwidths and disk IOs. What's the next step in getting the fix? I'll plan to make a new release in this month including other fixes and improvements. Please wait that. Please upgrade the plugin carefully as I'm not 100% sure this can resolve your problem. You should be ready to downgrade the plugin whenever you find the problem reproduce. If you can, you'd better introduce a testing envirinment. 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] [parameterized-trigger] (JENKINS-22856) doCheckProjects can get confused with Cloudbees Template plugin
ikedam commented on JENKINS-22856 doCheckProjects can get confused with Cloudbees Template plugin https://github.com/jenkinsci/copyartifact-plugin/pull/36#issuecomment-43407514 `getJobOverrides` only inserts the `Configurator`, which is not an `Item`. The `JobTemplate`, along with the `Attribute` and `Control`, are inserted using `f:withCustomDescriptorByName` (from the `Configurator`’s configuration screen). While the page URL remains that of the templatized job, if you look at the “AJAX” URL being passed to the `doCheck*` method (or whatever), you will see something longer that matches the ancestor list mentioned earlier. 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] [parameterized-trigger] (JENKINS-22856) doCheckProjects can get confused with Cloudbees Template plugin
ikedam commented on JENKINS-22856 doCheckProjects can get confused with Cloudbees Template plugin https://github.com/jenkinsci/parameterized-trigger-plugin/pull/68 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] [core] (JENKINS-22803) 'JellyTagException: For input string: ""' on job view
ikedam updated JENKINS-22803 'JellyTagException: For input string: ""' on job view Parameterized trigger plugin just calls Job#getLastSuccessfulBuild. It's not reasonable to expect java.lang.NumberFormatException is thrown from Job#getLastSuccessfulBuild, and I think this is a problem that should be fixed Jenkins core. Job#getLastSuccessfulBuild looks switched to use PeepholePermalink since jenkins-1.507. https://github.com/jenkinsci/jenkins/commit/88feabb4296d6483bdb5c85fed489e5014161ca5 I'm not sure what causes lastSuccessfulBuild, which is a symlink, points not null but an empty file name. Please report details how to reproduce this problem. Change By: ikedam (19/May/14 10:08 PM) Component/s: core Component/s: parameterized-trigger 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] [groovy-postbuild] (JENKINS-23116) Add tests for groovy-postbuild plugin
ikedam created JENKINS-23116 Add tests for groovy-postbuild plugin Issue Type: Task Assignee: ikedam Components: groovy-postbuild Created: 20/May/14 11:07 PM Description: There's no tests for groovy-postbuild-plugin. This makes it difficult for developers to contribute, and for me to maintain this plugin. Project: Jenkins Priority: Major Reporter: ikedam 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] [build-timeout] (JENKINS-23117) Support launcher in Perform Buildstep
ikedam created JENKINS-23117 Support launcher in Perform Buildstep Issue Type: Improvement Assignee: ikedam Components: build-timeout Created: 20/May/14 11:14 PM Description: Builders like "Execute shell" or "Execute Windows batch" does not work with "Perform Buildstep" now. Project: Jenkins Priority: Major Reporter: ikedam 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] [build-timeout] (JENKINS-23118) "Enable BuildStep Action" is not saved to disk
ikedam created JENKINS-23118 "Enable BuildStep Action" is not saved to disk Issue Type: Bug Assignee: ikedam Components: build-timeout Created: 20/May/14 11:24 PM Description: Manage Jenkins > Configure System > "Build-timeout Plugin > BuildStep Action" > Enable BuildStep Action is not saved to the disk. Project: Jenkins Priority: Major Reporter: ikedam 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] [build-timeout] (JENKINS-23118) "Enable BuildStep Action" is not saved to disk
ikedam commented on JENKINS-23118 "Enable BuildStep Action" is not saved to disk https://github.com/jenkinsci/build-timeout-plugin/pull/28 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] [build-timeout] (JENKINS-19612) NPE During Build - v1.530
ikedam
commented on JENKINS-19612
NPE During Build - v1.530
It looks that build-timeout is enabled for that project and is not fully configured.
Please give me followings:
config.xml of that project. It is usually located in {{${JENKINS_HOME}/jobs/(Project name)/config.xml}}
The screen shot of the configuration page of the project.
I want to see "Abort the build if it's stuck" is exactly unchecked.
If this problem started to occuer after upgrading Jenkins, let me know the version before upgrading.
What web browser do you use configureing?
What version of build-timeout plugin is installed in your 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
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-22834) Administrator-approved classpath additions
ikedam commented on JENKINS-22834 Administrator-approved classpath additions So you mean: As jar files can be added by a non-administrator user, administrators want to control them via script-security-plugin. Plugins are installed only by administrators and administrators already can control them. 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] [build-timeout] (JENKINS-23018) Absolute build timeout doesn't stop the build
ikedam resolved JENKINS-23018 as Not A Defect Absolute build timeout doesn't stop the build Change By: ikedam (31/May/14 2:49 PM) Status: Open Resolved Resolution: Not A Defect 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] [build-timeout] (JENKINS-22984) Allow Build-Timeout to exclude SVN sync time
ikedam resolved JENKINS-22984 as Cannot Reproduce Allow Build-Timeout to exclude SVN sync time Change By: ikedam (31/May/14 2:51 PM) Status: Open Resolved Resolution: Cannot Reproduce 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] [build-timeout] (JENKINS-9457) Build Timeout value field should accept any sort of parameter
ikedam resolved JENKINS-9457 as Fixed Build Timeout value field should accept any sort of parameter Released in build-timeout-plugin 1.14. It will be available in a day. Please try that. Change By: ikedam (01/Jun/14 2:17 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] [build-timeout] (JENKINS-23117) Support launcher in Perform Buildstep
ikedam closed JENKINS-23117 as Fixed Support launcher in Perform Buildstep Released in 1.14. Change By: ikedam (01/Jun/14 2:18 AM) 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] [build-timeout] (JENKINS-19773) Add the build timeout parameter
ikedam resolved JENKINS-19773 as Fixed Add the build timeout parameter Released in 1.14. It will be available in a day. Please try that. Change By: ikedam (01/Jun/14 2:16 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] [build-timeout] (JENKINS-20526) Allow timouts to be set via parameter
ikedam resolved JENKINS-20526 as Fixed Allow timouts to be set via parameter Released in 1.14. It will be available in a day. Please try that. Change By: ikedam (01/Jun/14 2:16 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] [build-timeout] (JENKINS-20164) Plugins Build-timeout and FSTrigger cannot be used in the same job
ikedam commented on JENKINS-20164 Plugins Build-timeout and FSTrigger cannot be used in the same job Released in 1.14. Please try that. 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] [build-timeout] (JENKINS-23118) "Enable BuildStep Action" is not saved to disk
ikedam closed JENKINS-23118 as Fixed "Enable BuildStep Action" is not saved to disk Released in 1.14. Change By: ikedam (01/Jun/14 2:18 AM) 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam reopened JENKINS-23012 Build-timeout plugin causes builds to slow Fixed version is released as 1.14. It will be available in a day. Please try that version. Please upgrade the plugin carefully as I'm almost but not 100% sure this can resolve your problem. You should be ready to downgrade the plugin whenever you find the problem reproduce. I'll close this ticket after you see it work. Change By: ikedam (01/Jun/14 2:21 AM) Resolution: Fixed Status: Resolved Reopened Assignee: ikedam Darrel Vuncannon 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] [parameterized-trigger] (JENKINS-23084) Support absolute file paths in "Parameters from properties file"
ikedam closed JENKINS-23084 as Fixed Support absolute file paths in "Parameters from properties file" Released in 2.25. Change By: ikedam (01/Jun/14 3:05 AM) 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] [parameterized-trigger] (JENKINS-22705) Parameterized Trigger Plugin setting is not retained: "Use files in matrix child builds"
ikedam commented on JENKINS-22705 Parameterized Trigger Plugin setting is not retained: "Use files in matrix child builds" Release fix in 2.25. It will be available in a day. Please try that. 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] [parameterized-trigger] (JENKINS-22856) doCheckProjects can get confused with Cloudbees Template plugin
ikedam closed JENKINS-22856 as Fixed doCheckProjects can get confused with Cloudbees Template plugin Released in 2.25. Change By: ikedam (01/Jun/14 3:07 AM) 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] [parameterized-trigger] (JENKINS-22281) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 - offending parameter not identified
ikedam commented on JENKINS-22281 FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 - offending parameter not identified Release fix in 2.25. It will be available in a day. Please try that. Now prints a message like this: WARNING: Ignoring RuntimeException thrown while converting StringParameterValue param1 on upstream #1. Falling back to original value. 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] [parameterized-trigger] (JENKINS-22229) Build from properties file fails if workspace does not exist
ikedam resolved JENKINS-9 as Fixed Build from properties file fails if workspace does not exist This fix is released in parameterized-trigger plugin 2.25. It will be available in a day. Please try that. Change By: ikedam (01/Jun/14 3:09 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] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
ikedam commented on JENKINS-22275 Save of job configuration doesn't work after removing a parameter under 'This build is parameterized' I cannot get your point. As @danielbeck said, JENKINS-22582 is fixed in 1.560. And it's not strange Jenkins 1.556 is still affected by that problem. What tells you JENKINS-21582 is fixed in 1.554? 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-23260) Copy Artifact plugin: job name not found when passed through a predefined parameter
ikedam commented on JENKINS-23260 Copy Artifact plugin: job name not found when passed through a predefined parameter "project security is not enabled" means you don't check "Enable security" in Configure Global Security page? 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] [build-user-vars] (JENKINS-23192) Build user variables support in downstream jobs
ikedam commented on JENKINS-23192 Build user variables support in downstream jobs What is build user variables? Let me know some examples. 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] [build-user-vars] (JENKINS-23192) Build user variables support in downstream jobs
ikedam commented on JENKINS-23192 Build user variables support in downstream jobs I got it. You mean a combination of Build User Vars plugin and Parameterized Trigger 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-23192) Build user variables support in downstream jobs
ikedam commented on JENKINS-23192 Build user variables support in downstream jobs Looks supported since build-user-vars-plugin 1.2. What version of plugin do you use? 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-23260) Copy Artifact plugin: job name not found when passed through a predefined parameter
ikedam commented on JENKINS-23260 Copy Artifact plugin: job name not found when passed through a predefined parameter You should have a look on those pages: https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact https://issues.jenkins-ci.org/browse/JENKINS-8727 https://github.com/jenkinsci/copyartifact-plugin/commit/2f202613be0e44c48b8185b7b639c25d18e06003 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] [build-user-vars] (JENKINS-23192) Build user variables support in downstream jobs
ikedam updated JENKINS-23192 Build user variables support in downstream jobs Anyway, this is no longer related to parameterized-trigger plugin. Change By: ikedam (04/Jun/14 11:37 PM) Assignee: huybrechts Component/s: parameterized-trigger 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-23181) NPE caused by copy artifcats while renaming job
ikedam
commented on JENKINS-23181
NPE caused by copy artifcats while renaming job
This means you have a broken "Copy artifacts from another project".
I want to know what broke that configuration (you cannot create that broken configuration in usual ways).
Let me know:
Did you upgrade copyartifact-plugin from a version < 1.26 ?
The configuration file format is changed since 1.25. This problem may be caused for the bad migration of configuration files.
Is there any strange logs when you starts Jenkins?
Migration of the configuration files is performed when Jenkins starts up. If some problems happen in the migration process, there would be error logs.
Let me see config.xml of the project with broken "Copy artifacts from another project" if you can find that.
Correct copyartifact configurations are like this in ${JENKINS_HOME}/jobs/PROJECTNAME/config.xml:
...
projectCopiedFrom
artifact.zip
false
...
In your case, it sounds like a tag does not exist (not only be empty, but not exist).
If there are many projects in your Jenkins, it would be difficult to find out that.
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-22460) Support artifacts permission
ikedam commented on JENKINS-22460 Support artifacts permission The current (Jenkins 1.567, matrix-project-plugin 1.2, maven-plugin 2.3) feature of artifacts permission in Jenkins: When launching Jenkins with "-Dhudson.security.ArtifactsPermission=true", Run.Artifacts is shown in "Matrix-based security" and " Project-based Matrix Authorization Strategy" in the Global Security Configuration page and "Enable project-based security" in the project configuration page. Jenkins seems not support per run ACL. Run.getACL() returns getParent().getACL() none of subclasses of Run does not override getACL() hudson.model.AbstractBuild hudson.model.Build hudson.model.FreeStyleBuild hudson.matrix.MatrixBuild hudson.matrix.MatrixRun hudson.maven.AbstractMavenBuild hudson.maven.MavenBuild hudson.maven.MavenModuleSetBuild 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-22460) Support artifacts permission
ikedam commented on JENKINS-22460 Support artifacts permission Should I test Item.READ also for Run ? 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-22460) Support artifacts permission
ikedam commented on JENKINS-22460 Support artifacts permission There are following problems to introduce this feature: Backward compatibility: Many users will face problems in copying artifacts introducing this feature (Especially if copyartifact will test Item.READ against Run). Should copyartifact introduce a Java property to disable this feature? Should copyartifact test run permissions only when project names are specified with variables? Copyartifact tests project permissions at runtime only when project names are specified with variables. Should it be applied also for run permissions? If tests them also when project names is specified without variables, more users will face problems. 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-20940) Project source of a multi-config project inside a folder not working
ikedam commented on JENKINS-20940 Project source of a multi-config project inside a folder not working This reproduces even in the lastet copyartifact 1.30. Jenkins 1.532.2 + cloudbees folder plugin 4.0.1 Project name 1.28 1.29 1.30 Job1 NG: Project name gets empty NG: Project name gets empty NG: Project name gets empty Test/Job1 NG: Class cast exception OK OK /Test/Job1 OK OK OK Projects: /Test: Cloudbees folder /Test/Job1: A free style project that creates an artifact. /Test/Job2: A multi-configuration project that copies an artifact from /Test/Job1 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-20940) Project source of a multi-config project inside a folder not working
ikedam commented on JENKINS-20940 Project source of a multi-config project inside a folder not working https://github.com/jenkinsci/copyartifact-plugin/pull/40 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-22460) Support artifacts permission
ikedam commented on JENKINS-22460 Support artifacts permission I think it is confusing configuration-time access checking for project names without variables. I'll disable configuration-time access checking and always perform access checking at runtime. Preserves backward compatibility providing a Java property to switch the bahavior. 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-23260) Copy Artifact plugin: job name not found when passed through a predefined parameter
ikedam resolved JENKINS-23260 as Not A Defect Copy Artifact plugin: job name not found when passed through a predefined parameter Change By: ikedam (19/Jun/14 11:27 PM) Status: Open Resolved Resolution: Not A Defect 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-11655) Upstream build points to wrong revision if there is more than one revision triggered the job
ikedam commented on JENKINS-11655 Upstream build points to wrong revision if there is more than one revision triggered the job Let me know details of "but the same SCM(subversion btw.) version was used as in upstream #88 which means that it run a different version of the binary and the testsuite, hence my testsuite failed." That sounds mean there are difference between behaviors of copyartifact and SCM, but I cannot see that's a case for all SCM plugins (svn, git, etc) or only for svn. 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] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
ikedam commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly @kbeal I cannot get what you say at all. What is VM? I cannot get how a virtual machine relates to this problem. What is +1? Which job reported NPE? 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] [build-pipeline] (JENKINS-14656) Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually
ikedam resolved JENKINS-14656 as Fixed Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually Looks fixed in https://github.com/jenkinsci/build-pipeline-plugin/pull/8 , build-pipeline-1.4. Change By: ikedam (23/Jun/14 11:49 PM) Status: In Progress 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] [ant] (JENKINS-15886) parameterized builds start default ant target in Ant-Task
ikedam updated JENKINS-15886 parameterized builds start default ant target in Ant-Task This is a parameter escaping issue of ant-plugin, and should be fixed in ant-plugin (or might be Jenkins core, I'm not sure how ant-plugin launches native processes). Change By: ikedam (24/Jun/14 12:19 AM) Component/s: copyartifact 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-17880) Not all files are copied.
ikedam resolved JENKINS-17880 as Duplicate Not all files are copied. Duplicates JENKINS-14900 Change By: ikedam (24/Jun/14 12:31 AM) Status: Open Resolved Resolution: Duplicate 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-17880) Not all files are copied.
ikedam assigned JENKINS-17880 to ikedam Not all files are copied. Change By: ikedam (24/Jun/14 12:30 AM) Assignee: ikedam 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-20850) when using default workspace "default" folder is also copied
ikedam commented on JENKINS-20850 when using default workspace "default" folder is also copied It sounds that you specified "Target directory". It can be empty. 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] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
ikedam commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly @kbeal I cannot get why you thouht your problem relates to this issue at all. It sounds that your problem rather relates to JENKINS-7557. 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] [matrix-project] (JENKINS-22863) All matrix jobs disappeared after upgrade to 1.562
ikedam commented on JENKINS-22863 All matrix jobs disappeared after upgrade to 1.562 Every plugin using /lib/project/matrix tag causes the same 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] [matrix-combinations-parameter] (JENKINS-23609) "Successful" and "Failed" link in matrix-combinations-parameter do not work
ikedam created JENKINS-23609 "Successful" and "Failed" link in matrix-combinations-parameter do not work Issue Type: Bug Assignee: Unassigned Components: matrix-combinations-parameter Created: 29/Jun/14 3:28 AM Description: All and None link work. Successful link always check the first checkbox only if it has never been built. Failed link always check the third checkbox only if it has never been built. Environment: Matrix combinations parameter 1.0.6 Project: Jenkins Priority: Major Reporter: ikedam 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] [matrix-combinations-parameter] (JENKINS-23561) Update to separated matrix-project-plugin
ikedam commented on JENKINS-23561 Update to separated matrix-project-plugin Alternate approach. Preserves compatibility for Jenkins < 1.561: https://github.com/jenkinsci/matrix-combinations-plugin/pull/7 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] [matrix-combinations-parameter] (JENKINS-23030) Matrix Combinations: Configuration changes cause NPE
ikedam assigned JENKINS-23030 to ikedam Matrix Combinations: Configuration changes cause NPE Change By: ikedam (29/Jun/14 5:48 AM) Assignee: ikedam 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] [matrix-combinations-parameter] (JENKINS-23030) Matrix Combinations: Configuration changes cause NPE
ikedam commented on JENKINS-23030 Matrix Combinations: Configuration changes cause NPE I tried another way in https://github.com/jenkinsci/matrix-combinations-plugin/pull/7 . Could you let me know an example step to reproduce the problem? I added a test to reproduce this problem, but that seems not happen in common usage. 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] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam resolved JENKINS-23012 as Fixed Build-timeout plugin causes builds to slow Thanks for the fix report. Please reopen this issue for the case the problem remains. Change By: ikedam (29/Jun/14 11:30 PM) Status: Reopened 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] [parameterized-trigger] (JENKINS-23440) Jenkins Parameterized Trigger Plugin doesn't process the 'Projects to Build' parameter correctly
ikedam resolved JENKINS-23440 as Duplicate Jenkins Parameterized Trigger Plugin doesn't process the 'Projects to Build' parameter correctly Change By: ikedam (30/Jun/14 2:05 PM) Status: Open Resolved Resolution: Duplicate 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] [build-timeout] (JENKINS-7513) Add the timeout globally by default for all projects not only by project
ikedam resolved JENKINS-7513 as Fixed Add the timeout globally by default for all projects not only by project build-timeout 1.14 supports variable expressions. You can define a global variable and control timeouts. Change By: ikedam (30/Jun/14 2:08 PM) 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.
