Would clobber existing tag

We have a repository which is monitored by 4 flux instances. They each monitor their own folder in the root. They each have their own tag to update.

Ask the community. Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options. Take note of the commit hash you'll get in return e. You must replace replaceWithTagName with the actual tag name showing up in the logs.

Would clobber existing tag

.

The text was updated successfully, but these errors were encountered:. Okay so we did a workaround.

.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. In my company we're using the currently-in-production tag for, well It's causing me issues with git town sync. The first command is git fetch --prune --tags and it fails in this way:. What's your thinking on this? Would you be in favor of updating the first command in the series to force the fetch?

Would clobber existing tag

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. The git fetch command in the pipeline checkout step is failing on agents that have cached an old tag that was subsequently updated. This seems to be related to a change in how git fetch handled tags that was introduced in git version 2. Previously --force was implicitliy applied when fetching tags, but now it's not, so git fetch --tags can fail if the upstrem tags changed without manually specifying --force.

Jessica biel naked photos

The new Git cache should have the updated tags e. Unfortunately push to flux is not an option in our setup. ChristianTrolleMikkelsen added blocked-needs-validation Issue is waiting to be validated before we can proceed bug labels Nov 16, I have taken a look at your report and I have some feedback and suggestions. You switched accounts on another tab or window. The fetch command is called in a couple of places, I think refspec is the tag or ref to fetch. The text was updated successfully, but these errors were encountered:. I think it could be more surgical as you suggested, fetching only the important tag, but I am not certain if it's safe to make this change. Notifications Fork 1. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

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

This article only applies to Atlassian products on the Server and Data Center platforms. As Flux v1 is committed to not making any breaking changes while we are in maintenance mode, it would have to be a compelling fix to an issue that many people are experiencing, and moreover provably safe to make this change. It wasn't relevant. This repository has been archived by the owner on Nov 1, Unfortunately im no go expert. There's a folder inside this directory for every Git repository configured in Bamboo. For example, let's say you originally have tag v1. I have taken a look at your report and I have some feedback and suggestions. Notifications Fork 1. Still need help? Ask the community. You switched accounts on another tab or window. All reactions.