[JIRA] [ssh-agent] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
ikedam updated JENKINS-24750 Cannot find user credentials when job is triggered with parameters Change By: ikedam (25/Sep/14 1:01 PM) Component/s: authorize-project 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-10439) IOException while archiving AND wrong build status
ikedam resolved JENKINS-10439 as Incomplete IOException while archiving AND wrong build status The reporter seems no longer here. Change By: ikedam (26/Sep/14 12:26 AM) Status: Open Resolved Resolution: Incomplete 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-16019) Copy Artifact Plugin isn't copying the last successful correctly
ikedam commented on JENKINS-16019 Copy Artifact Plugin isnt copying the last successful correctly Let me know the version of copyartifact you use. And please report steps to reproduce the 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] [copyartifact] (JENKINS-12412) copyartifact 1.21 fails in at least certain cross-platform copy scenarios
ikedam resolved JENKINS-12412 as Fixed copyartifact 1.21 fails in at least certain cross-platform copy scenarios This was an issue of Jenkins core. That is fixed in Jenkins 1.464. See also: JENKINS-13649 https://github.com/jenkinsci/jenkins/commit/c92c2217ecb0078f021fab7c9a053d9e63f12143 Change By: ikedam (24/Sep/14 10:41 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] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
ikedam commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters Write versions of Jenkins and related plugins 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] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
ikedam commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters I had a quick look at ssh-agents and credentials, but I don't think they depends on runtime authorization (that is, authorize-project). Do you mean your project works correct only if you uncheck "Configure Build Authorization"? 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-24810) The invoke build for each property file ParameterFactory Generates More than One Set of Builds, Doesn't Stop
ikedam
commented on JENKINS-24810
The invoke build for each property file ParameterFactory Generates More than One Set of Builds, Doesnt Stop
Unfortunately, FileBuildParameterFactory never outputs valid logs (not only for you case). That will be fixed in a future release.
Let me know:
Does that problem always occur? (every time you launch a build of that parent project?)
Do parent builds run on slaves?
Does that problem occur on any slaves? Or only on a specific slave?
Do builds stop to proceed after parameterized-trigger starts? (that is, parameterized-trigger doesn't finish?)
Could you attach config.xml of that project? That is placed at ${JENKINS_HOME}/jobs/(project name)/config.xml.
Could you attach whole console output of that parent build?
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-24810) The invoke build for each property file ParameterFactory Generates More than One Set of Builds, Doesn't Stop
ikedam commented on JENKINS-24810 The invoke build for each property file ParameterFactory Generates More than One Set of Builds, Doesnt Stop It sounds the correct behavior of nodelabelparameter plugin. You should uncheck "Run on all nodes matching the label" of NODE_LABEL. 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-9992) Execute Groovy script after the launch of the downstream jobs
ikedam commented on JENKINS-9992 Execute Groovy script after the launch of the downstream jobs Promoted Builds plugin helps you. 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-13024) Error in log indicating a missing descriptor
ikedam resolved JENKINS-13024 as Fixed Error in log indicating a missing descriptor @brian3791 It sounds a problem completely different from the one originally reported in this issue. Create a new issue if you still have that problem. Change By: ikedam (23/Sep/14 11:43 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] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions Removed "Known Issue" from Wiki 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] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
ikedam resolved JENKINS-9741 as Fixed Copy artifact loses file permissions Fixed in 1.21. I added a test to verify file permission handling: https://github.com/jenkinsci/copyartifact-plugin/pull/45 Change By: ikedam (23/Sep/14 4:37 AM) 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] [script-security] (JENKINS-15210) Add variable resolution to additional groovy class path
ikedam commented on JENKINS-15210 Add variable resolution to additional groovy class path Sorry, I misunderstood the problem. Anyway, it requires approaches other than using variables as jar files in workspaces shouldn't work correct in distributed builds. I agree with @danielbeck. It's often the case users want to reuse a script in multiple projects. 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] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
ikedam updated JENKINS-17418 Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors Groovy-postbuild delegates textareas for groovy script to script-security plugin since 2.0. I removed groovy-postbuild from components and added script-security instead. Change By: ikedam (21/Sep/14 2:09 PM) Component/s: script-security Component/s: groovy-postbuild 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-24163) Allow downstream jobs to push artifact updates to upstream jobs
ikedam commented on JENKINS-24163 Allow downstream jobs to push artifact updates to upstream jobs @jasonsmiley I think what you want is to rerun a multijob from the point it fails. You mean multijob M: Phase1: Run JobA Phase2: Run JobB-F Phase3: Run JobG (aggregates result of B-F) And you want to rerun only B and G if only B fails, don't you? Or, do you mean using "Trigger/call builds on other projects" of parameterized-trigger plugin? Anyway, I don't think they let you do what you want even if new features are added to copyartifact plugin. I recommend you try Promoted Builds plugin. It lets you do like this: Project A triggers project B-F. If all downstream of project A (that is, B-F) secceeds, a promotion of A triggers project G. If B failed, you can retrigger B with Rebuuld plugin, and a promotion can be activated if retriggered B succeeded. You need to understand Jenkins tracking files with fingerprinting. 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-12618) Copy Artifact plugin - Access is denied to copy content
ikedam resolved JENKINS-12618 as Incomplete Copy Artifact plugin - Access is denied to copy content Sounds a problem of inproper permissions on file system. Change By: ikedam (21/Sep/14 2:40 PM) Status: Open Resolved Resolution: Incomplete 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-15210) Add variable resolution to additional groovy class path
ikedam updated JENKINS-15210 Add variable resolution to additional groovy class path Changed component to script-security plugin as the classpaths resolution is done by Script Security plugin since groovy-postbuild 2.0 . I think this feature assumes to use libraries generated in builds. It's not generally secure, and should not be allowed. It should be run with another JVM instance, that is, you should launch new java processes. @jglick Can you have a look at this? I think this can be closed with "Won't Fix". Change By: ikedam (21/Sep/14 1:05 AM) Assignee: wolfs JesseGlick Component/s: script-security Component/s: groovy-postbuild 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-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
ikedam resolved JENKINS-16863 as Duplicate After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable The same root cause to JENKINS-14154. Change By: ikedam (21/Sep/14 1:06 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] [script-security] (JENKINS-24650) Add syntax highlighting like the Scriptler and Groovy plugin have
ikedam updated JENKINS-24650 Add syntax highlighting like the Scriptler and Groovy plugin have Now this is an issue for script-security as textareas of scripts are controlled by script-security since groovy-postbuild 2.0. Change By: ikedam (21/Sep/14 1:51 AM) Assignee: wolfs JesseGlick Component/s: script-security Component/s: groovy-postbuild 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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
ikedam commented on JENKINS-14154 Groovy script can not resolve import classes like hudson.scm.SubversionSCM https://github.com/jenkinsci/groovy-postbuild-plugin/pull/18 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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
ikedam assigned JENKINS-14154 to ikedam Groovy script can not resolve import classes like hudson.scm.SubversionSCM Change By: ikedam (21/Sep/14 2:03 AM) Assignee: wolfs 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] [groovy-postbuild] (JENKINS-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
ikedam started work on JENKINS-14154 Groovy script can not resolve import classes like hudson.scm.SubversionSCM Change By: ikedam (21/Sep/14 2:03 AM) Status: Open InProgress 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-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam updated JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Change By: ikedam (21/Sep/14 3:56 AM) Priority: Blocker Major 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-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam commented on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact https://github.com/jenkinsci/copyartifact-plugin/pull/44 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-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam started work on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Change By: ikedam (21/Sep/14 3:56 AM) Status: Open InProgress 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-14367) Copy Artifact / Archive Artifact: archive as root
ikedam resolved JENKINS-14367 as Duplicate Copy Artifact / Archive Artifact: archive as root Duplicates JENKINS-12379 Change By: ikedam (19/Sep/14 12:19 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-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam commented on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Yes, it no longer tests builds by string comparison, and we will be no longer bothered by "plugin=". I also have to add texts not to use build selecter variables as parameter filters. I don't agree "Upstream of" as it's confusing especially when used in a project configuration 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] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam assigned JENKINS-24626 to ikedam Parameter values of build selector change when upgrading CopyArtifact Change By: ikedam (16/Sep/14 10:19 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-13551) Copy Artifact fails if selector class=hudson.plugins.copyartifact.StatusBuildSelector is set
ikedam resolved JENKINS-13551 as Duplicate Copy Artifact fails if selector class=hudson.plugins.copyartifact.StatusBuildSelector is set Looks duplicate JENKINS-11073 and JENKINS-13515, and should have been already fixed in the latest version. Change By: ikedam (16/Sep/14 2:54 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] [parameterized-trigger] (JENKINS-24622) Upstream jobs have disapeared from job main page
ikedam commented on JENKINS-24622 Upstream jobs have disapeared from job main page Though I think that was a quite thouhtless change, it's a current feature and reverting would affect many users. I think adding an option to declare project dependency which defaults to false (compatible with current behavior), that provides a behavior compatible to 2.16. I can't get why they merged this pull request instead. https://github.com/jenkinsci/parameterized-trigger-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] [groovy-postbuild] (JENKINS-14523) Expand icons one can use for summaries like already done for badges
ikedam updated JENKINS-14523 Expand icons one can use for summaries like already done for badges Change By: ikedam (17/Sep/14 12:09 AM) Issue Type: Bug NewFeature 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-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam commented on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Though I believe I can remove "plugin" attribute by overwiting XStream2#createDefaultConverter, that's not a good approach as it might cause copyartifact stop working in a future version of Jenkins. https://github.com/jenkinsci/jenkins/blob/jenkins-1.565.1/core/src/main/java/hudson/util/XStream2.java#L122 Rather, I'm considering adding a new build selector "Downstream of". You can pick the build like this: Which build: Downstream of Upstream project: DepJob Upstream build #: 123 Target Downstream Project: MainJob 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-24163) Allow downstream jobs to push artifact updates to upstream jobs
ikedam commented on JENKINS-24163 Allow downstream jobs to push artifact updates to upstream jobs I finally got what you want: Project1 triggers Project2. Project2 creates a file "artifact.tgz" in its build. You want have Project1 to archive "artifact.tgz". I think that's extension not for copyartifact, but for ArtifactArchiver which is a part of Jenkins core. Or consider creating a new plugin. Also have a look at JENKINS-10861 . 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-24163) Allow downstream jobs to push artifact updates to upstream jobs
ikedam commented on JENKINS-24163 Allow downstream jobs to push artifact updates to upstream jobs @asmundo You can try multi-configuration project. It allows you to trigger child builds for multiple environments, and builds are aggregated into a parent build. It is a little complicated to configure, but easy to manage. 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-14108) Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only
ikedam resolved JENKINS-14108 as Wont Fix Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only It's the current designated behavior of Jenkins. Change By: ikedam (14/Sep/14 2:02 PM) Status: Open Resolved Resolution: WontFix 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-24694) Whitelisted method to test whether matrix parent build
ikedam created JENKINS-24694 Whitelisted method to test whether matrix parent build Issue Type: Improvement Assignee: ikedam Components: groovy-postbuild Created: 13/Sep/14 8:26 AM Description: Groovy-postbuild plugin introduces script-security. When groovy-postbuild is used in a matrix project and run both in parent builds and child build, it requires manager.build to test whether it is running on a parent build. It always requires administrators' script approval. I need a whitelisted method to test whether the current build is the parent or a child. 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] [groovy-postbuild] (JENKINS-24694) Whitelisted method to test whether matrix parent build
ikedam commented on JENKINS-24694 Whitelisted method to test whether matrix parent build https://github.com/jenkinsci/groovy-postbuild-plugin/pull/15 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-24695) Have manager.envVars whitelisted
ikedam created JENKINS-24695 Have manager.envVars whitelisted Issue Type: Improvement Assignee: ikedam Components: groovy-postbuild Created: 13/Sep/14 9:06 AM Description: manager.envVars is not whitelisted. But I love that property as I can use groovy exppressions like manager.envVars["foobar"] 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] [groovy-postbuild] (JENKINS-24695) Have manager.envVars whitelisted
ikedam
closed JENKINS-24695 as Wont Fix
Have manager.envVars whitelisted
Hmm... I planned to decorate envVars with `Collections.unmodifiableMap`, but that results unable to use `manager.envVars.expand("${foobar}")`.
I think that is not reasonable.
I decline this issue.
Change By:
ikedam
(13/Sep/14 9:19 AM)
Status:
Open
Closed
Resolution:
WontFix
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-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin
ikedam commented on JENKINS-24626 Unable to CopyArtifact from builds using older CopyArtifact plugin I found the root cause. It is caused for SELECT_ME=$SELECT_DEPJOB does not work. A build of SubJob with copyartifact 1.26 is recorded like this (see recorded with plugin="copyartifact@1.26"): hudson.model.ParametersAction parameters hudson.model.StringParameterValue nameSELECT_ME/name description/description valuelt;SpecificBuildSelector plugin=quot;copyartifact@1.26quot;gt; lt;buildNumbergt;1lt;/buildNumbergt;lt;/SpecificBuildSelectorgt;/value /hudson.model.StringParameterValue /parameters /hudson.model.ParametersAction When running MainJob is started with copyartifact 1.31, the build is launched like this (see recorded with plugin="copyartifact@1.31"): hudson.model.ParametersAction parameters hudson.model.StringParameterValue nameSELECT_DEPJOB/name description/description valuelt;SpecificBuildSelector plugin=quot;copyartifact@1.31quot;gt; lt;buildNumbergt;1lt;/buildNumbergt;lt;/SpecificBuildSelectorgt;/value /hudson.model.StringParameterValue /parameters /hudson.model.ParametersAction And they doesn't satisfy SELECT_ME=$SELECT_DEPJOB. As that serialization is the work of Jenkins core (or Jenkins framework), and I'm not sure I can fix that. I think we should consider an alternate way to do what @tom_ghyselinck want to do. 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-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam updated JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Updated the summary Change By: ikedam (14/Sep/14 4:10 AM) Summary: Unableto Parametervaluesofbuildselectorchangewhenupgrading CopyArtifact frombuildsusingolderCopyArtifactplugin 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-24622) Upstream jobs have disapeared from job main page
ikedam
commented on JENKINS-24622
Upstream jobs have disapeared from job main page
I succeeded to reproduce the problem.
Manage Jenkins Script Console
With parameterized-trigger-2.16:
Jenkins.instance.getItem("Job-B").upstreamProjects
Result: [hudson.model.FreeStyleProject@76712b2f[Job-A]]
With parameterized-trigger-2.17:
Jenkins.instance.getItem("Job-B").upstreamProjects
Result: []
It looks that DependencyGraph which notifies Jenkins project dependency is removed from TriggerBuilder since 2.17.
https://github.com/jenkinsci/parameterized-trigger-plugin/commit/e2e678807107e579c4af42d912d3c62a0564abb0
https://github.com/jenkinsci/parameterized-trigger-plugin/pull/19
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-9741) Copy artifact loses file permissions
ikedam
commented on JENKINS-9741
Copy artifact loses file permissions
Before writing tests, I tested the behavior in my environment (Jenkins 1.590.1 + Copyartifact 1.30, Linux master / slave).
It looks that the problem happens not when copying, but when archiving (that is, in upstream builds).
@tsackett
Can you see file permissions of archived artifacts?
They should be in ${JENKINS_HOME}/jobs/(project name)/builds/(build number)/archive . They look lose permissions when archiving on master.
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-24622) Upstream jobs have disapeared from job main page
ikedam commented on JENKINS-24622 Upstream jobs have disapeared from job main page Thanks for details. I'll test reproduction in my environment and see changes of codes in 2.17. 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-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
ikedam resolved JENKINS-22125 as Fixed FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 No details. Looks an invalid reopen. Change By: ikedam (11/Sep/14 11:34 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-24622) Upstream jobs have disapeared from job main page
ikedam commented on JENKINS-24622 Upstream jobs have disapeared from job main page I started to maintain parameterized-trigger-plugin since 2.19, and I'm not sure the behavior you expect. I have to see how it worked before you upgrade parameterized-trigger plugin. From what version did you upgrade parameterized-trigger-plugin? Can you downgrade the plugin and attach the screenshot with that version? Used in a build step, a upstream build is always running when triggered a downstream build. What's your expecting behavior with "Block build when upstream project is building"? The latest version of parameterized-trigger-plugin is 2.25, and 2.17 is old version. On the other hand, Jenkins 1.565.1 is the latest LTS. That sounds strange to me. Do you mean you found the problems in the latest parameterized-trigger-plugin and you found they occur not with 2.16 but with 2.17? Let me know if you also upgraded Jenkins core. As far as I know, parameterized-trigger-plugin doesn't handle displaying upstream projects nor "Block build when upstream project is building"?. They might be caused by upgrade of Jenkins core. 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] [p4] (JENKINS-24512) Add option to lock the created workspace to a host
ikedam reopened JENKINS-24512 Add option to lock the created workspace to a host Sorry! I commeted with a wrong message. That commet is completely not related to p4 plugin. Change By: ikedam (11/Sep/14 12:14 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobcopy-builder] (JENKINS-24515) Copy a job into a folder
ikedam closed JENKINS-24515 as Fixed Copy a job into a folder Released in 1.2.0 Change By: ikedam (11/Sep/14 12:23 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] [copyartifact] (JENKINS-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin
ikedam
commented on JENKINS-24626
Unable to CopyArtifact from builds using older CopyArtifact plugin
Let me know:
Does SubJob work fine after upgrading copyartifact to 1.31?
Did MainJob work fine before upgrading copyartifact to 1.31?
And could you attach following files?
configurations of those jobs. They are placed at ${JENKINS_HOME}/jobs/(jobname)/config.xml
console outputs for a succeeded build and a failed build.
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-24622) Upstream jobs have disapeared from job main page
ikedam commented on JENKINS-24622 Upstream jobs have disapeared from job main page Could you attach screen shots? (before upgrading and after upgrading) Please let me know the version of 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] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions Could you report more details of your problem? Especially, I want to know your OS and whether you use distributed build (master / slave). Copyartifact completely changed the copying mechanism in 1.21. Almost all comments in this page are already outdated, and I want to know problems with the latest version. I'll try to add automated tests for file permissions. 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-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions That known issue was added in 1.17, and may be outdated. https://wiki.jenkins-ci.org/pages/diffpagesbyversion.action?pageId=42470728selectedPageVersions=33selectedPageVersions=32 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] [windows-slaves] (JENKINS-22864) JVM Failure:Windows Slave Connection Reset
ikedam resolved JENKINS-22864 as Duplicate JVM Failure:Windows Slave Connection Reset Looks same to JENKINS-10582. This should be an issue of Java Native Access or usage of that in Jenkins. Change By: ikedam (02/Sep/14 10:40 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] [core] (JENKINS-10582) slave connection breaks thru EXCEPTION_ACCESS_VIOLATION
ikedam updated JENKINS-10582 slave connection breaks thru EXCEPTION_ACCESS_VIOLATION Change By: ikedam (02/Sep/14 10:54 AM) Component/s: windows-slaves 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-10582) slave connection breaks thru EXCEPTION_ACCESS_VIOLATION
ikedam commented on JENKINS-10582 slave connection breaks thru EXCEPTION_ACCESS_VIOLATION I'm also annoyed with this issue. This looks caused by JNA (Java Native Access), not by JVM, Sun or Oracle. (com.sun.jna is misleading!) Possible causes I think: Jenkins uses JNA in a bad way. JNA bundled with Jenkins is based on an old version JNA (3.3.0, latest is 3.5.2 and 4.1.0) and that version might have a bug in memory managing. Steps to resolve this: Find a concrete way to reproduce the problem. It looks happen only on Windows. It may happen only when launched as a Windows service. It may happen only with 64bits JVM or Windows. I think calling System.gc() on slave may trigger this problem. Write a sample code to reproduce JVM crash with JNA. 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-10582) slave connection breaks thru EXCEPTION_ACCESS_VIOLATION
ikedam updated JENKINS-10582 slave connection breaks thru EXCEPTION_ACCESS_VIOLATION Change By: ikedam (02/Sep/14 11:49 PM) Environment: Master:WindowsServer2003,JDK1.6.0_23_x64,Jenkinsv1.415Slaves:WindowsServer2003/2008,JRE1.6.0_23_x64 (JENKINS-22864)1.549OracleJRE1.7u40+(64bit) 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] [jobcopy-builder] (JENKINS-24515) Copy a job into a folder
ikedam created JENKINS-24515 Copy a job into a folder Issue Type: New Feature Assignee: ikedam Components: jobcopy-builder Created: 30/Aug/14 5:49 AM Description: It is useful if I can specify the target folder to copy a job into. 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] [copyartifact] (JENKINS-24084) Slave file leak build is interrupted during Copy Artifacts build step
ikedam updated JENKINS-24084 Slave file leak build is interrupted during Copy Artifacts build step Please report the version of copyartifact. Anyway, it happened here: https://github.com/jenkinsci/copyartifact-plugin/blob/copyartifact-1.31/src/main/java/hudson/plugins/copyartifact/FingerprintingCopyMethod.java#L79 As copyartifact closes the handle when interrupted in the finally clause, this looks the problem of Jenkins core, hudson-remoting. That is, even a file handle is closed in the master, it still remains open in the slave for some remoting problems. Change By: ikedam (30/Aug/14 5:48 AM) Environment: WindowsServer2012R2Java1.7.0_55-b13 Jenkinsis1.574(slave2.43) 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-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
ikedam commented on JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) It looks that URL#openStream for directories results file lists in directories. 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-24400) ClasspathEntryTest#pathURLConversion fails on Windows
ikedam created JENKINS-24400 ClasspathEntryTest#pathURLConversion fails on Windows Issue Type: Bug Assignee: ikedam Components: script-security Created: 24/Aug/14 6:18 AM Description: ClasspathEntryTest#pathURLConversion fails on Windows like this: --- Test set: org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest --- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec FAILURE! pathURLConversion(org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest) Time elapsed: 0.016 sec FAILURE! org.junit.ComparisonFailure: expected:[/tmp/]x.jar but was:[C:\tmp\]x.jar at org.junit.Assert.assertEquals(Assert.java:125) at org.junit.Assert.assertEquals(Assert.java:147) at org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest.assertRoundTrip(ClasspathEntryTest.java:38) at org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest.pathURLConversion(ClasspathEntryTest.java:34) Environment: script-security-1.5, Windows 8 (64bits) Project: Jenkins Priority: Minor 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] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
ikedam created JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Issue Type: Bug Assignee: Jesse Glick Components: script-security Created: 24/Aug/14 12:44 AM Description: script-security 1.5 introduced "Additional classpath". Those classpaths require administrators' approval. Class directories are valid for "Additional classpath". Once class directories are appoved, adding or replacing files in sub directories of those class directories no longer require approval. This should allow users to use classes that administrators doesn't want to allow. Possible resolution: Don't allow class directories for "Additional classpath" This doesn't cause critical regressions as it is easy to create jar file from class directories. When a class directory is specified, check all files in the class directory. Leave this as a limitation. I'll add a test and send a pull request to see this behavior. Environment: Jenkins 1.509.4, script-security 1.5, Java 1.7.0_45, Windows 8 (64bit) 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] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
ikedam commented on JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Pull request to demonstrate this problem: https://github.com/jenkinsci/script-security-plugin/pull/4 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-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
ikedam commented on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run I want to see how much time each steps of builds spend. Could you install Timestamper plugin, enable "Add timestamps to the Console Output" in your job, and attach a consple output that reproduces the 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] [maven] (JENKINS-24299) OutOfMemoryError cause maven projects hang
ikedam updated JENKINS-24299 OutOfMemoryError cause maven projects hang I reproduced the problem: Install Jenkins 1.565.1 Install git-plugin and restart Go to Manage Jenkins Configure System Add a valid JDK (I tested with jdk1.7.0_45) Add a valid Maven (I tested with auto-installed maven 3.2.1 Create a maven 2/3 project Add a git repository https://github.com/jenkinsci/build-timeout-plugin.git Setup Build as followings: Root POM: pom.xml Goals and options: -DforkMode=never test MAVEN_OPTS: -XX:MaxPermSize=16m Run a build Result: The build hangs with following output in console. Exception in thread "Channel reader thread: channel" java.lang.OutOfMemoryError: PermGen space There are cases that log is not output till abort the build (first abort). It looks that the log is buffered. The child java process still remains. Aborting the build does not work for the first time. The child java process still remains. Aborting the build again works. I attached console logs and outputs: Console text when the build hangs: hangingConsoleText.txt Thread dump (copied from the output from /threadDump) when the build hangs: hangingConsoleText.txt Thread dump when the build does not hang (launched without -XX:MaxPermSize): correctThreaddump.txt Output when launched maven in console: launchedFromConsole.log The process doesn't hang. (the control was returned) I launched it as following: set MAVEN_OPTS=-XX:MaxPermSize=16m mvn -DforkMode=never test Change By: ikedam (21/Aug/14 11:56 PM) Summary: Mavenprojectbuildfailstoterminatehangingbuildprocess OutOfMemoryErrorcausemavenprojectshang Labels: remoting Attachment: hangingConsoleText.txt Attachment: hangingThreadDump.txt Attachment: correctThreaddump.txt Attachment: launchedFromConsole.log Environment: Jenkins1.565.1,SLES11.3 ReproducedJenkins1.565.1,maven-plugin2.3,Java1.7,Windows8(64bits) Component/s: maven Component/s: core 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-24092) Matrix Project Plugin- Success and Failed filter: doesn't work
ikedam resolved JENKINS-24092 as Duplicate Matrix Project Plugin- Success and Failed filter: doesnt work Duplicates JENKINS-23609 Change By: ikedam (20/Aug/14 10:59 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-24152) New Build trigger that fires when builds of projects to copy from finished
ikedam
updated JENKINS-24152
New Build trigger that fires when builds of projects to copy from finished
Change By:
ikedam
(20/Aug/14 11:08 AM)
Summary:
Addanoption
NewBuildtriggerthatfireswhenbuildsofprojects
tocopy
artifactstotriggerjobforallupstreamjobscopied
from
finished
Description:
Worklike{{ReverseBuildTrigger}}(Buildafterotherprojectsarebuilt)
Itwouldbeniceiftherewasanoptioninthecopyartifactsplugintoautomaticallyusealllistedjobswhereartifactsarecopiedfromforthetriggeringmechanism.ThismeansthatintheendthejobIameditingshouldautomaticallybetriggeredifanyoftheupstreamjobshasbuiltwithoutmanuallyneedingtomanagetheupstreamtriggerlistifprojects.Fromourexperience,thesetwolistsdeviateeasilyincasesomeonechangesthejob.
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-22480) copyartifact plugin does not properly check files it has transferred
ikedam updated JENKINS-22480 copyartifact plugin does not properly check files it has transferred I think that's a problem of your system. I don't think checksums can always resolve the problem for that case. Even though the request is valid, I rather recommend you to fix your system. That would cause other problems. Change By: ikedam (20/Aug/14 11:16 AM) Issue Type: Bug NewFeature Priority: Major Minor 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-22480) option to check file checksums after copying artfacts
ikedam updated JENKINS-22480 option to check file checksums after copying artfacts Change By: ikedam (20/Aug/14 3:42 PM) Summary: copyartifactplugindoesnotproperly optionto check filesithastransferred filechecksumsaftercopyingartfacts 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-24299) Maven project build fails to terminate hanging build process
ikedam commented on JENKINS-24299 Maven project build fails to terminate hanging build process I'm triyng to reproduce OutOfMemoryError in a maven project by launching Jenkins with XX:PermGen, but I still fail to reproduce that. Could you tell me example steps to reproduce OutOfMemoryError? 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-24299) Maven project build fails to terminate hanging build process
ikedam updated JENKINS-24299 Maven project build fails to terminate hanging build process Change By: ikedam (19/Aug/14 10:37 AM) Labels: remoting Assignee: KohsukeKawaguchi Component/s: core Component/s: build-timeout Component/s: maven 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-24299) Maven project build fails to terminate hanging build process
ikedam updated JENKINS-24299 Maven project build fails to terminate hanging build process This rather looks an issue of Jenkins core, as build-timeout only aborts build steps and cannot abort hanged threads. I changed the component. Let me know followings: The version of your Jenkins. Do you run Jenkins on master / slave mode? https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds Can you reproduce the problem if needed? 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-12204) Add extension point for copy artifact to be able to copy the downstream build instead of the last successful
ikedam assigned JENKINS-12204 to ikedam Add extension point for copy artifact to be able to copy the downstream build instead of the last successful Change By: ikedam (18/Aug/14 10:25 AM) Assignee: huybrechts 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-12204) Add extension point for copy artifact to be able to copy the downstream build instead of the last successful
ikedam resolved JENKINS-12204 as Duplicate Add extension point for copy artifact to be able to copy the downstream build instead of the last successful Sounds completely same to JENKINS-10861 Change By: ikedam (18/Aug/14 10:26 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-14650) Please add specified by permalink:Latest promotion to the which build option for MATRIX projects
ikedam resolved JENKINS-14650 as Fixed Please add specified by permalink:Latest promotion to the which build option for MATRIX projects Copyartifact 1.31 allows you input the permalink manually. Have a look at JENKINS-22590 for details. Change By: ikedam (18/Aug/14 10:37 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] [script-security] (JENKINS-22834) Administrator-approved classpath additions
ikedam commented on JENKINS-22834 Administrator-approved classpath additions Pull request https://github.com/jenkinsci/script-security-plugin/pull/1 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 resolved JENKINS-16679 as Fixed project run gets hung up, when run simultaneously Looks fixed in Jenkins 1.558. Change By: ikedam (19/Aug/14 12:27 AM) 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-15476) Block until the triggered projects finish their builds doesn't notify upstream project when complete.
ikedam resolved JENKINS-15476 as Fixed Block until the triggered projects finish their builds doesnt notify upstream project when complete. Looks fixed in Jenkins 1.558. Change By: ikedam (19/Aug/14 12:28 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] [copyartifact] (JENKINS-24152) Add an option to copy artifacts to trigger job for all upstream jobs copied from
ikedam commented on JENKINS-24152 Add an option to copy artifacts to trigger job for all upstream jobs copied from I cannot get what you mean. Let me know an example configration with your requesting feature. 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-24163) Allow downstream jobs to push artifact updates to upstream jobs
ikedam commented on JENKINS-24163 Allow downstream jobs to push artifact updates to upstream jobs I think your problem can be resolved with Promoted Builds plugin, but I couldn't get details of your case. Please describe more details. Using "ProjectA", "ProjectB", ... would make it easy to understand. 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 resolved JENKINS-23181 as Cannot Reproduce NPE caused by copy artifcats while renaming job Though I can fix NPE not to happen even with a broken configuration, I leave that as it's not clear why the configuration is broken. The broken configuration can cause other problems, and that's the problem really to be fixed. I expect this NPE work a kind of a watchdog. Change By: ikedam (19/Aug/14 12:55 AM) Status: Open Resolved Resolution: CannotReproduce 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-24299) Maven project build fails to terminate hanging build process
ikedam commented on JENKINS-24299 Maven project build fails to terminate hanging build process Let me see which seems the problem you faced? Build timeout was not triggered. Build timeout was triggered, but the build didn't terminate. From your log, your case seems the latter one. Is that right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17702) CopyArtifact with parameter selection fails when parameters changed
ikedam
resolved JENKINS-17702 as Cannot Reproduce
CopyArtifact with parameter selection fails when parameters changed
Could not reproduce even with the new information. I tested with Jenkins 1.480.3 + Copyartifact 1.26 + Subversion 1.39 (bundled with Jenkins 1.480.3):
Create a free style project "ProjectX"
Create a file "artifact.txt" with its content "without_parameter"
Archive artifact.txt
Run ProjectX
Update ProjectX
Add a List Subversion tags parameter:
Name: MY_X_PARAM
Repository URL: https://svn.jenkins-ci.org/branches/
Change the name of the artifact to "artifact2.txt" (both copyartifact and archive) and its content to "parameter=${MY_X_PARAM}"
Run ProjectX with MY_X_PARAM=HUDSON-1467
Create a free style project "ProjectY"
Add a string parameter "USE_X_PARAM"
Add a Build selector for Copy Artifact parameter "PROJECT_X_BUILD"
Add "Copy artifact from another project"
Project name: "ProjectX"
Which build: Specified by a build parameter
Parameter Name: PROJECT_X_BUILD
Artifacts to copy: artifact2.txt
Target directory: packages
Parameter filters: MY_X_PARAM=${USE_X_PARAM}
Output the contents of packages/artifact2.txt
Run ProjectY with USE_X_PARAM=HUDSON-1467 and PROJECT_X_BUILD=Latest successful build
Result:
The build of ProjectY succeeded.
The output was: parameter=HUDSON-1467
Change By:
ikedam
(17/Aug/14 10:23 AM)
Status:
Open
Resolved
Resolution:
CannotReproduce
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] [analysis-core] (JENKINS-23752) Duplicated Warnings links when used with Flexible Publish plugin
ikedam
updated JENKINS-23752
Duplicated Warnings links when used with Flexible Publish plugin
I know this behavior well.
I conclude that it's not a bug (a behavior to be fixed), but a limitation (a behavior not to be fixed).
As it is very complicated, I'm not sure I can exactly explain the details (I know my English is poor). But I try that:
Post build steps (Publisher) displays links in the left side of project pages by implementing Publisher#getProjectActions.
You can use each Publisher at most only once in a project. For example, if you added "Archiving artifacts" to a project, you cannot add more new "Archiving artifacts" to that project.
Using Flexible Publish, you can define a same Publisher for multiple times. This is an irregular case. For example, you can add two "Archiving artifacts" for condition A and condition B. This results Publisher#getProjectActions of a same Publisher are called multiple times for a project. This results duplicated links in a project page.
As described before, Publisher should be defined only one in a project. So it's not a bug of Publisher to display duplicated links.
At the same time, Flexible Publish does not know how to handle links. Those links may be better to be displayed for each definition, or may be better to be displayed only once (like Warnings plugin).
As far as I know, this behavior doesn't results harmful, and I don't plan to fix it.
If you try to fix that, the way of SubProjectsAction of parameterized-trigger plugin may be helpful.
https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/SubProjectsAction.java
https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/resources/hudson/plugins/parameterizedtrigger/SubProjectsAction/jobMain.groovy
If multiple {{SubProjectsAction}}s are defined to a build, it aggregates all {{SubProjectsAction}}s to display.
I think aggregating WarningsProjectAction and displaying a link only for the first one would fix the behavior.
But it would get so complicated, and may cause other problems.
And you need to fix not warnings-plugin, but analysis-core-plugin. It may affect other plugins using analysis-core-plugin.
Change By:
ikedam
(17/Aug/14 11:29 AM)
Summary:
MSBuild
Duplicated
Warnings
linkdisplaystwiceonbuildsifaddedasconditionalbuildstep
linkswhenusedwithFlexiblePublishplugin
Issue Type:
Bug
Improvement
Assignee:
ikedam
UlliHafner
Component/s:
analysis-core
Component/s:
conditional-buildstep
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-24279) run custom shell script on Build timeout as pre-on-timeout hook
ikedam resolved JENKINS-24279 as Duplicate run custom shell script on Build timeout as pre-on-timeout hook Duplicates JENKINS-12744 Change By: ikedam (17/Aug/14 10:48 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] [parameterized-trigger] (JENKINS-23717) Add link to specific build ID in console output
ikedam resolved JENKINS-23717 as Wont Fix Add link to specific build ID in console output Downstream build numbers is to be removed as they can be wrong. Have a look at JENKINS-24257. Change By: ikedam (18/Aug/14 12:17 AM) Status: Open Resolved Resolution: WontFix 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-19806) Parameters passed to downstream jobs hiding option at downstream queue list
ikedam updated JENKINS-19806 Parameters passed to downstream jobs hiding option at downstream queue list That displays are handled not by parameterized-trigger plugin but by Jenkins core. I changed the component to core. Change By: ikedam (18/Aug/14 12:23 AM) Assignee: huybrechts 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] [parameterized-trigger] (JENKINS-17275) Use Environment Variable when triggering downstream jobs.
ikedam resolved JENKINS-17275 as Duplicate Use Environment Variable when triggering downstream jobs. Duplicates JENKINS-11280 . Though I agree that this is an improvement and not a bug, I merge issues to the older one. Change By: ikedam (18/Aug/14 12:32 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] [parameterized-trigger] (JENKINS-8141) Allow re-triggering of downstream projects with parameters from a prior source build.
ikedam resolved JENKINS-8141 as Wont Fix Allow re-triggering of downstream projects with parameters from a prior source build. Rebuild plugin allows you relaunch a build with the same parameters. Let's try that. https://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin Change By: ikedam (18/Aug/14 12:46 AM) Status: Open Resolved Resolution: WontFix 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-24257) Guessed downstream build # in console log can be wrong in Parameterized Trigger Plugin
ikedam updated JENKINS-24257 Guessed downstream build # in console log can be wrong in Parameterized Trigger Plugin Change By: ikedam (14/Aug/14 12:47 PM) Summary: BuildAtriggers Guesseddownstreambuild#inconsolelogcanbewronginParameterizedTriggerPlugin 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-24257) Build A triggers Guessed downstream build # in console log can be wrong in Parameterized Trigger Plugin
ikedam updated JENKINS-24257 Build A triggers Guessed downstream build # in console log can be wrong in Parameterized Trigger Plugin @danielbeck is right. There seems no way to guess correct build #. It should be removed as confusing. Change By: ikedam (14/Aug/14 12:46 PM) Summary: BuildAtriggers Guesseddownstream build B3timesviaParameterizedTriggerPlugin;allthreehavesame #inconsole output(butareconsecutive) logcanbewronginParameterizedTriggerPlugin 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-24199) Post Build trigger parameterized job does not resolve variables used for job name
ikedam resolved JENKINS-24199 as Duplicate Post Build trigger parameterized job does not resolve variables used for job name Duplicates JENKINS-11280 Change By: ikedam (12/Aug/14 12:39 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] [core] (JENKINS-23645) Archiving artifacts does not preserve timestamps if archived on master
ikedam
updated JENKINS-23645
Archiving artifacts does not preserve timestamps if archived on master
That's exactly what @danielbeck pointed.
Thanks for clarifying.
I updated the summary and the description.
I think it won't be fixed so soon, and you'd better try workarounds like:
Archive files with zip command in the upstream project, and extract them with unzip in the downstream project.
Have builds run only on slaves. This can be done by enabling "Restrict where this project can be run" in project configuration pages.
Change By:
ikedam
(12/Aug/14 11:21 PM)
Summary:
Archivingartifactsdoesnotpreservetimestampsif
filteris**
archivedonmaster
Assignee:
GregoryBoissinot
Environment:
Windows7
,Java1.8,Jenkins1.575
Description:
Whenabuildrunonthemaster,Archivetheartifactsdoesntpreservetimestamps.Itpreservestimestampswhenrunonslaves.Itlookscausedby{{FilePath.copyRecursiveTo}}.Originaldescription(theissuewasfoundnotofCopyartifact,butofArtifactArchiver):
Thetimestampsofartifactsarenotpreservedwhenarchivingartifacts,ORperformingaCopyArtifactoperationiftheartifactfilterissetto**.Forexamplethefilter{code}myfolder\**{code}willpreservetimestamps.WeusemutiplechainedJenkinsjobstoperformabuild.Ifthetimestampsofdependencyfilesintheartifactpassedbetweenjobsisnotpreserved,thensubsequentjobswillfail.
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-17702) CopyArtifact with parameter selection fails when parameters changed
ikedam
commented on JENKINS-17702
CopyArtifact with parameter selection fails when parameters changed
Could not reproduce. I tested with Jenkins 1.480.3 + Copyartifact 1.26:
Create a free style project "ProjectX"
Create a file "artifact.txt" with its content "without_parameter"
Archive artifact.txt
Run ProjectX
Update ProjectX
Add a choice parameter "MY_X_PARAM" with values only "test".
Change the content of artifact.txt to "parameter=${MY_X_PARAM}"
Run ProjectX (with MY_X_PARAM=test)
Create a free style project "ProjectY"
Add "Copy artifact from another project"
Project name: "ProjectX"
Which build: Latest successful build
Parameter filters: MY_X_PARAM=test
Output the contents of artifact.txt
Run ProjectY
Result:
The build of ProjectY succeeded.
The output was: parameter=test
Please report the detailed step to reproduce.
I'll close this issue in a month.
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-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions What's the status of this issue? Copyartifact looks preserve file permissions. FilePathCopyMethod without enabling flatten still breaks file permissions, but there's no way for users to use FilePathCopyMethod. I think I can fix that, but there's no way to test that. Anyway, even if there are users who want FilePathCopyMethod fixed, another issue should be created. I plan to close this issue with 'Fixed'. Please let me know if there is still a problem to fix. 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-23645) Archiving artifacts does not preserve timestamps if filter is **
ikedam commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** Let me see. The problem happened not at "Copy artifacts from another project" in a downstream project, but at "Archive the artifacts" in a upstream project, right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23927) Parameterized trigger should be able to optionally retry failed blocked builds
ikedam commented on JENKINS-23927 Parameterized trigger should be able to optionally retry failed blocked builds Retrying feature sounds useful not only for parameterized-trigger plugin but also for any build steps. How about creating a new plugin to retry any build steps? Anyway, the disign of Jenkins and parameterized-trigger plugin is not optimized for complex moduled projects like what you try. workflow-plugin may help you. Please have a look. 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-14108) Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only
ikedam commented on JENKINS-14108 Multiple parameterized upstreams with joined in one blocked while.. job result in multiple executions rather one only This looks a current designated behavior of Jenkins. When triggerd a job with different parameters, Jenkins should trigger builds for each parameters, and shouldn't merge them. It's recommended to use Promoted Builds plugin or Join plugin for this scenario. Anyway, this issue is very old, and I'm afraid there are no longer users interested in this issue. (And I don't think this is still a blocker.) I plan to close this issue with "Won't Fix" in a month. Please let me know if anyone still looks this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
ikedam commented on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run Is this problem still reproduced? As @km said, this shouldn't be triggered by build-timeout plugin for its design, and it seems something strange happen in communication between the master and slaves. I need more information to say what's the root cause, and please let me know you can still reproduce the 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] [build-timeout] (JENKINS-10439) IOException while archiving AND wrong build status
ikedam commented on JENKINS-10439 IOException while archiving AND wrong build status Let me know: how often it happens? It can be always reproduced if you set short timeout? If it rarely happens, it may be caused by another operator clicking the abort link manually. No abort operation message is output to console log since Jenkins 1.426 (JENKINS-5754). 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-23645) Archiving artifacts does not preserve timestamps if filter is **
ikedam commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** Please report your versions of Java, Jenkins, and copyartifact plugin. It is a known issue that timestamps are not preserved in Winsows. It is rather a limitation of Java on Windows. (see JENKINS-11073, JENKINS-13515). If you use Java = 1.6, please try Java 1.7 (and the latest LTE version of Jenkins) and see the problem reproduces. But I'm not sure why the filter affects the behavior. You'd better check the owner and permissions of the workspace folder of that job. Jenkins might fail to change the attributes of files directly under the workspace folder for its permission. 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.
