Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When deploying, I'm always prompted to enter a tag name even if I chose not to create one #940

Closed
bkosborne opened this issue Jan 8, 2017 · 2 comments
Closed

When deploying, I'm always prompted to enter a tag name even if I chose not to create one #940

bkosborne opened this issue Jan 8, 2017 · 2 comments
Assignees
@grasmash

Comments

@bkosborne
Copy link
Contributor

Example:

Would you like to create a tag? Typically, this is only done if you have currently have a tag checked out on your source repository. [y/n] [n] ?  n

Enter the name of the tag to create. This will be automatically appended with '-build' [] :

I also get an error "uknown switch -b" during the deploy:push-remote step, when BLT attempts to push the code to my build repo.

Downgrading to 8.6.8 resolves this.
@grasmash
Copy link
Contributor

grasmash commented Jan 8, 2017

Does the build artifact get pushed?

grasmash added a commit to grasmash/bolt that referenced this issue Jan 8, 2017
@grasmash
Fixes acquia#940: Prevent tag prompt.
dce9136
@grasmash grasmash self-assigned this Jan 8, 2017
@bkosborne
Copy link
Contributor Author

No it does not. Here's a snippet from the end of the build:

blt > deploy:tag:
error: unknown switch `b'
usage: git tag [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>] <tagname> [<head>]
   or: git tag -d <tagname>...
   or: git tag -l [-n[<num>]] [--contains <commit>] [--points-at <object>]
		[--format=<format>] [--[no-]merged [<commit>]] [<pattern>...]
   or: git tag -v <tagname>...

    -l, --list            list tag names
    -n[<n>]               print <n> lines of each tag message
    -d, --delete          delete tags
    -v, --verify          verify tags

Tag creation options
    -a, --annotate        annotated tag, needs a message
    -m, --message <message>
                          tag message
    -F, --file <file>     read message from file
    -s, --sign            annotated and GPG-signed tag
    --cleanup <mode>      how to strip spaces and #comments from message
    -u, --local-user <key-id>
                          use another key to sign the tag
    -f, --force           replace the tag if exists
    --create-reflog       create a reflog

Tag listing options
    --column[=<style>]    show tag list in columns
    --contains <commit>   print only tags that contain the commit
    --merged <commit>     print only tags that are merged
    --no-merged <commit>  print only tags that are not merged
    --sort <key>          field name to sort on
    --points-at <object>  print only tags of the object
    --format <format>     format to use for the output

blt > deploy:push-all:
blt > deploy:push-remote:
     [exec] To [obfuscated]
     [exec]    ba05ef4..435548c  master -> master
     [exec] error: unknown switch `b'
     [exec] usage: git push [<options>] [<repository> [<refspec>...]]
     [exec]
     [exec]     -v, --verbose         be more verbose
     [exec]     -q, --quiet           be more quiet
     [exec]     --repo <repository>   repository
     [exec]     --all                 push all refs
     [exec]     --mirror              mirror all refs
     [exec]     -d, --delete          delete refs
     [exec]     --tags                push tags (can't be used with --all or --mirror)
     [exec]     -n, --dry-run         dry run
     [exec]     --porcelain           machine-readable output
     [exec]     -f, --force           force updates
     [exec]     --force-with-lease[=<refname>:<expect>]
     [exec]                           require old value of ref to be at this value
     [exec]     --recurse-submodules[=<check|on-demand|no>]
     [exec]                           control recursive pushing of submodules
     [exec]     --thin                use thin pack
     [exec]     --receive-pack <receive-pack>
     [exec]                           receive pack program
     [exec]     --exec <receive-pack>
     [exec]                           receive pack program
     [exec]     -u, --set-upstream    set upstream for git pull/status
     [exec]     --progress            force progress reporting
     [exec]     --prune               prune locally removed refs
     [exec]     --no-verify           bypass pre-push hook
     [exec]     --follow-tags         push missing but relevant tags
     [exec]     --signed[=<yes|no|if-asked>]
     [exec]                           GPG sign the push
     [exec]     --atomic              request atomic transaction on remote side
     [exec]     -o, --push-option <server-specific>
     [exec]                           option to transmit
     [exec]     -4, --ipv4            use IPv4 addresses only
     [exec]     -6, --ipv6            use IPv6 addresses only
     [exec]
  [foreach] /Users/bosborne/Projects/site/vendor/acquia/blt/phing/tasks/deploy.xml:193:8: /Users/bosborne/Projects/site/vendor/acquia/blt/phing/tasks/deploy.xml:196:69: Task exited with code 129
[phingcall] /Users/bosborne/Projects/site/vendor/acquia/blt/phing/tasks/deploy.xml:184:31: Execution of the target buildfile failed. Aborting.

BUILD FAILED/Users/bosborne/Projects/site/vendor/acquia/blt/phing/tasks/deploy.xml:81:8: /Users/bosborne/Projects/site/vendor/acquia/blt/phing/tasks/deploy.xml:84:26: Execution of the target buildfile failed. Aborting.
; 7 minutes  6.35 seconds

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

@grasmash grasmash

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grasmash @bkosborne