Ticket #1076 (closed bug: done)

Opened 5 years ago

Last modified 4 years ago

Smoking Git Branches

Reported by: dukeleto Owned by:
Priority: minor Milestone:
Component: testing Version: 1.6.0
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

It was discussed on #parrotsketch that it would be nice if we had a way to smoke git branches. This would allow individual developers to choose to work in a git branch and still get useful test run info.

Change History

follow-up: ↓ 2   Changed 5 years ago by coke

Since there is no git but git-svn, isn't this just a matter of developers running 'make smolder' in their current checkout with a local branch?

in reply to: ↑ 1   Changed 5 years ago by bacek

Replying to coke:

Since there is no git but git-svn, isn't this just a matter of developers running 'make smolder' in their current checkout with a local branch?

Actually no. Main idea is postpone interaction with svn as late as possible. Because working with branches in svn (even with git-svn) is pain in the arse.

-- Bacek

follow-up: ↓ 4   Changed 5 years ago by coke

But you don't run 'make smolder' against svn; you run it against the files you have in your working directory. Whether those match exactly what's in svn, or match whatever your git branch is, what's the difference?

Or, what do you think needs to change for this to work?

Or, can we have some specific tasks/bugs to make this ticket closable?

in reply to: ↑ 3   Changed 5 years ago by bacek

Replying to coke:

Or, what do you think needs to change for this to work? Or, can we have some specific tasks/bugs to make this ticket closable?

I can think only one particular task - ensure that smolder report include proper information about git branch and revision.

-- Bacek

  Changed 5 years ago by coke

I don't think this is useful. The changes in this local checkout aren't necessarily shared or easily accessible to other developers, since we're not using git as the base VCS.

So, if there are failures, these failures would just add smoke where there isn't really any; If they pass, it doesn't matter because no one else can (easily) run this code.

Doing this for easily shared branches (svn now, or git if we do eventually switch) is good, but with the existing setup, this isn't helpful to me. How would this help you?

  Changed 5 years ago by dukeleto

I am talking about being able to run "make smolder" in a git branch of the parrot git repo (like the one on github, which anybody can fork and work on) and have smolder get the relevant info, like the sha1 of the commit/etc. I have done this already for other projects using Smolder. It is not hard.

  Changed 4 years ago by bacek

  • status changed from new to closed
  • resolution set to done

Hello.

We have successfully migrated to git. Closing ticket.

-- Bacek

Note: See TracTickets for help on using tickets.