Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Migrating openshiftio-cico-jobs to app-interface

> The jobs themselves will of course still be available in ci.centos.org, no change there.

That sounds good to me - I appreciate the desire and best effort to keep everything as open as possible. Being able to see what actually runs in the builds is often useful, so the buildlogs on ci.centos.org are good.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Thu, 12 Dec 2019 at 07:32, Maor Friedman <mafriedm@xxxxxxxxxx> wrote:
Thanks for your comments!

We completely understand the desire to stay as open source as possible.
With that said, I don't think that it is feasible for anyone outside of Red Hat to make changes to the job definitions.
One example of why would be - we are using an App SRE Vault instance, which is completely internal.

The jobs themselves will of course still be available in ci.centos.org, no change there.

After moving the definitions into app-interface, we would be able to make improvements and allow for more complex use cases, rather then just barely understanding what's going on.

Is this a price we are willing to pay?



On Wed, Dec 11, 2019 at 9:47 PM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Hello Radim, che-devers,

It would be great if che stayed as open as possible and that would include as much of the build infra as possible. That said, I cannot find links from any of the project metadata now to the current CI settings or infra. 

I hope having some feedback from the wider community helps. I am not currently active in Che, but in the past being able to see things such as build logs on CI instances is very helpful.
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 11 Dec 2019 at 10:50, Radim Hopp <rhopp@xxxxxxxxxx> wrote:
Once concern came to me right now - As Eclipse Che is community (public) project, moving the job definitions into private RedHat repository lowers visibility, which in general is not good for community/upstream projects.
Once(if) the job configuration will be moved, there is no way (AFAIK), how anybody from outside of Red Hat would be able to take a look at the jenkins job configuration (not mentioning changing it...). 

On Wed, Dec 11, 2019 at 3:22 PM Radim Hopp <rhopp@xxxxxxxxxx> wrote:
Adding che-dev to cc, as building of Eclipse Che is migrating to ci.centos and this change will be relevant to this team.

From my side, this looks like a very nice improvement! Changing/managing this 5000 cico yaml file was always a nightmare!
Anything which would break this beast into smaller, more manageable and almost-per-team-owned chunks/dirs/files is a huge improvement!
I'm looking forward to this change!

On Wed, Dec 11, 2019 at 8:04 AM Maor Friedman <mafriedm@xxxxxxxxxx> wrote:
Hello,

A kind reminder to express your thoughts, as we have received no comments on this subject.
This work is planned to take place next week.

Thanks!

On Tue, Dec 3, 2019 at 1:34 PM Maor Friedman <mafriedm@xxxxxxxxxx> wrote:
Hey team,

The App SRE team is considering to migrate the existing Jenkins job definitions from openshiftio-cico-jobs[1] into app-interface[2].

We are sending this mail to start a discussion around the subject. In case we find no substantial risk or concerns, we plan to start working on this in our next sprint, starting December 16th. We've created https://jira.coreos.com/browse/APPSRE-1213 to track this effort.

Some reasons why this would be helpful:
- App SRE already manages all other job definitions in app-interface (1 less surface for us to watch)
- It will allow the reuse of existing definitions already in app-interface (reuse definitions across jenkins instances)
- It will make the definitions queryable and will allow us to add more automation around it.
- It will allow the jobs to be path agnostic, so every team can have a single (or multiple) file with their own job definitions.

This means that PRs for jobs will be submitted to app-interface (gitlab.cee) and the GitHub repository will be deprecated.

Feel free to roam around the Jenkins resources section in app-interface[3] to get a sense of what this ~5000 line file can turn into.

Following the migration, if and when one happens, we will be able to easily iterate over the definitions and improve them.

Please let us know if you have any questions or concerns!

--
Maor Friedman
Senior Software Engineer, Application SRE team, Service Delivery
Red Hat


--
Maor Friedman
Senior Software Engineer, Application SRE team, Service Delivery
Red Hat
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--
Maor Friedman
Senior Software Engineer, Application SRE team, Service Delivery
Red Hat

Back to the top