Release script failed for 0.20.0 release #1211

Closed
heuermh opened this Issue Oct 14, 2016 · 5 comments

Comments

Projects
2 participants
@heuermh
Member

heuermh commented Oct 14, 2016

@jpdna @fnothaft

$ ./scripts/release/release.sh 0.20.0 0.20.1-SNAPSHOT
...
Switched to a new branch 'maint_spark2_2.11-0.20.0'
./scripts/release/release.sh: line 72: ./scripts/move_to_spark2.sh: No such file or directory

It looks like the Spark 1.x Scala 2.10 and 2.11 releases were tagged and deployed to the Sonatype staging directory ok.

The maven release plugin doesn't let you cut a release with uncommitted changes, so I'll have to copy release.sh over to a new script to make changes there.

I'm currently on the maint_spark2_2.11-0.20.0 branch but with Spark 1.x dependencies, as the move_to_spark_2.sh script did not run. I'm not sure yet what I'll need to do to fix this up and continue the release . . .

adam-upstream maint_spark2_2.11-0.20.0!
$ git status
On branch maint_spark2_2.11-0.20.0
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   adam-apis/pom.xml
    modified:   adam-assembly/pom.xml
    modified:   adam-cli/pom.xml
    modified:   adam-core/pom.xml
    modified:   distribution/pom.xml
    modified:   pom.xml

Untracked files:
  (use "git add <file>..." to include in what will be committed)

    adam-0.20.0.pom
    adam-0.20.0.zip
    adam-apis/pom.xml.releaseBackup
    adam-assembly/pom.xml.releaseBackup
    adam-cli/pom.xml.releaseBackup
    adam-core/pom.xml.releaseBackup
    distribution/pom.xml.releaseBackup
    pom.xml.releaseBackup
    release.properties
@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Oct 14, 2016

Member

Ah drat! The Spark 2 code is new to this release. My apologies for flubbing it; I'll PR a fix.

You could roll back the release, or just run it manually from here. Let me know if you'd like me to manually release the Spark 2 artifacts...

Member

fnothaft commented Oct 14, 2016

Ah drat! The Spark 2 code is new to this release. My apologies for flubbing it; I'll PR a fix.

You could roll back the release, or just run it manually from here. Let me know if you'd like me to manually release the Spark 2 artifacts...

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 14, 2016

Member

I would like to continue manually, I just need to get the working directory in the right state first.

Member

heuermh commented Oct 14, 2016

I would like to continue manually, I just need to get the working directory in the right state first.

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 14, 2016

Member

... think I got it, release:prepare went ok, running release:perform meow . . .

Member

heuermh commented Oct 14, 2016

... think I got it, release:prepare went ok, running release:perform meow . . .

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 14, 2016

Member

Artifacts are staged to orgbdgenomics-1048, log into https://oss.sonatype.org to verify.

Member

heuermh commented Oct 14, 2016

Artifacts are staged to orgbdgenomics-1048, log into https://oss.sonatype.org to verify.

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 14, 2016

Member

Signatures and distribution tarballs look ok to me.
I'll close the staging repository and enable sync to Maven Central at 6:00 pm CST unless I hear otherwise.

Member

heuermh commented Oct 14, 2016

Signatures and distribution tarballs look ok to me.
I'll close the staging repository and enable sync to Maven Central at 6:00 pm CST unless I hear otherwise.

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