[JIRA] [core] (JENKINS-24141) SCM with non-AbstractProject, revisited
Title: Message Title Alexander Vorobiev commented on JENKINS-24141 Re: SCM with non-AbstractProject, revisited Per http://stackoverflow.com/questions/30398465/how-to-get-culprits-or-committers-inside-a-jenkins-workflow-with-one-or-more-scm this blocks https://issues.jenkins-ci.org/browse/JENKINS-34763. Is it still correct? I see JENKINS-34763 as the main blocker on the way to Jenkins pipeline. Can this be prioritized? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24141) SCM with non-AbstractProject, revisited
Jesse Glick commented on JENKINS-24141 SCM with non-AbstractProject, revisited Perhaps also need to add SCM.buildEnvVars(Run, FilePath, MapString,String). 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-24141) SCM with non-AbstractProject, revisited
Jesse Glick created JENKINS-24141 SCM with non-AbstractProject, revisited Issue Type: Task Assignee: Unassigned Components: core Created: 06/Aug/14 9:00 PM Description: JENKINS-23365 made it possible to use SCM from other contexts. But there are still some SCM-oriented things stuck in AbstractProject/AbstractBuild which ought to be generalized. AbstractBuild.getChangeSets (as used by project-changes.jelly) does not implement any method. Either this should be pushed up into Run so that it can be used more generally (simple though an awkward introduction of SCM specifics into Run); or SCMTriggerItem should add getChangeSets(Run) (more sensible architecturally, though awkward since it could not have a generic type for the build). getCulprits and hasParticipant would seem to apply to any build with changes. AbstractProject.doRssChangelog could be moved elsewhere and use getChangeSets. View.AsynchPeople could use getChangeSets. Possibly there needs to be an interface for a Run with changes, tied somehow to SCMTriggerItem and with some default methods? Project: Jenkins Labels: scm api workflow Priority: Major Reporter: Jesse Glick 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.
