[Framework-Team] RFC: buildout.coredev all commits branch

[Timo Stollenwerk]

Hi,

two months ago the FWT discussed creating a buildout.coredev branch that
contains all commits to all packages in the Plone repo:

https://docs.google.com/document/d/1UVNLqQFrq8AJkmNxEO9J4flIqGTf_TbAqR3TWwFguRY/edit

We need this in order to be able to trigger the buildout.coredev Jenkins
jobs and properly passing the changelog to it.

As discussed back then Ramon implemented the functionality:

https://github.com/plone/buildout.coredev/commits/5.0-all-commits

As far as we can tell it works fine. Though, the only way to really test
it is to put it in production (we can not do fully automated rebases on
the all-commits branch therefore the branch diverged from the 5.0
branch, this problem will be gone if we switch to using the 5.0 branch).

We were working hard (especially Gil!) in the last month to get the new
Jenkins server ready for production:

http://78.47.49.108/

I think we could be ready within the next weeks. That would be a good
opportunity to switch the 5.0 branch to the all-commits functionality.

Any objections?

Cheers,
Timo

[Johannes Raggam]

no objections - i'm waiting for it.
i occasionally use http://jenkins.plone.org/roboto/ (which is a
interface to the "all commits" branch, no?) to see what exactly broke
something, and it seems to work fine.

thanks for pushing this forward!

Post by Timo Stollenwerk
Hi,
two months ago the FWT discussed creating a buildout.coredev branch that
https://docs.google.com/document/d/1UVNLqQFrq8AJkmNxEO9J4flIqGTf_TbAqR3TWwFguRY/edit
We need this in order to be able to trigger the buildout.coredev Jenkins
jobs and properly passing the changelog to it.
https://github.com/plone/buildout.coredev/commits/5.0-all-commits
As far as we can tell it works fine. Though, the only way to really test
it is to put it in production (we can not do fully automated rebases on
the all-commits branch therefore the branch diverged from the 5.0
branch, this problem will be gone if we switch to using the 5.0 branch).
We were working hard (especially Gil!) in the last month to get the new
http://78.47.49.108/
I think we could be ready within the next weeks. That would be a good
opportunity to switch the 5.0 branch to the all-commits functionality.
Any objections?
Cheers,
Timo
_______________________________________________
Framework-Team mailing list
https://lists.plone.org/mailman/listinfo/plone-framework-team

[David Glick (Plone)]

Post by Timo Stollenwerk
Hi,
two months ago the FWT discussed creating a buildout.coredev branch
https://docs.google.com/document/d/1UVNLqQFrq8AJkmNxEO9J4flIqGTf_TbAqR3TWwFguRY/edit
We need this in order to be able to trigger the buildout.coredev
Jenkins jobs and properly passing the changelog to it.
https://github.com/plone/buildout.coredev/commits/5.0-all-commits
As far as we can tell it works fine. Though, the only way to really
test it is to put it in production (we can not do fully automated
rebases on the all-commits branch therefore the branch diverged from
the 5.0 branch, this problem will be gone if we switch to using the
5.0 branch).
We were working hard (especially Gil!) in the last month to get the
http://78.47.49.108/
I think we could be ready within the next weeks. That would be a good
opportunity to switch the 5.0 branch to the all-commits functionality.
Any objections?

+1 from me. I'm looking forward to the new Jenkins server.

[Jens W. Klein]

On 2015-02-16 19:02, Timo Stollenwerk wrote:
[...]

Post by Timo Stollenwerk
We were working hard (especially Gil!) in the last month to get the new
http://78.47.49.108/
I think we could be ready within the next weeks. That would be a good
opportunity to switch the 5.0 branch to the all-commits functionality.
Any objections?

No! Go Go go! Good work! Thanks to you, Gil and Ramon!

Jens