zikula / coremanagermodule Goto Github PK

Possible automation:

Further ideas:

• ...

Only the "MainInstance" of the module will copy release assets from Jenkins to GitHub.

https://status.github.com/api

Even if the commit is the same, the latest build might have been triggered manually to update vendors.

[2017-07-20 17:56:49] request.CRITICAL: Uncaught PHP Exception Twig_Error_Runtime: "An exception has been thrown during the rendering of a template ("Warning: include(/home/www/core/src/modules/CoreManagerModule): failed to open stream: No such device")." at /home/www/core/src/themes/BootstrapTheme/Resources/views/Body/2col.html.twig line 4 {"exception":"[object] (Twig_Error_Runtime(code: 0): An exception has been thrown during the rendering of a template ("Warning: include(/home/www/core/src/modules/CoreManagerModule): failed to open stream: No such device"). at /home/www/core/src/themes/BootstrapTheme/Resources/views/Body/2col.html.twig:4, Symfony\Component\Debug\Exception\ContextErrorException(code: 0): Warning: include(/home/www/core/src/modules/CoreManagerModule): failed to open stream: No such device at /home/www/core/src/vendor/composer/ClassLoader.php:440)"} []

update to work with new Jenkins pipelines

Also, the Release is not updated with the copied Jenkins assets.

when closing a milestone on Core release, the CMM should migrate all open issues from the current milestone to the next "point" release (e.g. 1.4.1 -> 1.4.2)

Use coremanager module as an endpoint for zikula installations to check for notifications of core updates

refs zikula/ExtensionLibrary#81

And opening new job after specified commit

• https://getcomposer.org/doc/04-schema.md#files
• https://github.com/zikula/core/blob/1.4/src/lib/Zikula/Bundle/CoreBundle/Bundle/Bootstrap.php#L170

On the release of Core-1.4.2 I was not able to get the buttons and news articles to work until "reloading core releases" via CMM. I guess this needs to be accomplished in the Release Wizard somewhere so that other steps can complete properly.

When creating a new release, updating the Zikula_Core::VERSION_NUM did not work:

        <h1>Oops! An Error Occurred</h1>
        <h2>The server returned a "500 Internal Server Error".</h2>

        <div>
            Something is broken. Please let us know what you were doing when this error occurred.
            We will fix it as soon as possible. Sorry for any inconvenience caused.
        </div><br />
        <div class="alert alert-warning">Path &quot;src/lib/legacy/Zikula/Core.php&quot; is not a file.</div>

the template currently says

If the negative threshold is not reached before the posted deadline, then the build passes automatically.

We should add a deadline to the text. it could be an automatic interval (like 5 days or something) or it could be manually set - this would be more work of course.

The help texts defined here aren't displayed any longer.

add a checkbox to the workflow that identifies the release as a security release. This can add specific text to the announcement and maybe the title or something.

It would be cool if the news post could also post to Facebook, twitter, etc.

zikula/core@ec115aa

this should probably be done in two steps

1. change the date of the new release - do this before the release
2. add the template for the new version - do this after release.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Detected empty commit - aborting git push

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• fix(deps): update dependency cache/filesystem-adapter to v1.2.0
• fix(deps): update dependency http-interop/http-factory-guzzle to v1.2.0

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

received OutOfMemoryException when attempting Core-2.0-RC1

@cmfcmf ideas?