You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I customize in jx3 mi next version with this code because I don't want the "v" in the name of tag:
- image: ghcr.io/jenkins-x/jx-release-version:2.6.6
name: my-nextversion-master-minor
resources: {}
script: |
#!/usr/bin/env sh
set -x
if [ "$PULL_BASE_REF" == "master" ] || [ "$PULL_BASE_REF" == "main" ]; then
jx-release-version -next-version=increment:minor --debug --tag --tag-prefix="" > VERSION
else
jx-release-version -next-version=increment:patch --debug --tag --tag-prefix="" > VERSION
fi
cat VERSION
But I received a "false" error in the push process:
jx-release-version '-next-version=increment:patch' --debug --tag '--tag-prefix='
DEBUG: jx-release-version 2.6.6-dev+4b57fec running in debug mode in /workspace/source
DEBUG: Using "auto" version reader (with "")
DEBUG: Trying to read the previous version from the git tags first...
DEBUG: Found 55 semver tags with pattern ""
DEBUG: Previous version: 1.7.3
DEBUG: Using "increment" version bumper (with "patch")
DEBUG: Incrementing patch component
DEBUG: Next version: 1.7.4
DEBUG: git tag -a 1.7.4 -m "Release version 1.7.4"
DEBUG: git push --tags
FATAL: Failed to tag using version 1.7.4: failed to push tags to origin: authentication required
cat VERSION
1.7.4
But in my github repo the tag is correctly uploaded:
Why the FATAL error?
The text was updated successfully, but these errors were encountered:
If I don't use --tag-prefix="" (use the normal tag with prefix "v" -> jx-release-version -next-version=increment:minor --tag > VERSION) the problem doesn't appear :S
I test the plugin from [2.6.3] until [2.6.6]
I customize in jx3 mi next version with this code because I don't want the "v" in the name of tag:
But I received a "false" error in the push process:
But in my github repo the tag is correctly uploaded:
Why the FATAL error?
The text was updated successfully, but these errors were encountered: