Skip to content

ACTION REQUIRED: workflow change for merging changes to nodejs/node #2598

Closed
@orangemocha

Description

Based on previous discussion, feedback, and the approval by the TSC (#2434), we are adopting a new workflow for merging pull request in nodejs/node, and making any changes to the code branches at nodejs/node in general. The new workflow needs to be adopted by all @nodejs/collaborators for all changes to be merged to nodejs/node, starting this coming Monday at 2pm UTC: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Start+merging+changes+to+nodejs%2Fnode+with+Jenkins&iso=20150831T14&p1=1440

From that time on, please refrain from pushing changes to nodejs/node manually, and instead use the workflow documented at /~https://github.com/nodejs/node/wiki/Merging-pull-requests-with-Jenkins. I also added a wiki page specifically on how to deal with flaky tests.

The workflow for testing (but not landing) pull requests with Jenkins is unchanged, and now documented here: /~https://github.com/nodejs/node/wiki/Testing-pull-requests-with-Jenkins

I'll be monitoring Jenkins to make sure things keep working smoothly. Let me and @nodejs/jenkins-admins know if you encounter any issues with the CI infrastructure or to share your feedback. Thank you!

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to build files or the CI.metaIssues and PRs related to the general management of the project.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions