Skip to content

Conversation

@sbesson
Copy link
Member

@sbesson sbesson commented Nov 27, 2012

Fix issue reported in #13 as well as other bugs

  • fix bug when recording conflicting PRs list
  • Use `reset --hardrather thanmerge --ff-only``because the latter command seemed to hang on a couple of times when calling``p.wait`` in the call command

This script has been successfully tested with the builds 70 and 71 of the OMERO-merge-4.4 job.

joshmoore and others added 5 commits November 26, 2012 20:47
The issue we saw with ome/omero-scripts#12 was:

 * PR 12 opened and was merged properly.
 * PR 12 was merged.
 * No other PRs were open.
 * Therefore, the sha1 of the module wasn't changed.

In other words, the modification tracking that was
in place looked solely for PR merges but didn't
take into account whether or not the submodule
pointer needed to be bumped. Rather than worry about
trying to properly track that, this commit removes
the modification check. The next step is to
guarantee that the submodule will be updated
to the appropriate base.
Pass the base to all submodules in order
to fast-forward the pointer. If a ff is
not possible, the build will fail. Also,
if the submodule branch names do not
match that of the main repo, the build
will fail.
@sbesson sbesson mentioned this pull request Nov 27, 2012
@joshmoore
Copy link
Member

Comments (per IM): Don't like having git reset --hard on by default. Either a cmd-line flag or we warn about dirty repos.

Would also be good to know why it's hanging.

@joshmoore
Copy link
Member

Sebastien likes what I did (and it now actually works!) so merging.

joshmoore added a commit that referenced this pull request Nov 27, 2012
@joshmoore joshmoore merged commit 4aa9de2 into ome:master Nov 27, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants