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.

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

Tag before pulling and rebasing #1

Open
andreasf opened this issue Mar 18, 2016 · 1 comment
Open

Tag before pulling and rebasing #1

andreasf opened this issue Mar 18, 2016 · 1 comment
Labels

Comments

@andreasf
Copy link
Contributor

Tag should tag the current commit id of the working directory before pulling and rebasing. otherwise, manually triggering a job can lead to tagging the wrong commit.

Steps to reproduce:

  1. Create a pipeline that gets, tags and pushes
  2. Add a commit in the source repo and trigger the pipeline
  3. Increment the version resource so that another commit can be tagged
  4. Manually trigger the pipeline again.

Expected behavior:

The tip commit of the source repo should get tagged again.

Actual behavior:

Out pulls the tag commit from the destination repo. Since there is no new commit in the source repo, the old tag commit ("Added tag ... for changeset ...") is now at tip, and out tags it with the new version number.

@andreasf andreasf added the bug label Mar 18, 2016
@concourse-bot
Copy link
Collaborator

concourse-bot commented Jun 18, 2016

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

@vito vito added the bug label Oct 6, 2016
@vito vito removed the unscheduled label May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants