Nort TODO: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 11: Line 11:
=TODO=
=TODO=


* '''Manual''' - clean up and coalesce [[Nort_User_Manual]]
* '''Installation Sequence'''
* '''Installation Sequence'''
** Implement the equivalent of install -f (I can avoid it if I simply create a new snapshot), it should be easy now
** Implement the equivalent of install -f (I can avoid it if I simply create a new snapshot), it should be easy now

Revision as of 01:53, 29 November 2016

Internal

Testing

mvn -Dmaven.surefire.debug="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005" -Dtest=ReleaseCommandTest clean test

TODO

  • Manual - clean up and coalesce Nort_User_Manual
  • Installation Sequence
    • Implement the equivalent of install -f (I can avoid it if I simply create a new snapshot), it should be easy now
    • If the installation directory exists, unzip will ask for options, and I can’t see that so it will look like the program blocked.
  • undo/rollback functionality:
    • undo functionality in the JVM shutdown hook.
    • Sequences should have "rollback()" methods, not undo().
    • Test MavenProject.undo(), MavenModule.undo().
    • Rollback Git tagging:
4.2.2 source commit ok
fatal: tag 'release-4.2.2' already exists
WARN  SequenceController: failed to undo build sequence: undo() NOT YET IMPLEMENTED
[error]: failed to tag the local source repository

The undo solution for git tagging is:

git tag -d release-4.2.2
git push origin :refs/tags/release-4.2.2
  • model
    • A BINARY_DISTRIBUTION can have multiple extensions, not just one (“zip”) – refactor ArtifactType, see where we’re using extension and see what we can replace with.
  • 11/26/16 prevent the embedded installation script .install to accidentally overwrite the installation it is part of. Probably the best protection is to delete it.
  • GitHub Release
    • For non-snapshot releases, collect release-notes.md, query if they’re fine and make a GitHub release via API. It should be part of the publish sequence. Then clean release-notes.md.