RE: Automate CloudStack release packaging with Jenkins
Awesome, thanks Gabriel! If you need any help just shout, I think a few 'stackers have experience setting up Jenkins to package the code. Regards Paul. paul.an...@shapeblue.com www.shapeblue.com 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK @shapeblue -Original Message- From: Gabriel Beims Bräscher Sent: 06 April 2020 12:56 To: Sven Vogel Cc: dev@cloudstack.apache.org Subject: Re: Automate CloudStack release packaging with Jenkins Hello all, Considering that there are no objections, I will spin a Jenkins node this week :) Cheers, Gabriel. Em sáb., 4 de abr. de 2020 às 18:21, Sven Vogel escreveu: > I am aboard and can help. first with configuring. +1 from me. We use > Jenkins too and read from Pierre he has maybe an old config. since > corona I don’t got our test environment running in data Center :( .. > If this will better I can share Jenkins slaves. > > Cheers > > > __ > > Sven Vogel > Lead Cloud Solution Architect > > EWERK DIGITAL GmbH > Brühl 24, D-04109 Leipzig > P +49 341 42649 - 99 > F +49 341 42649 - 98 > s.vo...@ewerk.com > www.ewerk.com > > Geschäftsführer: > Dr. Erik Wende, Hendrik Schubert, Frank Richter > Registergericht: Leipzig HRB 9065 > > Zertifiziert nach: > ISO/IEC 27001:2013 > DIN EN ISO 9001:2015 > DIN ISO/IEC 2-1:2011 > > EWERK-Blog | LinkedIn | Xing | Twitter | Facebook > > Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. > > Disclaimer Privacy: > Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) > ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht > der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, > Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte > informieren Sie in diesem Fall unverzüglich den Absender und löschen > Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. > Vielen Dank. > > The contents of this e-mail (including any attachments) are > confidential and may be legally privileged. If you are not the > intended recipient of this e-mail, any disclosure, copying, > distribution or use of its contents is strictly prohibited, and you > should please notify the sender immediately and then delete it (including any > attachments) from your system. Thank you. > > Am 27.03.2020 um 17:07 schrieb Daan Hoogland : > > > > I'd love it to have a nightly @Gabriel Beims Bräscher < > gabrasc...@gmail.com> > > and in general i like the idea. Maybe (running in front of myself > > here) > it > > can have a build from custom commitish? > > anyway :+1: > > > >> On Fri, Mar 27, 2020 at 12:46 PM Gabriel Beims Bräscher < > >> gabrasc...@gmail.com> wrote: > >> > >> Hello @dev, > >> > >> Since release 4.12.0.0 I have been helping with the process of > >> making packages available at https://download.cloudstack.org. Such > >> a process takes time and demands someone to build the packages > >> "manually". > >> > >> The idea is to enhance it to a point that the RM in a future > >> release can press a button and the packages will be "automagically" > >> generated and > made > >> available at the mirrors. > >> > >> With that in mind, I would like to propose the addition of a > >> Jenkins > server > >> to help with the packaging process. PCextreme would be happy to > >> donate > and > >> configure a Jenkins master and a few slaves for doing that. Anyone > >> interested in donating Jenkins slaves would be welcome as well. > >> > >> The plan is to let Jenkins (e.g. https://jenkins.cloudstack.org ?) > >> open for any committer/PMC primarily as a tool for building > >> packages during the release process. Such Jenkins could serve for > >> multiple automation > purposes > >> but at first, the goal is to have a "release-packages" job for > generating > >> "VOTE" and release packages. Additionally, a set of people (e.g. > >> active PMCs and release managers) would have root access to the VM > >> to manage inside scripts, install dependency packages, and run > >> updates when necessary. > >> > >> Please let me know if that proposal suits the project needs. > >> In case we have no objections I will start working on it. > >> > >> Best Regards, > >> Gabriel. > >> > > > > > > -- > > Daan >
Re: Automate CloudStack release packaging with Jenkins
Hello all, Considering that there are no objections, I will spin a Jenkins node this week :) Cheers, Gabriel. Em sáb., 4 de abr. de 2020 às 18:21, Sven Vogel escreveu: > I am aboard and can help. first with configuring. +1 from me. We use > Jenkins too and read from Pierre he has maybe an old config. since corona I > don’t got our test environment running in data Center :( .. If this will > better I can share Jenkins slaves. > > Cheers > > > __ > > Sven Vogel > Lead Cloud Solution Architect > > EWERK DIGITAL GmbH > Brühl 24, D-04109 Leipzig > P +49 341 42649 - 99 > F +49 341 42649 - 98 > s.vo...@ewerk.com > www.ewerk.com > > Geschäftsführer: > Dr. Erik Wende, Hendrik Schubert, Frank Richter > Registergericht: Leipzig HRB 9065 > > Zertifiziert nach: > ISO/IEC 27001:2013 > DIN EN ISO 9001:2015 > DIN ISO/IEC 2-1:2011 > > EWERK-Blog | LinkedIn | Xing | Twitter | Facebook > > Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. > > Disclaimer Privacy: > Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist > vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der > bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, > Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte > informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie > die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. > Vielen Dank. > > The contents of this e-mail (including any attachments) are confidential > and may be legally privileged. If you are not the intended recipient of > this e-mail, any disclosure, copying, distribution or use of its contents > is strictly prohibited, and you should please notify the sender immediately > and then delete it (including any attachments) from your system. Thank you. > > Am 27.03.2020 um 17:07 schrieb Daan Hoogland : > > > > I'd love it to have a nightly @Gabriel Beims Bräscher < > gabrasc...@gmail.com> > > and in general i like the idea. Maybe (running in front of myself here) > it > > can have a build from custom commitish? > > anyway :+1: > > > >> On Fri, Mar 27, 2020 at 12:46 PM Gabriel Beims Bräscher < > >> gabrasc...@gmail.com> wrote: > >> > >> Hello @dev, > >> > >> Since release 4.12.0.0 I have been helping with the process of making > >> packages available at https://download.cloudstack.org. Such a process > >> takes > >> time and demands someone to build the packages "manually". > >> > >> The idea is to enhance it to a point that the RM in a future release can > >> press a button and the packages will be "automagically" generated and > made > >> available at the mirrors. > >> > >> With that in mind, I would like to propose the addition of a Jenkins > server > >> to help with the packaging process. PCextreme would be happy to donate > and > >> configure a Jenkins master and a few slaves for doing that. Anyone > >> interested in donating Jenkins slaves would be welcome as well. > >> > >> The plan is to let Jenkins (e.g. https://jenkins.cloudstack.org ?) open > >> for > >> any committer/PMC primarily as a tool for building packages during the > >> release process. Such Jenkins could serve for multiple automation > purposes > >> but at first, the goal is to have a "release-packages" job for > generating > >> "VOTE" and release packages. Additionally, a set of people (e.g. active > >> PMCs and release managers) would have root access to the VM to manage > >> inside scripts, install dependency packages, and run updates when > >> necessary. > >> > >> Please let me know if that proposal suits the project needs. > >> In case we have no objections I will start working on it. > >> > >> Best Regards, > >> Gabriel. > >> > > > > > > -- > > Daan >
Re: Automate CloudStack release packaging with Jenkins
I am aboard and can help. first with configuring. +1 from me. We use Jenkins too and read from Pierre he has maybe an old config. since corona I don’t got our test environment running in data Center :( .. If this will better I can share Jenkins slaves. Cheers __ Sven Vogel Lead Cloud Solution Architect EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik Schubert, Frank Richter Registergericht: Leipzig HRB 9065 Zertifiziert nach: ISO/IEC 27001:2013 DIN EN ISO 9001:2015 DIN ISO/IEC 2-1:2011 EWERK-Blog | LinkedIn | Xing | Twitter | Facebook Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. Disclaimer Privacy: Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank. The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you. > Am 27.03.2020 um 17:07 schrieb Daan Hoogland : > > I'd love it to have a nightly @Gabriel Beims Bräscher > and in general i like the idea. Maybe (running in front of myself here) it > can have a build from custom commitish? > anyway :+1: > >> On Fri, Mar 27, 2020 at 12:46 PM Gabriel Beims Bräscher < >> gabrasc...@gmail.com> wrote: >> >> Hello @dev, >> >> Since release 4.12.0.0 I have been helping with the process of making >> packages available at https://download.cloudstack.org. Such a process >> takes >> time and demands someone to build the packages "manually". >> >> The idea is to enhance it to a point that the RM in a future release can >> press a button and the packages will be "automagically" generated and made >> available at the mirrors. >> >> With that in mind, I would like to propose the addition of a Jenkins server >> to help with the packaging process. PCextreme would be happy to donate and >> configure a Jenkins master and a few slaves for doing that. Anyone >> interested in donating Jenkins slaves would be welcome as well. >> >> The plan is to let Jenkins (e.g. https://jenkins.cloudstack.org ?) open >> for >> any committer/PMC primarily as a tool for building packages during the >> release process. Such Jenkins could serve for multiple automation purposes >> but at first, the goal is to have a "release-packages" job for generating >> "VOTE" and release packages. Additionally, a set of people (e.g. active >> PMCs and release managers) would have root access to the VM to manage >> inside scripts, install dependency packages, and run updates when >> necessary. >> >> Please let me know if that proposal suits the project needs. >> In case we have no objections I will start working on it. >> >> Best Regards, >> Gabriel. >> > > > -- > Daan
Re: Automate CloudStack release packaging with Jenkins
I'd love it to have a nightly @Gabriel Beims Bräscher and in general i like the idea. Maybe (running in front of myself here) it can have a build from custom commitish? anyway :+1: On Fri, Mar 27, 2020 at 12:46 PM Gabriel Beims Bräscher < gabrasc...@gmail.com> wrote: > Hello @dev, > > Since release 4.12.0.0 I have been helping with the process of making > packages available at https://download.cloudstack.org. Such a process > takes > time and demands someone to build the packages "manually". > > The idea is to enhance it to a point that the RM in a future release can > press a button and the packages will be "automagically" generated and made > available at the mirrors. > > With that in mind, I would like to propose the addition of a Jenkins server > to help with the packaging process. PCextreme would be happy to donate and > configure a Jenkins master and a few slaves for doing that. Anyone > interested in donating Jenkins slaves would be welcome as well. > > The plan is to let Jenkins (e.g. https://jenkins.cloudstack.org ?) open > for > any committer/PMC primarily as a tool for building packages during the > release process. Such Jenkins could serve for multiple automation purposes > but at first, the goal is to have a "release-packages" job for generating > "VOTE" and release packages. Additionally, a set of people (e.g. active > PMCs and release managers) would have root access to the VM to manage > inside scripts, install dependency packages, and run updates when > necessary. > > Please let me know if that proposal suits the project needs. > In case we have no objections I will start working on it. > > Best Regards, > Gabriel. > -- Daan
Automate CloudStack release packaging with Jenkins
Hello @dev, Since release 4.12.0.0 I have been helping with the process of making packages available at https://download.cloudstack.org. Such a process takes time and demands someone to build the packages "manually". The idea is to enhance it to a point that the RM in a future release can press a button and the packages will be "automagically" generated and made available at the mirrors. With that in mind, I would like to propose the addition of a Jenkins server to help with the packaging process. PCextreme would be happy to donate and configure a Jenkins master and a few slaves for doing that. Anyone interested in donating Jenkins slaves would be welcome as well. The plan is to let Jenkins (e.g. https://jenkins.cloudstack.org ?) open for any committer/PMC primarily as a tool for building packages during the release process. Such Jenkins could serve for multiple automation purposes but at first, the goal is to have a "release-packages" job for generating "VOTE" and release packages. Additionally, a set of people (e.g. active PMCs and release managers) would have root access to the VM to manage inside scripts, install dependency packages, and run updates when necessary. Please let me know if that proposal suits the project needs. In case we have no objections I will start working on it. Best Regards, Gabriel.
