Skip to content

Convert to manually-triggered release process #1531

Description

@garrettjonesgoogle

For the last several releases, the release process hasn't run properly in Travis, and I have had to run various components manually. It's really hard to figure out what happened and didn't happen during the release process because there is no messaging. So, I would like to change the release scripts (specifically https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/utilities/after_success.sh ) so that they are designed to be run from the command line by a team member instead of by Travis. I intend to make the process a one-shot command so that only two steps are required in the happy case: 1. start the script, 2. verify it succeeded.

I am filing this as an issue to get any comments anyone has about this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

type: processA process-related concern. May include testing, release, or the like.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions