[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann commented on JENKINS-24739 import additional job properties Did not have all this data in mind when opening this issue. Also didn't find the next build number plugin before. Will use this now as a workaround. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann updated JENKINS-24739 import additional job properties Change By: Tobias Hartmann (17/Sep/14 9:33 AM) Description: When importing a job from another instance also make it possible to import other job properties than the configuration xml.Being able to conveniently import the job history information and the nextBuildNumber file would ease the process of moving jobs without breaking existing environments. Edit: As an import of a complete job history is a too heavy task better performed separately just having the option to import parts of it like the nextBuildNumber file would be very convenient. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann commented on JENKINS-24739 import additional job properties I don't wanna copy the whole workspace. I was more thinking in terms of build result reports and logs but this also is a massive amount of data for longer running jobs. At least an option to import the nextBuildNumber would be nice to be able to build the connection between an old job and its copy on a new system. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann edited a comment on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration. Edit: We independent Jenkins instances running that were added with increasing demands, but are now moving to a better scalable master-slave setup. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann edited a comment on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration. Edit: We had independent Jenkins instances running that were added with increasing demands, but are now moving to a better scalable master-slave setup. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann edited a comment on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann commented on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server it'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration. 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann created JENKINS-24739 import additional job properties Issue Type: New Feature Assignee: Unassigned Components: job-import Created: 17/Sep/14 7:49 AM Description: When importing a job from another instance also make it possible to import other job properties than the configuration xml. Being able to conveniently import the job history information and the nextBuildNumber file would ease the process of moving jobs without breaking existing environments. Project: Jenkins Labels: job Priority: Minor Reporter: Tobias Hartmann 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.
