[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
kutzi updated JENKINS-18907 Expose svn current revision in addition to the last-changed revision Change By: kutzi (29/Jul/13 8:31 AM) Summary: Addfeature Exposesvncurrentrevisioninaddition to expose the latest last-changed revision numberofacheckout This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
Kevin Phillips commented on JENKINS-18907 Expose svn current revision in addition to the last-changed revision Your proposal indeed sounds reasonable. I was actually considering putting in a pull request. I am not that familiar with that process as I've never done that before but I had considered figuring that out at some point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
Kevin Phillips edited a comment on JENKINS-18907 Expose svn current revision in addition to the last-changed revision I had one somewhat-unrelated question. You mention that externals should be avoided if possible - do you know of another way of managing complex sets of dependencies between subsystems without using externals? I am working in a C++ shop so we don't have the luxury of advanced dependency management tools like Maven, Nexus and such. Externals seem like the only practical solution for this in our case. Also, just so you know, all three of the "potential use cases" I outlined above we actually do use (or have tried) at our site... so they aren't really "potential" in that regard. And use case #1 is our most common usage pattern at the moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
Kevin Phillips commented on JENKINS-18907 Expose svn current revision in addition to the last-changed revision I had one somewhat-unrelated question. You mention that externals should be avoided if possible - do you know of another way of managing complex sets of dependencies between subsystems without using externals? I am working in a C++ shop so we don't have the luxury of advanced dependency management tools like Maven, Nexus and such. Externals seem like the only practical solution for this in our case. Also, just so you know, all three of the "potential use cases" I outlined above we actually do use (or have tried) at our site... so they aren't really "potential" in that regard. And option #1 is our most common usage pattern at the moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
kutzi commented on JENKINS-18907 Expose svn current revision in addition to the last-changed revision Basically, the workflow I would propose is this: Fork the Jenkins repository at Github Clone your forked repository Create a new branch for the change Do the changes Send out the pull request See also https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-pullrequest This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
kutzi commented on JENKINS-18907 Expose svn current revision in addition to the last-changed revision "do you know of another way of managing complex sets of dependencies between subsystems without using externals? I am working in a C++ shop so we don't have the luxury of advanced dependency management tools like Maven, Nexus and such" Dependency management would have been my recommendation... - It's vastly superior to externals IMO I don't know much about C++ development, so I cannot give you any advise how to do dep management there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Expose svn 'current' revision in addition to the 'last-changed' revision
Kevin Phillips commented on JENKINS-18907 Expose svn current revision in addition to the last-changed revision I figured it was a long shot, but that is the story of my life Dependency management in C++ is a complex beast and I haven't found any good tools (and very few not-so-good tools) to do the job. Externals handle the basics code dependencies for us, and we use Visual Studio to handle some of the project / module dependencies but VS doesn't scale well to very-large-scale cross-team projects unfortunately (and it isn't cross platform either which sucks). I just mention all this because even if use case #1 should be avoided, I think it is a very real and important use case that isn't all that uncommon. I wouldn't discount it out-of-hand. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
